Jobber automation: quote follow-up, job flow, and which tier you actually need

Most software a trades business is offered is a sales CRM with the words changed. Jobber is not — it models the shape work actually takes in a home service business: a request comes in, someone quotes it, the job gets scheduled and assigned, it gets done, it gets invoiced, and it gets paid. Because the data model matches reality, the automations you can build on it are about the things that genuinely cost trades businesses money, rather than about pipeline stages nobody updates.

Why the data model matters more than the feature list

In a generic CRM you have contacts, deals and activities, and you spend the first month deciding which of those a job is. In Jobber the objects are requests, quotes, jobs, visits, invoices and clients — with a property attached to the client, because a customer with three rental properties is one relationship and three locations.

That distinction sounds like pedantry and is the entire reason the automations work. An automation can say "when a visit is completed, do X" because a visit is a real object with a real completion state. In a sales CRM you would be inferring that from a stage change somebody remembered to make.

Recurring work is the clearest example. Lawn care, cleaning, maintenance contracts — these are a first-class concept in Jobber, not a workaround. Any business with a service schedule will find this alone worth the migration.

What Jobber costs

Additional users are listed at $29/month each across all tiers. Month-to-month pricing without a commitment is meaningfully higher than the annual figures above — Core, for example, is listed at $49/mo with no commitment. Source: the vendor’s own pricing page, read August 5, 2026. Prices change — verify before you commit.

The tier structure is about automation, not features

Reading Jobber's tiers as a feature list misses what is actually being gated. Broadly, the entry tier gives you the core workflow — quoting, scheduling, invoicing — for one person. Moving up adds the automated communication (booking confirmations, reminders, on-the-way notifications) and then the automated follow-up, particularly on quotes.

That means the upgrade question has a specific answer rather than a vague one. Ask: what would automated quote follow-up be worth to me?

Take the quotes you sent last quarter that never got a reply. Multiply by your average job value and a conservative conversion rate on follow-up. For most trades businesses that number comfortably exceeds the difference between tiers, because unanswered quotes are the largest and least visible source of lost revenue in the trade.

Note also that the additional-user cost is listed separately and applies across tiers, so a growing crew changes the arithmetic. And month-to-month pricing without a commitment is meaningfully higher than the annual figures.

The five automations that change the numbers

• Quote follow-up with a stop condition. Two or three touches over two weeks, cancelling the moment the customer replies or the quote is approved. The stop condition is not optional — a sequence that chases someone who already said yes actively costs you the goodwill you just earned.
• On-the-way notification. Status change to en route sends a text with an arrival window. Eliminates the "where are they" call, and customers consistently rate the same visit better when they were not left wondering.
• Job complete to invoice, immediately. The delay between finishing and invoicing is pure lost cashflow. Trigger the invoice from job completion and push it into your accounting system in the same flow.
• Review request after payment. Not after the job — after payment, when the transaction is genuinely complete and the customer feels finished with it. Reviews compound into every future enquiry.
• Recurring service reminders. For maintenance and seasonal work, a reminder ahead of the due date with a booking link. Turns a customer who might have called into one who did.

Connecting Jobber to everything else

Jobber has an API and supports webhooks, so events inside it can drive workflows outside it. The patterns worth building:

• Website enquiry to Jobber request, so nothing arrives by email and waits to be re-typed. Every manual re-entry is a chance to lose one.
• Job status to Slack — but exceptions only. A channel that fires on every status change gets muted in a week.
• Photos and notes into a durable store, so job documentation survives independently of the subscription.
• An LLM step to triage inbound requests — classify urgency and service type from the customer's free-text description, so dispatch starts with structure rather than prose.
• A weekly summary: jobs completed, revenue invoiced, quotes outstanding, anything overdue. Owners make decisions weekly and usually look at their numbers monthly.

Where Jobber stops fitting

• Complex dispatch. Jobber schedules well. It is not a route optimisation and capacity planning system for a large fleet. Businesses running dozens of technicians with skill-based assignment usually outgrow it, and ServiceTitan is the usual destination.
• Long consultative sales. If your work involves months of relationship-building before a contract, that is a sales process, and a CRM models it better than a job platform.
• Deep inventory management. Parts tracking is basic. Businesses with real warehouse operations need something purpose-built alongside it.
• Per-user growth. Additional users are charged individually, so a crew that grows quickly changes the cost picture. Model it at your projected headcount rather than today's.

For the large middle of the trades market — a handful to a couple of dozen people, doing scheduled work at customer properties — Jobber fits the business rather than asking the business to fit it. That is a rarer quality in software than it should be. If you are weighing it against alternatives, our free audit will look at your actual workflow rather than the feature grid.