What Happens If Your Product Actually Succeeds? | Product Development for Scale

When developing a new physical product, one question tends to dominate everything else:

What if nobody buys it?

It is a reasonable concern.

Founders want to minimise risk, keep early development costs under control and avoid committing too much money before they know whether there is genuine demand. That often leads to a very sensible goal: build the first version as cheaply as possible, get it in front of customers and see what happens.

But there is another question that is discussed far less:

What happens if it works?

What happens if 50 orders become 500? What happens if a retailer wants 5,000 units? What happens if the product suddenly needs to be manufactured consistently, packaged efficiently, shipped internationally and produced at a cost that leaves enough margin to build an actual business around it?

A product can be cheap to launch and extremely expensive to scale.

That is where many early product-development decisions start to matter.

The cheapest first version isn't always the cheapest product.

Bootstrapping product development is not inherently a bad strategy.

In fact, for many early-stage businesses it is exactly the right thing to do.

There is little reason to spend tens of thousands of pounds on tooling for a product nobody has tested. Small-batch manufacturing, 3D printing, off-the-shelf components and manual assembly can all be extremely useful ways of getting a product into users' hands without making a huge initial commitment.

The problem comes when minimising today's cost becomes the entire development strategy.

A founder may:

• Choose the cheapest prototype.

• Avoid tooling.

• Use readily available components.

• Assemble the product manually.

• Accept a slightly higher unit cost because the initial quantities are small.

Again, none of those decisions are necessarily wrong.

The important question is:

Where do those decisions lead if the product succeeds?

A product that works perfectly well at 20 units may become completely impractical at 2,000.

• Maybe each product takes 15 minutes to assemble.

• Perhaps six different components need to be purchased from six different suppliers.

• Maybe an enclosure that works beautifully as a 3D print cannot easily be injection moulded.

• Perhaps the product has never been engineered around repeatable tolerances.

• Maybe the packaging is too large, the shipping costs are too high or the manufacturing cost leaves almost no margin once distributors and retailers are involved.

None of those problems are particularly visible while producing the first handful of units.

At scale, they become very visible.

Are you developing the cheapest possible version - or a believable path to scale?

This is the distinction that matters.

Early-stage product development does not need to mean immediately designing for millions of units.

But if the ambition is eventually to build a scalable product business, there should at least be a believable route from the first version to the thousandth.

That means asking questions such as:

• How many units does this product ultimately need to sell for the business to work?

• What does the product need to cost at that volume?

• How will it eventually be manufactured?

• How many separate components does it require?

• How complicated is it to assemble?

• Can the design move from low-volume manufacturing into higher-volume processes without fundamentally starting again?

These are not questions that only become relevant once a product is successful. They influence how the product should be designed in the first place.

Two very different development paths that impact product development for scale.

There are broadly two ways an early product can develop.

Both approaches have value. Prototype-first development prioritises speed, learning and low initial commitment. Scale-aware development introduces commercial, manufacturing and cost considerations earlier. In practice, the strongest approach is often a balance of the two: validate the product as early and efficiently as possible, without making decisions that unnecessarily limit what happens if demand grows.

Scale-aware development does not mean manufacturing at scale immediately. It means preserving the option to scale later.

Design for where you are. Plan for where you want to go.

Imagine a business producing a specialist desk accessory.

The founder intends to manufacture a few hundred units each year, sell them directly online and perhaps even assemble some of the product themselves. That can be a perfectly good business. There may be no reason whatsoever to optimise the product for 100,000 units.

Now imagine another business developing a consumer product that ultimately needs to be stocked by major retailers and sold internationally. The first production run might still only be 100 or 500 units. But the development strategy should be very different.

If the commercial model eventually relies on selling tens of thousands of units, then decisions around tooling, material selection, manufacturing processes, assembly time, packaging, logistics and unit cost become fundamental to whether the business can work. You do not necessarily need to pay for all of those things on day one. But you should understand where you are heading.

Small savings become very large numbers.

One reason professional product development can feel expensive at the beginning is that its financial impact is difficult to see at prototype quantities.

Saving £1 from the manufacturing cost of a product hardly matters when you are producing 20 units. At 100,000 units, that same £1 is worth £100,000.

Removing three minutes of assembly time from a prototype may seem equally insignificant. If you are building ten products by hand, it probably is. When thousands of products are moving through an assembly line, those minutes begin to translate directly into labour, capacity and cost. The same applies to component count, packaging volume, rejected parts, fasteners, manufacturing tolerances and dozens of other seemingly small design decisions.

At low quantities, poor design decisions can be absorbed. At high quantities, they are multiplied.

The cost of redesigning later.

This is another reason early development decisions matter.

Changing a CAD model before production might take a few hours. Changing the same part after tooling has been manufactured, packaging has been ordered, suppliers have been contracted and inventory has already been produced is a very different situation. The later a fundamental problem is discovered, the more expensive that problem usually becomes.

That does not mean every detail needs to be perfected before testing. Quite the opposite. Physical products should be prototyped, tested, challenged and changed. The objective is simply to make those changes while they are still relatively inexpensive to make.

Why professional product development can look expensive.

For an early-stage founder, spending money on industrial design, engineering or design for manufacture before significant sales exist can understandably feel difficult to justify.

The immediate comparison is often something like:

Why spend thousands developing this properly when I can get a basic version made for much less?

But those two things are not necessarily solving the same problem.

The cheapest route may answer:

Can I make one?

A more considered development process asks:

Can we make this repeatedly, reliably and economically - and can the business still work when we do?

Industrial design and engineering are not valuable simply because they make a product look more polished. Done properly, they influence how a product is assembled, manufactured, transported, maintained, packaged and eventually scaled. Their value therefore tends to increase as production volume increases.

Ironically, the founders who intend to manufacture the largest quantities often have the greatest reason to take those early decisions seriously.

You don't need to choose between testing and scalability.

There can be a tendency to see this as a binary decision.

Either you create a rough inexpensive MVP and test the market or you spend heavily engineering a fully production-ready product. There is a large amount of space between those two extremes.

A product can be intentionally designed so that its first version is appropriate for prototyping or small-batch manufacture while its underlying architecture still makes sense for future production.

Perhaps early enclosures are CNC machined or 3D printed while being designed with future injection moulding in mind.

Perhaps an off-the-shelf component is used initially while the design leaves room for a custom alternative later.

Perhaps assembly remains manual during early batches, but the number of parts and fixing methods are already being considered for higher volumes.

That is often a much more useful objective than trying to create the cheapest possible prototype.

Spend according to the stage you are at, but design according to where you intend to go.

What happens if 100 orders become 10,000?

Nobody knows exactly how successful a new product will become. That uncertainty is precisely why committing enormous amounts of capital to production too early can be dangerous but uncertainty is not a reason to ignore scale completely - it is a reason to develop with flexibility.

The aim is not to predict exactly how many products will eventually be sold. It is to avoid making early decisions that unnecessarily close off future options.

So alongside asking whether people will buy the product, it is worth asking another question:

If people do buy it, are we actually ready for what happens next?

Because the biggest problem with a product that was never designed to scale may not be that it fails.

It may be that it succeeds.