CRM and Job Management
CRM Management for roofing contractors
The question you cannot answer today was decided months ago, by somebody quietly choosing not to capture something.
A system built around real questions
Fields that earn their place, because somebody can name the question each one answers. Everything else comes out — an unused field is not neutral, it is a small tax on every person who scrolls past it.
Permissions that follow what a person does rather than how senior they are. That distinction sounds pedantic until somebody edits a record they did not understand, or cannot see one they needed.
And the configuration written down with its reasoning. Not a manual — a record of why it is like this, so the next change is made by somebody who knows what depends on what.
You cannot ask a question backwards
Nearly every complaint about a CRM turns out to be a complaint about a decision made when it was set up. Where does the work come from. Which estimator is losing which kind of job. How long anything takes. These arrive months later as reasonable questions and are, at that point, unanswerable — not because the system is bad but because the answer was never captured.
This is what makes configuration a foresight problem rather than a tidying one. Almost everything else in a back office can be caught up: a ledger can be brought current, a file can be assembled after the fact. History cannot. If nobody recorded a reason at the moment somebody knew it, that reason is gone, and no diligence now recovers it.
The pressure runs the other way too, which is why systems drift toward bloat. Every request to add a field is individually sensible, nobody counts the cost, and eventually there are forty of them and the ones that matter are lost among the ones that do not. A field that is usually blank teaches everybody that blank is acceptable, and that lesson spreads to the fields you actually needed.
So the work is mostly subtraction and sequence: fewer things, asked at the moment somebody genuinely knows the answer. That is a duller description than most people expect and it is where the leverage sits.
What a good configuration can survive
There is a practical test for whether a setup will hold, and it is not whether it looks tidy today. It is whether it survives the three things that reliably happen: somebody leaves, the business starts doing something new, and a question nobody anticipated gets asked.
A configuration survives a departure if the reasoning is written down rather than held by the person who built it. It survives a change in the business if the fields describe what is true about work rather than mirroring one team’s current process. And it survives a new question only if enough was captured at the time — which is the part that cannot be retrofitted and is therefore the only part worth being conservative about.
We work inside whatever platform you already run. Roofing companies mostly use JobNimbus, AccuLynx, ServiceTitan, Jobber or Buildertrend, and the principles here are the same in all of them because they are about what your business needs to answer rather than about any product’s features. Orders, access and configuration all happen in your own account at your direction; there is no arrangement of any kind between this brand and any platform, and no claim to authorised or privileged access.
Roofing Back Office is not affiliated with, endorsed by, or certified by any software vendor named on this site. All product names and trademarks are the property of their respective owners.
The layer everything else in the department sits on
This desk sits inside CRM and Job Management, which owns the department boundary — including how customer information is held and where administering a system stops short of determining any obligation about that data. That is set out there rather than repeated here. What is particular to this page is that it is upstream of the rest: every other function in the department works inside whatever this one decided.
What owners ask about their own system
Our CRM is full of fields nobody fills in. Is that a training problem?
Almost never. A field that goes unfilled is usually one nobody could answer at the moment it was asked for, or one whose answer changes nothing downstream. People are quite good at working out which of those they are looking at. The fix is to remove the field or move it to the point in the process where somebody actually knows, not to ask harder.
What do you actually change?
What the system captures, who can see and edit it, and where in the process each thing is asked for. Then we write down why, which is the part that is almost always missing. A configuration nobody documented is one the next person will either be afraid to touch or will change without knowing what depended on it.
Do you tell us which CRM to use?
No. Which platform a roofing company runs on is a commercial decision with switching costs attached, and it depends on things we have no view of. We work inside whatever you already use — JobNimbus, AccuLynx, ServiceTitan, Jobber, Buildertrend or something else — in your own account, at your direction. We are not affiliated with, endorsed by or authorised by any of them.
Why does this matter more than just using the thing?
Because a question you cannot answer today was decided months ago by somebody choosing not to capture something. If nobody recorded why a job was lost, no amount of diligence now produces that history. Configuration is the only part of this that has to be got right in advance, which is why it gets a page of its own.
We have three people who all set it up differently. Where do we start?
With what the business needs to be able to ask, written as questions rather than as fields. Most disagreements about configuration dissolve once the question is on the table, because it turns out two people were solving different problems. What survives that exercise is a much shorter list than anybody expected.
Do you need admin access to our system?
We work at whatever level of access you grant, in your own account, and we make no claim to authorised or privileged access to any platform. What we would ask for is enough to make the changes you have agreed and to see the effect of them; anything beyond that is yours to withhold, and a good configuration is one you can audit yourself afterwards.
Configuring a system is not a regulated act
Nothing on this page rests on a published rule, because none governs how a company chooses to arrange its own system of record. Saying that is better than borrowing a rule written for something else. Configuring and maintaining a system of record is not itself regulated. The DATA held in it is, and that axis belongs to the crm-job-management department page, which argues it from the safeguards and breach-notice rules.
What it is held to instead: The system answers the questions the business actually asks of it, rather than the questions it was configured for.
Where the regulated part of this subject lives: the crm-job-management department page.
Name a question your system cannot answer
If one comes to mind immediately, the field that would have held it was decided against at setup, and that is fixable going forward.