Operating system for service stations

The problem

Service stations and independent garages run on a patchwork of paper schedulers, parts spreadsheets, and a CRM that does not understand bays. Owners burn hours reconciling parts margins; technicians double-book bays; customers wait without status updates; the operator data is locked in three apps and never reconciled.

The approach

We are building a vertical SaaS for service stations: bay scheduling tied to technician availability, parts inventory with supplier integrations and live margin analytics, customer portal with status updates and rebook flows, and retention loops that bring repeat customers back at the right interval. Built around the actual workflow of a busy garage, not adapted from generic CRM. Stripe handles billing; Postgres holds the operator data.

Stack and engineering choices

• Next.js application
• Postgres core
• Stripe billing + payments
• Bay scheduling engine
• Parts inventory + margins
• Customer portal with status
• Supplier integration adapters

Outcome

Operators run the day-to-day shop on one system instead of three. Parts margins are visible per job; bay double-booking is impossible by design; customers self-serve status. Retention loops increase per-customer lifetime revenue without manual outreach.