Workflow Apps

Case Study · SaaS

Septic360

Multi-tenant field-service SaaS for septic companies on Next.js and Supabase: scheduling and dispatch, a custom form builder, field capture, branded reports, and Stripe billing.

SaaS · Next.js · React · Supabase · Stripe

The Situation

Septic360 is field-service software for septic companies: inspections, tank pumping, installation, and maintenance. The first version proved the product. Its custom inspection forms were good, and paying inspectors used it. But it had outgrown its foundation.

  • Data belonged to users, not companies. Records were scoped to the individual inspector, so two people at the same company couldn’t share a customer, and isolation between companies wasn’t enforced at the database.
  • Scheduling was a date field. There were no working hours, crews, conflict checks, or multi-day jobs. Hydrostatic tests, which need consecutive working days, had to be handled by hand.
  • Everything was an inspection. Pumping and installation work didn’t fit the data model.

What We Built

A ground-up rebuild on Next.js 15, React 19, and Supabase. We kept the product behavior inspectors already relied on and replaced the architecture under it.

  • Account-scoped multi-tenancy. Every business record belongs to a company account, and Postgres row-level security enforces it. A crew shares one customer list, and no company can read another’s data.
  • A generic job and service core. Inspection is one service type among several. Each job carries service line items with their own forms, resources, and schedule. Adding sewer or stormwater work later means new service types, not a schema change.
  • A real scheduling engine. Working hours, crews and trucks, time off, conflict detection, multi-day jobs, and a dispatch board. Services can require adjacent working days, which is how hydrostatic tests are booked. Homeowners can book inspections online.
  • The custom form builder, ported. Sections, repeatable groups, a dozen field types, conditional logic, and drag-and-drop editing, with fields mapped into report templates.
  • Field completion. Crews complete forms on site with photo and signature capture stored in Supabase Storage.
  • Documents and billing. Branded inspection reports are generated and emailed from completed forms. Stripe handles platform subscriptions per seat.
  • A CRM built for the trade. Customers, contacts, and properties in three tiers, with Google Places address lookup.

Architecture Decisions

Fix tenancy first. Moving data from users to accounts touches every table, so it went in before any new feature. Row-level security means a missed filter in application code can’t leak data across companies.

Model the business, not the first use case. Building a general job and service core instead of a better inspection form is what let pumping, installation, and maintenance launch together.

Build on a maintained foundation. The app runs on a current SaaS starter kit in a pnpm and Turborepo monorepo, so authentication, billing, and account management stay on an upgrade path instead of becoming custom code to maintain.

Ship in phases. CRM, multi-service jobs, scheduling, public booking, field capture, and document generation each landed as a reviewable phase on a working app.

What Changed

Septic companies run their whole operation in one system: a lead becomes a customer and a property, a job is booked against real crew availability, the work is captured in the field, and a branded report goes out when it’s done. The platform is built to add new service lines without another rebuild.

Have a Similar Project?

Tell us what you're working on. You'll hear back within one business day.