What the work looks like when it is finished
Four builds, written up honestly: what the problem actually was, what got built, and what it deliberately does not do.
Case studies
Selected work
Marketplace app
Provisioning console A new sub-account from blank to a reviewable draft in minutes. Around a hundred values proposed per location, each with its source and a confidence figure.
Read more ›Marketplace app
FrontDesk Assist Live queues, a speed-to-lead clock and a team leaderboard, installed into the sub-account. White-labels for agency resale.
Read more ›Migration
Zapier to self-hosted n8n Per-task pricing stopped making sense at volume. Lower cost per run, and headroom to scale.
Read more ›Automation
Automated client onboarding Server-side setup of a new HighLevel account through the API, instead of a person working down a checklist.
Read more ›The pattern
Build the platform layer once, then put products on it
The first custom app is expensive because you are paying for OAuth, token handling, install and uninstall flows, webhooks and data sync. The second, third and fourth are cheap, because that work is already done and does not get rewritten.
That is why two apps exist rather than one, and why the second took a fraction of the time.
Something similar on your account?
Start here
Start with the audit
A written architecture record and a staged plan, useful whether or not I build the rest.