Hexona Systems· The engagement
The Leakage Diagnostic.
A two week intensive that starts the day you grant access. Every leak found is priced against your own numbers. If the leakage is immaterial, the report says so in its first paragraph and we tell you not to hire us.
01The deliverable
What you receive.
All three are yours to keep, whether or not you ever hire us to build anything.
- The report
- Written, and the substance of the engagement. Every leak found is quantified as an annual figure, with the system it was measured in and the period it covers named beside it. Ranked by recoverable dollars against the effort to recover them, so the order to work in is the order it is written in.
- The readout
- Ninety minutes, live, with whoever you want in the room. We walk the findings and take the argument. If a number does not survive your scrutiny it comes out of the report.
- The roadmap
- A sequenced build plan with a cost and a timeline against each phase. We write it so that somebody else could execute it without us, because a roadmap you cannot take elsewhere is a hostage rather than a plan.
02How it runs, and how it is measured
- 01
Access
You provision credentials and the clock starts. Not before: between commissioning and access sit kickoff scheduling and provisioning, which realistically take a further five to ten days.
- 02
Instrumentation
We trace every path a lead can take through your systems and find where each one stops. Most of the work happens here and most of it is not visible to you.
- 03
Interviews
Four to six conversations, thirty minutes each, across sales, operations and service. We are looking for the gap between what the system records and what people actually do.
- 04
Quantification
Each leak is priced against your own numbers, annualised, and ranked. Anything we cannot measure in a system you own does not go in the report.
- 05
Readout
The report lands, then the ninety minutes. Two weeks from access, end to end.
What we need from you.
- Systems access
- CRM, inbound channels, calendar, ticketing, and any other system that touches a lead.
- An owner
- One person who can grant that access and answer questions without escalating. This is the single most common reason an engagement stalls.
- Time from your people
- Four to six people for thirty minutes each. No preparation required of them.
- Twelve months of history
- Whatever your systems already hold. We do not ask you to assemble anything; if it is not in a system, it is not evidence.
How a leak becomes a number.
Every figure in the report is calculated from your data and nothing else. We take a population out of your systems, split it on the thing we believe is failing, and compare what each half actually went on to do. The difference between them, applied to your own volume at your own margin, is the annual figure.
That is the whole method, and it is deliberately unglamorous. It means any number in the report can be checked by anybody with access to the same systems, including you, on the day of the readout.
What we will not count
- Anything we cannot measure in a system you own
- If the evidence is not in your systems, it is an argument rather than a finding, and arguments do not get a dollar figure.
- Benchmarks from other companies
- What a comparable business converts at tells you nothing about what yours would have converted at, and it is the easiest number in this industry to quote and the hardest to defend.
- Improvements we assume rather than observe
- We do not price what a fix ought to deliver. We price the gap that is already sitting in your data, which is why the figures survive being argued with.
- Anything that needs new demand
- Recovered revenue is demand you have already paid for. Generating more of it is a different problem and, usually, a different firm.
03Terms, and what follows
| Term | |
|---|---|
| Fee | $5,000 |
| Credit | Credited in full against implementation, if you proceed |
| Duration | A two week intensive, which is ten business days from systems access |
| Delivered by | Led by the principal, with one or two operators |
| Afterward | You are under no obligation, and the report is yours either way |
| If there is nothing to find | The report says so in its first paragraph and we tell you not to hire us |
Your systems, and what happens to them.
- A mutual NDA, before any credential is issued
- Signed both ways and signed first. Mutual because the exchange runs both ways: we see how your business actually operates, and you see the method we use to take it apart. Nothing is provisioned until it is executed.
- Read-only access wherever the system allows it
- We are looking at what your systems already recorded, not changing anything in them. Where a platform has no read-only role, we say so before you grant access and we agree the narrowest scope that still answers the question.
- Named people only, and you see the list first
- Access is granted to individuals named to you in writing before the engagement starts, and to nobody else. Anyone who touches your systems is bound by the same NDA, whether they are an employee of the firm or working under contract to it.
- You revoke the access, not us
- At the readout you revoke every credential yourself, from inside your own systems, on your own schedule. You do not have to take our word for it or wait for us to confirm, which is the only version of this term that is worth anything to you.
- Raw exports are destroyed at readout
- Anything pulled out of your systems to do the analysis is deleted when the engagement closes. What we keep is the report itself and the working behind its figures, because we have to be able to stand behind a number if you challenge it later.
- Your data is used for your engagement and nothing else
- Not for benchmarks, not for a case study, not shown to another client, and not used to train anything. If we ever want to publish a record of the work, we ask, and we publish only the version you have approved.
After the diagnostic.
There is no obligation. The report and the roadmap are yours whether you build with us, build it yourself, or hand the whole thing to somebody else.
If you do proceed, the roadmap prices each phase before that phase begins and the diagnostic fee comes off the first one. You approve phases one at a time and are never asked to commit to a total, because until the diagnostic is finished neither of us knows what the total is.
Recovery is then measured after each phase, in the same system the leak was found in and against the same baseline. That measurement is what produces a sealed figure, and it is why a sealed figure is always smaller than what was found.
- Pricing
- Fixed price per phase, agreed before the phase begins
- Typical total
- $15,000 to $75,000 across all phases
- Diagnostic fee
- Credited in full against the first phase
- Commitment
- You commit one phase at a time, and never beyond the phase you have approved
04Straight answers
The questions buyers ask here.
Including the two where the honest answer is inconvenient for us.
How much does the diagnostic cost?
- $5,000, fixed. It is credited in full against implementation if you proceed, which means that if you build with us the diagnostic effectively cost nothing, and if you do not, you keep the report and the roadmap anyway. The fee does not move once scope is agreed, and scope does not move once access is granted.
How long does the diagnostic take?
- A two week intensive, which is ten business days from systems access. The anchor matters: the clock starts when credentials are provisioned, not when you commission the work. Between those two points sit kickoff scheduling and provisioning, which realistically take a further five to ten days. We state it this way rather than as "two weeks from purchase" because the second version will slip and then read as a bait-and-switch.
What actually arrives at the end of it?
- Three things. A written report, which is the substance: every leak quantified as an annual figure, with the system it was measured in and the period it covers named beside it, ranked by recoverable dollars against the effort to recover them. A ninety-minute live readout with whoever you want in the room, where we walk the findings and take the argument — if a number does not survive your scrutiny it comes out of the report. And a sequenced build plan with a cost and a timeline against each phase, written so that another firm could execute it without us.
What happens if you find nothing worth fixing?
- The report says so in its first paragraph and we tell you not to hire us. That is not a courtesy, it is a term of the engagement. We would rather return a null result to a company at the bottom of our range than manufacture a finding, because the only thing this firm sells is that a published figure means one specific thing.
What do you need from us to run it?
- Access to every system that touches a lead — CRM, inbound channels, calendar, ticketing. One owner who can grant that access and answer questions without escalating, which is the single most common reason an engagement stalls. Thirty minutes each from four to six people across sales, operations and service, with no preparation required of them. And whatever twelve months of history your systems already hold; we do not ask you to assemble anything, because if it is not in a system it is not evidence.
Who actually does the work?
- Led by the principal, with one or two operators. The principal leads every engagement rather than selling it and handing it over, which is the reason a ten-day diagnostic can work at all: the same short list of failures turns up in almost every company, and pattern recognition is what compresses the timeline.
Are we the right size for this?
- The firm operates at $3M–$15M revenue. Below that range the leakage is usually not large enough to justify the engagement, and we will say so on a call rather than take the fee and tell you afterwards. Above it, the constraint is usually that the number of systems involved makes a two-week window unrealistic, which is a scoping conversation rather than a refusal.
How is this different from hiring a management consultant?
- Scope and evidence. A consulting engagement typically produces recommendations drawn from interviews and benchmarks; this produces figures measured inside your own systems, with the system and the period named against each one. Anything we cannot measure in a system you own does not go in the report. The other difference is the follow-on: the fee is credited against a build we would do ourselves, so the roadmap is written by people who have to execute it.
Commission it.
$5,000, credited in full against implementation. The clock starts the day you grant access, not the day you pay.
Commission a diagnostic $5,000Or talk first.
Thirty minutes, with the principal, and no deck. Bring the part of the operation you already suspect. If it is not worth commissioning we will say so on the call rather than in a report you paid for.
hamza@hexonasystems.com