Leadership's guess going in: “maybe eight people use it.” The anonymous survey came back: nineteen.
Survey was anonymous and scored the conditions around people, not the people — stated up front, 91% response rate.
| Condition | What we found | Evidence | Binding? |
|---|---|---|---|
| Knowing how | Adequate in pockets. Three estimators self-taught to a high standard; most others one prompt deep. | MEASURED | No |
| Able to | Tools present (two paid seats, many personal accounts). No shared setup, no company knowledge connected — answers are generic because the AI can't see Meridian's data. | MEASURED | Partly |
| Feeling safe | Dominant blocker. Survey verbatims: “not sure I'm allowed to put client docs in”, “feels like cheating”, “don't want to be the one who caused a leak”. 14 of 19 users hide or downplay their use. | MEASURED | YES |
| Room in the day | Estimating team runs at tender-deadline load; new methods abandoned under pressure (“no time to do it the new way twice”). | MEASURED | YES |
| Environment allows it | No stated permission line, no worked examples, no checking routine. A confident wrong answer in a variation claim would currently reach the client unchecked — confirmed by the estimating manager. | MEASURED | YES |
Read in one line: your people are further ahead than you thought, and the business is further behind than they are. More training targets the two conditions that aren't the problem.
| Where | Basis | $/month | Status |
|---|---|---|---|
| Variation claims — drafting & assembly hours carried by senior estimators | One measured hour, extrapolated across 11 claims/month (see split-hour sheet) | $14,300 | ESTIMATE |
| Tender responses — repeat content rebuilt from scratch each submission | Interviews, 3 recent tenders reviewed | $9,800 | ESTIMATE |
| Site reports & client correspondence — office rework of field notes | Sampled week, 2 project admins | $6,200 | ESTIMATE |
| Paid AI seats currently delivering the above: unused | Licence billing | $400 | MEASURED |
| Recoverable, at conservative uptake | All figures become measured in week 3 if you proceed; every estimate is flagged until then | ≈ $30,700 | ESTIMATE |
| # | Question | Why it matters |
|---|---|---|
| 1 | Which client contracts restrict where project documents can be processed? | Sets the permission line staff are guessing at GAP |
| 2 | Who do you trust to say what a “good” variation claim looks like — and will you give them the hours to write it down? | The checking standard everything hangs on GAP |
| 3 | Estimating’s deadline load: what comes off their plate during the 16 weeks? | New habits don't form at 100% load GAP |
| 4 | Is the exit horizon 3–5 years? | Decides how hard we document for due diligence GAP |
Meridian doesn't have an AI adoption problem — it has an ownership vacancy. Nineteen people already use the tools; nobody owns what happens after that. The blockers are permission, deadline load, and a missing definition of “good” — none of which training touches. Fix those three in the estimating workflow first (fastest payback, highest judgment content), and the ≈$30,700/month stops leaking. If we proceed and fewer than 60% of the cohort are genuinely applying it in live work by the program's end, remediation is at our cost — your decision stays defensible either way.
Reading this as an owner of a 20–300 person firm? Your version of this page will differ in scale, not shape: the hidden-user count, the three binding conditions, and the monthly figure move — the pattern doesn't. The question the diagnostic answers is only ever which numbers are yours.