Customer skip requests that fix lawn routes

Micro-SaaSWeb1 monthNext.jsSupabaseMapboxStripe

The idea

Every lawn operator knows the 6am text: skip us this week. The crew eats the drive time anyway because the route was planned around that stop, and then the billing argument arrives later, the customer assumes no cut means no charge, while the operator’s flat-rate maths assumed 4.3 visits a month. The skip itself is trivial; the uncompensated consequences are the problem.

Full field-service suites like Jobber solve this inside a much bigger product these operators do not want. The wedge is coupling the skip to both consequences automatically: the route re-sequences so the crew never drives a dead leg, and the billing rule fires per the customer’s plan, stated in writing on the very page they skip from.

Who pays

Solo and two-crew operators pay 29 USD/month; recovered drive time and killed billing disputes each justify it alone. These buyers refuse per-user field-service pricing, so flat and cheap is the pitch. Distribution: lawn care Facebook groups and the r/lawncare business threads, plus the large lawn-business YouTube scene where operators review tools constantly.

MVP scope

  • Customer import with geocoding, service day, crew, and billing type
  • Tokenised customer skip link with cutoff enforcement and clear billing statement
  • Automatic route re-sequencing via cached Mapbox drive-time matrix
  • Billing rules on skip: per-visit unbilled, flat-rate billed
  • 5am crew route sheet by text with ordered stops and navigation links
  • Skip for v1: estimates and invoicing beyond skip adjustments, GPS crew tracking, chemical application records, customer mobile app
// Build prompt — paste into Cursor / Claude Code / Lovable / Bolt
Build SkipRoute, a web app for small lawn care operators that turns customer skip requests into automatic route and billing adjustments.

Stack: Next.js (App Router), Supabase (Postgres + auth), Mapbox (Matrix API for drive times, GL JS for maps), Stripe for customer billing and operator subscription.

Core flow: the operator imports customers (name, mobile, address geocoded via Mapbox, service day, billing type: per-visit or flat-rate monthly) and assigns them to a crew and weekday. Every customer gets a permanent tokenised link, no login, showing their next scheduled visit with a Skip this visit button, disabled after a cutoff (default 7pm the night before). A skip immediately: removes the stop, re-sequences the remaining route using a nearest-neighbour pass over a Mapbox Matrix API drive-time matrix, and applies the billing rule, per-visit customers are not charged for skips while flat-rate customers are, with both rules stated plainly on the skip page. Each morning at 5am the crew gets a text linking to their route sheet: ordered stops with navigation links and skip flags.

Pages: operator dashboard with today's routes on a map, customer roster with billing type, crew management, skip log with billing outcomes, route sheet (mobile, per crew, per day), settings for cutoff time, billing.

Implementation details: cache the drive-time matrix per route-day and only recompute affected legs on a skip, keeping Mapbox costs sane. Late skips after cutoff notify the operator for a manual decision instead of auto-applying.

Pricing: 29 USD/month up to 2 crews via Stripe Checkout, 14-day trial.

// More Micro-SaaS ideas