JobNimbus Pricing Explained: Tiers, Seats, and What CRM Doesn't Buy

JobNimbus is one of the most common CRMs in residential roofing, and "JobNimbus pricing" is one of the most common searches roofers type at 9pm after a demo. The honest answer up front: JobNimbus does not publish a public rate card. Neither do most CRMs in this trade. Pricing is quoted per company, usually after a call, and it moves with seat count, add-ons and contract length. Anyone who hands you a hard number as fact is guessing.

What we can do is explain the shape of the bill, because the shape is public and it is consistent: a base platform tier plus a per-user charge, with feature gates between tiers. That structure matters more than the exact dollar figure, because it decides what your bill looks like at three users versus ten. And then there is the bigger question this post is really about: once you have paid for the CRM, what have you actually bought? You have bought a place to put leads. You have not bought a single lead, and you have not bought a reason to knock one specific door tomorrow morning.

1. The tier structure: what changes as you move up

Roofing CRMs in the JobNimbus class generally sell in three bands. Names vary, but the pattern does not:

• A starter or core tier. Contact and job management, pipeline stages, basic scheduling, some document storage. Enough to run a small crew that mostly needs one place to track jobs.
• A mid tier. Automation, more custom fields, better reporting, integrations with accounting or estimating tools, sometimes a customer portal.
• An upper tier. Advanced permissions, API access, heavier automation, dedicated onboarding, sometimes multi-location support.

The thing to watch is not the tier name. It is which specific features you need and which tier they sit behind. Roofers consistently report that the jump that hurts is not the base subscription, it is discovering mid-quarter that the automation or integration you assumed was standard is a tier up.

2. The per-seat multiplier is the real bill

This is where the total gets decided, and it is why two roofers can quote wildly different "JobNimbus costs" and both be right.

The model is per user per month. So the arithmetic is simple and unforgiving:

• A 3-person operation (owner, one office/admin, one salesperson) pays roughly three seats plus the base platform. This is usually the cheapest configuration, and it is the one where a CRM genuinely earns its money, because three people can actually keep a shared pipeline clean.
• A 10-person operation (owner, two office, seven sales or production) pays roughly ten seats plus the base, plus whatever tier unlocks the permissions and reporting you need to manage ten people instead of three.

The multiplier effect is the point. If a seat runs somewhere in the range contractors report paying, going from three seats to ten is not a 3x increase in the software line, it is closer to 3x on the seat portion plus a tier upgrade plus the add-ons that only make sense at scale. Onboarding and implementation fees, where they apply, also scale with headcount, because they scale with how many people need training.

A few structural notes worth knowing before you sign:

• Seats are usually named users, not concurrent users. If you have eight people who occasionally need access, you may be paying for eight seats to serve four people's worth of daily use. Ask specifically whether read-only or field-only seats exist at a lower rate.
• Contract length is a lever. Annual commitments commonly price better than month-to-month, but they also lock the seat count in. If you are hiring seasonally, model the annual number at your peak headcount, not your winter headcount.
• Add-ons stack. Payment processing, texting, extra storage, third-party integrations. These are individually small and collectively real.

3. What a CRM budget does not buy you

Here is the part that no pricing page addresses, and it is the reason this post exists.

A CRM is a container. It is very good at what happens after a lead exists: scheduling the inspection, moving the job through stages, generating the estimate, invoicing, keeping the crew on the same page. If your problem is "we lose track of jobs," buy a CRM. That is the correct tool.

But if your problem is "we do not have enough doors to knock," a CRM cannot solve it, at any tier, at any seat count. You can pay for ten seats and still open the app on a Tuesday morning to an empty pipeline. The software will faithfully track nothing.

This is the gap where roofing companies quietly buy two things and think they bought one. They buy the CRM, and then they buy leads from a marketplace to fill it. And that second purchase has a structural problem the first one does not: pay-per-lead marketplaces sell the same lead to multiple contractors. You are paying per lead for a race, and the homeowner filled in a form three days ago and has already taken four calls.

4. Where lead sourcing actually sits in the stack

Draw the stack honestly and it has three layers:

1. Sourcing. Where does a name come from at all?
2. Qualification. Is this roof actually worth a trip, and is there anything forcing a decision on this house now?
3. Execution. Scheduling, estimating, production, invoicing, payment. This is the CRM layer.

Most roofers spend their software budget on layer three and their lead budget on a marketplace that handles layer one badly and layer two not at all. Nobody in that arrangement ever tells you which blocks are worth your morning, or which specific house has a reason to say yes this month.

That is the layer Roofbird occupies, and it is deliberately not a CRM. It is self-serve: you sign up, tell it where you work, and it reads satellite and ground-level Street View imagery to score roofs in minutes. No sales call, no per-lead fee, no shared marketplace.

Concretely, here is what it does that a CRM cannot and a marketplace will not:

