Skip to content
All answers

Working with us

How can you tell if a software studio can handle a business your size?

The short answer

Ask what they run themselves, not only what they have launched for other people. Systems a studio operates every day have met the failures that only appear at scale, and a portfolio of launches does not prove anyone stayed to meet them.

Updated

Ask what they run, not what they launched

A launch is a photograph. An operating system is a film — it has a second year, a supplier who changes a feed format without telling anyone, a month when the volume triples.

So the useful question is not "what have you built?" but "what are you responsible for on a Tuesday?" A studio that cannot answer it concretely has shipped software and then left, which is a different trade.

The numbers worth asking for

Ours are operating facts rather than launch facts: a hundred and eighteen thousand products on one live storefront at Shopflooring, a hundred and seventeen automation workflows in service across Business OS, eleven businesses coordinated through one identity provider.

One more, and it comes with its own caveat, because this page is about exactly that distinction. Contractor OS is a forty-five-table domain model where every financial document posts a balanced entry and no money value is stored as a floating-point number — and we run it as a live demo rather than as somebody's production ledger. It is built and demonstrable. It is not carrying a stranger's invoices this month.

That float decision is still the sort of answer to listen for. It is taken early, it is tedious, and it is the difference between accounts that reconcile and accounts that are a penny out in a way nobody can find.

Eight of our eleven are our own

This is worth saying plainly, because it cuts both ways. Most of the portfolio is software we built for ourselves and still run — which means we carry the consequences of our own architecture, and it also means it is not a wall of client logos.

Judge it as what it is. It is stronger evidence than a logo that something works at scale, and weaker evidence that a stranger enjoyed working with us. Ask for both.

What to ask us

What breaks most often, and what was done about it. Which decision in the estate turned out wrong, and what it cost to reverse. How a change reaches production. Those answers are hard to invent and easy to check.

Asked next

Does a small studio mean a single point of failure?

It is a fair worry, and the answer to look for is documentation rather than headcount. Ask whether decisions are written down with their reasoning, whether another engineer could pick the system up from what exists, and what the handover looks like if the engagement ends.

Should we ask for client references?

Yes, and ask what they are references for. A reference confirms what someone was like to work with; it rarely tells you whether a system survived its second year. Both questions are worth asking, of different people.