Tuesday named the problem.
The sequence is backwards. And every asset in your system is carrying weight it was never built to carry.
Today I want to show you exactly what that looks like on your sales page. Because that’s where the problem is most expensive. And most invisible.
Here’s what your sales page is probably doing right now.
It’s meeting someone who hasn’t decided anything needs to change yet. So the page has to create that decision. That’s the first job.
Then, because they’re still not convinced, it has to show them what staying stuck is costing them. That’s the second job.
Then, because they’re still hesitating, it has to earn their trust, dissolve their doubts, and make the offer. That’s the third job.
One page. Three jobs. A stranger at the top and a paying client at the bottom.
No wonder it converts at 2%.
The page isn’t bad. It’s doing an impossible job.
No single page can take someone from “I’m fine” to “I’m buying” in one scroll. Not when they’ve been burned before. Not when they’ve heard every promise. Not when they filter everything through years of disappointment.
The fix isn’t better copy.
It’s giving the page one job.
When the sequence is right, your sales page does one thing.
It confirms a decision the person has already made.
By the time they land on it, they’ve already felt the cost of staying stuck. They’ve already seen where they’re headed if nothing changes. They’ve already worked through their doubts. The decision is done.
The page doesn’t create any of that. It just confirms it.
Which means every word can do one thing with precision. The opening doesn’t need to grab attention from scratch. It confirms what the person already recognises. The offer doesn’t need to convince. It arrives as the obvious next step.
That’s a different page. Same sections. Completely different job.
And it reads differently too. Not like a sales page. Like a conversation with someone who already understands.
That’s what the DAC Sales Page Architect builds.
Not a better version of the page that’s doing three jobs. A page with one job, built to do that job completely.
The Bot
Your turn.
The Bot: https://poe.com/DAC_SalesPage_Arch?invite_code=5b5993c9-1fe6-4a65-9e40-d69c3e2cd012
What the bot needs to work
Three things. Each one makes the page sharper.
1. Your buyer’s private language. Not how you describe their problem. How they describe it to themselves, at 2am, when nobody’s watching. The words they’d never use in a meeting but that live rent-free in their head. This is what makes someone read your page and think “how did they know that?” Without it, the page sounds like you. It needs to sound like them.
2. A clear picture of what your offer needs to do. Not what it includes. What it needs to accomplish, step by step, inside the mind of the person reading. Which doubts it needs to dissolve. Which fears it needs to address. In what order. This is what keeps the page from jumping to the offer before the person is ready for it.
3. The specific job this page has in your sequence. What state is the person in when they arrive? What needs to be true when they leave? A page built without knowing this tries to do everything. A page built with this does one thing precisely.
If you’ve been with this newsletter since Week 1, you already have all three. Your Avatar Intelligence Dossier (Week 1), your Offer Brief (Week 2), and your Asset Architecture (Week 3) are exactly these three things, in document form, ready to paste in.
What if you haven’t run the first three bots yet?
You can run this bot with a paragraph about your offer and your audience.
It will produce something. Better than what most people build on their own.
But here’s the honest answer.
The reason your current page is doing three jobs is because it was built without knowing what job it was supposed to do. Giving the bot the same surface-level input produces a cleaner version of the same problem.
The three upstream documents aren’t homework. They’re the difference between a page that describes your offer and a page that creates a decision.
If you haven’t run the first three bots yet, start there. Each one takes 20–45 minutes. Each output feeds the next. By the time you bring all three to this bot, the page it builds fits into a sequence that’s already been working on your prospect, before they ever arrive.
The Prompt Sequence
Prompt 1: Submit your three documents.
I’m going to give you three documents simultaneously.
Document 1 — my buyer’s language and psychology: [Avatar Intelligence Dossier - attached]
Document 2 — my offer architecture: [Offer Brief - attached]
Document 3 — my asset map and page brief: [Asset Architecture - attached]
Confirm receipt of all three. Tell me which page to build first and why. Show me the entry state of the prospect when they arrive and the exit state the page needs to produce. Don’t start building yet.
Prompt 2: Show me the plan before you write.
Before writing any copy, show me the full plan: the awareness level of the prospect, the exact language you’re pulling from the dossier, the doubts this page needs to dissolve, and the headline sequence from top to bottom. I want to confirm everything before we proceed.
Prompt 3: Build the page.
Plan confirmed. Build the complete page from opening through call to action. Write what skimmers see and what buyers read. Include design notes for every section. Run the quality check before delivery. I want the finished page, not a draft.
What comes back
A complete page. Ready to use.
Every section written twice. Once for the person who skims: the headlines, subheads, and opening lines that tell the full story on their own. Once for the person who reads everything: the full paragraphs, the calculations, the moments that create the shift.
Design notes for every section. What the page needs to feel like at each point. What to avoid. What would undermine the copy’s job.
A quality report. Every check the bot ran before handing it to you. If anything didn’t pass, it was fixed first. You get the finished version, not a draft with notes.
What’s coming next
You now have the page that confirms the decision. The Post-Purchase Onboarding Sequence (Week 4) protects the decision after it’s made. Both are built.
But there’s a gap in the middle that most people never fill.
The sales page confirms a decision. It doesn’t create one. For cold traffic, people who don’t know you yet, sending them directly to a sales page asks them to go from “I’m fine” to “I’m buying” in one scroll. That’s the three-jobs problem Tuesday named. And the page, no matter how well it’s built, can’t do it alone.
Next Tuesday: the asset that does the decision-completion work upstream, so that by the time the right person reaches your sales page, they’ve already decided. Next Thursday: the bot that builds it.
Before you close this, open your current sales page.
Read the first paragraph.
Ask one question: is this written for someone who has already decided something needs to change, or for someone who hasn’t decided anything yet?
You’ll know immediately. And you’ll understand exactly what changes when the page has one job instead of three.
— Razvan