Client builds and pages
The Blueprint: build a client account
From intake form to a complete, reviewed account build you approve before it runs.
What you'll get
- One intake form your new client fills in, and a complete build plan for their account written from their answers.
- A two-part checklist: everything GHL Command builds for you, and the short list only you can do, in order.
- A hard stop before anything is created. You read the plan, you change what you want, and nothing touches the account until you approve it.
Say this
Run the Blueprint for a new client.
Build my Blueprint from the intake this client just submitted.
Show me the plan first. Do not build anything yet.
The pro prompt
The exact ask we run on real client accounts
Run the GHL Command Blueprint for a new client. The business: [Radiance Med Spa], a [med spa] in [Austin, Texas]. What they sell: [body contouring and injectables]. Their main goal for the next 90 days: [fill the consult calendar]. Install the intake form in my [MCP Testing] account, give me the link to send them, and once their answers are in, build the plan from those answers. Show me the full plan before anything is created: pipeline and stages, custom fields, tags, calendar, form, funnel, the emails and texts written out, and every workflow. Mark clearly which items you will build and which ones I have to do myself in GHL. Build nothing until I say approved.
Click the box to select it, then press ⌘C (or Ctrl+C)
Everything in [brackets] is yours to change. The last line is the gate. The Blueprint is designed to stop there and wait for a human.
What happens when you ask
- Claude installs the intake form in the account and gives you a link to send the client.
- When their answers land, it turns them into a build plan: pipeline, fields, tags, calendar, form, funnel, messages, workflows. Every message written out in full.
- You read it and change anything in plain English. Then you approve, and only then does it start creating things in the account.
- It builds in order, checks each piece exists after it creates it, and hands you the manual checklist for the parts that need a human in GHL.
Good to know
- Triggers get scoped to the thing you actually meant. An appointment trigger can be tied to one calendar, so a caregiver interview does not start the family consultation sequence. A reply trigger can be narrowed to a tag or to whether the reply was a yes or a no, instead of firing on every inbound message. Missed calls can be caught by call outcome, and failed phone-number checks by validation state. Say which one you mean in plain English and the plan carries it through.
- If a workflow step moves a deal to a new stage, the plan makes it find the deal first. That pairing is checked before the build runs, because a stage move on its own saves cleanly and then does nothing at all.
- The manual list is short but real: connecting a payment provider, phone and A2P registration, connecting social accounts, and domain settings. Those need a human with account access, and no tool can honestly do them for you.
- Run it on a fresh sub-account, or one you are happy to have built into. It creates a lot.
- The build plan is worth keeping. It is the document you walk your client through on the kickoff call.
- Budget an hour end to end, most of it your review time. The building itself is minutes.
- Needs the full license.
Where people go wrong
| What happened | The fix |
|---|---|
| "It built into the wrong client's account." | Confirm the account before you approve. Ask "which account am I in" and say the account name inside the prompt. |
| "I approved without reading the messages." | The messages are the client's voice going out to their patients. Read them. Editing takes minutes; a bad send costs a relationship. |
| "Some workflows are not live." | Built is not published. Blueprint leaves things reviewable on purpose. Publish them yourself once you have read them. |