Why fleet-size matters for software decisions
Operations at different scales have fundamentally different software needs. Features critical at 50 vehicles are irrelevant at 2. Features sufficient at 2 vehicles fail at 10.
Matching software to actual needs — not aspirations and not legacy — produces better operational outcomes and better economics.
The six fleet-size categories and their software needs
Solo (1–2 vehicles)
Operator profile: Owner-driver, maybe one additional. Minimal office staff.
Software needs: Basic booking widget, simple scheduling, basic payment processing, light communication tools.
Appropriate options: Free tiers of OTA-attached platforms (Bokun), simple booking tools, or integrated platforms like TMMR at entry level.
Typical spend: $0–$2,000/year.
Small (3–5 vehicles)
Operator profile: Few drivers, owner still operational, basic office function.
Software needs: Integrated booking + dispatch + driver management. See best tour operator software for small operations.
Appropriate options: Entry-tier integrated platforms. TMMR at base pricing works. Also OTA-attached if OTA-dependent.
Typical spend: $1,500–$5,000/year.
Growing (5–10 vehicles)
Operator profile: Operations manager emerging, more drivers, formal processes developing.
Software needs: Multi-user integrated platform, real-time dispatch, driver mobile app, fleet management, basic reporting.
Appropriate options: Full integrated platforms. TMMR fits this scale particularly well.
Typical spend: $2,500–$8,000/year.
Mid-size (10–25 vehicles)
Operator profile: Full management hierarchy, 20+ drivers, formal operations.
Software needs: Advanced reporting, deeper driver management, maintenance tracking, compliance features, integrations with accounting.
Appropriate options: Full integrated platforms with scale support. TMMR Sommelier tier (coming soon) or equivalent.
Typical spend: $4,000–$15,000/year.
Mid-market (25–75 vehicles)
Operator profile: Executive management, formal programs, often multi-location.
Software needs: Enterprise-capable platforms with API, multi-user roles, advanced reporting, compliance programs, integrations.
Appropriate options: Enterprise tiers of integrated platforms. Some operations use mixed stacks at this scale.
Typical spend: $15,000–$50,000+/year.
Enterprise (75+ vehicles)
Operator profile: Mid-market to large business with full infrastructure.
Software needs: Enterprise platforms with full customization, API ecosystem, multi-location support, advanced BI, enterprise support.
Appropriate options: Enterprise platforms or custom-built solutions.
Typical spend: $50,000+/year.
What specific features matter at each scale
Booking engine
- Solo: Basic widget sufficient.
- Small: Branded flow matters.
- Growing: Multi-channel (direct + OTA) integrated.
- Mid+: Advanced customization, A/B testing, conversion optimization.
Driver management
- Solo: Basic contact tracking.
- Small: Scheduling plus basic performance.
- Growing: Full driver profiles, mobile app, communication tracking.
- Mid+: Performance analytics, HR integration, advanced certification tracking.
Dispatch
- Solo: Not needed as dedicated function.
- Small: Basic real-time coordination.
- Growing: Real-time dispatch view with changes.
- Mid+: Advanced dispatch, multi-dispatcher support, automation.
Fleet management
- Solo: Minimal.
- Small: Basic vehicle records and maintenance.
- Growing: Full lifecycle plus real-time tracking.
- Mid+: Advanced telematics, predictive maintenance, deep analytics.
Reporting
- Solo: Basic financial summaries.
- Small: Standard P&L plus booking reports.
- Growing: KPI dashboards, per-vehicle economics.
- Mid+: Advanced analytics, custom reporting, BI integration.
Compliance
- Solo: Minimal if under thresholds.
- Small: Document tracking.
- Growing: Expiration alerts, DQF basics.
- Mid+: Full programs, DOT compliance, audit readiness.
Common fleet-size software mistakes
- Over-buying for current scale. Enterprise features for small operations wastes money.
- Under-buying after growth. Growing operation stuck on small-operator tools.
- Not planning for growth. Platform must support realistic growth trajectory.
- Feature-chasing. Buying based on features rather than scale needs.
- Vendor lock-in without evaluation. Long contracts before testing scale fit.
Matching software to scale
Three principles.
Match to current reality
What size are you actually running? Not aspirational size.
Account for growth trajectory
Software should support 24-month projected growth. Avoid platforms you’ll outgrow in a year.
Avoid over-engineering
Buying enterprise features before needing them wastes money and complexity.
Related reading
- Best Tour Operator Software for Small Operations
- Tour Operator Software Reviews
- Tour Operator Software Pricing
- Tour Operations Software: One Platform vs. Frankenstack
- Fleet Management Software for Tour Operators
Frequently asked questions
What software works for solo tour operators?
Basic tools suffice. Free OTA-attached platforms (Bokun), simple booking widgets, or entry tiers of integrated platforms.
What’s the sweet spot for TMMR?
5–50 vehicles. TMMR serves smaller and larger operations too but platform particularly fits this range. See pricing.
How much should I budget for software?
1–4% of revenue typically for well-consolidated operations. Higher spend suggests over-tooling; lower suggests gaps.
When should I upgrade software?
Before current platform becomes bottleneck. Reactive upgrades under capacity pressure produce worse outcomes.
Can I use spreadsheets at any scale?
For solo operators yes. Above 3–5 vehicles, spreadsheets stop scaling.
What enterprise features matter at 50+ vehicles?
API access, multi-user roles, advanced reporting, multi-location support, enterprise support/SLAs.
Should I use multiple platforms or one?
Integrated single platform typically beats stacks at most scales. See one platform vs. frankenstack.
How often should I evaluate software?
Annual review minimum. Also when operation changes materially (growth, new products, new locations).
What’s the biggest fleet-size software mistake?
Mismatching scale. Over-buying wastes money; under-buying constrains operations.
Does TMMR scale to large operations?
Yes. TMMR serves operations from small through mid-market. See product capabilities.
About TMMR
Tour Management Made Right (TMMR) was built in Sonoma, California by a tour operator who got tired of running a growing wine tour business on spreadsheets, group texts, and paper logs.
Driver Ops — driver management, scheduling, performance, mobile app, tips, communication.
Routing & Logistics — route planning, itineraries, tracking, fleet management, manifests.
Business Ops & Reporting — bookings, guests, invoicing, expenses, documents, reporting, integrations.
Pricing: $100/month + $10 per driver.