Breasy connects service providers with the customers and operations that need them. We serve 250+ providers completing 10,000+ jobs a year across 10 markets — and we did it with a custom-built platform instead of a stack of off-the-shelf tools.
When we raised, the pitch was "we do the thing." The proof had to be that we were actually doing it — which meant building the thing before anyone else would.
The thesis
Service providers lose hours every week to tools that weren't built for the way they actually work. Quotes scattered across email. Jobs tracked in notes apps. Pricing estimated on gut. The tax on being a small service business is coordination overhead — and the tools that claim to fix it are either overbuilt for enterprise or underbuilt for anything past a solo operator.
What I built
Built the full-stack platform end to end. Architecture choices that mattered:
- AWS + Bubble.io as the backbone. Bubble for the speed of iteration that a seed-stage team needs; AWS for the primitives (storage, functions, queues) that Bubble couldn't handle cleanly. The line between the two was drawn intentionally — everything that changed often went in Bubble, everything that had to be reliable went in AWS.
- Web + mobile from day one. Service providers live on their phones during the day and at desks at night. The platform had to work in both contexts without feeling like a port of the other. Responsive-first, not app-first.
- AI pricing models. A quote assessment engine that read incoming jobs and returned a recommended bundle and price range, trained on our closed-deal data. The goal wasn't automation — it was removing the anxiety of "am I underpricing this?" that slows every service operator down.
- Automation layer (n8n + Chrome extension). The parts of the work that didn't need human judgment — status updates, follow-ups, internal handoffs — got offloaded to workflows. Coordination time across the team dropped 60% measured end to end.
- Quote-to-close tooling. Reduced quote turnaround from 7 days to 5 and lifted close rate from 50% to 70%.
The scope was a platform, not a product. Ten markets, 250+ providers, 10,000+ jobs a year, both sides of the marketplace, ongoing — with a team that's still small enough that the architecture has to hold up under real stress.
What changed
The platform is live and operating. The key measure isn't a vanity stat — it's that the scale the product supports today was built by a team that stayed lean the whole way. No 30-person engineering org, no agency build, no enterprise-stack rebuild. One operator with taste, opinions, and the right tools made for the right job.
This is the proof point I point to when small business owners ask "can I really run a real platform without spending $500K?" The answer is: yes, if you pick your stack like you mean it.
By the numbers
- 250+ service providers on platform · 10,000+ jobs completed per year
- 10 markets active
- Coordination time −60% via automation workflows
- Quote turnaround: 7 → 5 days
- Close rate: 50% → 70%
—
If you're building or scaling something custom, that's what I do at OhDavid.
