The proposal should leave with the inspector
The gap between an inspection and a priced, readable proposal is where foundation repair revenue leaks — and it is almost entirely a document assembly problem, not a judgment problem.

the window closes faster than the paperwork moves
An inspector spends ninety minutes in a basement, takes forty photographs, measures deflection, notes soil and drainage conditions, and leaves with the homeowner's full attention. Then, in a large number of branches, the proposal arrives two to five days later as a PDF with a number on it. The attention is gone. So is the urgency, and frequently so is the job — to a competitor who left something on the kitchen table.
Ask why the delay exists and the answer is never judgment. It is assembly: pulling the price sheet, matching product to condition, writing the scope narrative, inserting photos, applying the financing options, and formatting something a homeowner will actually read. Two to three hours of clerical work per inspection, performed by the most expensive field person in the branch, at night, after a full day of appointments.
what a homeowner is actually buying
Not piers. A homeowner is buying an explanation they can repeat to a spouse. The proposals that close explain what is happening under the house in plain language, show the photograph that proves it, state what will be done and in what order, and price it in a way that maps to a monthly payment. Most of that is templated content selected by the observed condition — which is exactly what an agent does well.
The parts that are not templated — whether this wall needs anchors or a beam, whether the engineer has to be involved, whether the soil report changes the approach — remain the inspector's call. The agent should never make a structural determination. It should make the inspector's determination legible and priced within minutes of them writing it down.
the operating change this forces
Same-day proposals expose a pricing discipline problem that slow proposals conceal. When every proposal takes three days, inconsistent pricing across inspectors looks like normal variation. When they are generated from one price book in the driveway, the variation becomes visible immediately — and so does the inspector who has been discounting to close. Most branches discover this in week two and it is uncomfortable and worth it.
The second change is warranty language. Proposals produced by hand drift; the standard terms slowly diverge across a branch network until a claim arrives and legal discovers four versions in the field. Generated documents make the terms one thing, versioned, and auditable — which matters far more in a roll-up than anyone budgets for.
measure the window, not the effort
The metric is time from inspection completion to proposal delivered, and the target is minutes. Track close rate against that interval and the curve will make the business case without a slide. Track inspector evening hours too — the retention effect of giving field staff their nights back is not soft, it is a hiring cost you stop paying.
the financing conversation belongs in the same visit
Foundation repair is rarely paid in cash, and the financing decision is entangled with the timing decision far more tightly than most sales processes acknowledge. A homeowner who hears a number, says they need to think about it, and receives a financing link three days later has had three days to talk themselves out of a five-figure structural repair, price the alternative of doing nothing this year, or get a second opinion that undercuts the first on price alone. Presenting financing options — term, monthly payment, approval likelihood — inside the same visit, tied to the actual proposal rather than a generic offer, keeps the decision inside the moment when the homeowner is still standing in the room that convinced them something needs to happen. Branches that move financing into the inspection visit consistently see a higher share of proposals convert on the spot, not because the financing terms changed, but because the decision never left the house.
the ninety-day rollout, and what to leave alone
Start with the price book, not the software. Any branch network still running on inspector judgment for pricing needs one canonical, versioned price book mapped to diagnosis categories before proposal generation can mean anything, and that consolidation exercise alone typically surfaces the discounting problem before a single proposal is automated. In the first month, build the templates against that price book for the five or six most common diagnosis patterns, which will cover the large majority of inspections. In the second month, pilot live in-visit generation with two or three inspectors who are enthusiastic rather than skeptical, and use their exceptions — the proposals that needed a manual override — to define the permanent human-in-the-loop boundary. In the third month, expand branch by branch, gating each branch's rollout on that branch first adopting the unified price book, not the other way around. What should not change in any of this is who signs off on the structural diagnosis: the inspector's judgment about what the house needs is the one part of this workflow that a faster document should make more visible, never more automated.
