GRAIL
Our work What we do Why GRAIL Essays Industry Briefings Book a call

Contents

14 min read
What's Changing Across Your Commercial Network, GRAIL industry briefing cover
An Industry Briefing from GRAIL

What's Changing Across Your Commercial Network

Your delivery margin is drifting on accounts your rate card says should hold. Your senior application specialists are approaching retirement. Your quote-to-close cycle has not moved in a decade. Three problems that are actually one. A briefing for operations leaders at B2B industrial firms.

B2B Industrial · COO
Prepared by Johan Grönstedt  ·  GRAIL
For European mid-market B2B
industrial operations leaders
Date April 2026
Reading time14 min
Read the briefing
Executive Summary

You have seen this across your commercial engine

Why is our advisory margin drifting when the rate card has not changed?What happens to our key accounts when our senior specialists retire?Why has our quote-to-close speed not improved in a decade?

Every COO or Head of Operations at a mid-sized B2B industrial firm in Europe has had the same Monday morning. Three items on the operations review. First: the field service summary from the Hamburg account. A key customer submitted two application-validation questions last week. Lars answered both correctly and quickly. Lars retires in fourteen months, and his counterpart in Sweden has never worked this account. Second: the frame contract tender for an automation client. Seven days to submit, three of which were waiting for the application specialist to sign off on the technical compliance section. The procurement team's benchmark turnaround was five days. Third: the quarterly numbers. Realisation on your application advisory services is down four points against the same quarter last year. Same number of service calls. Same rate card. More senior hours per ticket, and clients who can compare your costs against AI benchmarks are beginning to push back.

You have run this commercial engine for a long time. The pattern used to be legible. Hire the best application engineers you could find. Build the accounts around them. Protect the quality floor. Hold margin. The business worked because the people made it work.

Something shifted. Your senior specialists are spending two hours in preparation for interactions that should take twenty minutes. Your cycle times on standard application inquiries are stuck at seven to ten days while faster competitors are quoting in two. And you can name the eight or ten specialists whose retirement inside five years will cost you more in lost accounts than any margin programme has recovered in the last decade.

This is not a you problem. It is an industry problem and a commercial-engine problem arriving at the same time. Most B2B industrial COOs are treating them as separate. The ones who see them as one are already building the advantage that will be very hard to close.

This briefing covers what is happening in your sector, what it means inside your commercial network, and the three questions your operations team should answer before the next board review.

Lens One  ·  Your Industry

B2B industrial just lost the equation that kept the commercial layer valuable

For three decades, the competitive advantage in B2B industrial distribution and technical sales rested on the same thing: individuals who understood the customer's application deeply enough to add value beyond what the catalogue could say. You could not automate that. You could not standardise it. Every company in your sector spent years trying to close the performance gap between their best application engineers and the rest. None of them did. The knowledge was personal, it was biographical, and it was the reason the margins held.

AI changes who can access that knowledge. When expertise that took fifteen years to accumulate can be extracted from work artifacts and made available to any application engineer at the moment they need it, the basis of advantage shifts. The question stops being "who has the best individuals" and starts being "who has the best knowledge infrastructure." The companies that see this first compete like organisations twice their size. The ones that do not find that their best people are still irreplaceable, but replaceable by a competitor who has made their average people as effective as your best.

Your supply chain is already optimised. Your logistics software is already good. The knowledge supply chain still runs on people: getting the right application wisdom to the right interaction at the right moment. That is the gap.

Digital procurement is compressing the product-availability layer from a different direction. Industrial procurement teams now arrive at tenders with AI-powered cost benchmarks that already model what AI-efficient delivery should cost. By the time your account manager walks into the meeting, the comparison has been run. Your product price may hold. Your advisory cost is increasingly visible. The firms building knowledge infrastructure are staying ahead of that comparison. The ones defending the status quo are going to have an uncomfortable conversation with procurement every quarter.

Lens Two  ·  Your Function

Your application teams, your accounts, and your cycle time feel it every week

