Inside a Bohaus Sprint: A Roofing Company

The situation

The client is an owner-led roofing company doing residential replacements and repairs, much of it insurance work after storms. Three install crews, a repair crew, a couple of sales reps who do inspections, a production manager, and an office manager who handles insurance paperwork and billing. JobNimbus or AccuLynx is the CRM. CompanyCam holds photos. QuickBooks runs the books. Leads come from the website, a phone line, door-knocking and referrals.

When a hailstorm rolls through, the phone lights up. That week decides the season.

What the sprint finds

In Discover, we draw the stack on one page. Every system, and a line wherever information moves between them, marked automatic or manual.

The page tells a clear story. Website leads arrive in an inbox. Phone leads are written on a pad and entered later. Canvassing leads live in a rep's phone. Referral leads come by text to the owner. Only some reach the CRM, and they arrive at different times with different details.

The stack is acting as an org chart nobody drew. Whoever checks the inbox owns web leads. Whoever answers the phone owns those. Reps own their own. After a storm, nobody owns the overflow.

Downstream, inspection photos sit in CompanyCam but are not linked to the job in the CRM until someone does it by hand. Insurance scope documents arrive by email and get saved to a desktop. Supplements depend on the office manager remembering which claim needs one.

In Diagnose, we rank the broken connections. Lead intake to scheduled inspection ranks first, because it is where storm demand is won or lost.

What it builds

In Build, we make the CRM the single home for leads and jobs.

Every lead source feeds it: web forms directly, phone calls through a short intake script, canvassing through a simple mobile form, referrals forwarded from a dedicated number. Each lead gets an owner by rule, territory or rotation, and is offered inspection slots. Leads that do not book get follow-up on a schedule. During a storm surge, the overflow goes to a queue the office manager can see.

CompanyCam projects are created and linked to the CRM job automatically, so inspection photos are on the job before the rep leaves the driveway. Insurance documents emailed to a claims address are attached to the right job.

Each system gets a named owner. The production manager owns the CRM. The office manager owns the claims inbox and the QuickBooks connection. Reps own their own pipeline, but inside the shared system, not their phones.

Hand over

In Hand over, the office manager, production manager and reps learn the new flow. A one-page map of the stack, with owners, goes in the playbook with the intake script and storm-surge rules. The team gets a dashboard of leads by source, inspections booked and contracts signed, plus a roadmap. Supplement tracking is often next.

What changes

After a storm, every lead lands in one place and gets an owner. Inspections are booked while the homeowner is still interested. Photos and insurance documents are on the job, not on someone's phone or desktop. The owner can see the pipeline without asking three people.

The stack is something the company designed, and can keep improving.

What this means for your business

Every business runs on a stack that shapes how work moves, and most were never designed. Draw yours on a page. Mark the manual transfers, the duplicate data and the systems without an owner. Fix the most expensive connection first.

A roofer's is storm leads. An electrician's might be estimates. A garage door company's might be parts on trucks.

A Bohaus Sprint starts with that map, then builds one live system on top. Six weeks, fixed scope, and a team trained to run it.