Dispatch-only vs all-in-one: why field software costs what it costs
Every incumbent monetizes through the money features, which is why you can't buy just a schedule board. The structure behind the pricing, and when unbundling is right for you.
Disclosure: Bloombilt builds Dispatch, which is the unbundled kind. This post argues for a category we happen to be in, so treat the argument sceptically and check the parts that are checkable. The pricing facts are all linked.
Try to buy just a schedule board for a crew business. You mostly cannot.
Every established option bundles dispatch with quoting, invoicing, payments, and usually marketing. Aspire’s Crew Control at around $39 per crew per month is the closest thing to dispatch-only in the green industry, and even it includes invoicing. Everything above it is a suite.
That is not laziness. It is the business model, and understanding it tells you when to fight it.
Why the bundle exists
The money features are where the money is. Payment processing at 2.9% + 30¢, which is Jobber’s published card rate as of 2026-07-26, is a revenue stream that scales with your business rather than with your headcount or your usage. A company running $40,000 a month through the platform generates meaningfully more than its subscription.
Once payments are the economic engine, the software’s job is to get your invoices flowing through it. Which means the software has to do invoicing. Which means it has to do quoting, so the invoice has something to come from. Which means it needs your client list. And now it is a suite, and dispatch is one screen inside it.
Per-seat pricing does the rest. $29/mo per additional user is the standard shape. It scales with headcount, which is convenient for the vendor and painful for a business whose headcount is its product. Your crew of eight is a cost centre in the pricing model and a profit centre in your actual business.
None of this is villainous. It is a coherent model that funds a lot of genuinely good software. But it explains why you cannot buy the one screen you wanted: the one screen does not fund the company.
What you actually pay for
Ask a five-to-fifteen person lawn crew what they use daily: client list, recurring visit scheduling, crews seeing their day on a phone, invoicing, and some routing.
What goes unused: marketing automation, campaigns, pipeline, the customer portal, most advanced reporting, and a good chunk of the quoting workflow.
If that is you, you are funding features built for companies several times your size. That is the “I use 20% of it” complaint, and it is not really a complaint about quality. It is a complaint about structure.
The case for unbundling
You already have the money features. Most companies past a certain size already run QuickBooks, and QuickBooks already does invoicing, sending, and payment collection. Buying a second system that also does invoicing means either running two sets of books or syncing them, and sync between two systems that both think they own invoices is where the classic problems live: duplicate customers on name mismatch, line items collapsing into a generic service item, tax settings fighting each other.
Composing an invoice in the field tool and letting QuickBooks create, send, and collect it is simpler than either alternative, and it means your books were never in two places.
Scope you do not buy is scope you do not implement. Suite onboarding runs weeks. A tool that only does scheduling and field work can be running in days, because there is less of it to configure and less of it to get wrong.
You stop paying for the roadmap you are not on. A suite’s engineering effort is spread across payments, marketing, reporting, and everything else. A tool with a narrow scope spends all of it on the narrow scope.
The case against unbundling
This is the part unbundled vendors skip, so here it is.
Two systems is genuinely worse than one, all else equal. Two logins, two support conversations, two places data can drift. “All else equal” is doing real work in that sentence, but the cost is real.
Integration is a dependency you now own. If your dispatch tool composes invoices into QuickBooks, that integration has to keep working. When it breaks, it is your problem and there are two vendors to call.
You will eventually want something on the excluded list. Quoting, most often. If you grow into bidding work, a tool that deliberately does not quote becomes a constraint, and you are shopping again.
The suites are mature. Jobber, Service Autopilot, LMN, and SingleOps have years of edge cases handled. A narrow tool has fewer features and also fewer years.
How to tell which you are
Write down the five things that are actually broken this month, not the things that would be nice.
If they span quoting, costing, scheduling, invoicing, and reporting: buy a suite. Pick the one whose organizing idea matches your business. We compared the three heavy green-industry suites here.
If they are all in one area, usually crew coordination: buy the tool for that area. Going suite-shopping because dispatch broke is how companies end up implementing a marketing module they will never open.
If you are solo: you probably need neither. Yardbook is free and covers a solo operator’s whole business.
Where we sit
Dispatch is unbundled on purpose: a drag-and-drop schedule board, a crew mobile app that works with no signal, timestamped proof photos on every job, recurring jobs with season bounds, and invoicing composed in the app and sent through QuickBooks. QuickBooks stays the books. We never hold money, never process payments, and never touch card data.
That is not modesty, it is the design. Not monetizing through payments is what lets the subscription be the whole price, and refusing the money features is what keeps the tool small enough to learn in an afternoon.
The honest cost of that choice: no quoting in v1, no payroll, no route optimization, no marketing. And Dispatch is new, where the suites are not. If you need any of those, or need a decade of track record, we are the wrong tool and we would rather say so now.
What we’d tell you
The bundle is not a scam and the unbundle is not a revolution. They are two structures with different failure modes, and the right one depends on how many of your problems live in one place.
Count your five broken things. If they cluster, unbundle. If they scatter, buy the suite.
Fifteen minutes if you want a second opinion on which you are, including if the answer is that you should stay where you are.