The Business Diagnostic
Where this sits. This is the written diagnosis you receive at the end of the free Business Diagnostic. Illustrative sample. “Velmora Distribution” is a fictional company and every number below is invented. The method, the scoring and the format are exactly what you receive — built on your numbers instead.

Example: a distribution company

A sample diagnosis.

Page 1 · Decision memo

Business Diagnostic — Velmora Distribution · September 2026 · Prepared by Luca-Ștefan Tamaș, LT Strategy Partners

Enter every order once. See margin every week. Keep the CRM you have — and actually use it.

Velmora's leadership brought five problems to the session. Three are worth fixing now, in this order, and only one of them needs anything built. The other two can wait: one is mostly a symptom of the first, and the other is an €85,000 purchase that wouldn't fix what is actually failing.

  • Orders are typed three times, and it costs about €31,000 a year. Every order goes into the ERP, then into the warehouse picking sheet, then into the invoicing app — three people, about 30 hours a week. Most picking errors and invoice corrections start here. The fix is the one build in this diagnosis: connect the systems you already have, so an order is entered once.
  • Margin shows up six weeks late, and discounts are given blind. The margin report is put together by hand around the 12th of the next month, without transport costs or the discounts agreed on the phone. In three months of invoices, 11 of the top 40 clients were below target margin once transport was counted. The fix is a weekly report and one rule, not a new system.
  • The CRM isn't the problem — nobody was shown where it fits. Two of eight sales reps use it, and the weekly sales meeting runs from their own spreadsheets. A new CRM would repeat the story with a different logo. The fix is a change in how that meeting runs, and two working sessions with the team.

What leadership already suspected, now with numbers: the order desk's complaint about typing the same order over and over is the most expensive problem in the company — more expensive than the ERP everyone complains about.

Owners & the first 30 daysOperations manager: owns the order flow, end to end, from this week. Finance manager: a weekly margin check by hand for the top 40 clients, starting next Monday.

Page 2 · The problem map

Five problems, one map.

Scores for the three fixes worth making

Diagnostic dimensionA · OrdersB · MarginC · CRM
Value at stakeGAA
Data realityGAR
How the work really runsAGR
Error tolerance vs stakesGAG
Whether the fix can be measuredGGG
Cost, effort & ownershipAGG
Exposure & dependencyAGG
  • G Solid — nothing here stands in the way of a fix
  • A Addressable gap — the condition to meet is named
  • R Comes first — a fix won't hold until this is solved
  • A / How the work runs (amber): about a quarter of orders arrive on WhatsApp, outside any inbox. The fix needs one way in for orders, agreed with the sales reps first.
  • A / Ownership (amber): the order desk, the warehouse and finance each own a piece of the flow; nobody owns all of it. One owner is named before anything is built.
  • A / Dependency (amber): only one person knows how invoices get into the invoicing app. It is written down in the first phase, before anything changes.
  • B / Value (amber): the €25,000 base case comes from three months of invoices; the full year will move it, most likely up.
  • B / Data reality (amber): discounts appear only as free text in invoice notes, and transport costs sit in a separate spreadsheet. Both need a proper field in the ERP.
  • B / Error tolerance (amber): a wrong margin figure would push discounts the wrong way. The report is checked against the accounts every month.
  • C / Value (amber): the licence cost is known (€4,800 a year); what the missed follow-ups cost isn't, so it isn't counted.
  • C / Data reality (red): the CRM holds about 30% of active customers; the rest live in the reps' own spreadsheets.
  • C / How the work runs (red): the weekly sales meeting runs from those spreadsheets, so nothing pulls anyone into the CRM. This comes first.

The binding constraint at Velmora: orders enter the business three times — most of what goes wrong downstream starts there.

What matters most was agreed with Velmora's leadership before scoring: cash and margin first, then the order desk's time. No aggregate score is reported — the weakest dimension decides; averages hide.

Page 3 · What to fix, and how

Three fixes, in order.

One build A · Enter every order once

