How working together actually goes
Audit, stage, apply, hand back. You keep the account and the data throughout, and nothing touches live customer data until you have signed off the phase.
The method
Four steps, every time
Audit
A technical look under the bonnet: pipelines, fields, workflows, integrations and what is actually firing.
Stage
The plan written up so you can review it, priced and prioritised, before anything is built.
Apply
Built in slices you can test and sign off, each one validated before the next.
Hand back
Documented, with you still owning the sub-account and the data. Always.
Engagement models
Three shapes, depending on the work
Most engagements start with a paid technical audit. It produces a written architecture record and a staged plan, and it is useful to you whether or not I build the rest.
From there the work is either a defined project with phases and sign-offs, or a retained arrangement with an agreed block of build time each month for roadmaps that keep moving. Marketplace app builds are usually a project followed by a retainer, because an app needs maintaining after it ships.
What shapes the price
The honest variables
Account complexity
How much needs unpicking before anything new can safely go on top.
Integration surface
How many systems are involved, and how well documented they are.
Live risk
Whether the account is running live customer traffic while the work happens.
Ongoing need
Whether this is a project that ends or a roadmap that keeps moving.
What is not included
Worth saying out loud
Your HighLevel subscription, and any third-party service the build depends on, stay in your name and on your card. That is deliberate: you keep the account, the data and the commercial relationships.
Prices are quoted after the audit, not before it. A number given before anyone has looked under the bonnet is a guess, and guesses are how projects go wrong.
Start with the audit
Start here
Start with the audit
A written architecture record and a staged plan, useful whether or not I build the rest.