The argument, in full

An AI practice needs two capabilities

Most MSPs have built one. Why the commercial half decides who leads the deal — and who ends up quoting against somebody else’s requirement.

Start here

Customers don’t buy AI.

They buy a change to how the business works, and only then do they buy the technology that delivers it. The order matters more than anything else on this page.

The partner who leads the commercial conversation is better positioned to own the technology implementation that follows. Not guaranteed to. Better positioned — because that conversation is where the requirement gets written.

The two capabilities

Both are required. They are not the same skill.

An AI practice needs a commercial half and a technical half. Almost every stalled practice in the channel comes from a business having built one of them extremely well and assuming it covered both.

The commercial half

AI business consulting

Where value is created in a customer’s business. What the work should become. What the change is worth, and whether the case survives a CFO. Sold to the CEO, CFO and COO — before a requirement exists.

Most MSPs have not built this.

The technical half

AI technology implementation

How the technology is architected, licensed, configured, integrated, secured, deployed, adopted and supported. Sold to the CIO and the technical buyer, and delivered against a requirement somebody else wrote.

This is your asset, and a real one.

Neither half is superior. The commercial half is simply earlier in the sequence — and earlier is where the requirement gets written.

What it costs

Being brought in after the business decision has already been made.

One problem, showing up at two different points in the same opportunity.

Before the decision
We only hear about it when they ask us to quote.
After the build
We built exactly what they asked for, but there was no next conversation.

Whoever leads the commercial conversation writes the requirement everybody else quotes against. A requirement written without you leaves you competing inside somebody else’s decision — often on scope and price rather than business value.

Not because the technical work is inferior. Building that business was correct. Stopping there is what costs you.

The same opportunity, two positions

What changes when you are in the room first.

Arriving after the decision
Leading the decision

AfterA quote request, pre-shaped, with the scope already fixed
LeadingAn executive conversation about where value is created

AfterYou meet the IT manager and procurement
LeadingYou meet the CEO, CFO and COO

AfterYou compete on scope and price against three other quotes
LeadingYou compete on the quality of the case you built with them

AfterDeal size is bounded by somebody else’s requirement
LeadingDeal size is bounded by the value you identified

AfterDelivery, then silence
LeadingThe next workload, and the one after that

Where we stop

Twelve rows. One clean division.

The full boundary. The left column is the capability we build and, where required, supply. The right column is yours, always, without exception.

TechGrowth — the commercial half
You — the technical half

We doExecutive discovery with the customer’s leadership
You doSolution architecture
We doWhere AI changes the economics of that business
You doLicensing, tenancy and commercial supply
We doProcess and operating model redesign
You doConfiguration and integration
We doPrioritisation of opportunity against feasibility
You doData platform, governance and security
We doThe business case
You doAgent and workload build
We doThe investment case and supporting evidence
You doTesting and quality assurance
We doTarget operating model
You doMigration and cutover
We doProof of concept design and executive proof
You doProof of concept build
We doExecutive roadmap and implementation pack
You doImplementation and deployment
We doChange and adoption design
You doAdoption tooling and enablement delivery
We doBenefits definition and measurement model
You doManaged service, support and optimisation
We doExecutive governance of the commercial intent
You doTechnical governance of delivery

We sell no software, no licences and no implementation. The build is yours.

The alternatives

What an owner does if we do not exist.

Six reasonable options, and where each one runs out.

Option one

Carry on as we are

No cost, no disruption, and the technical business keeps running.

Where it fails
The quote request arrives pre-shaped. Margin compresses one renewal at a time.

Option two

Hire a commercial director

Permanent capability, owned internally, on the payroll.

Where it fails
Twelve months and six figures before the first executive conversation. Most candidates have run a sales function, not a transformation.

Option three

Vendor enablement

Technical fluency and certification, usually free.

Where it fails
It teaches the product. It does not produce a business case a CFO will approve.

Option four

Join a peer group

Benchmarking, good company, and an annual event.

Where it fails
Peer comparison is not a capability. Nobody comes into the business and builds anything.

Option five

Build an internal bench

Full control, full margin, and the capability is yours outright.

Where it fails
Expensive to recruit, slow to season, and idle between engagements. Few MSPs at this size can carry it.

Option six

Bring in a consultancy

Credibility and executive access, immediately.

Where it fails
They own the relationship and have no reason to hand the build back. You become a subcontractor inside your own account.

The pattern underneath all six. Every one of them either leaves the commercial capability unbuilt, or fills the gap in a way that costs you the customer relationship. That shared failure is the actual problem — which is why the argument is never about your technical practice, your people or your vendors.

Win the business case before you win the build.

Commercial decision first. Implementation revenue after. That is the whole causal chain, and everything we sell follows from it.

What follows from it

Build the capability. Buy the capacity while it builds.

Capability takes quarters to build. Your customers will not wait that long, so you do not have to.

Build the capability

Growth Executive

£15,000 a year

  • On site, inside your business, with the leadership and management teams.
  • The commercial half installed step by step, on your own offers and accounts.
  • Not training, not coaching, not a peer group.

How Growth Executive works →

Buy the capacity while it builds

Customer AI Revenue Engine

From £3,000 per engagement

  • Specialist capability brought into a live customer engagement.
  • You own the customer, lead delivery and sign every deliverable.
  • It ends at implementation readiness. You win the build.

How the Engine works →

A seat in the decision, not a slot in the quote list.

The fastest way to test any of this is against your own business. Ninety minutes on where your AI practice is constrained, what removing that constraint is worth, and an honest answer on whether we are the right people to help.

Win the business case before you win the build.