Builds your agency's own client-acquisition pipeline: positioning, cold outreach, proposals, objection scripts, pricing and GHL automations.
Produces the machine your agency uses to win clients: a positioning statement and differentiation matrix, four outreach sequences (cold email, cold SMS, warm nurture, post-discovery ghost follow-up), a merge-field proposal template, anonymised case studies pulled from your completed client workspaces, eight objection scripts, an eight-stage GHL pipeline with six workflow automations and a Conversation AI qualifier, and two to four pricing tiers with revenue modelling. Everything is written GHL-ready so you can implement it the same day. This is an agency asset you build once in your own _default workspace, not a per-product build you repeat.
This skill has no button. You start it by saying what you want. Any of these will do it:
| If you actually want | Use this instead |
|---|---|
| Closing the inbound leads your own funnel and ads already produced | sales-conversion-engine |
| Building a sales system for a client, inside a client workspace | sales-conversion-engine |
| What you need | Why | |
|---|---|---|
Your _default workspace active, not a client workspace | this skill exists to get your agency more clients, not to help your clients get customers, and that distinction drives every decision it makes | Required |
An offer document (offer-output.md) | the skill checks for it before Phase 1 and offers to run /build-offer, because outreach, proposals and objection scripts all anchor to the offer | Required |
| A GoHighLevel account for your agency, and admin access to it | Phase 5 builds the pipeline and six workflow automations, and they live in your main GHL agency account, never in a client sub-account | Required |
| Answers to the Phase 1 discovery questions | it asks what services you sell, who your ideal client is, what you charge, your current and target client count, your biggest acquisition challenge, whether you have case studies, and what is already set up in GHL; it will not re-ask for anything already in your workspace files | Required |
A verified-claims.md registry with entries marked consent: ok-as-stated | results, numbers and testimonials in outreach and proposals only survive if they trace to it; anything else comes out as a [PROOF GAP] marker | Required |
| A name for this sales track | sales assets are multi-variant, so the skill asks for a name and files the deliverables under it | Required |
| GoHighLevel MCP connected | without it the pipeline, workflows and Conversation AI are still written out in full but as documentation you implement by hand | Optional |
At least one completed client workspace with ica-output.md and offer-output.md | the case study generator cross-reads them; with none it skips case studies and offers to format results you supply verbally | Optional |
A brand voice profile (voice-profile.md) | without it the cold outreach reads generic; the skill offers a quick voice build from a website URL or a two or three sentence description | Optional |
Existing positioning.md and audience.md | used to pre-populate the differentiation matrix and ideal client profile; building them from scratch is normal on a first run | Optional |
| Web research tools available (Firecrawl, Perplexity, or WebSearch and WebFetch) | market research runs before Phase 1 and is blocking; it looks at competitor outreach, current response-rate benchmarks and which channels are being spam-filtered right now | Optional |
.docx files, updates the dashboard, asks whether you want presentation slides, writes the agency-sales-output schema, appends to assets.md, and asks how each deliverable landed.agency-sales-output.md schema file, with variant deliverables in their own subfolder.docx of each deliverable, a dashboard section, and optional cumulative slidesverified-claims.md. Client data is anonymised by default and the skill asks permission before naming a client, but the consent conversation with that client is still yours to have.| The mistake | Do this instead |
|---|---|
| Running it inside a client workspace | Switch to _default first. This builds your agency's acquisition system, not a client's. |
| Building the pipeline in a client sub-account | It belongs in your main GHL agency account. Client sub-accounts are for client work. |
| Positioning that says 'small businesses' or 'we care about results' | The validation rules reject both. Name a specific audience, a differentiator a competitor cannot copy, and a measurable outcome with a timeframe. |
| Pricing a retainer without counting the sub-account cost | Retainers should be at least 5x the $47 per month sub-account cost, so $235 per month is the floor, and setup fees should cover the actual build cost. |
| Putting a client's name in outreach or a case study without asking | The skill anonymises by default. Get explicit permission before you name anyone in marketing material. |
| Expecting this to close the inbound leads your funnel produces | That is /build-sales. This one is for cold prospects who never raised a hand. |
Finish at least one client build before running this. The case study generator cross-reads completed client workspaces and writes anonymised case studies for you, so your proposals and outreach arrive with proof already in them instead of a [PROOF GAP] marker.