This is what you'd actually receive.
Before you send an assessment link to your team, you should see the deliverable. This page walks through a readout the way your leadership team would receive it — the headline numbers, the blind spots, the evidence, and what to do first.
Everything on this page is a composite, illustrative example — the company, the numbers, and the quotes are representative of the kinds of findings these assessments surface, not a specific client engagement. Your readout is built entirely from your team's answers, and if there's no material leak, it says so.
Subject of this example: a mid-market commercial contractor — roughly $40M revenue, ~120 people, project-heavy operations.
What leadership sees first.
One week after the link went out: 14 of 16 invited people responded across four role groups. The headline numbers, then every leak theme — click one to see the evidence behind it.
Change orders and owner-approved extras slip through the billing process — work performed but never invoiced. Two role groups reported it independently; neither knew the other was seeing the same leak.
"More than we'd like. Maybe 2 or 3 a month slip through unbilled. They range from a few hundred dollars to five figures on a big one."
"Last month we paid a sub for work tied to a change order nobody logged — we ate the cost because it never got billed to the owner."
Answers are anonymous and role-tagged. A finding only becomes a headline when multiple roles point at the same leak.
What the team knew that leadership hadn't heard.
Going in, leadership named bid leveling as the pain. The team — independently, role by role — surfaced two bigger leaks nobody had put on the table. This is the moment the readout earns its keep.
Unbilled change orders
~ $100,000 / yr in work performed but never invoiced
Project managers reported 2-3 change orders a month slipping past invoicing. Finance independently flagged subcontractor invoices tied to change orders that were never logged. Neither group knew the other was seeing the same leak.
Consensus 3/5 · reported by two role groups independently
Margin blindness, three weeks a month
cost overruns surface weeks after the spend
Reconciled job costs lag the field by seven to ten days. Operations discovers overruns only when accounting catches up — too late to course-correct while the job is still active. Decisions run on stale numbers most of each month.
Consensus 3/5 · finance, operations, and PMs each described it
In this example, customer support scored highest across the board (4/5 on use depth). The readout names strengths as plainly as leaks — so effort goes where the leaks are, not where the noise is. And when there's no material leak at all, the honest answer is a short readout and no pitch.
Leadership logs what they expect to find before the link goes out.
Anonymous and role-tagged — no one sees anyone else's answers.
Strong cross-role signal leadership didn't predict = blind spot.
Every function, scored on the same six questions.
No black box: every part of the business gets scored 1-5 from the team's answers. Orange is a bottleneck worth attention; green is already mature. In this example, finance is the constraint and support is the strength.
| Use | Data | Flow | Delegate | Team | Risk | |
|---|---|---|---|---|---|---|
| Sales | 3 | 2 | 2 | 1 | 3 | 1 |
| Operations | 2 | 3 | 2 | 2 | 2 | 2 |
| Support | 4 | 3 | 3 | 3 | 2 | 2 |
| Finance | 1 | 2 | 1 | 1 | 1 | 3 |
| Delivery | 3 | 4 | 3 | 2 | 3 | 2 |
TBI is the annual value leaking out of the operation — dollars never billed, hours burned on manual work, growth you can't take on. The assessment frames your TBI; the Audit + Playbook prices the fixes — so the ROI is defined before you spend a dollar.
One honest recommendation — not a tool list.
The readout ends with an order of operations, sorted by what the evidence supports.
Fix first
- Change-order capture: one flow from field approval to invoice — plug the $100K leak before any AI.
- A weekly job-cost snapshot while the real fix is built — stop deciding on stale margin.
Build next
- Single-entry job costing: enter once, land in both systems — recover ~55 hrs/mo.
- Live margin visibility for leadership — overruns surface while the job can still be corrected.
Skip for now
- Generic AI tools and chat assistants — nothing here needs one yet.
- Anything touching estimating — one role group's signal isn't enough evidence to fund it.
Want your numbers instead of an example?
Apply for one of the complimentary Assessment slots — normally $5,000. One link to your team, ten minutes per person, and a readout like this built from your business in about a week.
Sample assessment readout · illustrative example — not a client engagement