Product Company or Project Shop?

Project work gives predictable cash but locks up people; product work offers scale but spends money with no visible return. We oscillated between the two for years until we changed the question.

From identity to capability

Instead of asking whether we are a product or a project company, ask which capabilities have appeared three or more times across projects.

Only repeated capabilities deserve productisation, such as permission backends, content management or reporting engines. A one-off feature becomes a liability even if it ships as a product.

The compromise we settled on

We turn high-reuse modules into an internal component library. It is never sold, but it removes about thirty percent of the code from each project.

Each year we pick one direction for a small product bet, capped at two months and two people, so failure never threatens the core business.

Projects keep us alive; products give us room to imagine. Turn repetitive work into assets before talking about transformation.