Owner-managed technology firms, whether managed service providers, development agencies, IT consultancies or small software businesses, share a distinctive strength and a distinctive weakness. The strength is technical: the work is genuinely good, and the clients who understand it value it. The weakness is commercial: the business around the work has rarely received the same rigour as the work itself.

The result is a familiar pattern. Revenue grows, the team grows, the technical reputation grows, and the margin does not. This report sets out where that margin goes, and the operating disciplines that bring it back.

Technical excellence is not a business model

The founding story of most owner-managed tech firms is a technical one. A capable engineer or technician starts taking on clients, delivers well, and grows by referral. The commercial machinery, meaning pricing, scoping, contracts, pipeline and reporting, is assembled as an afterthought while the founder focuses on the thing they are best at.

That works until it does not. At five people, the founder can compensate for weak commercial process with personal effort. At fifteen or twenty, the gaps compound: work is under-scoped because scoping is informal, under-priced because the rate card has not moved in three years, and over-delivered because the culture rewards solving the problem rather than solving the problem within the agreed scope.

The tech firm's margin problem is rarely a demand problem. It is the accumulation of small commercial decisions that were never actually made: rates that drifted, scope that crept, and contracts that renewed on old terms because nobody owned the renewal conversation.

Pricing the work, not the hours

Most owner-managed tech firms price on time: a day rate, an hourly rate, or a fixed fee derived from an internal estimate of hours. Time-based pricing is easy to administer and easy to defend, but it quietly punishes the firm for being good. The team that solves a problem in two days that would take a competitor five earns less for being better.

The correction is not necessarily a wholesale move to value-based pricing, which is hard to operate and harder to sell. It is a set of practical adjustments. Productising the recurring work, so that monitoring, maintenance, support tiers and retainers are sold as defined packages with defined margins rather than as accumulated hours. Reviewing the rate card annually against cost inflation and market rates, with a clear communication plan for existing clients. Charging properly for the expertise embedded in scoping and architecture work, which is often given away free as pre-sales.

The recurring revenue question deserves particular attention. A tech firm with a high proportion of contracted, recurring revenue is a fundamentally different business from one that resells its capacity project by project. It is more predictable, more resilient, and more valuable at exit. Most owner-managed firms know this. Fewer have an explicit plan for shifting the mix, with targets, packaging and a sales motion designed around it.

Scope discipline in technical delivery

Over-servicing in a tech firm has a specific character: the small fix done while in the codebase, the ticket resolved that sits outside the support contract, the emergency handled at no charge because the client was in trouble. Individually, each is defensible. In aggregate, they are a significant share of the team's capacity doing unbilled work that the client does not even know they received.

The remedy is visibility first, policy second. Time tracked against contracts and projects, honestly, shows where the unbilled work is going. From there the firm can decide deliberately: some of it is relationship investment worth making, some of it should be converted into paid scope, and some of it should simply stop. What changes the economics is that the decision is made rather than defaulted.

The technical founder as bottleneck

In most owner-managed tech firms, the founder is still the most capable technician in the building. That creates a specific trap: the hardest problems, the biggest clients and the critical decisions all route to the founder, and the business's capacity is capped by the founder's calendar.

The escape is the same discipline that applies in any owner-managed business, applied to a technical context. Documented standards for how work is done, so quality does not depend on who does it. A genuine second tier of technical leadership, developed deliberately and given real authority rather than escalation duty. And a founder role that is defined by the decisions only the founder can make, not by being the last line of support.

The numbers that matter

A tech firm of five to forty people does not need a finance function to run on numbers. It needs a short set of measures, maintained honestly and reviewed on a fixed rhythm:

  • Recurring versus project revenue: the mix, the trend, and the renewal dates of the contracts that make up the recurring base.
  • Gross margin by client and by service line: which contracts actually pay, and which are subsidised by the rest of the book.
  • Utilisation on billable work: including the unbilled technical work that is currently invisible.
  • Vendor and licence spend: the tool stack grows quietly; a twice-yearly review of licences, cloud spend and supplier contracts routinely recovers meaningful margin.
  • Pipeline beyond referral: what new work is coming, and how much of it depends on the founder's personal network.

None of this requires new software. It requires a spreadsheet, a fixed weekly and monthly rhythm, and the willingness to act on what the numbers show.

The commercial layer is buildable

The encouraging conclusion is that none of these problems are technical, and none of them require the firm to change what it is good at. The commercial layer that most owner-managed tech firms are missing is a finite piece of work: pricing reviewed and restructured, scope made explicit, recurring revenue packaged, a second tier developed, and a simple operating rhythm installed. The technical excellence that built the business then starts paying the owner what it has been worth all along.

← All perspectives