Roofing contractors · Unsigned proposalsUpdated Sep 22, 2026

Roofing Proposal Follow-Up Software

A roofing proposal is not finished when the PDF is sent. It is finished when the owner either signs, asks a real objection, or ages out of the sales process. Most roofing CRMs treat that middle period like a note field. That is where the money leaks.

Book a Process Automation Audit → All solutions

The position

The follow-up problem is rarely a texting problem. It is a state problem: the system has to know which roof was measured, which proposal tier was opened, what milestone the job is in, and when the next action is justified.

Mechanism

proposal state machine

We model each proposal as a living sales object instead of a file attachment. The state machine decides what should happen next, and the CRM becomes the place the team sees it rather than the place the logic has to live.

Capture the roof and customer once

The lead, property, satellite measurement and customer record share one identity, so follow-up is tied to the actual roof instead of a disconnected contact note.

Generate the proposal from structured data

Good, better and best tiers are derived from the measured roof and selected options. The proposal is no longer a static document the system forgets after sending.

Track the unsigned state explicitly

A proposal that is opened but unsigned enters its own state with a timer, owner and next action. That state can be reported on, reassigned and resolved.

Push milestones back to the CRM

The CRM still shows the pipeline, but stage changes come from the source of truth. Sales sees what happened without rebuilding the workflow by hand.

Why generic CRM follow-up misses the point

A generic CRM can remind a rep to call someone. That is useful, but it does not answer the operational question: what exactly is the rep following up on? In roofing, the answer depends on the measured roof, the proposal tier, the customer's objections and the job's stage.

When those facts live in separate tools, automation becomes blunt. Everyone gets the same nudge because the system cannot see the difference between a price objection, a no-show appointment and a homeowner who opened the proposal twice but has not signed.

The better build is not more messages. It is one object that carries the roof, proposal and pipeline state together, then lets the follow-up logic read that object before it acts.

The mechanism matters more than the message

Owners usually ask for better follow-up copy first. Copy helps, but copy cannot fix a system that does not know what happened. If the sales record cannot tell whether a proposal is unsigned, expired, revised or waiting on production, the best message in the world is still guessing.

That is why we start with the proposal state machine. Each state has a small number of valid next moves. A signed proposal exits sales. An unsigned proposal gets a timed sequence. A revised proposal resets the clock. A production handoff stops the sales reminders entirely.

The result feels simple to the team because the complexity is below the surface. Reps see the next action. The owner sees the pipeline. The customer hears from the company at the right moment.

Case File · Residential Roofing

They ran on paper. We rebuilt everything.

Good People Roofing moved from hand-typed quotes and forgotten follow-ups to a connected sales-ops platform: satellite roof measurement, AI-built tiered proposals, self-running follow-up and one command center from lead to signed roof.

Satellite roof measure
AI-built proposals
Self-running follow-up
14-day unsigned-proposal follow-up

Read the case file →

Next clicks

Where this fits in the site

Roofing contractors

The industry page covering roof measurement, proposals and the sales-to-production handoff.

Open

Process automation software

The neutral solution spoke for turning manual follow-up and handoffs into owned software.

Open

Good People Roofing case file

The public build this page is grounded in.

Open

FAQ

Is this a replacement for JobNimbus, AccuLynx or another roofing CRM?

Not automatically. If your CRM already handles the pipeline well, we can build the proposal and follow-up layer around it and push stage changes back. Replacement only makes sense when the current system is the bottleneck.

Can follow-up stop when a proposal is signed?

Yes. That is the point of modelling proposal state directly. Signed, revised, expired and production handoff states can all stop or change the automation without a rep remembering to update a separate list.

Does the system need satellite roof measurement?

No, but it is often the cleanest way to make proposals structured from the start. The important part is that proposal data is readable by the system rather than trapped in a file.

Build around the process

If the bottleneck is real, the software should name it.

The audit maps the process, the current tools, and the first system worth owning.

Book a Process Automation Audit →

Why generic CRM follow-up misses the point

The better build is not more messages. It is one object that carries the roof, proposal and pipeline state together, then lets the follow-up logic read that object before it acts.

The mechanism matters more than the message

The result feels simple to the team because the complexity is below the surface. Reps see the next action. The owner sees the pipeline. The customer hears from the company at the right moment.

They ran on paper. We rebuilt everything.

Satellite roof measure

AI-built proposals

Self-running follow-up

14-day unsigned-proposal follow-up

Read the case file →