Field service work, and what it had to survive
Three systems running in trades businesses. The test is a technician in a basement and a customer who will not wait.
Every one started with the same leak. Work arrived faster than the business could catch it. A phone nobody could answer. A schedule held in someone's head. Money moving between strangers with no rules for when a job goes wrong.
Across the three
3
systems running in trades businesses
2
countries served
3
shared integrations: Twilio, Stripe, QuickBooks
1
marketplace holding money between strangers
Systems running in trades businesses
Three builds, three different leaks
Same industry shape, three different points of failure. The software followed the leak, not a template.
| Build | The leak | What we built | Where it runs |
|---|---|---|---|
| ZhoopZhoop | The phone went unanswered during the rush. | AI receptionist that books and orders parts. | Multi-branch auto repair |
| Maidily | Scheduling lived in one person's head. | Operations platform with payments and books. | Residential cleaning companies |
| WorkmateAI | Money moving between strangers, no rules. | Disputes, held funds and compliance. | Australian trades marketplace |
Different trades, identical physics
A repair shop, a cleaning company and a trades marketplace look like three businesses. They fail in the same four places, which is why one team can build for all of them.
The work happens away from a desk. A customer decides in minutes. Whoever is holding the phone usually has both hands busy already.
- The phone is the product, not the dashboard behind it.
- Offline is a requirement, not a feature.
- Marketplaces are two products: matching, then money.
- ZhoopZhoopThe unanswered phone.
- MaidilyScheduling held in a head.
- WorkmateAIMoney between strangers.
Three leaks, three builds. None of them started with a dashboard.
Four things that repeat across all three
Different businesses, same physics. None of these three run from a desk, and a customer's patience runs out in minutes, not hours. Every fix below had to survive someone working with both hands full.
- 01The phone is the product. ZhoopZhoop's value is answering during the rush, not the software behind it.
- 02Integrations decide the build. Twilio, Stripe and QuickBooks show up in nearly every one of these systems.
- 03Offline is a requirement, not a feature. Anything assuming signal fails in a basement or a rural driveway.
- 04Marketplaces are two products. Matching is the easy half. Holding money and settling disputes is the other.
“They will treat your vision like their own and build it that way.”
Ron Klabunde · Founder, SmartREI ↗
Common questions
01Do you only work with trades businesses?+
No. Field services is one of several sectors we build in, and these three are the systems running in it today. They share a shape: work away from a desk, decisions made in minutes, software used by someone with both hands busy.
02Can you integrate with the field software we already use?+
Usually. Jobber and Housecall Pro have open APIs. ServiceTitan gates access per tenant. That one needs your own admin's approval, so it is a project with a vendor dependency, not a switch we flip.
03What does a build like these usually start with?+
An audit of where jobs are leaking. Missed calls, late dispatch and failed payment capture look similar from the outside and need very different software. Each of these three started at a different point on that line.
04Do you work outside the United States?+
Yes. WorkmateAI is an Australian marketplace, which brought its own worker-classification and payment rules. Regulatory homework is part of the build rather than an afterthought.
