JobProgress vs JobNimbus: Which Fits Roofers (2026)

Pick the system that holds the job

A roofing or restoration owner who searches this comparison is close to signing. The estimate has to come back signed, the crew has to get a date, and the retail invoice or the insurance file has to reach the books without someone typing it twice. JobProgress and JobNimbus both claim that path. They are not the same company, and one name in the search is no longer the name on the order form.

JobProgress is the earlier name of Leap's contractor CRM, and JobNimbus is a separate board-based CRM sold to roofing and exterior contractors. TL;DR: choose the Leap CRM when you need a public seat price and you can step up to the multi-user plan for production rules; choose JobNimbus when the office runs on boards and storm-file tools and can wait for a written quote.

Key Takeaways

• Leap acquired JobProgress on March 10, 2022, and sells the CRM under the Leap name, while subcontractor help still points crews at the old JobProgress web app.

• The Essential plan on Leap is $79 per month for one user. The Team plan starts at $298 per month for the first user, and each added user is $99 per month.

• JobNimbus marks every plan Quote-based and publishes caps instead, including 3 users and 10 automations on Essentials and 100 automations on Premium.

• Stage locking and automated production follow-up are not included on the one-user Essential plan.

• Six people on the Team plan list at $793 per month, or $9,516 over 12 months, using only those published rates.

• A person still has to approve a homeowner text or a bookkeeper export when the status payload is incomplete.

The name on the contract changed

On March 10, 2022, Leap acquired JobProgress. Combined reach then: more than 2,400 according to PR Newswire (2022). The release described one platform for CRM, project management, and in-home sales, and it named Nexa Equity as the majority investor then. Use that headcount as a 2022 figure. It is not a current customer count.

JobProgress base: more than 1,700 according to PR Newswire (2022), and the same release said Leap then served more than 700 home contracting businesses. Leap's help still sends unpaid subcontractors to the old JobProgress web address rather than to a phone app. Read that page before you print a training bookmark: subcontractor access in Leap CRM. If a login, an invoice, or a deck still says JobProgress, ask whether the seat is the current Leap CRM, the separate SalesPro selling app, or a legacy user who has not moved. This guide prices the CRM plans Leap states in public. It does not fold a second product's fee into that number.

Who this is for

This is for an owner or office manager at a roofing or restoration company who will pick soon. You already know the office needs a home for the lead, the estimate, the crew date, and the invoice. You are deciding whether the CRM formerly sold as JobProgress, now sold as Leap, or JobNimbus, matches how a job already moves across your desk. Retail reroofs and carrier files can share one coordinator, and that split belongs in the demo.

Red flags: you only need aerial measurements and not a job record; you will not sign until a dollar amount is printed on a public page; you need production automation while staying on a one-user seat. The first flag is a measuring-tool purchase, and the closer article is the Roofr and JobNimbus comparison. The second flag means a JobNimbus decision cannot be finished from the website. The third flag means the one-user Leap plan will feel empty in week one.

How we evaluated these tools

The weights are a buying agenda, not a lab score. Nothing here was timed in a yard, and no rank was invented. A figure appears only when a page opened for this article carried it. Published price carries 20% because an owner this close to a signature has to budget seats before the call. Estimating and production each carry 20% because those are the two reasons the search was typed. Measurement and storm files carry 15%, the path into the books carries 15%, and the admin weight of automation caps carries 10%. The points column repeats the weight so your own demo can be scored later. It is not a score assigned to either vendor.

A retail crew can let estimating and production decide the demo. A restoration office can let the storm-file row outweigh a faster proposal screen, because a file that never returns from the carrier does not need a prettier cover page. Write pass or fail in the margin after you watch your own statuses. Do not borrow a winner from a vendor's comparison chart.

Side-by-side on the decisions that move a job

The matrix stays on public claims. A named partner is a partner a vendor page actually lists. A blank is silence, not proof that a feature is absent and not proof that it exists.

The dollar cells belong to the Leap CRM an owner still looks up under the old name. They are spelled out again in the pricing section. JobNimbus's help catalog is where Xactimate, HailTrace, EagleView, and Hover show up by name, which matters when the adjuster's file is the scope. Leap's install pages describe measurements, supplier ordering, and crew dates more than they name an insurance-estimating brand on the pages checked here. If claims handling is the whole argument, read JobNimbus and AccuLynx for roofing companies and AccuLynx alternatives for roofing companies before you treat either CRM as a claims desk.

The kitchen-table document is a related choice, not the same choice. If the objection is the proposal itself, use proposal software for roofing companies, then check whether the signed total returns to the job without a download and a retype.

What you can budget before a sales call

Pricing checked October 10, 2026. Essential price: $79 per month according to Leap (2024). Team starting price: $298 per month comes from that same FAQ, where each added user is $99 per month and production automation is not on the Essential plan. An August 11, 2026 Leap comparison says the Team plan includes the first user in its starting price and states no added fees for add-ons or upgrades. Listed trial length: 14 days according to Roofing Software Guide (2026), which also lists no free Leap plan.

