Business

One System or Two? Connecting Door Knocking to Production for Roofing Teams

Count the real cost of running roofing sales and production in two systems, then use a handoff checklist that gets every sold job built right.

GameForce Team

One System or Two? Connecting Door Knocking to Production for Roofing Teams title card

Most growing roofing companies end up with two systems: an app the reps knock with and a production system the office builds jobs in. It works, until a detail falls in the gap between them. The color the homeowner picked. The gate code. The skylight the adjuster approved. The promise that the crew would start "early next month."

This guide helps you decide between one system and two by counting what the gap really costs, then gives you a handoff checklist that works either way.

Count what two systems cost you

The cost of two systems is not the second login. It is the retyping, and the mistakes that come with it. Run this count on your last ten sold jobs:

  1. List every field someone typed twice. Homeowner name, address, phone, scope, material, color, claim number, notes.
  2. List every change after the sale. A new start date, an upgraded shingle, a supplement, an access note. Each one has to be updated in both places.
  3. Ask who noticed each change, who updated each system and who told the homeowner.
  4. Mark every job where something went wrong because one system had old information: a wrong color delivered, a crew showing up to a locked gate, a homeowner told two different dates.

Then estimate the office time spent on the double entry in a normal week. Now you have a real number to weigh against the work of moving to one system. If the count is small and nothing went wrong, two systems may be fine. If the same mistakes keep repeating, the gap is costing you jobs and reviews.

The sold job handoff checklist

Whether you run one system or two, a job is ready for production only when these are complete. Print it, or build it into your sold stage.

SectionWhat production needs
HomeownerNames of everyone on the contract, best phone, how they want updates
PropertyAddress, access notes (gate, pets, where to park), HOA approval if needed
ScopeRoof areas, measurements, tear off or overlay, decking language in the contract
MaterialsProduct line, color, and who confirmed the selection with the homeowner
ExtrasGutters, skylights, vents, flashing and anything else that was sold
InsuranceClaim number, adjuster meeting status and the approved scope, if it is a claim job
DocumentsThe signed agreement, current version only, plus photos labeled by area
PromisesAnything the rep said about timing, cleanup or special requests, in plain words
MoneyWhat has been collected and what is due when
Open questionsEach one with an owner and a due date

The "Promises" row matters most. If the rep told the homeowner the crew would protect the garden or start before a family event, production has to know, or the homeowner hears two different stories.

Make production accept the job

A job should not slide into production just because sales marked it sold. Give production an acceptance step: someone reviews the checklist and either accepts the job or sends it back with a specific question.

"Sent back: color not confirmed with the homeowner, due Thursday, owner: office manager" is useful. A job sitting quietly between departments for a week is not. Track how often jobs get sent back and why. The same reason three weeks in a row is a training topic for reps, not a production problem.

Separate facts, promises and open questions

A good job record keeps three things apart:

  • Facts: what is signed and confirmed. "Architectural shingle, color confirmed by homeowner on the call."
  • Promises: what was said but not yet scheduled. "Rep said start in about three weeks."
  • Open questions: what nobody knows yet. "Decking condition unknown until tear off."

Mixing them is how a tentative date becomes a broken promise. "Homeowner asked for next week" is not "crew confirmed for next week."

Give homeowner updates a schedule and an owner

Homeowners call the office when they do not know what is happening. Set a standard update at each stage, and name who sends it:

StageUpdate the homeowner hears
SoldWhat happens next and who will contact them
Permit and materialsThat the job is being prepared, without a promised start date until one is set
ScheduledThe confirmed start date and what to expect on the day
InstallA same day check in from the crew lead or the office
CompleteThe final walkthrough, cleanup, any paperwork and the same review request every customer gets
PaidA thank you and the paid in full receipt

Decide who owns each update, sales or production, before the job is handed off. Otherwise both assume the other one called. Asking for the review at the right moment is its own skill, covered in Reviews After the Install.

Handle changes after the signature

Changes are normal: an upgrade, a supplement on a claim job, a new start date. What breaks jobs is a change that reaches one person and not the others. Use one rule: every change gets recorded in the job record first, with who approved it, and then the homeowner hears it from the update owner.

On claim jobs, keep the weather report, your inspection findings and the insurer's decisions apart. Each one serves a different purpose. How to Find Hail Hit Streets Before You Knock covers the field stage, and Insurance Claims for Roofing and Restoration Contractors covers tracking a claim from the adjuster meeting to the final check.

Test one system or two with the same job

In any demo, bring one job you sold last month and run it through:

  1. The rep marks it sold with the checklist filled in.
  2. Production accepts it, or sends it back with a question.
  3. The homeowner changes the color.
  4. The start date moves a week.
  5. The job finishes, gets invoiced and paid.

At each step, ask both sides what they now believe will happen and whether anyone typed something twice. The setup that gets through all five steps with no retyping and no conflicting answers is the one to choose. The Canvassing App Checklist gives a matching test for the field side, and From Signed to Paid covers the money end.

Sales to production in GameForce

Run sales, operations and fulfillment in one place.

On select plans, sold deals turn into jobs: schedule the crew, track every stage, and let the homeowner watch progress in their own portal.

  • Insurance claims
  • Inspection reports
  • Review management

Send the invoice, record the payment and track your reps' commissions from the same place.

FAQ

Should a roofing company use one system or two?

Count the double entry and the mistakes it causes on your last ten jobs. If both are small, two systems can work. If the same errors keep repeating, one system that carries the job from the knock to the payment is usually worth the move.

What should a sales to production handoff include?

The homeowner's details, access notes, the full scope, materials and color, any insurance claim details, the signed agreement, every promise the rep made, money collected and open questions with owners.

Who should update the homeowner after the sale?

Name an owner for each stage before the handoff. The homeowner should hear from one person at a time, with the latest information.

How do we stop details getting lost between sales and production?

Add an acceptance step, keep facts, promises and open questions separate, and record every change in the job record before anyone tells the homeowner.

Follow a job from sale to paid

Book a demo and bring one job you sold last month, or start a free trial. For the bigger picture, read What a CRM Misses.

Put your next step into practice.

See what a clearer sales day can look like.

Read next