Role-Priced Seats: Total a Roofing CRM by Crew Mix, Not Headcount

Most per-seat math is simple: one rate times everyone who logs in. Role-priced seats break that shortcut. Under this model, the price of a login depends on what kind of user it is — an admin or owner seat costs one amount, a sales or office seat another, and a field seat a third — often on top of a base platform fee. Two roofing companies with exactly the same headcount can therefore pay noticeably different totals, and the same company can watch its bill change without hiring anyone, just by reclassifying who does what. If a quote prices seats by role, total it by crew mix, not by headcount — or you are not looking at your price.

How role pricing is put together

A role-priced quote usually has two layers. The first is a base or account fee for the platform itself. The second is the seat layer: each person priced at the rate for their assigned role. The vendor, not you, defines what counts as which role — and the vendor's labels rarely match your job titles exactly. Is the owner who also sells an admin or a sales seat? Is an estimator sales, office, or admin? Is a production manager who uploads photos and moves stages a field seat or something more expensive? Every person who wears two hats is a classification question, and each answer moves the total. That is why the current pricing comparisons that rank for "roofing crm cost" no longer quote a single per-user rate: they itemize the base plus a different rate per role, then total a named crew — one admin, so many sales, so many field — before they annualize it, the same structure our first-year vs. steady-state cost guide uses for its formula.

Worked math: three 5-person crews, three different bills

Run three crews of five through the same illustrative role rates. The rates below — $80 for an admin seat, $60 for a sales or office seat, and $40 for a field seat — are round example numbers chosen to make the mix effect visible. They are not any vendor's price; vendors that price by role set their own rates and several do not publish them at all, so substitute the rates from your own written quote the same way.

Same headcount, same rates, a $40-a-month spread — $480 a year — decided entirely by mix. Now add a base fee on top, as many role-priced quotes do: at an illustrative $200-a-month base, those crews pay $500, $480, and $460. The base dilutes the difference; it does not erase it. And compare all three against the single-rate version in our roofing CRM cost guide — five people at a flat illustrative $50 a user is $250 a month regardless of who does what — to see what the role layer itself adds: not just a higher total for most mixes, but a total you cannot predict from a headcount.

Growth changes the mix before it changes the headcount

The mix effect compounds when you hire, because roofing hires are never evenly spread across roles. Before storm season you might add two field seats and one sales seat: at the illustrative rates that is $40 + $40 + $60 — $140 a month more. A different growth step — a second office admin and two more reps — is $80 + $60 + $60, or $200 a month more, for the same three hires. Our roofing CRM pricing tiers vs. flat pricing breakdown already advises forecasting headcount 12 months out; under role pricing you have to forecast the mix 12 months out — which roles you will add, in which order — and price that crew, not today's. You can run the single-rate version of that forecast in our roofing CRM cost calculator; for a role-priced quote, run the calculator's total as a floor and then re-total it role by role from the quote itself.

The classification questions to settle in writing

• What exactly defines each priced role — the permissions the login gets, the features it can use, or simply the label the vendor assigns it?
• Which role covers the people who wear two hats in a small company: the owner who sells, the estimator who also runs production, the office manager who closes the books?
• Is there a base fee, and does it include any seats — or is every login priced on top of it?
• When someone's role changes mid-contract or mid-month, when does the new rate apply, and is the change prorated?
• How are seasonal help, subcontractors, and view-only logins priced — at the field rate, at a lower rate, or not at all?
• Can a seat be downgraded to a cheaper role as easily as it can be upgraded, and who has to remember to ask?
• Does choosing a cheaper role for someone remove tools they actually need — photo upload, stage moves, estimate access — or only admin functions they never touch?

Get the answers against your actual named crew list, in writing, before you sign. A quote priced on an assumed mix — "five users" with no roles named — is not a quote for your company; it is a quote for a company shaped like the vendor's example.

The behaviour role pricing quietly creates

Any model that prices logins differently invites the same two workarounds, and both cost more than the seat saved. The first is misclassification: putting a person in the cheapest role that technically fits, then discovering the limited login cannot do a task their week requires — so the work moves back to texts, a notebook, or someone else's account, and the job record goes partial. The second is sharing the expensive login: if the admin seat costs the most, the admin password gets shared the widest, which breaks exactly the accountability and same-day offboarding discipline our guide to CRM access and offboarding sets out — one login per person, role matched to the job, access removed the day someone leaves. Neither workaround is dishonesty; both are a pricing model pushing against how a small crew actually works. Count that friction as part of the quote, the same way you count seat rationing itself.

Pricing roles are not permission roles

Keep two different ideas separate, because vendors use the same word for both. Permission roles decide what a person can see and change — a genuine access control you want, covered in the offboarding guide above. Pricing roles decide what that person's login costs. In GableFlow the two are deliberately unlinked: team roles — owner, admin, manager, and user — control who can see and change what on a job, and they have no price at all. You assign the role a person needs to do their work, and the bill does not move. In a role-priced system, every permission decision is also a pricing decision, and that is the pressure that produces the workarounds above.

How to total a role-priced quote fairly

• List every person who will log in over the next 12 months by name, with the role the vendor would assign them — not just a headcount
• Multiply each group by its quoted rate, add the base fee, and annualize the result before comparing it with anything
• Re-run the same list at your storm-season crew mix, because that is the most expensive version of your year
• Add the usage layer that sits outside seats — measurement reports, texting, and processing — using our roofing CRM add-on audit as the checklist
• Divide the annual total by closed jobs if you want the unit view, using the method in what a roofing CRM costs per signed job
• Finally, compare the total against a published flat price you can read without a sales call — totals against totals, not a starting rate against a total

Where GableFlow fits

GableFlow has no seat layer to total. It is $40 a month flat for the whole company — $480 a year — with every feature included, unlimited seats, and no per-seat fees, whatever the crew mix: the owner, the office, the reps, and the field all log in at the same zero marginal cost, and a storm-season hire changes the workload, not the bill. The product itself is the core loop a small roofing and storm-restoration company runs on: the six-stage pipeline (Lead → Prospect → Approved → Completed → Invoiced → Closed), branded estimates, photo reports, invoices and payments, and team roles for owner, admin, manager, and user — roles that govern access only, never price. A 7-day free trial lets you put your actual crew, in their actual roles, on one real job and judge the record they produce. See GableFlow's features for how those roles and the pipeline work in practice, or check the flat $40/month pricing itself.