Setting Up Your AI Project

The two-minute setup that makes every tool in this system work: one project, five files, one tool per conversation — in Claude, ChatGPT, or any AI you already use.

The Fletcher Method™ — Customer Engine Academy™

Section 1: The One Thing That Matters

It doesn't matter which AI you use — Claude Code, Claude Cowork, ChatGPT, or another capable tool. What matters is two things: you use ONE primary tool, and you work inside a project — not a fresh chat opened the way you'd ask a quick question.

A project is a home with memory: the tool files we give you live there, and — just as important — the outputs live there too. When a builder saves your script, that file goes in the project, because every downstream tool reads it.

What "project" means in your tool: in Claude, create a Project (or a folder if you're in Claude Code). In ChatGPT, create a Project. In anything else, one dedicated folder. Name it after your offer — the business you're launching.

Section 2: Your Toolkit — Five Files, Each Where You Learn It

Five files run this whole system, and you download nothing ahead of time — each one lives in the module where you learn it:

File	Where you get it
The SCRIPT VSL Builder — writes your VSL script	Module 5
The Winning Workshop Builder — writes your webinar script	Module 7
The Slide Builder + your theme — browse six themes, download one, customize to your brand	Module 6
The bonus tools — the Mini-VSL Mod, the Sales Call Mod, and the 8 Buying Beliefs Scorecard	Module 8
Your saved outputs — the script files and deck the tools create	Saved by the tools, into your project

Each module also has its written guide — like this one. Read them where they show up; they're the quick-reference version of what the video teaches.

Section 3: Set Up Once — Two Minutes

Create a project in your AI

Or one folder — named after your offer. Everything from here on happens inside it.

Add each file as the modules hand them to you

Into the project's files — never loose in a random chat.

One tool per conversation

Start a new chat in the project for each tool: one conversation to build your script (and keep that conversation for script revisions), a separate one when it's time to build slides.

Save the outputs back to the project

Your approved script file is the one thing everything else reads — the Slide Builder, the Scorecard, the mods. Your finished deck lives there too.

The one mistake: the wrong file in the wrong chat is the only way to break this system. One tool per conversation — each module tells you exactly which file to open.

Section 4: Troubleshooting

A tool is asking questions another tool already answered? You're probably in a chat without the project's files. Check that the conversation lives inside your project and the saved script file is there.
The tool "forgot" your script? Share the script file into the conversation (or paste its contents). The stamped file — not the chat history — is the source of truth.
Changed your offer, price, or proof? Update it in the builder that made the file, re-approve, and let everything downstream rebuild from the new file. Never hand-edit the saved script.
Switching AI tools mid-course? Fine — move the project folder's files. The tools are cross-platform by design.

That's the whole setup

Two minutes now, and every module after this just works: open the module, grab its file, new conversation, go.

Ready to Build Your Customer Engine?

Work with me to install all the systems, AI tools, and coaching you need to launch and grow your business.

Join Customer Engine Academy™