The problem
Orders arrive by email, by phone and on WhatsApp, and are typed into the ERP, then into the warehouse picking sheet, then into the invoicing app.
What it costs, conservative base case
3 people × ~10 hours a week × 46 weeks × €10 an hour (Velmora's loaded cost) ≈ €14,000 a year of typing. Add about 40 corrected invoices a month and the second deliveries caused by wrong orders: ≈ €17,000. About €31,000 a year in all.
The fix
Connect what you already have: the order is entered once, in the ERP, and reaches the warehouse and the invoicing app on its own. WhatsApp orders go to one shared order inbox. No new system.
Effort
6–8 weeks, in three phases.
How we'll know it worked
Typing hours per 100 orders, corrected invoices a month, and picking errors — measured before, and 30 days after.
Owner
Operations manager.

A report and a rule B · See margin every week

The problem
Margin is known around the 12th of the next month, without transport costs or the discounts agreed on the phone.
What it costs, conservative base case
In three months of invoices, 11 of the top 40 clients were below target margin once transport was counted. Base case: at least €25,000 a year in discounts on orders that were already below target.
The fix
A weekly margin report by client and by product, built from ERP data, with transport and discounts included. And one rule: any discount above 5% gets a margin check before it's promised.
Effort
2–3 weeks. Most of the work is agreeing what “margin” means at Velmora.
How we'll know it worked
The share of orders discounted below target margin, every week.
Owner
Finance manager, with the sales director for the discount rule.

A process change and training C · Get the CRM used

The problem
Two of eight sales reps use the CRM bought 18 months ago; the weekly sales meeting runs from their own spreadsheets.
What it costs, conservative base case
€4,800 a year in licences, plus follow-ups that never happen — unmeasured, so not counted.
The fix
Give the CRM three jobs: customers, quotes and follow-ups. Move the active customers in. Run the weekly sales meeting from the CRM. Two working sessions with the reps, on their own accounts.
Effort
3 weeks, mostly your team's time; one half-day workshop.
How we'll know it worked
Quotes followed up within 7 days, and reps active in the CRM each week.
Owner
Sales director.

Confidence: scored at walkthrough depth — on systems described in the session, not inspected. Declared assumptions: loaded cost from Velmora's payroll figures; order volumes and corrections from the last three months; discounts from a sample of 600 invoices.

Page 4 · Not worth fixing yet, and next steps

What to leave alone — and what happens next.

Not worth fixing yet

Don't buy it now D · Replacing the ERP

Everyone complains about the ERP, and there is an €85,000 quote on the table to replace it. But the ERP isn't what's failing: orders are typed around it, the margin report is built outside it and the CRM sits next to it. A new ERP would inherit all three problems. What would change this: if, a year after A, B and C, the ERP is still what stops a fix, it goes back on the list — with a business case.

Not yet E · Barcode scanning in the warehouse

Picking errors are real — about 1.5% of orders — but roughly two thirds of them start with a re-typed order. Scanning would cost around €20,000 to fix the third that's left. What would change this: we measure again 60 days after A goes live. If errors stay above 0.5% of orders, scanning comes back with a business case.

Next steps — with us or without us

  1. Name one owner for the order flow (yours to do, this week). No project needed: one person, responsible for an order from the first message to the invoice.
  2. Start the margin check by hand (yours to do, from next Monday). The top 40 clients, last week's invoices, transport included. A spreadsheet is fine — the habit matters more than the tool.
  3. Give the CRM its three jobs (yours to do, one meeting). Customers, quotes, follow-ups. Everything else waits.
  4. Scope the order integration. With us or anyone else: map the flow, check how the ERP and the invoicing app can connect, and get it priced in phases.

If you want help, this is where each fix fits

  • A → a Solve engagement in three phases: map the flow, connect the systems, then run the team on the new flow and measure.
  • B → a Diagnostic Sprint on numbers and decisions, or the first phase of A.
  • C → a half-day team workshop and two follow-up sessions with the sales reps.

This document is yours either way.

This is the document your leadership team receives — built on your numbers, in your words.

Start with the Business DiagnosticWhen the answer is an AI system: a sample Gate Zero verdict