Your commercial network. Account coverage is unevenly distributed across your best specialists. A handful of your strongest application engineers carry a disproportionate share of the accounts that matter most. The other accounts get adequate coverage. None of this is visible in the CRM. It is visible every time a key account gets a slow response because the one person who knows their application history is occupied with something else. The commercial engine runs on individuals because no infrastructure connects what each specialist knows to the team around them.

Your application advisory. Your senior application engineers are your scarcest resource. They carry application knowledge built over fifteen to twenty years. On a standard week they deliver eight to twelve hours of the complex advisory only they can provide. The remaining hours go into preparation work the firm has not yet built infrastructure to carry: digging up past specifications, checking regulatory compliance, building comparisons. The person who should be spending their week on the hardest application questions is spending it on work that does not need their judgment.

Your quote and configuration teams. A standard application inquiry runs seven to ten days from receipt to validated recommendation. Roughly half of that elapsed time is waiting: waiting for the application specialist to be available, waiting for a regulatory check to come back, waiting for a historical comparison to be assembled. The firms that have rebuilt this workflow close the same inquiry in two to three days. Same quality. Same application depth. The wait time is gone because the information retrieval no longer requires a senior person to do it manually.

Your senior application specialists. Your ten to twenty most experienced application engineers carry client-specific knowledge that took decades to build and has never been written down. When one of them retires, your firm has roughly eighteen months before the accounts they carried start going to tender. The conversations are already on your calendar. You know which retirements are coming. The question is whether the knowledge transfer has started or whether it is still on next quarter's agenda.

Your account continuity. Your strongest client relationships are held by people, not by the firm. A senior application engineer leaves, and with them goes the specific application history, the client's unwritten preferences, the context from ten years of interactions. The next person inherits the account but not the intelligence. Some accounts survive the transition. Some do not. The ones that do not go to tender, and the firm spends two years rebuilding what it should never have let walk out the door.

Delivery. Knowledge. Continuity.

The firms pulling ahead are building one piece of infrastructure

Your sector is under pressure from two directions. Digital procurement is compressing the product-availability margin from below, making transparent what used to be bundled. At the same time, your commercial engine is running on knowledge that lives in individuals' heads, making your best people simultaneously your most valuable asset and your biggest operational risk. Both forces arrived in the same window. Most B2B industrial COOs are managing them as two separate problems. They are one.

You do not have a margin problem, a retirement problem, and a cycle-time problem. You have one problem: the knowledge that makes your commercial engine valuable has never been separated from the specialists who carry it. Every margin drift is a symptom of that. Every slow quote cycle is a symptom of that. Every account that goes to tender after a retirement is a symptom of that. The single thing that fixes all three is not a new CRM, not a training programme, not a new performance metric. It is infrastructure that holds what your specialists know and makes it available to everyone who needs it.

Look at the firms pulling ahead in this sector. They are not better at hiring. They are not paying more for senior specialists. They are treating application knowledge as a firm asset under active construction rather than as a personal possession that happens to sit in the building. Every client interaction makes the infrastructure smarter. The specialist who retires adds to it on the way out. The account manager who joined last year operates with the accumulated judgment of someone who has been doing this for twenty years.

You can tell which camp a firm is in from one question: can you point to one thing in your commercial organisation that is measurably more capable this quarter than last? The firms that can are already closing the accounts you thought were yours.

The window is eighteen to twenty-four months. The adoption question is settled. Your question now is whether you build the infrastructure your commercial engine will run on for the next decade, or wait until the retirement that was predictable becomes the crisis that was avoidable.

Two Paths

What most firms are doing. What the leaders are doing instead.

Every B2B industrial COO has had the AI conversation. Most are making the same four decisions. A smaller group is making different ones. The difference is architecture, not tooling.

