Copy pack
Build from the verified source Master Prompt and Build Contract for the waitlist landing starter. Preserve the demo, proof honesty, pricing boundary, FAQ, and form states.
Master Prompt Build Contract
Master Prompt
# Master Build Prompt: BuildPilot Waitlist
Build BuildPilot Waitlist as a landing-page starter product for an AI meeting notes tool. The starter should feel like opening a premium SaaS editorial waitlist page first: a confident hero, a transcript stream that resolves into a decision rail, audience segment controls, a three-step how-it-works section, Free/Pro pricing selection, placeholder proof, FAQ accordion, and a bottom email waitlist form with validation, loading, and success states.
Product purpose:
- Explain BuildPilot as an AI meeting notes tool that turns conversations into clear decisions, owners, and follow-ups.
- Help a visitor understand the promise, choose whether the Free or Pro positioning fits, read honest FAQ answers, and request early access.
- Keep the page honest: proof stays placeholder until real quotes exist, and pricing stays positioning only.
Required facts to preserve:
- BuildPilot is a landing page, not an app dashboard, meeting recorder, CRM, checkout, or standalone form app.
- The hero must explain the value proposition clearly.
- The page includes a notes-to-decisions demo showing raw meeting notes becoming decisions, owners, and follow-ups.
- Audience segment controls for Product teams, Client services, and Ops leaders change the headline, demo output, and waitlist context.
- Include a three-step how-it-works section: capture notes, extract decisions/owners, send clear next steps.
- Include Free and Pro pricing cards as static positioning only, with Free/Pro pricing selection state.
- Testimonials must be clearly labeled placeholder proof only.
- Include a short FAQ accordion.
- Put the bottom email waitlist form at the end of the page and cover missing email, invalid email, loading, and success states.
UI style and color tokens:
- Overall surface: premium SaaS editorial landing page, useful and direct rather than a generic blue template.
- Page background #F4F7FB, product surface #F8FBFF, primary ink #12213A, primary action blue #2F63D8, warm attention #F4B95F, border #D8E0EE, muted panel #EDF3FF.
- Use 8px radius cards, dense but readable SaaS spacing, clear keyboard focus, restrained shadows, dark ink hero contrast, warm amber attention, and lucide-style icons for notes, audience, FAQ, waitlist, reset, and copy actions.
- The signature visual is the notes-to-decisions demo: a transcript stream beside a decision rail, with numbered placeholder note lines becoming concrete Decision, Owner, Follow-up, and Blocker outputs. Do not replace it with a fake screenshot, hero illustration, dashboard, or decorative scene.
Required layout:
- Open with the BuildPilot product preview first, not a Build Companion walkthrough.
- Use available browser width for the landing page preview.
- Top bar: BuildPilot mark, section buttons for Demo, Pricing, FAQ, Waitlist, and Reset.
- Hero/demo: dark premium hero canvas, headline, short explanation, primary waitlist action, secondary demo action, audience segment controls, proof-boundary strip, transcript stream, extracted decision rail, and clear placeholder-data labeling.
- Middle band: three-step how-it-works cards and Free/Pro pricing cards. Pricing cards are buttons and selecting one changes the selected plan state and waitlist context.
- Proof/FAQ: placeholder proof slots labeled as empty until real proof exists, plus FAQ accordion with only one open answer at a time.
- Bottom waitlist: work-email input, Request access button, missing-email validation, invalid-email validation, submitting/loading message, success message, and selected audience/plan context.
- Copy rail: visible tabs only for Master Prompt and Build Contract. Do not show Step Guide, repo bundle, QA/Fix walkthrough, dashboard metrics, or extra product modes on the migrated route.
Interaction rules:
- Section buttons change the active section indicator and waitlist context.
- Audience segment controls change the hero headline, supporting copy, raw meeting notes, extracted follow-up, and waitlist context.
- Free/Pro pricing selection changes the selected plan label and waitlist context without adding checkout.
- FAQ buttons expand the selected answer and collapse the previous answer.
- Bottom email waitlist validates empty and invalid email, shows a loading message while submitting, then shows a joined-success state.
- Reset restores Product teams, Free plan, Demo section, default FAQ, empty email, and idle form state.
State model:
- Audience states: Product teams, Client services, Ops leaders.
- Plan states: Free selected, Pro selected.
- FAQ states: pricing, placeholders, privacy/meeting-data answer.
- Waitlist states: empty, invalid, submitting, joined.
- Demo data states: raw notes and extracted follow-up remain schematic placeholders.
Demo data shape:
- Use short placeholder meeting-note snippets with fictional first names only.
- Extracted output should include Decision, Owner, Follow-up, and Blocker lines where relevant.
- Label proof and demo notes as placeholder content.
- Do not imply real meeting data, real customers, real logos, real metrics, private transcripts, calendar access, recording, or production AI processing.
Acceptance criteria:
- The route opens as a product-like BuildPilot landing page with no Build Companion walkthrough.
- Master Prompt and Build Contract are the only visible copy tabs.
- Notes-to-decisions demo turns raw meeting notes into decisions, owners, and follow-ups.
- Audience segment controls visibly change the headline, demo output, and waitlist context.
- Free/Pro pricing selection changes selected plan state and does not add checkout.
- FAQ accordion changes the visible answer.
- Bottom waitlist form covers missing email, invalid email, loading, and joined-success states.
- Placeholder proof remains clearly labeled and does not invent testimonials, logos, customer names, or metrics.
- Preview and copy both preserve landing-page scope, meeting-notes intent, sections, states, and non-goals.
Non-goals:
- No fake proof, fake testimonials, fake customer logos, fake company names, fake user quotes, fake metrics, revenue numbers, productivity percentages, or social-proof claims.
- No checkout, Stripe, payment processing, billing flow, account creation, subscription management, or plan enforcement.
- No dashboard, app dashboard, meeting recorder, transcription backend, calendar integration, CRM, team workspace, analytics dashboard, AI agent runtime, or production meeting-data workflow.
- No real meeting data, private transcript storage, real customer data, privacy/security/compliance certification, or production readiness claims. 