Foundation repair is an inspection-to-proposal business

the conversion window nobody instruments

A residential structural repair company lives on a simple sequence: a homeowner calls, an inspector visits, a proposal is presented, and some percentage sign. Every operator in this vertical measures crew productivity and job margin closely, because those are visible in the field. Far fewer measure the inspection-to-proposal window with the same rigour, and that window decides more revenue than crew efficiency ever will.

The reasons are practical. Inspections run two to three hours, produce photographs, measurements, moisture readings and a diagnosis, and the proposal is often built afterward in an office by someone reconstructing what the inspector saw. Same-day presentation converts materially better than next-week presentation in almost every home-services category, and the gap between them is administrative, not diagnostic.

where agents fit the workflow

The obvious application is proposal assembly: convert inspection notes, photographs, and measurements into a scoped, priced, homeowner-readable proposal before the inspector leaves the driveway. The diagnosis stays with the inspector, who is a trained professional making a structural judgment. The document assembly, product selection against the diagnosis, warranty language, and financing options are mechanical and slow.

The second application is the follow-up sequence. Unsold inspections are the largest asset most of these companies do not manage. A homeowner who did not sign in week one is not a lost lead; they are a lead with an unresolved objection, usually price or urgency. Systematic, personalised follow-up against the specific diagnosis in their file — not a generic drip campaign — recovers a meaningful share of that population.

the multi-branch complication

At one location, this is a coaching problem. Across thirty branches acquired over a decade, it is a data problem: different inspection forms, different pricing sheets, different CRM configurations, and no consistent definition of a qualified inspection. Any AI capability deployed on top of that inconsistency will produce thirty different answers and be blamed for the underlying variance.

Which is the real sequencing lesson for this vertical. Standardise the inspection record first — the same fields, the same diagnosis taxonomy, the same photo protocol at every branch — and the automation becomes straightforward. Skip it, and you will spend the program budget discovering that your branches were never running the same business.

the numbers that actually run the business

Pull the funnel apart and most owners are surprised by where the volume disappears. Roughly a third of scheduled inspections no-show or reschedule before the inspector arrives. Of the ones completed, same-day proposals close at close to double the rate of proposals delivered more than forty-eight hours later, and the gap widens further past a week. Financing applications submitted during the inspection convert at a materially higher rate than financing offered by phone the next day, because the homeowner is still standing in the space that scared them into calling in the first place. None of these numbers require a new sales process to fix. They require the paperwork to move at the speed the homeowner's attention actually moves.

Set against that, the average branch tracks leads generated, inspections run, and jobs sold — three points on a line with two enormous, unmeasured gaps between them. The gap between inspection scheduled and inspection completed is a logistics and reminder problem. The gap between inspection completed and proposal delivered is the one that costs the most money and gets the least attention, because it happens after hours, off the clock, in an inspector's truck or kitchen table at 9pm.

what changes when the proposal leaves with the inspector

Move proposal assembly into the visit itself and three things happen that operators do not fully anticipate. First, close rate moves, predictably, in the direction the funnel numbers already predicted — this is the easy win and the one that gets the project funded. Second, pricing discipline becomes visible for the first time, because a proposal generated from one price book in real time exposes the inspector who has been quietly discounting to close, something a three-day-old PDF never revealed. Third, inspector retention improves, because the two to three hours of evening paperwork per inspection was quietly the least enjoyable part of a job people otherwise like, and giving it back changes how long good inspectors stay.

measuring it and rolling it out over ninety days

The metric that matters is time from inspection completion to proposal delivered, tracked in minutes, not days, alongside same-visit close rate and financing attach rate. In the first thirty days, instrument the current state honestly — most branches have never measured this interval and the baseline itself is informative. In the next thirty, pilot proposal assembly on two or three branches with a single, unified price book and diagnosis taxonomy, because rolling this out on top of inconsistent branch data reproduces the multi-branch problem inside the pilot. In the final thirty, expand to the rest of the network only after the pilot branches show the close-rate and pricing-consistency effect holding, and use the pilot's exception cases — the proposals that needed an engineer, a structural judgment, or a manual override — to define what stays with a human permanently. The goal at the end of ninety days is not a faster document. It is a business that finally knows, in real numbers, what its own inspection-to-proposal window has been costing it for years.