The brief
Every new plumber or roofer meant rebuilding the same sub-account by hand, so the owner was doing setup in the evenings instead of selling. They wanted one structure worth cloning, with their name on everything the client touches.
What they bought
What we built
- 01
Branded the platform
Custom domain, logo, login screen, mobile app, and help docs. Nothing a client opens says Votel or VotelOps.
- 02
Designed the sub-account blueprint
One structure for a service business — pipeline stages, calendars, intake forms, and the fields behind them — saved as a template so account two starts populated.
- 03
Wired up the tools each trade already ran on
Payments, calendars, and quoting connected per account instead of left as homework for the client.
- 04
Ran launch QA and handed over
Form submission through to booked job, tested the way a client would use it, then a runbook and a walkthrough call.
What they got
- A branded Votel instance on their own domain: login screen, mobile app, and help docs all carrying their name
- One populated sub-account template — pipeline, calendars, intake forms, and four core workflows
- Eleven more accounts cloned from that template by the agency, unassisted
- A written runbook plus a recorded walkthrough of why it is structured the way it is
What their client sees
- Their agency's name and logo on the login screen and mobile app
- A working pipeline on day one, not an empty account
- Help docs in the agency's voice, not a third party's
What we'd tell you on a call
Most of the work in a rollout is deciding the structure once. After that, each new sub-account is a clone and a phone call.
How we document projects: white-label engagements are confidential (our name never appears on the client side), so each write-up covers the scope, the sequence, and the result by vertical rather than naming the agency behind it. Screenshots are taken from the real build and redacted accordingly.