From concept to prototype in one to three weeks

A prototype’s job is to end an argument. The faster it does that, the more the program is worth.

The gap between an approved rendering and a physical unit is where most display programs lose their time. Not in design, and not in production — in the weeks between them, while a team debates something that a physical object would settle in ten seconds.

We build prototypes in one to three weeks. That’s not a speed claim for its own sake; it changes what the prototype is for.

What a fast prototype actually buys you

When prototyping takes six or eight weeks, the prototype becomes a final check — a confirmation of a decision already made, arriving too late to change much. When it takes one to three, it becomes a decision-making tool. You can put a real unit in front of a retailer before the program is locked. You can find the problem while it’s still cheap.

The things a physical prototype reveals are consistently the things renderings hide: how the unit feels when a shopper reaches for the bottom shelf, whether the header reads from the end of the aisle, whether a store associate can actually assemble it correctly the first time, how it behaves when it’s only half full.

Three paths, depending on what you need to prove

Not every prototype needs to do the same job, so we scope them differently.

One week — production-grade material and colour, integrated power and LED lighting, existing brand assets, production-grade printing. This is the fastest path to something you can put in a room and react to.

Two weeks — adds stock screens and CMS integration, plus some new content. This is where digital elements enter the conversation and you can evaluate motion and messaging rather than imagining them.

Three weeks — the advanced path for complex builds and multi-component programs. Cameras and sensors, electronic shelf labels, inventory tracking, audience analytics, CMS and reporting. Appropriate when the program’s value depends on the technology working, not just being present.

What makes the timeline possible

Speed here is a facilities question more than a scheduling one.

We run a 10,000 square foot model shop with 3D printing for expedited prototyping, CNC capability, and a large-format router — with design and engineering in the same building. Nothing goes out to a vendor and comes back. When an engineer wants to change a shelf angle, they walk to the shop floor.

That co-location is the whole mechanism. Most prototyping delays aren’t machining time; they’re handoffs, shipping, and waiting for someone else’s queue. Removing the handoffs removes the weeks.

Sample boards and pre-production

Prototyping doesn’t end with the unit. We produce sample boards to streamline how a program ships and to reduce the time it takes to reach stores — the same principle applied one step later in the chain.

The practical implication

If your current process treats the prototype as the last gate before production, it’s worth asking what would change if it were the first gate instead. Testing a physical unit early tends to surface the expensive problems while they’re still design problems.

That’s the argument for speed. Not shipping sooner — deciding sooner.

Have a program that needs to move quickly? Start a conversation.

Categorised in: Process

This post was written by Alexandra Zelcer