Roofing CRM Multi Location: What Changes at 5, 10 and 15 Offices
What breaks first as a roofing company adds offices, and what a roofing CRM needs to handle location reporting, permissions and rep leaderboards.
What changes in a roofing CRM when a company goes multi location? The CRM has to limit each person to the offices they work in, report by location instead of only company wide, and tie sales goals and rep leaderboards to each market. Trussi does this with location based access, location filters on reporting, and goals set per location and per rep, on one plan at $40 per user per month.
Why a roofing CRM multi location setup is a different job than one office
One office runs on proximity. The owner knows which crew is behind, which rep is soft and which adjuster is slow, because all of it happens within earshot. Add a second market and the first thing to go is hearing everything. Add a fifth and the owner is reading a report somebody else assembled. By the time a company is running ten or fifteen offices, the CRM is no longer a place to keep records. It is the only place the company can see itself.
Treat the numbers 5, 10 and 15 in this guide as rules of thumb about where the work changes shape, not as thresholds from a study. Your mix of storm markets, retail markets and branch managers will move the lines. What does not move is the order in which things break: visibility first, then permissions, then accountability.
Around five offices: visibility breaks first
At five offices the owner still knows every branch manager by first name and still picks up the phone. What fails is the report. The monthly number arrives from a spreadsheet each branch builds a little differently, and the review meeting turns into an argument about whose definition of a lead or a sale is right instead of a conversation about the market.
The fix is one pipeline with the location on every job. In Trussi, locations are set up on the Locations screen, and much of what a person can see is scoped by the locations they are attached to. The pipeline counts on the home dashboard follow that scope: a location restricted role sees the stages and unassigned leads it is allowed to see, and an admin sees every job in the account. The Sales Leaderboard has a location filter, so the same board answers how the whole company is doing and how one market is doing without anybody exporting a thing.
Set the locations up carefully on day one, because a lot hangs off them. A lead's location decides who is offered the lead and which branch manager is told when it is flagged for follow up. Each location can also hold its own company documents, so every office has its own warranties, licences and insurance certificates ready to attach to an email or a supplement.
Around ten offices: permissions become the real work
Somewhere near ten offices the question stops being who can see the numbers and becomes who can change things. Roofing has plenty of ways to hurt itself with a stage change. Somebody pushes a job to production before the deposit clears, or a rep covering a storm in another market opens jobs that belong to a different branch.
Trussi ships seven roles: Admin, Account Admin, Back Office, Branch Manager, PM, Crew Lead and Subcontractor. An account can also build custom roles on top of any of them, and which capabilities each role holds is editable per account under Settings and Permissions, so two companies can give the same role different access. Because users are scoped to their locations, moving somebody between locations changes which projects they can open. That is the point of it, and it is worth knowing before you move a rep for a storm.
Stage control matters as much as screen access. By default only Account Admin and Back Office can move a job past the Lead stage, and each stage has its own grid for who can move a job forward, move it back or set a sub stage. At ten offices you want that grid set on purpose, not inherited.
People move too. A branch gets bought, a few estimators become branch managers on the same Monday, a season ends and someone leaves. Trussi lets you change several roles at once and spells out every change before it saves, and archiving a person takes them off the team list without deleting the jobs they are named on. We wrote that up in run your team list in one pass.
Lead flow changes at this size too. With routing switched on, a lead that arrives without a location goes to the nearest one, worked out from the customer's own geocoded address and not from a ZIP code table. If the address never located, Trussi falls back to the customer's state, but only when exactly one of your locations sits in that state. With two branches in the same state it will not guess. Offering can then rotate the lead through the project managers and branch managers you have listed for that location, one hour to respond each, with a daily cap per person. Both switches are off until an account admin turns them on. Behind that sits the intelligence pillar: Trussi scores 1,500+ leads a month with patented lead scoring, so the lead that reaches the rotation already carries a ranking.
Around fifteen offices: the leaderboard and the goal start to matter
At fifteen offices the company number hides more than it shows. One market can be slipping behind a strong one, and a leaderboard that mixes storm markets with steady ones is a recipe for the wrong argument. Two things have to be true for the board to be trusted: everybody knows what it counts, and the goals behind it fit each market.
The Sales Leaderboard ranks whoever a job is assigned to by dollar value, not by lead count or close rate, and it has a toggle between two numbers that are not the same. Signed totals the approved job value of jobs that reached your Won stage for the first time in the period. Collected totals payments actually recorded in the period, whatever stage the job is in now. A job signed last quarter that collects this month counts toward Collected this month. The presets are This Month, This Quarter and This Year, and you can narrow the board to one location or leave it on all locations you have access to.
Goals are set per year, and per location or per rep, not once for the whole company. Pick annual, and the leaderboard prorates the target to the period you are viewing. Pick monthly, and you can set twelve separate numbers, which is the mode for a storm market that spikes or a new branch that ramps. The company annual figure is calculated from the location goals, so raising a market raises the company number. A rep with no goal shows a dash, not a zero, so a blank means nobody set a goal, not that nobody sold anything.
Above the leaderboard sits the Executive area: sales, cash flow, collections and team views, each separately permissioned, so seeing one does not mean seeing the others. The dashboards report revenue and job profitability by market, so a market with strong revenue and thin margin shows up as exactly that. That is what broad operations from first knock to final invoice buys you at this size: the sale, the build and the collection all sit on the same job record, so the numbers by market are not stitched together by hand.
Six questions to put to any roofing CRM before you roll it across offices
The wider checklist is in how to choose a roofing CRM. For a company with several offices, these six are the ones that separate a tool built for one shop from one that holds up across many.
- Can you limit a person to specific locations, and does every list, dashboard count and activity feed respect it? In Trussi the pipeline counts, the Latest Activity feed and the AI assistant all follow the same location scope.
- Can sales goals be set per location and per rep, by the year or by the month?
- Does the leaderboard say what it counts, and can you tell signed work from collected cash?
- When a lead arrives with no location, what happens when two branches share a state?
- Who can move a job between stages, and can you change that stage by stage instead of once for the whole company?
- Can you move a group of people to a new role in one pass and see what will change before it saves?
What it looks like at scale
Trussi is live for a $70M roofing operator across 18+ locations. It deploys in 17 days, and 176 project managers are in the system today. We say that plainly because multi location is where a roofing CRM either holds up or does not, and you should be able to ask a vendor who runs on it every day.
The price does not climb with your office count. It is one plan at $40 per user per month, so the bill follows your headcount, and you can read it on the pricing page. That $40 is a deliberate strategy to lead this market, not a discount, and it sits beside the other things we hold ourselves to: broad operations from first knock to final invoice, intelligence in the pipeline, white glove onboarding and transparent pricing.
RoofCON week, Oklahoma City
RoofCON runs November 10 to 12 at the Oklahoma City Convention Center, and we will be there. If you run several offices and want to walk through how your locations, roles and goals would be set up, book a time at trussi.ai/contact and we will confirm where to meet. Bring your org chart and a list of your locations, and we will set one up on screen together.
If you will not be in Oklahoma City, book a demo at trussi.ai/contact so your team is live before spring storms. Bring the same org chart and location list to that call.