The Customer Engine isn't a pile of templates. It's a system — and like any system, the parts connect to each other.
Here's the structure: you've got three engines inside the Customer Engine. The Offer Engine defines exactly what you sell and who it's for. The Content Engine gives you the core messaging and copy you'll use everywhere. The Traffic Engine turns that into the mechanism that brings in leads and converts them.
Each engine has steps. Each step has an AI prompt that builds it for you. But here's the part people miss — the prompts build on each other.
Your MDM (Million Dollar Message) feeds into your Roadmap. Your Roadmap feeds into your Model Builder. Your SCRIPT pulls from all three. Your EA is built directly from your SCRIPT. Your Winning Workshop or Authority Amplifier uses everything that came before it.
This is not a collection of random tools you can use in any order. Skip a step, and the next one breaks — because the AI is expecting inputs you haven't created yet.
You've got options. Here's what I recommend:
Claude (claude.ai) is the preferred tool for this system. It handles long-form, structured writing extremely well — which is exactly what you're doing when you build your MDM, Roadmap, SCRIPT, and EA. Go to claude.ai and start there.
Perplexity is a solid second choice and works well for this system too.
ChatGPT works if that's what you're most comfortable with. Just know the prompts were built and refined in Claude, so you'll get the best results there.
The tool matters less than the habit — and the one habit that matters most is this:
Here's why this is non-negotiable: every prompt in this system needs to see what you built in the previous step. When you start building your Product Roadmap, the AI needs access to your MDM. When you start your SCRIPT, the AI needs your MDM, your Roadmap, AND your Model Builder.
If you open a fresh chat for each prompt, the AI has no memory of your previous work. It's starting from zero every time — and your outputs will be generic instead of specific to your business.
One project. One Customer Engine. Everything connected.
This takes about five minutes. Do it before you do anything else.
If you're using Perplexity or ChatGPT, start a new thread. The goal is a dedicated, persistent space just for your Customer Engine — not a general-purpose chat you use for everything else.
Call it "My Customer Engine" or "[Your Business Name] Customer Engine." Naming it matters — it keeps this project mentally separate from other AI work you're doing, and it's easy to find when you come back to it.
Head to the Member Resources page and download the MDM Builder prompt. This is Step 1 — the Million Dollar Message. Everything else in your Customer Engine builds from this.
In Claude, you can attach files directly to your project. Upload the MDM Builder prompt there. In ChatGPT or Perplexity, paste the prompt content into your thread.
Once the prompt is in, the AI knows exactly what to do. It'll ask you questions, guide you through the inputs, and build your MDM with you. Your job is to answer honestly and completely — the more specific you are, the better your outputs.
Go back to the Member Resources page and download the Product Roadmap prompt. Upload it to the same project — the one that already has your MDM in it. This is how the AI builds your Roadmap using your MDM as the foundation.
One step at a time, same project, in sequence. That's it. By the time you finish, you'll have a complete, connected Customer Engine — and every piece will be custom-built for your specific business.
Here's every step laid out. For each one: read the guide first, then use the AI prompt. The guide teaches you what you're building and why. The prompt builds it. You need both.
Your core offer statement. Everything starts here.
This is the foundation of your entire Customer Engine. Your MDM defines who you help, what you help them do, how you do it differently, and why it works. Every other step in your system references back to this — which is why you can't skip it or rush it.
Read the guide first, then use the AI prompt.
Your unique 3-stage, 9-step system. Uses your MDM.
Your Roadmap is the proprietary framework you take clients through. It's what makes your approach feel systematic and credible — and it comes directly from your MDM. The AI uses your MDM outputs to build this, which is exactly why they need to be in the same project.
Read the guide first, then use the AI prompt.
Your pricing and business model. Uses your MDM + Roadmap.
The Model Builder takes your MDM and your Roadmap and turns them into your actual business model — your offer tiers, your pricing structure, the way you deliver your work. This step also determines which conversion mechanism you'll build in Step 6.
Read the guide first, then use the AI prompt.
Your 6 blocks of core copy. Pulls from all Offer Engine outputs.
This is where your Offer Engine outputs get turned into messaging. Your SCRIPT has six blocks — each one draws from your MDM, your Roadmap, and your Model Builder. This is the content layer that feeds everything in your Content Engine and Traffic Engine. All three Offer Engine steps must be done before you touch this one.
Read the guide first, then use the AI prompt.
Your sales document. Built directly from your SCRIPT.
The EA is the document you use to enroll clients — it could be a sales page, a proposal, or a one-pager depending on your model. It's built directly from your SCRIPT blocks. Not rewritten. Not recreated. The SCRIPT goes in and the EA is structured around it.
Read the guide first, then use the AI prompt.
Your conversion mechanism. Your Model Builder path determines which one.
Your Model Builder output will point you toward one of two paths: the Winning Workshop (a live or recorded training event that converts) or the Authority Amplifier (a content-driven approach that builds trust at scale). You build the one your model calls for — not both. This is your traffic-to-enrollment bridge.
Read the guide first, then use the AI prompt.
I'll say it again because it's the most common mistake people make: do not start a new chat for each prompt.
Here's what breaks when you do that:
Every time you start fresh, you lose the compounding effect. The whole point of the system is that each step is informed by what came before it. One project equals one Customer Engine equals everything connected and working together.
These are the four mistakes I see most often. All of them are avoidable — but only if you know to watch for them.
The SCRIPT pulls from your MDM, your Roadmap, AND your Model Builder. All three have to be done first. If you jump to SCRIPT early — even if you feel ready — you'll get messaging that's not grounded in your full offer architecture. Go back, finish the Offer Engine, then build your SCRIPT.
The prompts build on each other. Same project, always. A new chat is a fresh start — the AI has no memory of your MDM, your Roadmap, or anything else you've built. You'll waste time regenerating context and your outputs will be weaker for it.
The guide teaches you what you're building and why. The prompt builds it. They work together. If you skip the guide, you won't know what good looks like — and you won't be able to tell the AI when an output is off. Read the guide first, every time.
Your SCRIPT blocks go into the EA verbatim. The EA adds Content Blocks around them — it frames and sequences your SCRIPT, it doesn't replace it. If you rewrite your SCRIPT blocks inside the EA, you break the connection between the two documents. If you want to change your SCRIPT, go back to the SCRIPT step and change it there. Then rebuild your EA from the updated version.
You've got everything you need to get started. Here's the exact path forward:
That's it. The system will guide you from there. Each step tells you what to do next. Trust the sequence and don't skip anything — the whole thing is designed to build on itself.