The next table is list-price arithmetic on those Team rates. It is not a discounted quote.

The one-user plan stays $79 per month and is not the base of that table. Multiplying $79 by headcount would invent a seat fee that is not published for Essential. Some older Leap pages still show different bundle math, including a three-user figure that does not match the August 2026 comparison. Match the order form to the $298 and $99 rates before the number goes into a budget.

Premium automation cap: 100 automations according to JobNimbus (2026). The same page caps Essentials at 3 users, 3 boards, 10 automations, and 2 integrations, caps Pro at 10 users, 5 boards, 30 automations, and 5 integrations, caps Premium at 19 users with unlimited boards, and lists Enterprise at 20+ users with unlimited automations and integrations. Multi-location is unsupported on Essentials, up to 2 locations on Pro, and up to 5 on Premium. One grid says Pro integrations are a max of 5 and another shows 5+, so the quote should name the count. Every button says Request pricing. The page says setup fees are not required, monthly or annual terms exist, and a 14-day trial is offered with no credit card required. An FAQ on that page also describes an account price plus role-based pricing for admin, sales, and field seats. Ask which model the quote uses, because the cards and the FAQ are not the same sentence.

Contacts, estimates, documents, eSign, reports, invoices, financing, supplier links, QuickBooks, and payments are described as unlimited on every package. Marketing and texting bundles are separate add-ons on a request path. Automated texts depend on the Engage texting tool being part of the subscription. No dollar figure is printed here for that vendor because its site does not print one.

The handoff where files go quiet

The subscription is rarely the costly hour. The costly hour is the status change that nobody turns into the next artifact. A supplement note, a material order, or a crew text sits until the owner finds it at night. Both products can store the job. The open question is what happens after the status, when a person or a second system has to act.

A proposed workflow from US Tech Automations can subscribe to a JobNimbus webhook, read status_name, and open an internal task when that status matches the column your office uses for a supplement or a material order. The output is the review task, not a text to the homeowner. Prerequisites are an API key, a webhook address you control, and the status names from your own account, because those names are configured per company. The automation help states that custom fields are not included on webhook actions, so a total stored only in a custom field will not arrive and a person still opens the job. Treat this as a configurable design with a required human review. It is not a live install and it is not a measured time cut. The field list is on the JobNimbus webhook actions page.

A second proposed US Tech Automations workflow covers the sold job that still has to become an invoice on the Leap side. The trigger is a stage change on the Team plan. The action pulls the job with the API token from developer settings and parks a draft. The output is a held export. QuickBooks receives a record only after the bookkeeper accepts the customer match and the amount. Prerequisites are that token, the match rule, and a person who clears the queue. If the only need is an email when the stage moves, the CRM's own follow-up may be enough and the extra layer should stay off. A measure order has the same shape of pause. Sending a JobNimbus job to EagleView is the narrow version: the report comes back, and a person confirms squares before the estimate changes.

A six-person list-price month

Picture a six-person roofing and restoration office pricing the year before any sales call. The first user on the Team plan is $298 per month, and each of the other five users is $99, which comes to $495, so the list total is $793 per month and $9,516 across 12 months. That total is arithmetic on the published Team rates, not a negotiated invoice. The same six people fit inside a Pro user cap of 10 and do not fit inside an Essentials cap of 3, and JobNimbus stays Quote-based until a rep sends numbers. Default API page: 1,000 records according to JobNimbus (2026), and those docs default the sort to date_created, so the office can list the oldest open jobs first. The sort shows which files have been waiting. It does not price the seat.

Leap, the product JobProgress became

The Leap CRM record runs from the lead through the appointment, the estimate, production stages, and the invoice. Public notes on the one-user plan include lead intake, scheduling, ready-made workflows, tasks, digital estimates, and a price library. The production FAQ draws a hard line at stage progression, stage locking, and automated task or email follow-up, and it keeps those off Essential. A solo roofer who writes every estimate can live there. A coordinator who expects the job to advance itself cannot. Team is the plan that adds people at $99 per month and is the plan tied to those production rules.

Best fit is a company that wants the public seat math, sells from a tablet or a kitchen table, and will pay for Team once a second person touches the job. The limits are the one-user wall, the missing production automation on Essential, and SalesPro sitting beside the CRM as its own selling product. Do not paste a rumor about that second product onto the $298 CRM rate. Implementation, as Leap describes it, includes onboarding and an API token from the developer area when another system must trade appointments or documents. Unpaid subs get a narrower portal and are pointed at the old web login. Confirm they see only assigned jobs before that portal is on. Material ordering against a supplier such as SRS is described on the plan and install pages, which is a different check from the monthly seat.

JobNimbus when the board is the business

JobNimbus is the CRM that puts the pipeline on boards and then meters those boards, the automations, and the integrations by plan. The office that already thinks in columns will recognize it faster than an office that lives inside one worksheet. Capterra score: 4.6 from 482 reviews according to Capterra (2026). That figure is a review aggregate updated in September 2026. It is not a timed production test, and it is not a price.