• It tells you where to scan before you draw anything. Search a town, suburb or ZIP and it ranks the neighbourhoods in view: housing era, what share of roofs read as weathered, how many homes are actually there counted from building footprints, whether hail has hit in the last 12 months, and how walkable the block is. Scattered acreage on long driveways gets flagged as bad canvassing even under a perfect storm, because a morning is measured in doors per hour. When nothing in view clears the bar, it says so instead of offering you three neighbourhoods to skip.
• It reads every roof from two angles. The top-down tile and a ground-level Street View of the façade get read together into one assessment, which catches side-visible granule loss, algae streaking, curling shingles, patched sections and rusted flashing that a top-down view misses. It also compares the roof against its immediate neighbours: if the houses either side have visibly been re-roofed and this one has not, that gets flagged, because a street where everyone else already went new is the strongest social proof in the trade.
• It separates NEED from NOW. NEED is how badly the roof needs replacing, from condition and roof age read off the shingles. NOW is whether anything is forcing a decision on this house: visible active damage like a tarp or missing shingles, hail damage on this specific roof, a recent purchase, patching already attempted, neighbours who have re-roofed. Neighbourhood hail deliberately does not raise NOW, because every home in the scan shares it and it cannot separate one door from the next. Most homes in a settled neighbourhood honestly have no trigger, and Roofbird says so rather than inventing urgency.

5. The payoff: the homeowner, not just the house

This is the part that makes the whole stack work, and it is where the CRM budget argument lands.

Every lead in Roofbird shows the full property record free, as soon as it is scanned: owner name, whether they live there or it is an absentee or rental owner, estimated market value with a confidence figure, year built, last sale date and price, beds and baths, living square footage, lot size, stories, garage, annual property tax, and mortgage lender. It also estimates owner equity, because equity is what decides whether someone can say yes. Where the deed record cannot support an estimate, it says so instead of guessing.

Only the phone and email sit behind a one-click unlock. Every number is DNC-scrubbed and labelled: "clear" means it was checked against the federal Do Not Call registry and is safe for a manual sales call; "DNC" means do not call it; "verify" means the scrub could not confirm either way, so treat it as unknown. Manual dialling only. No texting, no auto-dialler. And a lookup that finds no contact never costs you a credit.

That is the difference between a container and a reason. A CRM holds the lead you already have. A marketplace rents you a lead four other contractors are calling. Roofbird hands you the address, the roof assessment, the reason to knock this door this week, and the homeowner's own DNC-scrubbed number to call before you drive.

6. Budgeting both layers honestly

If you are pricing out a stack, do it in two lines, not one:

• Line one: execution. Your CRM. Pick the tier that matches your headcount, count seats at peak, and read the feature gates carefully. Expect the per-seat multiplier to dominate.
• Line two: sourcing. This is where Roofbird sits. The free trial is 25 leads and 10 homeowner-contact unlocks, no credit card. Hunter is $199/mo for 500 leads and 50 unlocks. Hunter Pro is $499/mo for 2,000 leads and 150 unlocks, plus data export. Extra contact unlocks are $1 each. Unlimited service areas on paid plans. Flat monthly price, never per lead.

Two things worth knowing about that quota: low-quality roofs are dropped before they reach your list and do not count against your monthly quota, so you are charged for leads worth working rather than everything the scan looked at. And a building anyone has already assessed is never re-assessed from scratch, so re-scanning an area surfaces genuinely new homes instead of the same roofs again.

Next steps

1. Get a real JobNimbus quote for your actual headcount, at your peak season seat count, and ask which features you need sit behind which tier. Do not accept a number without a seat count attached.
2. Write down what that number buys: job tracking, scheduling, estimating, invoicing. All layer three.
3. Then ask the harder question: where do the leads come from, and does anything in your stack tell you which block to work tomorrow and which house has a reason to buy now?
4. If the answer is "a marketplace," run the free Roofbird trial on your own territory. 25 leads, 10 contact unlocks, no credit card. Scan the area you already work and compare what comes back to what you are paying per shared lead.

A CRM is worth its money. It is just not a lead source, and no per-seat structure will ever make it one.

FAQ

Q: How much does JobNimbus cost? A: JobNimbus does not publish a public rate card, so there is no honest single number. Pricing is quoted per company over a call and typically combines a base platform tier with a per-user monthly charge, plus add-ons. The seat count and the tier you need are the two variables that decide your bill, so ask for a quote at your real headcount rather than a generic figure.

Q: Is JobNimbus priced per user or per company? A: The model is a base platform fee plus a per-seat charge, so it is effectively both. That is why a three-person shop and a ten-person shop can quote very different totals for the same product. Going from three seats to ten multiplies the seat portion and often pushes you into a higher tier for permissions, reporting and automation.

Q: Does a roofing CRM generate leads? A: No. A CRM stores, tracks and moves leads through your pipeline after they exist. It is an execution tool. If your bottleneck is not having enough doors to knock, a CRM at any tier will not fix it, because you will be paying for seats to manage an empty pipeline. Sourcing and qualification are a separate layer of the stack.

Q: How does Roofbird fit alongside a CRM like JobNimbus? A: Roofbird sits upstream. It finds and scores roofing leads from satellite and Street View imagery, tells you which neighbourhoods are worth your morning, and gives you the homeowner's DNC-scrubbed phone and email on a one-click unlock. You then push those leads into whatever CRM you already run for scheduling, estimating and invoicing. It replaces the lead marketplace, not the CRM.

Q: Does Roofbird guarantee a sale or predict who will buy? A: No. Roofbird reads roofs from imagery and reports what it finds: condition, estimated roof age, wear signs, a NEED score, a NOW score with a plain-English reason, and the public property record. It surfaces a reason to knock a specific door and the homeowner's contact details. Whether that homeowner buys is up to your pitch and their situation.