The default pathDefend the rate cardTreat retirements as an HR transitionDeploy AI tools on the existing workflowKeep account relationships personalThe leaders' pathRebuild the cost basis of each delivery tierExtract application knowledge from work already doneRebuild the inquiry workflow around what agents carryBuild account intelligence as a firm asset
The default path The leaders' path
Defend the rate cardSenior hours per ticket rise. Realisation drifts as procurement benchmarks tighten. Rebuild the cost basis of each delivery tierMap tasks by who must own them. Price accordingly. Margin widens while the rate holds.
Treat retirements as an HR transitionPlan a hire, run a brief handover, watch the account go to tender six months later. Extract application knowledge from work already doneCapture from call notes and service reports. The specialist becomes the escalation layer. Knowledge stops walking out.
Deploy AI tools on the existing workflowIndividual productivity rises. Cycle time does not move. The bottleneck is still the specialist. Rebuild the inquiry workflow around what agents carryConfiguration lookup, compliance check, historical comparison automated. Ten-day inquiry closes in two.
Keep account relationships personalEvery departure is a risk event. The strongest relationships are the highest-concentration risks. Build account intelligence as a firm assetInteraction history, client preferences, application context documented. The next specialist inherits the asset.

Same commercial network. Same twelve months. Opposite outcomes. The architecture is the decision.

Three Questions

Margin Per Delivery. Account Continuity. Cycle Time.

Three questions every B2B industrial COO is tracking. None of them used to be connected. They are now.

01 · Margin Per Delivery02 · Account Continuity03 · Cycle Time
01  ·  Margin Per Delivery

Why is our advisory margin drifting when the rate card has not changed?

Application advisory is bundled into the product margin. The cost is invisible until it moves. When senior preparation time per interaction rises because the specialist retrieves context manually, cross-checks compliance by hand, builds comparisons from scratch, the cost per engagement rises with it. Procurement teams that benchmark with AI-cost comparisons already know what AI-efficient delivery should cost. The rate card stays. The margin conversation is coming.

02  ·  Account Continuity

What happens to our key accounts when our senior specialists retire?

Eight to fifteen of your most experienced application engineers carry the client relationships that anchor your revenue base. Each holds client-specific knowledge accumulated over decades that has never been formalised. When one retires, the account transitions, the context does not. Industry experience is that one in three major accounts goes to tender within eighteen months of the primary specialist's departure. The retirements are not a surprise. The plan for them often is.

03  ·  Cycle Time

Why has our quote-to-close speed not improved in a decade?

A standard application inquiry runs seven to ten days. Roughly half of that time is waiting for a senior specialist to retrieve context that could now live in infrastructure the firm has not built. Competitors who have rebuilt their inquiry workflow close in two to three days. Same quality. Same application depth. In industries where procurement teams score on response speed alongside price, the slow firms are losing tenders they are not even tracking as losses yet.

Four Moves

What the firms leading this play are actually doing

Four concrete moves any B2B industrial COO can start this quarter. Each addresses one part of the commercial network. Together, they build one architecture the firm runs on.

1234
1

Commercial network: map each interaction to the task level, rebuild delivery costs around what still requires a senior

Take your ten most common application inquiry types. List the tasks inside each: application match, configuration check, regulatory compliance, comparison, write-up, client call. Mark each: agent-handled, composite, specialist-only, retired. What remains is a delivery model with a fundamentally different cost base. The COO who walks into the board meeting with this map controls the margin conversation.

2

Application advisory: extract expert knowledge from work already being done, not from interviews

Documentation sprints have failed in every industrial firm for twenty years. Extract from artifacts specialists already produce: call notes, technical responses, service reports, redlined specifications. The firm captures reasoning as a side-effect of paid work. The specialist remains the escalation layer and quality authority. Their role expands. The knowledge stops being biographical.

3

Quote and cycle time: rebuild the inquiry workflow around what agents carry from receipt to first draft

The seven-day inquiry cycle exists because each step requires a person. Build infrastructure that carries configuration lookup, regulatory cross-check, historical comparison, and draft specification. The specialist reviews the output in thirty minutes instead of assembling it over three days. The inquiry that took ten days closes in two. The same team serves three times the volume.

4

Account continuity: treat every major account as a knowledge asset the firm owns, not a relationship a person holds

Start with your ten highest-revenue accounts. Build a record for each: application history, configuration decisions, client preferences, regulatory context, unwritten rules. When the specialist rotates, retires, or moves, the next person inherits the asset. The account does not go to tender because the relationship lives on the firm's architecture, not the specialist's biography.

