MENU

Do you still need an enterprise PLM?

The PLM contract is up for renewal. Three years in, the tech packs are still finished in a spreadsheet, the size charts live in someone's downloads folder, and half the product team logs in only when they have to.

In March 2025 I wrote that it wasn't Airtable versus PLM, and that most brands probably needed both. There were things a specialist tool could do that we couldn't. Twenty months is a long time in technology, and that's no longer true.

The short answer: for most growing product brands, no. You can build the PLM features you need on top of your own product data, starting with what hurts now, and add BOMs, tech packs and grading as the business grows into them.

An enterprise PLM still earns its place in a couple of situations, and I'll come to those. Here's what's changed, how I'd build it up, and what it costs next to an enterprise licence.

"A playbook is just someone else's experiences written down: their range, their team, their factories, their mistakes."

Oliver Rhodes, CEO, Nolo

Can you build a PLM to replace Centric?

Yes. We're replacing Centric PLM for the second time right now (the first was Represent, where Centric was replaced in four months).

We're rebuilding the whole feature set on a PLM data architecture we've already proven, with custom interfaces on top. What the brand gets is more connected to the rest of the business, easier for the team to pick up, and a fraction of the ongoing licence cost.

The parts that used to stop us are solved:

  • Grading and measurements
  • Tech packs, using a code-based document generator built into the system
  • Image markups

The difference is where we start. Enterprise PLMs promise customisation at the outset, then make it very hard to reach. We start with the customisation, so the system fits how the team develops product from the first day it's live.

Where should a PLM build start?

Usually with the product data itself. Once more than four or five people are touching product information, it needs one home: styles, colourways, suppliers, costs, coding and the product hierarchy, managed by the whole team in one place.

That's the foundation. From there you add PLM features as they earn their place:

  1. BOMs (bills of materials) when costing gets complicated
  2. Tech packs when you're missing deadlines producing them
  3. Fewer hands on technical documentation, once tech packs come off the system
  4. Size blocks, standard measurement charts and grading as size ranges grow or you work with more suppliers

If your product data is already in good shape and the pressure is somewhere else (costing, say, or sampling), start there instead. The order follows where the business is under strain.

Why build it up instead of rolling out the whole PLM?

Because no product team in a growing brand has time to spare. I haven't met one yet.

Anyone who's been through an enterprise PLM rollout knows how hard they are to land. They run for months, sometimes years, and the team often drifts back to spreadsheets before it's finished.

Starting small and adding features one at a time gets the parts you need live first. It's the lowest-risk way I know to do this.

Can the same product data run your ERP too?

For a lot of smaller brands, yes. Brands turning over £5m to £50m often need the product data in order before they've brought in an ERP at all.

The same system that grows into your PLM can take on purchase orders and wholesale orders, all hanging off the product data you started with. Complexity doesn't mean you have to buy an expensive enterprise tool any more.

Should you follow PLM best practice?

I'd worry less about what the acronym stands for. These software categories are breaking down, and what matters is what your business, your processes and your workflows actually need.

A playbook is someone else's experience written down: their range, their team, their factories, their mistakes. It rarely stands up next to a system built around how you work, now that building one costs a fraction of what it used to.

We often build things to get a client live that we know aren't textbook best practice. That's fine. The aim is to make improvements easy, without forcing everyone to bend their process to how some expert thinks it should run.

What does an enterprise PLM cost compared with building your own?

Enterprise PLM licences run at roughly £200 to £300 per user per month, before professional services. They promise customisation, and it's hard to get to.

Specialist PLMs cost less, but they're built around someone else's best practice.

Airtable seats cost a fraction of an enterprise licence. That means everyone who touches product data can be in the system, from design to buying to the warehouse, and you get the customisation as well.

Is PLM still the right category?

PLM was designed around a small set of specialist workflows. Brands now want workflows that run across teams, sit alongside the AI they're using (actual AI, not Adobe Illustrator) and connect to the rest of the business.

So I'd ask the question the other way round. Why would you take such a core part of your critical path and keep it in a separate, legacy application, when the whole thing could sit in one version of the truth?

When does an enterprise PLM still make sense?

There are two cases I'd still point to:

  • Your designers work in Adobe and need their files and CADs linked to the product record
  • You're a large group with a PLM already running across several brands

In the second case, you'll usually get more from connecting Airtable around the PLM than from replacing it.

If neither of those is you, and a PLM renewal or demo is coming up, talk to us before you sign. You might already have the start of your PLM.

Enterprise PLM alternatives: quick answers

Is Airtable a PLM?

Out of the box, it's a flexible database. Built on a proven PLM data architecture with custom interfaces, it does the job of one: styles, colourways, BOMs, samples, costings and tech packs, all on the same product data.

Can Airtable replace Centric PLM?

For most growing product brands, yes. We're replacing Centric for the second time, rebuilding its feature set around how the brand develops product. Larger groups with Centric already embedded across several brands tend to get more from connecting Airtable around it.

How much does an enterprise PLM cost compared with Airtable?

Enterprise PLM licences run at about £200 to £300 per user per month, before professional services. Airtable seats cost a fraction of that, so everyone who touches product data can have access instead of a few licensed users.

How long does it take to get a PLM live?

The product data foundation takes weeks, and the system keeps evolving from there as you add features. Enterprise PLM rollouts take months, sometimes years.

What's the difference between a product master and a PLM?

A product master holds the core product data: styles, colourways, suppliers, costs, coding and hierarchy. A PLM adds the development workflows on top, such as BOMs, tech packs, sampling and grading. Built on the same data, one can grow into the other.

When do you still need an enterprise PLM?

When your designers work in Adobe and need files and CADs linked to the product record, or when you're a large group with a PLM already running across several brands.

Should you follow PLM best practice?

Only where it fits how you work. Best practice is someone else's range, team and factories written down. When building around your own process costs a fraction of what it used to, it rarely beats a system shaped to the way you develop product.

Before you renew the PLM

01
The PLM features that used to need a specialist tool, from grading to tech packs, can now be built on your own product data.
02
Start where the pressure is and add BOMs, tech packs and grading as you need them, instead of rolling everything out at once.
03
An enterprise PLM still fits when designers need Adobe files on the product record, or a large group already runs one across its brands.