Five Products, Sixty Days, One Spine

Shipping five products in a sixty-day window sounds like a stunt. It is not, and I want to explain why, because the explanation is the entire strategy of the company.

We did not ship five products. We shipped one platform, five times. That distinction is not wordplay. It is the difference between a team that would have burned out and a team that compounded.

The trap of the standalone product

Most companies build products as islands. Each one gets its own login, its own permissions, its own data model, its own way of handling the boring but critical parts. Five island products means five copies of the same hard, unglamorous foundation, each slightly different, each with its own bugs, each aging on its own schedule. You do not have a portfolio. You have five startups sharing a logo and a very tired team.

The math on that is brutal. The visible part of a product, the part a customer sees, is a small fraction of the work. The invisible part is identity, access control, auditability, the way the system proves what it did. Build that five times and you have spent almost all of your effort five times over on the parts no customer ever compliments you for.

What one spine changes

A spine is the shared foundation every product stands on. For us that is the governed control plane. The agent orchestration, the policy layer, the six-layer authorization model, the human approval gates, the hash-chained audit trail, the identity system. Those are built once, hardened once, and improved once for everyone.

When the spine exists, a new product is not a new foundation. It is a new surface on an existing one. The team gets to spend its time on the thing that is actually different about this product, the specific workflow for manufacturing, or waste and fleet, or events, or real estate, because everything underneath is already solved. That is how five products fit in sixty days. Four fifths of each one was already done before the sixty days started.

Leverage is not the same as speed

I want to be careful here, because this can sound like a story about moving fast, and it is not. It is a story about leverage. Speed without leverage is just a team sprinting, and sprinting does not scale. You cannot sprint your way to ten products. You will fall over around three.

Leverage is different. Leverage means the second product is cheaper than the first, the third is cheaper than the second, and the shared foundation gets stronger every time you lean on it. A bug fixed in the spine is fixed for everything. A capability added to the spine is available to everything. The portfolio does not divide your attention. It concentrates your investment in one place that pays off in ten.

The discipline it demands

This only works if you are ruthless about what belongs in the spine and what belongs in a product. Put too much in the products and you are back to islands. Put the wrong thing in the spine and you have coupled everything to a decision you will regret. The judgment call, made constantly, is whether a given piece is something every product needs or something only this one does. Get that call right often enough and the whole thing compounds. Get it wrong and you have built a monolith with extra steps.

Five products in sixty days is not the achievement. The spine is the achievement. The products are just the proof that it works. Anyone can announce a lot of launches. The question is whether the eleventh one is cheaper than the tenth, or whether you are quietly running five companies and hoping no one notices the seams.

We built the spine first so we would never have to.