Case study: five SaaS tools, one dashboard, and a quieter Monday morning

A services firm we work with — 22 people, US-based, handles recurring field work for commercial clients — came to us last spring with a familiar complaint. Their ops manager was spending the first ninety minutes of every Monday copying numbers between tabs.

Here's what they were paying for: a scheduling tool, a CRM, a separate invoicing app, a time-tracking product, and a project management board. Five logins, five bills, five sources of truth that didn't agree with each other. Total spend was about $1,400/month, plus the soft cost of the Monday morning ritual and the disputes it created with clients when numbers didn't line up.

This isn't a niche story anymore. Retool's 2026 Build vs. Buy Report found that 35% of enterprises have already replaced at least one SaaS product with a custom-built app, and Newsweek's coverage of the same shift points to AI-assisted engineering as the reason the math finally works for smaller teams too.

What we actually built

We spent two weeks shadowing the ops manager and the two people who touched the tools most. The goal wasn't to recreate every feature of every product. It was to figure out which 20% they actually used.

What shipped, six weeks in:

- A single web app with role-based logins for office staff and field techs - Job scheduling tied to a shared calendar, with route grouping - Client records, job history, and notes in one place (no separate CRM) - Time entries captured from the field on a phone, tied to the job - Invoices generated from completed jobs, exported to their accountant's QuickBooks

We didn't build a project management module. They didn't need one. The job board did that work.

What changed

The Monday morning copy-paste is gone. The ops manager now spends that time on collections calls, which has its own measurable effect. Client invoice disputes dropped because the invoice references the same timestamps the client sees on the job confirmation email.

Software spend went from roughly $1,400/month to about $180/month in managed infrastructure costs. We're not going to claim that's the only number that matters — the build wasn't free, and there's ongoing work as their process changes. But the payback math was clear inside a year.

The part we didn't expect

They've come back twice since launch to add things: a customer portal for one of their bigger accounts, and a simple parts-inventory view. Neither was in scope originally. Both took under a week.

That's the pattern we keep seeing. Once a team has software shaped like their actual work, the next improvement is obvious. The hard part was the first one.

If your stack looks like the one above and Monday morning sounds familiar, the discovery call is free. We'll tell you whether a build makes sense or not.