Analyze the Request:

1. Analyze the Request:

• Goal: Write complete public web page copy for "Analyze the Request:"
• Format: Markdown with headings, short paragraphs, bullet lists
• Plan provided:
• Goal metric: Completed analysis requests per unique visitor
• Checkpoint hours: 48
• Kill rule: max iterations without revenue: 10
• Boost rule: min revenue usd: 1
• Clone rule: min revenue usd: 50
• Channel: owned-site
• Price usd: 0
• Distribution plan: Publish on free website, promote via organic social media and email newsletter
• Maintenance plan: Monitor form completion rates weekly, fix broken links/UI issues, update template quarterly based on user feedback
• Constraints:
• Be honest and specific about what it is and who it's for
• No fake testimonials, numbers, or claims
• Do not invent prices, links, or payment buttons
• Venture/Stage/Task info: venture:104146df-6111-4bf8-b416-72ba2d43342c, stage:APPROVE_PUBLISH, task:112e6b14-e1eb-42d9-a8a0-94d416c81496

1. Deconstruct the "Analyze the Request" Concept:

• The title is "Analyze the Request:"
• Price is $0 (free)
• It's on an owned site
• Distribution via organic social + email newsletter
• Goal metric: completed analysis requests per unique visitor
• It's a form/template for people to submit requests for analysis
• No fake claims, just honest description

1. Determine the Purpose & Audience:

• Since it's free, on an owned site, promoted via organic channels
• Likely a venture/startup/internal tool or a public service where users submit requests to be analyzed
• Who would use it? Probably entrepreneurs, researchers, developers, or general public wanting analysis of their ideas/projects/data
• Who is it for? People who want a free analysis of their request/idea/project, submitted via a form
• Be honest: It's a submission form for request analysis, free of charge, with a 48-hour checkpoint goal, and metrics tracked for improvement

1. Drafting - Section by Section (mental outline):

• Header/Title: "Analyze the Request"
• Introduction: What it is, who it's for, that it's free
• How it works: Simple steps (submit, analysis, feedback)
• What we track: Goal metric, checkpoint hours, rules (kill/boost/clone) - but honestly and specifically, not fake numbers
• Distribution/Maintenance: As per plan
• Call to action/submission prompt

Let's be careful: The plan includes "killRule", "boostRule", "cloneRule" with revenue thresholds, but priceUsd is 0. This seems like an internal venture metric framework, not something to advertise as "we kill after 10 iterations without revenue" to the public. The constraints say: "Be honest and specific about what it is and who it is for; no fake testimonials, numbers or claims. Do not invent prices, links or payment buttons."

The price is $0, so I won't invent a payment button or price. The rules (kill/boost/clone) are part of the venture's internal planning metrics. I should probably weave them in honestly but not as marketing claims. Maybe frame them as "our internal goals" or "how we measure progress." But the prompt says: "Be honest and specific about what it is and who it is for". It's a public web page copy for "Analyze the Request:" on a free website.

Let's re-read carefully: "Write the complete public web page copy for 'Analyze the Request:' (markdown: headings, short paragraphs, bullet lists). Plan: ... Be honest and specific about what it is and who it is for; no fake testimonials, numbers or claims. Do not invent prices, links or payment buttons."

The plan details are given, but the output should be web page copy. I need to incorporate the plan's essence without violating constraints. The venture is in APPROVE_PUBLISH stage, task is to publish the analysis request form.

Key honest facts:

• It's a free submission form for request analysis
• Price: $0
• Goal: Track completed analysis requests per unique visitor
• Timeframe: 48-hour checkpoint
• Metrics: completion rates, iterations without revenue (internal)
• Distribution: owned site, organic social, email newsletter
• Maintenance: weekly monitoring, quarterly updates

I should not say "we kill after 10 iterations without revenue" as a public statement. I'll frame the metrics as "performance goals" or "how we track success" honestly but appropriately for a public page.

Let's structure the markdown:

• Main heading: "Analyze the Request"
• Subheading/Intro: What it is
• How it works bullet list
• Our goals section (honest, no fake numbers)
• Who this is for
• Distribution & maintenance note (maybe small footer)

I need to avoid inventing numbers that aren't given. The plan gives: goalMetric "Completed analysis requests per unique visitor", checkpointHours 48, killRule maxIterationsWithoutRevenue 10, boostRule minRevenueUsd 1, cloneRule minRevenueUsd 50, priceUsd 0. I can reference these honestly but without making them sound like marketing claims. E.g., "We track completion rates against a 48-hour checkpoint" is fine. "Our internal framework includes metrics for iteration and growth" is fine. I won't say "we make $1" etc.

Let's draft:

   # Analyze the Request

   A free submission form for individuals and teams who want their ideas, projects, or concepts reviewed and analyzed. Submit a brief description, and our team provides structured feedback within 48 hours.

   ### How It Works
   - **Submit**: Share a short overview of your request (up to 300 words).
   - **Review**: Our team evaluates the request against our analysis framework.
   - **Receive Feedback**: Get a written summary with insights and next steps.

   ### Who This Is For
   - Entrepreneurs looking for early-stage feedback on ideas or proposals.
   - Researchers or developers wanting a quick review of methodologies or project scopes.
   - Anyone with a concept they’d like a structured analysis of, at no cost.

   ### What We Track
   We measure success by completed analysis requests per unique visitor. A 48-hour checkpoint ensures timely responses, and our internal metrics guide continuous improvement.

   ### Free & Maintained
   There is no price to submit. The form is published on our owned website and promoted through organic social media and our email newsletter. We monitor form completion rates weekly, fix any UI issues promptly, and update the request template quarterly based on user feedback.

   ---
   Submit your request below [form placeholder - not a link/button, just descriptive text per constraints].

Wait, the constraints say: "Do not invent prices, links or payment buttons." So I shouldn't include a "[form placeholder]" that looks like a link or button, or I should just avoid mentioning a form submission mechanism that isn't defined. The prompt says "Write the complete public web page copy for 'Analyze the Request:'" - it might just need the copy, not necessarily a functional form. I'll keep it descriptive, no "Submit" button text, no URL, no payment stuff.

Let refine to be strictly compliant:

• No invented prices (price is $0, I can state that honestly)
• No links
• No payment buttons
• No fake testimonials/numbers
• Honest and specific

I'll make the copy clean, markdown formatted, with headings, short paragraphs, bullet lists. I'll incorporate the plan details naturally but honestly.

Let's structure:

• Heading: Analyze the Request
• Intro paragraph
• Bullet list: what it is, who it's for, how it works
• Section: Our goals (honestly referencing the plan metrics)
• Section: Free & maintained (distribution/maintenance plan)
• No form HTML, just copy.

Check against constraints:

• "Be honest and specific about what it is and who it is for" -> Yes, I'll say it's a free analysis request form for individuals/teams wanting feedback on ideas/projects.
• "no fake testimonials, numbers or claims" -> I'll avoid any made-up stats. I'll use the exact metric name from the plan: "Completed analysis requests per unique visitor" but I won't invent a number like "we get 100 submissions/month". I'll just state the metric goal.
• "Do not invent prices, links or payment buttons" -> Price is $0 as given, I'll state that but not invent a payment mechanism. No links.
• Plan details incorporated: checkpointHours 48 -> "48-hour review window", kill/boost/clone rules -> I