Best fit is a roofing or restoration office that wants the board, the storm-tool names in the help catalog, and a quote it can mark up. EagleView, Hover, HailTrace, Xactimate, CompanyCam, and the supplier links sit in that catalog, with QuickBooks called out on every package. The limits are the missing public price, the automation ceiling that forces an upgrade, the integration ceiling on the two smaller plans, webhook payloads that skip custom fields, and no multi-location support on Essentials. Implementation level follows the plan, paid professional services are optional, and later users have to stay inside the plan cap. Ask whether field seats are inside the included user count or priced by role. After the job is sold, the city file is often a second tracker. Contractor permit tracking is the right companion if a CRM status is not the permit.

Building the gap in Zapier, Make, or n8n

Many offices will not buy a second CRM. They will try to stitch the status change to email, text, and the books. Zapier, Make, and n8n can support run histories, retries, error branches, and audit evidence when a person configures those controls and watches them. They do not arrive as a finished desk. The buyer owns observability, idempotency, escalation, access control, and maintenance, including who is called when a token dies on a Saturday after a hailstorm.

A proposed US Tech Automations design can hold the risky step. It can key idempotency to external_id so a retried webhook does not create a second invoice, and it can require a named person to clear exceptions before a message leaves. Prerequisites are the vendor credentials, a written status map, and that reviewer. If a Make or n8n scenario already has those controls and someone on payroll owns it, keep it. The connector is a fair path. It is a path you have to finish and then maintain.

US Tech Automations is the wrong layer when the crew never leaves one system. If rules inside the JobNimbus cap already text the crew, or if stage rules on the Team plan already email the coordinator, a second product only adds a key to rotate. A shared mailbox and a weekly export are enough when you do not need a held review on every status change. Skip the extra system if nobody will clear the queue.

Glossary for the buying meeting

• CRM: the customer and job record the office works from, as distinct from a measuring app or the accounting file.

• Production board: the column view of open jobs. JobNimbus caps the count by plan. Leap describes custom workflows and a progress board.

• Essential plan: the one-user Leap CRM plan at $79 per month, without the production automation set.

• Quote-based: a price that exists only after the vendor writes it down. That is the public price position for JobNimbus.

• Webhook: a message sent when a record changes. It counts against an automation cap when the product meters active automations.

• status_name: the status field a JobNimbus job requires and can send in a webhook payload.

• date_created: the timestamp the JobNimbus API docs use as the default sort on list calls.

• Idempotency: a control that lets the same event arrive twice without creating a second invoice or a second text.

Mistakes that show up after kickoff

• Signing a JobProgress order without asking whether the seat is current Leap CRM, SalesPro, or a user still aimed at the old web app.

• Dropping a third-party price guess onto JobNimbus. The site you would pay does not print a dollar amount.

• Expecting stage locking on Essential because the demo account was Team.

• Assuming every subcontractor login is free. Leap's help separates an unpaid portal from paid sub users.

• Enabling automated homeowner texts before the texting add-on is actually on the subscription.

• Letting the first webhook create an invoice, with no stop when status_name is the wrong column.

Questions to settle before you sign

Is JobProgress still a separate product you can buy?

No. Leap acquired JobProgress on March 10, 2022 and sells the CRM as Leap. The old name still appears on subcontractor sign-in help, so ask which login a crew bookmark opens before you train anyone.

Does JobNimbus publish a dollar price?

No. JobNimbus marks Essentials, Pro, Premium, and Enterprise as Quote-based and publishes user, board, and automation caps instead. The Team plan on Leap starts at $298 per month for the first user, which is a different vendor's public list and not a substitute for that quote.

Can one person buy the Essential plan and still automate production?

No. Leap's production FAQ says stage progression, stage locking, and automated follow-up are not on Essential. That plan is $79 per month for one user. Production rules sit with the Team plan.

Which public docs name Xactimate?

JobNimbus lists Xactimate in its integration help, along with EagleView, Hover, and HailTrace. Leap's pages checked here emphasize measurement integrations, estimates, and production stages. Confirm the actual import with your own sample file either way.

What must a person review before a text or an invoice goes out?

A person reviews the outbound text and the bookkeeper reviews the export. Webhook payloads skip custom fields, and a retried event can duplicate an invoice if nothing checks external_id or the status. Native CRM rules are enough only when they already cover that pause.

When is Zapier, Make, or n8n enough?

They are enough when someone on staff configures retries, an error branch, a run history, and a human stop, and then owns them. They are the wrong bet when nobody will maintain idempotency, access, and the Saturday failure. A single CRM rule is the better buy when the job never leaves that CRM.

Which office should sign which contract

Choose the Leap CRM, the product the search still calls JobProgress, when the office needs a number it can budget, a one-user place to start, and a clear step up to Team for production rules and added people at the published $99 rate. Choose JobNimbus when the board is how the coordinator already thinks, the storm-file catalog matters, and a written quote is acceptable. Neither choice finishes the evening handoff by itself.

If the status change still needs a held task, a stopped duplicate, and a person on the queue, see how US Tech Automations configures this before you add another login. Bring the status names, the API access your plan actually includes, and the name of the person who will reject a bad payload.