GorillaDesk vs ServiceM8

Light, self-service ramp with one well-known sore point. Switchers from QuickBooks, Jobber, Markate, Beevio and paper report smooth, well-documented moves; one operator moved ~1000 customers from PestPac self-service and was "using it 100% within a week" (Livinirie_84), and the vendor advertises free data migration + unlimited training, no contract. The recurring friction is QuickBooks Online sync ("do not sync QBO... a nightmare" — multiple operators). (research/gorilladesk/log.md MigrationPain.)

Fast to start, easy to leave, with a tailoring learning curve. Best onboarding datapoint: "super easy to set up... set it all up in 2 hours after my first customer called" (MisterSirManDude, US HVAC solo). Low lock-in regret — clean switches both into SM8 (ex-Jobber, ex-Simpro) and out of it (to HaloPSA, Ascora) with no data-loss horror stories, month-to-month. Friction is config effort ("requires a lot of work to tailor" — Puzzled-Bottle-3857; "a bit of a learning curve" — labaton). (research/servicem8/log.md MigrationPain.)

Per-route tiered subscription ($49 Basic / $99 Pro / $149 Growth), no contracts, no setup fees, 14-day trial. Cost scales by number of routes, not headcount — unlimited admin users on every plan. First-hand operators call it the affordable/transparent option: "$49 a month... they don't charge you when you call them for help like pestpac" (Tughernutts), "best bang for my buck" (horriblyfantastic), "Its $50/mo but it does it [all]" (Rhawn, r/sweatystartup). Wrinkles: one documented price increase ("locked in pricing before they raised it" — Jahweez) and per-route pricing that multiplies for multi-route shops. (research/gorilladesk/log.md PricingHonesty; _raw-capture.md Rhawn.)

Job-volume tiers (Free / $29 / $79 / $149 / $349), unlimited users — structurally unusual: you pay by jobs-per-month, not per seat. No contract, 14-day trial. Operators call it "best value by far" (frivolouspig), "dirt cheap" (modal_enigma), "wins on price ~$29/mo but more bare bones" (techresearch95). A SM8 mention even surfaces inside a pest thread as a cheap-solo option ("Servicem8 now offering a free plan for solo operators" — Forward-Ask-3407, r/pestcontrol). Fine print: the free tier is thin (~3 active jobs) and SMS is a paid add-on. (research/servicem8/log.md PricingHonesty; _raw-capture.md Forward-Ask-3407.)

Liked-but-glitchy in its niche. Many pest operators call the app user-friendly and industry-shaped (material usage attaches to invoices; pull-from-previous-service), and a field tech under a GD owner cosigns the workflow. But specific, repeated complaints drag it down: "many glitches... unresponsiveness, not being able to save PO's" (PacknPaddle), bugs saving images, can't create a customer without all fields filled, 2-page printed invoices when listing materials/EPA#. Net: workable and liked by small shops, rough edges that compound at scale. (research/gorilladesk/log.md FieldUsability.)

iOS-first and best-in-class on Apple — repeatedly the standout reason operators pick it ("better than Jobber for the person doing the work" — TrailsideHandyman). The dominant, recurring caveat is platform: "really only cater for Apple. The Android app doesn't do everything" (bluetuxedo22); "10/10 if it supported Android" (Cold-Couple8387). A limited "ServiceM8 Lite" Android app now exists (Master_Enyaw). Other gotchas: some features are desktop-locked (Inertia-619); notification/online-booking defaults can miss callouts or duplicate jobs. (research/servicem8/log.md FieldUsability.)

Recurring routes are the product's core identity. Automated recurring billing, stop-by-stop route optimization, and chemical tracking are the cited differentiators; an owner reports GD has "route optimization that will help with tightening a route" (rgstephe, 20+ yr owner). Limit: it does not yet auto-insert a job into a nearby upcoming route — operators do that opportunism manually ("I use Gorilla Desk and manually do this 1-2 times a month" — aflo322). Still, daily route density is what GD is built around. (research/gorilladesk/log.md Coverage; _raw-capture.md rgstephe + aflo322.)

Recurring/job scheduling is solid but generalist, not route-density-first. Operators praise scheduling + automatic ETA texts for small teams (jassem91). It's built for varied trades doing discrete jobs, not for pest/lawn/pool daily-route optimization with chemical tracking. (research/servicem8/log.md Coverage.)

Purpose-built for recurring-service trades — pest control above all, then lawn and pool. Operators repeatedly describe it as industry-shaped ("seamless for our industry," chemical/material tracking attached to invoices, state-compliance reporting incl. wind speed/direction) and made by a pest operator. A first-hand GD pest user is explicit that it's pest-shaped: "I use GorillaDesk for pest control, and it would work well for lawn care, but it'd be overkill" (airhighfive, r/sweatystartup). No HVAC/plumbing/electrical/general-contracting fit surfaces in any logged thread. (research/gorilladesk/log.md Coverage; _raw-capture.md airhighfive.)

Trades-generalist FSM used across electrical, plumbing, HVAC, locksmith, pressure-washing, cleaning, handyman, even non-standard trades (sewing-machine repair — modal_enigma). Operators name it as a category-standard answer for solo→small teams ("game changer" — jassem91; "good enough for most people" — naishjoseph1). Community skews heavily AU/NZ with real US/Canada/UK presence. No pest-specific chemical/EPA compliance tooling surfaces — it's broad, not vertical. (research/servicem8/log.md Coverage.)

Small-shop tool with a real ceiling. Operators put the comfortable range at solo through ~5 techs; one owner names ~5 techs as "where Gorilla becomes not as helpful," and owners view it as a small-company tool (perception "isn't for 'big' companies" — andy_1232). Above ~15 techs, reporting/API/PO-handling gaps bite; FieldRoutes/PestPac are the cited step-up for heavier pest operations. (research/gorilladesk/log.md Coverage + Crew-Size Verdict.)

Strong solo→small, thinning evidence past ~5-20. Best fit is the solo-to-small-team band (Trick-Necessary4601 notes it earns its keep above ~3 staff); as crews grow, the gaps that surface are reporting/profitability and payment-status visibility ("becoming problematic" for an ex-Jobber operator growing on SM8 — H-E-BSport50) and a clunky pre-field/CRM side (GeekCohenAU). Almost no first-hand 20+ evidence; the simPro/ServiceTitan class is the cited step-up. (research/servicem8/log.md Coverage + Crew-Size Verdict.)