Dispatch software is a product category dominated by names built for enterprise operations: Onfleet, Bringg, Route4Me, OptimoRoute. These are good products. They're also priced and shaped for fleets running 100+ drivers — and the evaluation framework that makes sense at that scale doesn't translate to 2–25 drivers.
If you're a 12-driver courier, an 8-tech HVAC shop, a 15-vehicle moving company, or any service business below the enterprise floor, you need a buyer's guide written for you — not a feature-by-feature dump against Salesforce-shaped competitors. Here it is.
1. Pricing model — flat or per-driver?
This is the single biggest decision and it gets buried under feature lists. Per-driver pricing means your software bill scales linearly with headcount. At $40–60/driver/month (typical for the enterprise products), a 10-driver fleet pays $400–600/month before any features kick in. At 20 drivers, it's $800–1,200/month.
Flat-tier pricing decouples your software bill from headcount. You pick a tier with caps you can live with, you pay one number, you grow without your software bill compounding. For most small fleets growing from 5 to 25 drivers over a year or two, flat pricing saves $5,000–15,000/year directly.
2. Driver mobile experience — native app or PWA?
Enterprise dispatch vendors ship native iOS + Android apps. That's the right call when your drivers are full-time employees on company devices. It's the wrong question entirely for small fleets, where most drivers use their personal phones and resist installing yet another app for yet another job.
Progressive Web Apps (PWAs) solve this without the install friction. The driver opens a URL, signs in, and works — same UI as a native app, no app store, no IT department. Offline support and push notifications still work via modern browser APIs. The trade-offs are minor (slightly slower cold-start, slightly less polished animations) and almost never matter for a dispatch workflow.
Test it: ask your most senior driver to open the vendor's mobile experience without help and complete their first job. If they need a 15-minute walkthrough, the product is wrong for your fleet — regardless of how impressive it looked in the sales demo.
3. Customer tracking — included or add-on?
In 2026, customer tracking links are table-stakes. Uber Eats and DoorDash trained every consumer to expect them; refusing to ship them is refusing to compete. The question isn't whether your vendor supports them — they all do — but whether they're included in your tier or sold as an add-on.
If they're an add-on, calculate the all-in cost honestly. Most vendors price tracking links at $1–3/job or as a monthly platform fee. At 750 jobs/month (a typical small-fleet volume), that's an additional $750–$2,250/month on top of base pricing. Compare against vendors that include it.
4. Customer self-serve booking — what nobody else ships
The differentiator at the small-fleet end of the market is the customer portal: a tenant-branded URL where your repeat customers sign in, see their history, watch active jobs, and self-book new pickups or service calls. Enterprise products typically don’t ship this because their customers (UPS Store franchisees, 3PL operators) already have proprietary booking flows.
For a small fleet with 30–50 repeat B2B accounts (law firms, medical clinics, dealerships, property managers), this changes the math. Each phone booking burns ~4 minutes of dispatcher time on address re-entry and confirmation; a portal booking takes 30 seconds of glance time when the alert fires. At 200 portal-eligible bookings per month, that's 11 hours of dispatcher attention reclaimed — at $28/hour loaded wage, $310/month directly.
5. Skill + capacity matching — soft or hard?
Every dispatch product claims to support driver skills (CDL class, certifications, vehicle types). The question is whether the matching is enforced at assignment time or relegated to a search-and-filter UX the dispatcher has to remember to use.
Soft matching is a feature that exists in marketing copy. Hard matching means an assignment to an unqualified driver is rejected at the action layer with a clear error — not after the driver shows up at a job they can't legally do. For HVAC dispatching EPA 608-only work, plumbing dispatching journeyman-level repairs, or courier work requiring CDL-A, hard matching is the only kind that matters.
6. Proof of delivery — how robust?
Every product ships photo + signature capture. The differentiation is in retention, audit trail, and dispute resolution. Three questions to ask:
- Retention window — 30 days? 90? 365? Disputes commonly land 60–90 days post-job, especially for B2B.
- Geo-stamp + time-stamp on capture — provable in a chargeback context?
- Searchable by customer / driver / date in the dashboard, or buried in a per-job detail page?
On the low end, you get a photo nailed to a job record with no search. On the high end, you get a full audit trail with retention guarantees that makes disputes a 30-second lookup. The difference matters the first time you eat a $400 chargeback because you couldn't find the proof.
7. Route optimization — luxury or necessity?
Route optimization sells itself. Every vendor has it. The honest question for a small fleet is whether it moves the needle for YOUR operation today.
Route optimization is a force multiplier when your drivers do 15+ stops per day on similar territory. For a 5-stop HVAC tech, the dispatcher's mental model is faster than the solver — and the optimizer's overhead (set up depot, set up time windows, plug in skill constraints) costs more time than it saves. For a same-day courier with 25 drops, the math reverses sharply.
If you don't have 15+ stops per route, route optimization is a feature that sounds compelling and never gets used. Save the budget for features that move daily.
8. The honesty test
The last test isn't a feature comparison. It's how the vendor talks to you. Ask: 'When is your product the wrong choice?' If the answer is anything other than a specific, honest list of operational profiles where they're a poor fit, walk away. Every product has trade-offs; a vendor unwilling to name theirs is one you'll regret three months in.
The small-fleet buyer's checklist
- Flat pricing, not per-driver
- PWA driver experience (or at minimum no IT-led app rollout)
- Customer tracking links included, not an add-on
- Customer self-serve portal for repeat customers (if you have any)
- Hard skill + capacity matching, not soft suggestions
- Proof of delivery retention measured in months, not weeks
- Route optimization scored against your actual stop density
- Vendor willing to say where they're a poor fit