1. BRIEF DIAGNOSIS Primary objective: Create reusable instructions for writing a conversion-focused homepage for an early-stage invoicing application. Intended audience: English-speaking freelancers and independent consultants who need a straightforward way to create, send, and monitor invoices. Facts that must be preserved: - Branded invoice templates - Automatic total calculations - PDF export - Payment status tracking - Recurring invoice reminders Information that must not be invented: - Customer testimonials - Performance statistics - Payment integrations - Accounting integrations - Guaranteed payment speed Conservative assumption: The primary homepage conversion goal is encouraging the visitor to start using the product or explore the product further. The exact CTA wording should remain editable. Success criteria: The copy is clear, scannable, benefit-focused, credible, and based only on verified product capabilities. 2. PROMPT ARCHITECTURE BLUEPRINT Expert role: SaaS conversion copywriter with experience writing credible early-stage product pages. Execution sequence: 1. Review supplied product facts. 2. Separate verified capabilities from assumptions. 3. Identify the audience’s likely workflow problems without presenting them as researched facts. 4. Build the homepage message hierarchy. 5. Write every required section. 6. Run a claims and consistency check. 7. Deliver clean homepage copy. Output contract: Hero, problem, benefits, features, three-step process, FAQ, final CTA, and claims check. Failure controls: The prompt must label missing facts, avoid invented proof, and omit unsupported product capabilities. 3. PRODUCTION PROMPT Act as a senior SaaS conversion copywriter who specializes in clear, credible homepage messaging for early-stage software products. Create conversion-focused homepage copy using the following inputs: Product name: <PRODUCT_NAME> Product summary: <PRODUCT_SUMMARY> Verified features: <VERIFIED_FEATURES> Target audience: <TARGET_AUDIENCE> Primary conversion action: <PRIMARY_CTA> Brand tone: <BRAND_TONE> Additional restrictions: <RESTRICTIONS> Before writing, separate the supplied information into: - verified product facts; - reasonable audience assumptions; - missing information. Do not present assumptions as research findings. Develop the page in this order: 1. Hero section - One clear headline - One supporting subheadline - One primary CTA - One optional low-friction secondary CTA 2. Problem section - Describe the audience’s invoicing workflow frustrations carefully - Do not exaggerate consequences - Do not claim every customer experiences the same problem 3. Benefits section - Provide three to five outcome-focused benefits - Connect each benefit to a verified feature 4. Features section - Explain every verified feature in plain language - Do not introduce unlisted integrations or capabilities 5. How it works - Explain the product in three simple steps - Keep the process credible and easy to scan 6. FAQ - Write five useful questions and answers - If an answer requires unavailable information, use <CONFIRM WITH PRODUCT OWNER> instead of inventing it 7. Final CTA - Restate the main practical value - Use a direct but non-aggressive invitation 8. Claims check Create a final table with: - claim; - supporting supplied fact; - status: verified, assumption, or confirmation needed. Writing requirements: - Use concise English. - Prefer specific benefits over broad hype. - Do not invent testimonials, statistics, guarantees, integrations, awards, or comparisons. - Do not claim the product makes customers pay faster. - Keep paragraphs short and headings scannable. - Make the completed copy ready for a website editor. 4. QUICK PROMPT Write a clear, conversion-focused homepage for <PRODUCT_NAME>, an invoicing application for <TARGET_AUDIENCE>. Use only these verified features: <VERIFIED_FEATURES> Include: - hero headline and subheadline; - primary CTA; - problem section; - three to five benefits; - feature explanations; - three-step process; - five FAQs; - final CTA. Use a modern, trustworthy tone. Do not invent testimonials, statistics, integrations, guarantees, or performance claims. Mark missing product information as <CONFIRM WITH PRODUCT OWNER>. End with a short claims check. 5. INTERACTIVE PROMPT Act as a SaaS homepage copywriter. Before writing, ask no more than five questions: 1. What is the product name? 2. What exact action should the visitor take? 3. Which features are currently available? 4. What tone should the brand use? 5. Are there any claims or capabilities that must not be mentioned? After receiving the answers, create a hero, problem section, benefits, features, three-step explanation, FAQ, and final CTA. When an answer is missing, state the assumption and continue. Never invent testimonials, statistics, integrations, or guaranteed results. 6. VARIABLE GUIDE <PRODUCT_NAME> Required. Enter the public name of the software. Good: ClearBill Weak: My app <PRODUCT_SUMMARY> Required. Explain the product in one factual sentence. Good: A browser-based tool for creating and tracking branded invoices. Weak: The best invoicing solution ever. <VERIFIED_FEATURES> Required. List only currently available capabilities. Good: PDF export, invoice templates, payment status tracking. Weak: Everything freelancers need. <TARGET_AUDIENCE> Required. Define a specific buyer group. Good: Independent consultants and freelance designers. Weak: Everyone. <PRIMARY_CTA> Required. State the action the visitor should take. Good: Create your first invoice. Weak: Click here. <BRAND_TONE> Optional. Describe the communication style. Good: Clear, calm, and modern. Weak: Make it amazing. <RESTRICTIONS> Optional. List claims or subjects that must be avoided. Good: Do not mention integrations or guaranteed payment speed. Weak: No bad writing. 7. RELIABILITY TEST Normal Case: The prompt receives complete product facts and produces every homepage section. All feature claims remain traceable to supplied information. Sparse Case: The prompt receives only a product summary and audience. It labels missing features and CTA details rather than inventing them. Unavailable FAQ answers use <CONFIRM WITH PRODUCT OWNER>. Conflict Case: The user requests “aggressive hype” but also prohibits unsupported claims. The factual restriction takes priority. The prompt can use energetic wording without creating false proof or guarantees. 8. QUALITY SCORE Clarity: 5/5 Controllability: 5/5 Completeness: 5/5 Factual safety: 5/5 Output consistency: 5/5 Practical usability: 5/5 No revision required. 9. REFINEMENT COMMANDS 1. Make the copy 30% shorter while preserving every section. 2. Add more audience-specific language for freelance consultants. 3. Make the tone warmer without adding hype. 4. Create a more premium version of the hero section. 5. Strengthen the factual safeguards and claims check. 6. Produce three alternative hero directions for A/B testing.