← Notes

The quiet cost of not having a specialist

Small companies rarely fail from one big mistake. They lose ground slowly, in all the places they could never afford to hire.

· 5 min read

Ask a small business owner what holds the company back and you will usually hear something concrete: cash flow, a difficult client, not enough hours.

The honest answer is often less dramatic. Most small companies are not losing to a single big problem. They are losing a little ground in a dozen places at once, and every one of those places is somewhere they could never justify hiring a specialist.

What "we'll manage without one" actually costs

Nobody decides to skip having an analyst. What happens is that a decision gets made on intuition instead of numbers, and the cost of that decision never appears on any statement, because you never find out what the other choice would have earned.

Multiply that across a business:

  • No analyst. Pricing gets set by feel and stays there for three years.
  • No technical writer. The handover document does not exist, so the knowledge lives in one person's head until they leave.
  • No compliance specialist. You find out about the requirement when someone asks for it.
  • No designer. The proposal that goes to a serious client looks like it came from a smaller company than you actually are.
  • No one owning security. It is fine, it is fine, it is fine, and then it is not fine.

None of these appear as a line item. Every one of them shows up in the results eventually, usually as something you blame on market conditions.

The frustrating part is that these are not exotic skills. They are ordinary professional competence that a hundred-person company simply has in the building and a fifteen-person company does not.

What changed

For the first time, a small company can produce a decent version of most of that work without employing the specialist.

Not an excellent version. Not a substitute for a genuine expert on something high-stakes. But the gap that matters is not between "AI-assisted" and "expert" — it is between "AI-assisted" and nothing at all, which is what was there before.

We have watched this happen inside our own business. Books that used to sit unreconciled now reconcile to the cent. Documentation written properly instead of being an item that moves down the list forever. Security work that would have needed a contractor, done as routine maintenance. None of it is glamorous. All of it was previously skipped.

The trap, and it is a real one

Here is where this goes wrong, and it goes wrong often enough to be worth more space than the good news.

A tool that lets you produce specialist-shaped work does not give you a specialist's judgement. You can now generate a financial analysis, a security review, a compliance checklist. What you cannot generate is the instinct to know that this particular analysis is subtly wrong, or that the review missed the thing that actually matters in your setup.

So the rule we work by: use it to do work you could not otherwise afford — but never for work where being confidently wrong is worse than not doing it at all.

A rough first draft of your documentation is much better than nothing. A confident, wrong interpretation of your regulatory obligations is much worse than nothing, because nothing at least leaves you appropriately worried.

The distinction is not about how important the task is. It is about what happens when the output is wrong and nobody notices. If the answer is "we lose a bit of time", go ahead. If the answer is "we find out from a regulator, a customer, or a breach", get a human who knows.

The practical version

Take ten minutes and list the roles your business does not have. Not the ones you are hiring for — the ones you long ago accepted you would never have.

That list is where the value is. It is also, almost always, a list nobody has looked at in years, because the answer was permanently "we can't afford that."

The answer has changed. It is worth re-reading the list.


NEXT3LABS builds and runs high-stakes custom software from Singapore. We write up what actually happened on our own projects — including the parts that went wrong.

Working on something where being wrong is expensive? Message us on WhatsApp — no pitch, happy to compare notes.

More notes · Other ways to reach us