TL;DR
- Use Grok 4.5’s Canvas as a live document, not a chat, so the page and the conversation stay separate.
- Feed it a fixed prompting pattern: audience, offer, proof, and section-by-section spec.
- Draft the full page in one sitting instead of trading paragraphs across a chat thread.
- Export the Canvas and hand it to your other AI tools for revisions, so the draft never lives only in chat history.
A client asked for a landing page on a Tuesday and wanted it by Friday. I had the offer clear in my head but nothing on a screen, and the usual move was a blank document I’d avoid for an hour.
Most landing-page work starts as a prompt dropped into a chat window. You get a wall of text back, you argue with it line by line, and the version you actually wanted disappears three revisions deep. The chat thread becomes the only record of what you decided, so next month’s refresh costs you the same hour all over again.
Why Canvas changes the draft
Grok 4.5’s Canvas keeps the page and the conversation in two different places. You write and edit the document on one side, and you talk to Grok about it on the other. That sounds minor until you realize your landing page is no longer buried under forty messages about whether the headline should say “trusted” or “proven.”
The Canvas holds the current best version at all times. When you ask for a change, Grok edits the document in place instead of printing a new block of text you have to copy out by hand. That single difference is what makes a one-sitting draft possible, because you stop上下文 switching between reading chat and rebuilding the file.
I used to think the bottleneck was writing the copy. It wasn’t. It was the overhead of moving words from the chat to the doc and back. Canvas removes that hop, which is the kind of small thing that saves more time than any “prompt hack” people sell.
The prompting pattern
The draft only comes fast if you give Grok a structure up front. A scattered brief produces a scattered page, and then you spend the sitting fixing the structure instead of the words. I use the same four-part spec every time.
First, the audience. One sentence on who this page is for and what they’re trying to do. Second, the offer. What the client is selling and what the reader gets. Third, the proof. The specific result, number, or credential that makes the claim believable. Fourth, the section list. I name the sections I want in order: headline, problem, solution, proof, offer, call to action.
Giving those four parts before asking for a single sentence keeps Grok from inventing a frame you didn’t ask for. You’re briefing a contractor, not rolling dice.
Handing it to your AI team for revisions
Once the Canvas holds a real draft, the work shifts from creation to judgment. That’s the part your other AI tools are better at than you doing it alone. I export the Canvas as a file and drop it into my revision loop, where a second model checks the page against the brief and flags sections that drift from the offer.
This is where the “AI team” idea actually earns its keep. Grok drafts, a different tool reviews, and you make the calls. The draft lives in a file now, not in chat history, so the next person who touches it (including next-month you) starts from the page, not from a search through messages.
The revision handoff is also where client feedback gets cheap. Paste their notes into the reviewer tool with the export, and you get a marked-up version instead of a vague “make the tone warmer” that you have to interpret twice.
The Prompt
Here is the spec I paste into Canvas to start the draft. Replace the brackets with the client’s details.
You are drafting a landing page for a solo professional's client. Do not write filler or motivational language. Follow this brief exactly.
AUDIENCE: [one sentence: who this page is for and what they're trying to do]
OFFER: [what is being sold and what the reader receives]
PROOF: [the specific result, number, or credential that backs the claim]
SECTIONS (in this order):
1. Headline (one line, no cliche)
2. Problem (what the reader is stuck on)
3. Solution (how the offer fixes it)
4. Proof (the evidence from above, stated plainly)
5. Offer (what to do and what it costs)
6. Call to action (one clear next step)
Write each section as finished copy, not bullets. Keep sentences short. Flag any section where the brief is too thin to write confidently.Take It Further
The packaged version of this pattern, including the revision-loop setup and the brief template I reuse for every client, is in the SoloBuilt kit catalog. Every workflow I document lands in The Dispatch first, so that’s the place to catch the next one before it’s written up here.