Run by the engineer who writes the code.

[01]

Practitioner-led

We ship our own software on the same stack we use for clients. Every recommendation is one we've had to live with — the maintenance, the refresh cycle, the 2am page.

[02]

Senior-led, end to end

The people who scope your project are the people who build it — senior engineers, reachable directly, with no account layer or delivery relay in between.

[03]

Specific over generic

We name the system, the constraint, the year. Vague claims are easy to make and impossible to check, so we don't make them.

[04]

Built to outlast us

We optimise for the team that maintains the software after we've gone: boring stacks, clear documentation, and no lock-in.

Three phases. Most engagements move through all three; some stop after discovery, and that's a legitimate outcome.

[01]

Discovery2–3 weeks · fixed fee

We sit with the people doing the work and scope something worth committing to. You get an honest recommendation, even when it's not yet.

[02]

BuildEmbedded

We design, build, and ship in stages, against real data, with you close enough to course-correct.

[03]

OperateOngoing

Software nobody maintains quietly fails. We stay on, usually on a retainer, through the refresh cycles and the changes.

Kyle ThomsonEngineering & delivery

Kyle leads the technical work — platforms, agents, and the parts that have to hold up under audit. He started Kola after a decade building software inside regulated businesses, and that experience is where most of the opinions on this site come from.