Strategy

Services, as software: the category shift your professional-services firm hasn't priced yet.

22 April 2026 Blackflake Editorial 7 min read

Every major technology platform shift redefines an industry's margin profile. Cloud did it to infrastructure. SaaS did it to enterprise software. AI agent platforms are doing it right now to professional services — law, medicine, accounting, consulting, procurement. The winners will not be the firms that bolt AI onto their hourly billing. They will be the firms that understand the category has changed underneath them.

The thesis, in one paragraph

A professional-services firm today sells hours. A law firm bills £500/hour for partner time on a contract review. A consulting firm bills £150/hour for an associate on a deck. A BPO bills by the seat. Revenue scales with headcount, and margin scales with the firm's ability to hire and retain expertise. Services-as-software changes the unit economics. The firm now sells the outcome — a contract review, a market analysis, a regulatory filing — packaged as an AI-delivered system the client buys, owns, and runs. The revenue stops scaling with billable hours. It scales with licences.

Why this matters to a CEO

If you run a services firm today and a competitor moves first:

  • They will deliver the same outcome at 10–40% of your cost.
  • They will retain the margin you used to pay your junior staff.
  • They will ship new verticals in weeks while you plan the next office lease.
  • Your existing clients will ask why you are still billing by the hour.

The shift is not optional. The question is whether you lead it, follow it, or get acquired by whoever does.

What a services-as-software product actually looks like

It is not a chatbot. It is not a ChatGPT wrapper dressed up with your firm's logo. A real services-as-software product has:

  • An ingestion layer that takes a client matter (contract, case, claim, invoice) and extracts the domain facts.
  • A domain-reasoning layer — agents with codified expertise in the vertical's rules and jurisdictional context.
  • A context memory — the client's prior matters, the firm's house style, the governing law.
  • A verification layer that audits the AI output against firm standards before partner review.
  • An ownership model — the client licenses the system, owns their data, and the reasoning is inspectable.

This is what Blackflake builds. Not because it is the only way, but because it is the only way that preserves the margin.

A worked example — Polish commercial litigation

Consider a mid-sized Polish law firm that handles 800 commercial disputes a year.

Today:

  • Average associate time per matter: 14 hours
  • Associate billable rate: 400 PLN/hour
  • Revenue per matter: 5,600 PLN
  • Associate cost per matter: ~1,700 PLN
  • Gross margin: ~70%

With a Legal AI vertical deployed:

  • Associate time drops to 3 hours per matter — automated clause extraction, risk scoring, draft generation.
  • Partner review time: 1.5 hours at 900 PLN/hour = 1,350 PLN.
  • New pricing: fixed-fee analysis at 3,500 PLN + partner review billed at cost = ~4,100 PLN/matter. The firm becomes price-competitive.
  • Associate cost per matter drops to ~370 PLN.
  • Gross margin rises to ~90%, on a lower top line, but with capacity to serve 3× more clients per associate.
"The firm that runs the AI pockets the delta. The firm that doesn't, gets outbid on every contract."

Illustrative. Actual deltas depend on matter mix, associate seniority, and deployment specifics. But the shape of the change is robust across jurisdictions and practice areas.

The three transitions to plan

If you are a services-firm leader thinking about this shift, you have three decisions — each with a 1–2 year lead time.

1. Productise vs. platform-license

Do you build the AI vertical yourself and sell it as your firm's product, branded as yours? Or do you license an underlying engine (Blackflake, Harvey, Spellbook, etc.) and compose the vertical on top? The first path preserves your brand on the deliverable. The second path lets you ship a year faster.

2. Reprice the work

Billable hours survive for high-judgment partner-level work. Commoditised tasks — contract review, basic tender drafting, ICD-10 coding, due-diligence document summaries — move to licence revenue or fixed-fee delivery. Your pricing page needs a new section before your competitor's does.

3. Rearchitect the team

Junior-associate growth slows. The partner-associate ratio widens. The bottleneck moves from hiring associates to training the AI on your firm's house standards. You need an internal role that didn't exist two years ago — an AI operations lead who owns the deployment.

The honest counter-argument

A services-firm partner reading this will say: "Our value is the relationship, the judgment, the bar-admitted authority — AI can't replace that." That is correct and it is also beside the point. No one is trying to replace the partner. The shift moves the junior associate work into software, not the partner's judgment. The partner's role becomes more valuable per hour, not less, because the partner now sits on top of a higher-leverage system.

The firms that misread this will point at the partner's irreplaceability and keep billing juniors by the hour. That is exactly the strategy that loses.

Closing

Services-as-software is not a future bet. It is happening in production today in law, healthcare, and procurement. The firms that treat it as an efficiency hack — "we'll use AI to make our juniors faster" — will lose the margin to firms that treat it as a category shift.

Blackflake exists to build the underlying engine for that shift. The first three verticals are Legal AI, MedAssist, and TenderAI. Each is a services-as-software product built on the same engine. The economics on the far side of the shift are what is worth building toward.


— Blackflake Editorial 22 April 2026