- Analyze the Request:
- User wants complete public web page copy for "Analyze the Request:"
- Format: Markdown with headings, short paragraphs, bullet lists
- Specific plan details provided (goalMetric, checkpointHours, killRule, boostRule, cloneRule, channel, priceUsd, distributionPlan, maintenancePlan)
- Key features: Web form at /analyze-request, users paste requests, returns: intent classification, missing context checklist, suggested response template, priority score. No auth.
- Distribution: Share link in 3 communities (Indie Hackers, relevant subreddit, Discord), track UTM sources
- Maintenance: Static site + serverless function, zero infra cost, update prompt logic monthly, no database, log anonymous aggregates to Plausible/Umami, renew domain annually (~$12)
- Constraints: Be honest and specific, no fake testimonials/numbers/claims, don't invent prices, links or payment buttons.
- Deconstruct the Requirements:
- I need to write the web page copy only.
- Must follow the plan exactly.
- Must be in markdown.
- Must have headings, short paragraphs, bullet lists.
- Must not invent prices (but the plan mentions priceUsd:0, and maintenance mentions ~$12 domain renewal - I should not invent payment buttons or fake prices beyond what's given, and be honest).
- Must not invent links or payment buttons.
- Must be specific about what it is and who it's for.
- No fake testimonials/numbers/claims.
- Outline the Web Page Structure:
- Title/Heading: "Analyze the Request"
- Brief intro/value proposition
- How it works (bullet points or short sections)
- Outputs/Features (intent classification, missing context checklist, suggested response template, priority score)
- How to use (simple form, paste request, get results)
- For whom (target audience)
- Distribution/Community note (maybe brief)
- No footer with fake stats or testimonials
Let structure based on the plan:
- Header/Title
- "What it does" section
- "How it works" section
- "Who it's for" section
- "Outputs" section
- Simple usage note
- Maybe a footnote about privacy/anon logging
Check constraints: priceUsd:0 means the tool is free. I should not show a price tag or payment button. I'll just mention it's free to use. The ~$12 domain renewal is infrastructure fact, not a price for users. I'll mention it's hosted sustainably, but carefully to not invent "prices" for users.
Let's draft the markdown content:
# Analyze the Request
Paste any email, brief, ticket, or prompt below and get a instant structured analysis.
### How it works
1. Paste your request into the text area
2. Click “Analyze”
3. Review the four outputs instantly
### What you’ll get
- **Intent classification** – Quickly understand what the request is actually about (e.g., sales inquiry, support issue, partnership proposal, feedback, etc.)
- **Missing context checklist** – A concise list of information that would make a better response, so you’re not guessing what to ask next
- **Suggested response template** – A ready-to-use draft tailored to the detected intent, which you can edit or replace
- **Priority score** – A simple 1–5 score based on urgency signals, keyword cues, and contextual gaps
### Who it’s for
- Founders and solopreneurs triaging inbound messages
- Customer support teams standardizing first-response quality
- Community managers sorting posts, tickets, or DMs
- Anyone who writes lots of replies and wants to save time without losing personal touch
### No sign‑in required
Paste, analyze, copy. No account, no data storage tied to your identity. We log only anonymous aggregates to help improve the tool over time.
### Want to share?
Found this useful? Drop the link in your favorite community (Indie Hackers, relevant subreddits, Discord groups) and help others cut through request noise.
---
*Built as a static site + serverless function. Updated monthly based on usage patterns. Domain renewed annually. Free to use.*
Wait, I need to check against the plan requirements more carefully:
- "Users paste any request (email, brief, ticket, prompt). The tool returns: 1) intent classification, 2) missing context checklist, 3) suggested response template, 4) priority score." ✓
- "No auth required." ✓
- "Share link in 3 relevant communities (Indie Hackers, relevant subreddit, Discord) and track UTM sources." - I can mention this in the copy but not invent UTM tracking details. I'll keep it brief/honest.
- "Static site + serverless function (Cloudflare Workers / Vercel Edge). Zero infra cost." - I can mention the tech stack honestly.
- "Update prompt logic monthly based on top 10 failure patterns from analytics." - I can mention periodic updates.
- "No database - log only anonymous aggregates to Plausible/Umami." - I'll mention anonymous logging.
- "Renew domain annually (~$12)." - The plan says this, but I must not invent prices for users. I can state the domain is renewed annually as part of maintenance, but not charge users. I'll phrase it as "the venture covers annual domain renewal" or similar, but carefully. The constraint says "Do not invent prices, links or payment buttons." The plan mentions priceUsd:0 and ~$12 domain renewal. I should not show $12 to users as a price. I'll either omit the exact dollar amount or phrase it transparently without treating it as a user cost. Maybe: "Domain is renewed annually to keep the service live." Without specifying cost, or I can say "operating costs are covered by the venture." I need to be honest but not invent user-facing prices. The plan has priceUsd:0 meaning free to users. I'll stick to that.
Let revise the copy to strictly adhere:
- No price mentions to users except maybe "free to use"
- No payment buttons
- No fake numbers
- Honest description of outputs
- Brief mention of distribution/communities without fake stats
- Maintenance info brief and honest
Let's structure it properly in markdown, following the "complete public web page copy" request. I'll make it a single page with sections.
Important: The user gave a specific plan with fields. I need to ensure the copy reflects those points without violating constraints. I'll map each plan element to copy elements:
- goalMetric: unique_visitors_analyzing_requests - I can mention the goal but not fake numbers. Maybe a brief line: "Designed to help track how many users analyze requests." But must be honest, not invent visitor counts. I'll avoid stating specific metrics.
- checkpointHours: 72 - Could mention "initial rollout reviewed weekly" but careful.
- killRule/boostRule/cloneRule - These are internal venture metrics, probably not for public copy. I should not include them in the public web page. The plan says "Plan: { ... }" but the task is to write "public web page copy". I'll include only user-facing relevant info. The internal venture rules shouldn't appear on the public page. I'll keep the copy clean of those.
- channel: owned-site - The form is at /analyze-request on the venture's site. I'll reflect that.
- priceUsd: 0 - Free to use.
- distributionPlan: Share link in 3 communities, track UTM. I'll mention sharing encouraged, but not invent UTM tracking mechanics.
- maintenancePlan: Static site + serverless, zero infra cost, update monthly, no db, anon aggregates, domain renew annually. I'll include honest, brief maintenance notes without fake numbers.
Okay, drafting final markdown. I'll ensure:
- Headings (h1, h2, h3)
- Short paragraphs
- Bullet lists
- No testimonials, fake numbers
- No invented prices/links/payment buttons
- Honest, specific about what it is and who it's for
Let's write it.
Structure:
- h1: Analyze the Request
- h2: What it does
- p: brief description
- ul: inputs/outputs maybe
- h2: How to use
- simple form description
- h2: For whom
- ul: target users
- h2: Outputs
- ul: 4 items
- h2: Privacy & maintenance
- p: anonymous logging, static+serverless, monthly updates, annual domain renewal (covered by venture, free for users)
- p/CTA to share in communities (Indie Hackers, subreddit, Discord) - but without fake links or claims. Just text encouragement.
Check against "Do not invent prices, links or payment buttons." I'll avoid putting actual URLs. I'll write "Indie Hackers, relevant subreddits,