GRAIL  ·  How We Think

Four options. None can do what we do.

The B2B industrial COO has four places to go for help. Each for a specific reason, none of them works.

The large consulting firms' operations practices sell multi-month diagnostics by partner-led teams. They produce operating frameworks. They cannot put working knowledge infrastructure into your field service team in three months. Their revenue model depends on the hours your problem creates.

ERP and CRM implementation partners optimise data flow between systems. The application wisdom a twenty-year specialist carries does not live in the CRM. A system migration does not extract it. Different problem, significant cost.

Sales enablement and content platforms capture what the expert said, not how they reasoned. Call recordings, templates, libraries. The judgment that makes a recommendation defensible is not in the recording.

Your internal IT function builds dashboards and deploys copilots. IT optimises for standardisation. It does not sit close enough to how application specialists work to codify their reasoning.

The market offers four things you have already said no to. GRAIL is the fifth option.
What You GetWhy It Matters
What You Get
  • Senior advisory that speaks commercial-floor vocabulary, not diagnostic decks
  • Working infrastructure your application teams use the same week
  • Custom agents built on your actual application knowledge and account base
  • The start of a knowledge asset your best specialists feed over time
  • No vendor lock-in at any phase of the engagement
Why It Matters
  • Founded by operators who have run commercial delivery organisations
  • Business first, technology second
  • Three weeks from first meeting to working infrastructure in the field
  • Your teams own the infrastructure from day one, IP transfers immediately
  • Every next step earned by what shipped, never assumed
GRAIL  ·  How We Work

Three sessions with your commercial leadership. Working infrastructure from week one.

Three workshops. Each delivers standalone value. Each earns the right to the next.

How to thinkYour commercial infrastructureReady to run
Workshop 01

How to think

Walk through what is happening in your sector and inside your commercial engine. Build the first piece of infrastructure in the room: an account-specific agent extracted from records you already have. Your operations leadership leaves with a shared view of what to do next and the first working piece of infrastructure in their hands.

Workshop 02

Your commercial infrastructure

A half-day build. Your Head of Application Engineering, Head of Field Service, Head of Quotes, and Head of Key Accounts each leave with five to ten pieces of working infrastructure: application-matching agents, inquiry-workflow tooling, account-intelligence assets for your most critical relationships. Infrastructure the teams use the same week.

Workshop 03

Ready to run

Refined infrastructure from real use. The rollout plan across your wider commercial organisation. The knowledge-extraction plan for the retirements on your calendar. The account-continuity plan for your highest-risk relationships. And the board numbers: margin per delivery by segment, cycle time by inquiry type, account-continuity exposure by specialist.

Three weeks. No IT project. No board approval needed to start. The infrastructure your commercial engine is already running on when we finish.

Five Questions

For your next operations review

The questions where your team cannot agree on an answer are the ones worth the longer conversation. Ask these honestly before the next board cycle.

On your last ten application advisory interactions where the margin came in below plan, how many lost ground because senior preparation time ran higher than expected? Do you measure this, or do you only see it in the realisation number at quarter end?

If your three most experienced application specialists retired next quarter, what would happen to the accounts they carry? What has actually transferred to the rest of your team in the last twelve months, and how would you verify it?

What is your average quote-to-close cycle on a standard application inquiry, and what is the fastest your closest competitor closes the same inquiry? If you do not know the second number, how are you planning to find out?

Can you point to one part of your commercial organisation that is measurably more capable this quarter than last? Not more active, not better staffed. Measurably more capable at the core application advisory work that drives your margin.

Which of your account managers or application engineers is already working in a way that the rest of your team will need to work by 2028? What would it take to make that the default across your commercial network rather than the exception?

If any of these produces a disagreement in your operations team, that is the conversation worth having before the board asks the same question.

Industry Briefings

Continue reading

Johan Grönstedt  ·  GRAIL  ·  johan@grail.works  ·  grail.works
Talk to GRAIL about your management team
Sources and limitations

This briefing draws on GRAIL's engagement experience with leadership teams and on public company disclosures. Figures are illustrative unless a source is named beside them. A sourced edition is in preparation.