Field services · Operations & billing
Mueller Landscaping Services
A seasonal field-services business running scheduling, client communication, and recurring billing by hand.
The challenge
Work was coordinated across phone calls, texts, and spreadsheets. Recurring billing depended on someone remembering to send an invoice, and the owner had no single view of the season.
The insight
The bottleneck was not sales or crew capacity. It was the administrative loop between work completed, client communication, and payment collected.
What we built
A client-facing portal with service visibility, documents, and recurring payments, backed by an operations view for the business.
Engineering approach
React and TypeScript front end, Postgres with row-level security for tenant isolation, Stripe for recurring billing with webhook-driven state, and transactional email for client notifications.
How we worked together
Built alongside the owner in short review cycles so the workflow matched how the business already ran rather than forcing a new process.
What changed
Recurring billing and client communication run through one system instead of manual follow-up.
What lasts
The business owns the portal, the data model, and the payment configuration, and can add services without engineering help.
Similar problem?
Tell us what the work looks like today and we will tell you honestly whether AI is the right answer for it.
Start a conversation