Roofing contractors · CRM
Keep every enquiry, site visit and quotation in one record the whole office can read.
A CRM for a roofing contractor is the single record of each job from first call through site visit, quotation, signature and the roof afterwards. GullySales works on setting up that record in a tool your office will open, with the stages and reminders that move a quotation along.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Last updated 14 Nov 2026.
For roofing contractors
Where it usually goes wrong, and what we would do.
“The job lives in the site engineer's phone”
Measurements, photographs and the owner's remarks sit in a personal WhatsApp and a notebook. When that engineer is on another roof, nobody in the office can answer the owner's second call. A shared record moves those details to where everyone can read them.
“A quotation needs a stage of its own”
A shed job passes through enquiry, visit, measurement, quotation, negotiation, signed and lost. Where stages are not named, a quotation sent looks the same as a job closed, and nobody is accountable for the call that should follow.
“A roof outlasts the sale”
The plant you roofed calls again about a leak, an extension or insulation, which makes a past site the likeliest next enquiry. A record that stops at signature discards the roof type, sheet, date and contact that make that call easy.
“The roofing spreadsheet breaks once three people share it”
One person can run a roofing pipeline in Excel. Add a partner, an estimator and a telecaller, and versions diverge, rows are overwritten and no reminder fires. A CRM keeps the history of who did what and gives each person a task list.
What we do
What we deliver for roofing contractors.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Pipeline stages for roofing jobs
Stages named for how you work: enquiry, visit booked, measured, quotation sent, negotiation, signed, handed over, and lost with a reason.
Result: Every job sits in one stage that you can count.
Fields for the roof
Site address, roof type, area, span, sheet and structure, plus the person who decides and the person who holds the budget.
Result: A repeat call opens with the earlier job already on screen.
Tool choice and setup
A comparison of CRMs in ordinary use in India, such as Zoho CRM, HubSpot or LeadSquared, set against your team size and phones, followed by configuration.
Result: Your team works in a tool they can open on a phone.
Reminders and task lists
A task for every visit due and every quotation sent, assigned to a named person.
Result: Each quotation always carries a next step.
Source and lost-reason tracking
Each enquiry tagged with where it came from, and each lost job with the reason the owner gave.
Result: You can read which sources bring signed jobs.
Import of past owners
Completed jobs loaded from your files, with a note of whether the owner agreed to be contacted.
Result: Past owners can be reached before the rains.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
What a roofing CRM holds for each site and each quotation.
- Roof type and building use
- Filled by the site engineer after the visit. Lets the office see whether the pipeline is leaks, sheds, warehouses or terraces.
- Decision maker and signer
- The estimator records who calls and who signs. Prevents chasing the plant manager when the owner holds the budget.
- Quotation stage and date sent
- Updated by whoever sends the file. Drives the follow-up list and shows quotations that have gone quiet.
- Reason lost
- Entered when the owner says no, for example price, scope, timing, or another roofer. Shows whether the scope explains the price.
- Site address and handover date
- Filled when the job closes. Starts the list of sheds to revisit before the next monsoon.
- Source of the enquiry
- Marked by the person who answered the phone: map, dealer, site board, builder or a previous owner. Shows where the next rupee should go.
Who it is for
This is written for these roofing contractors.
- Metal and colour coated sheet roofing contractors
- PEB and factory shed roofing contractors
- Polycarbonate and skylight roofing installers
- Terrace shed and car park roof installers
- Tile roofing and truss contractors
- Roof insulation and cool roof specialists
- Roof leak repair and maintenance crews
- Structural steel and roofing combined fabricators
- Warehouse and cold storage roofing contractors
Before you decide
When this may not be the right fit.
- The office has one person and the quotations fit in a notebook you already read each morning
- Site engineers will not report back after visits, and a system would be filled only by the desk
- You have not decided who owns the follow-up calls, so a pipeline view would show overdue quotations no one acts on
Before you decide
Agree the work. Know how to judge it.
CRM for roofing contractors: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from roofing contractors. Anything missing is noted in the written scope, with who will supply it.
- Your present spreadsheet or notebook
- Whatever records jobs today, however messy. We need to see it to move it. A photograph of a notebook page is enough if that is what you have. Without it the system starts empty.
- Names and roles of the people using the CRM
- Names and roles of those who will enter or read data. It decides permissions. Include whoever answers the phone, because the first record is made there. Unlisted people end up sharing a login.
- A decision on who owns the data
- The owner or the company, not a single employee. The tool is then opened in the company's name, with the owner as administrator. Settle the account holder before setup so a departure cannot take the records.
- The quotation numbering you use
- Your present numbering and filing of quotations. If quotations are numbered by hand in a register, bring the register so we can match its sequence. It must match the tool, or the records will not agree with paper.
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Trace one signed roof from first call
We pick a recent job and follow it through your office from the first call to the final payment, noting each note, sheet and message and who touched it. You tell us where it nearly slipped. We also ask who holds the file at each point, since that decides whose phone the reminder goes to. The trace gives the stages the system must record.
- 2
Name the stages a roofing job passes
From the trace we write the stages: enquiry, site visit, quotation sent, under discussion, signed, in progress, handed over. You correct the names and add the stage your trade needs. A separate stage for a site visit already done but not yet quoted is added, because that is where jobs wait longest. The stages are agreed before anything is built.
- 3
Set up the fields for the roof
We add fields for roof area, sheet type, structure, site address and handover date, and decide which are required. Your engineer reviews the list. We keep the number of required fields small, because an engineer on a roof will skip a form that asks twenty questions. A field for the next inspection date is added for roofs with a maintenance arrangement. The record then holds what you need for a repair call a year later.
- 4
Load past owners from your register
We clean and import the customer register with each job, roof and year. You check a sample against the files. Jobs with a missing site address or roof type are listed for the office to complete from the old files. Duplicates are merged only with your approval.
- 5
Teach the office on live enquiries
We sit with your office and enter real calls into the tool, set the reminders and show how an engineer can update a job from a phone. You decide who owns the data. We stay until a full working day's enquiries are handled in the tool and nobody reaches for the old notebook.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Is a CRM too heavy for a roofing firm with a small office?
Our engineers will not type into a system. What then?
Who owns the data if we change the tool?
How do we record a repeat owner who comes through a builder?
Our site engineers will not type into a system. What then?
Is a CRM too heavy for a small roofing office?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for roofing contractors
Related work to consider.
Closest to this: leads and follow-up
Also for roofing contractors
Or start from the overview: sales and marketing for roofing contractors.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.