Build it once: why software and joinery belong in the same workshop

The hand-off gap

The usual way to build an interactive space is to split it three ways. A design studio draws it. A software house writes the application. A fit-out contractor builds the joinery and installs the hardware. Each is good at their part. None of them owns the seams.

Those seams are where projects go wrong. The screen is a different size by the time it's specified. The cable run wasn't designed into the cabinet. The content was built for a resolution the wall can't drive. Nobody lied; the information just degraded every time it crossed a company boundary.

What "one workshop" actually changes

When the same team designs the interaction, writes the software, builds the joinery, and installs it, the seams stop being contractual. They become internal — a conversation across a bench, not a variation order.

• The cabinet is drawn around the hardware, not the other way round.
• Content is authored for the exact panel it will run on.
• The person who wrote the software is in the room when it's mounted.

None of that is exotic. It's just hard to do when the work is spread across three balance sheets.

Where it shows up

It shows up on install day, when the build is calibration rather than problem-solving. It shows up in the budget, because there's no margin stacked at every hand-off. And it shows up a year later, when something needs updating and there's one number to call instead of three pointing at each other.

Closing

"Build it once" isn't a slogan about craft for its own sake. It's an operational position: fewer boundaries, fewer translations, one accountable line from first sketch to opening day.