Design the product and write the grading prompt

Write your one-sentence product description

Open your notes app and write this sentence, filling in the blanks for your product.

• Fill in this template: "My tool helps [WHO] do [WHAT] so they can [OUTCOME]."
• Your answer: "My tool helps non-developer founders grade their landing page copy so they can improve it before sharing it with the world."
• This sentence is not marketing fluff — it is the decision-making filter for every feature you will build or skip.
• If a feature does not serve this sentence, it does not belong in Version 1.
• Write it at the top of your notes doc. You will look at it every day this week.
• You will also use this sentence as your landing page headline on Day 7.

Define the four elements you will grade

In your notes, write down the four elements of a landing page your tool will grade, and what makes each one good vs bad.

• Element 1 — Headline: one sentence that names the benefit, not the feature. Good: "Grade your landing page copy in 30 seconds." Bad: "AI-powered copywriting tool."
• Element 2 — Subheadline: one or two sentences that explain who it is for and what happens when they use it. Good: "Built for non-developer founders who just shipped something and want real feedback, not compliments."
• Element 3 — CTA button text: 3–6 words that describe the action. Good: "Grade my copy free." Bad: "Submit" or "Click here."
• Element 4 — Feature bullets: 3–5 lines that each name one specific outcome the user gets, not a feature the product has. Good: "Find out if your headline describes a benefit or just a feature." Bad: "AI-powered analysis."
• Write a short example of GOOD and BAD for each of the four elements in your notes.
• This matters because the AI grader needs to know what it is judging against. Vague criteria produce vague scores.
• You are building a grader, not a rewriter. The AI gives scores and suggestions — the user makes the changes. That is Version 1.

Write the system prompt that powers the grader

This is the most important thing you will do all week. Write the exact instruction you will give Claude inside your app.

• Copy this system prompt word for word into your notes:
• "You are a conversion copywriter reviewing a non-developer founder's landing page copy. Grade each of the four elements below on a scale of 1 to 10. For each element give: the score, one sentence explaining why you gave that score, and one specific rewrite suggestion. Be honest, not encouraging. A score of 7 or above means it is working. A score below 5 means it needs a full rewrite. Format your response exactly as shown:"
• "HEADLINE SCORE: X/10\nWhy: [one sentence]\nRewrite: [your suggestion]\n\nSUBHEADLINE SCORE: X/10\nWhy: [one sentence]\nRewrite: [your suggestion]\n\nCTA SCORE: X/10\nWhy: [one sentence]\nRewrite: [your suggestion]\n\nBULLETS SCORE: X/10\nWhy: [one sentence]\nRewrite: [your suggestion]\n\nOVERALL SCORE: X/10\nTop priority fix: [one action item]"
• The phrase "Be honest, not encouraging" is doing a lot of work. Without it, Claude will be too kind and the scores will be useless.
• The strict format matters — on Day 3 you will parse this output and display each section as a separate card in the UI.
• Do not change the format yet. Test it first, then adjust if needed.

Test the prompt on a real landing page in Claude

Go to claude.ai and test your system prompt against a real page before writing any code.

• Open a new Claude chat at claude.ai.
• Start your message with the system prompt you just wrote, then add a blank line.
• Below it, paste the four elements from a real landing page — use your own site, NonDevApps.com, or any product page you know.
• Format your input exactly like this: "Headline: [paste headline]\nSubheadline: [paste subheadline]\nCTA: [paste button text]\nFeature bullets:\n[paste each bullet on its own line]"
• Send the message and read every word of the output.
• Ask yourself three questions: Is this honest? Is it specific? Would I pay $15/month to know this for every page I build?
• If the answer to any of those three is no, adjust the system prompt and test again.
• Test on at least two different landing pages before moving on. Consistency across inputs matters.
• If every score is above 7, the prompt is being too kind. Add this line: "Most first-draft landing page copy scores between 4 and 6. Do not inflate scores."

Write your launch plan before you build anything

Write three sentences in your notes before you close today. Founders who plan distribution before they build ship faster.

• Sentence 1: The one community or platform I will share this on when it launches. (Not "social media" — a specific subreddit, Discord, Slack, LinkedIn group, or email list.)
• Sentence 2: The message I will post when I get my first real paying subscriber.
• Sentence 3: The first person outside my friends and family who has this problem and would use this tool.
• Good answers are specific: "I will post in r/SideProject and r/indiehackers" not "I will share online."
• r/SideProject, r/indiehackers, r/webdev, and Product Hunt are all strong launch platforms for this type of tool.
• You do not need to act on this today. You need to write it down so you are not figuring it out on Day 7 when you are tired and excited and just want to ship.
• The best product launch posts include: what you built (one sentence), who it is for (one sentence), a link, and an offer to give something free in the comments.