30 ChatGPT Prompts That Build Waitlist Pages

You are a growth marketer who builds waitlists with a simple referral loop in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: join, then share to move up. Not a homepage. Not a paid checkout. </context> <inputs> - Product teaser: [PRODUCT] - Who it is for: [AUDIENCE] - Early perk: [PERK] - Referral mechanic: [MOVE UP THE LIST] - Share link placeholder: [SHARE LINK] - Proof I have: [COUNT, QUOTES, OR NONE] - Capture: [EMAIL] - Vibe: [MINIMAL / PLAYFUL] </inputs> <task> Build these sections: 1. Centered hero, promise, accessible email form, benefit-led button 2. You are number X microcopy slot I can wire later (do not invent a live count) 3. Three early-join bullets led by [PERK] 4. Proof strip from [COUNT, QUOTES, OR NONE] or [VERIFY] 5. Share to move up block with [SHARE LINK], a one-tap copy cue, and short how-it-works copy 6. Privacy line and minimal footer </task> <constraints> - Form first, share second. Sharing is not required to join. - Accessible labels. Single email field unless I asked for more. - Do not invent a live queue position or a waitlist total. - Mobile-first. One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then explain how to hook [SHARE LINK] and the position slot to a real waitlist tool.

You are a referral marketer who writes give-get waitlist pages in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: join with email, then share because both people get something. Not a multi-page site. </context> <inputs> - Product: [PRODUCT] - Audience: [AUDIENCE] - What the joiner gets: [YOUR PERK] - What the friend gets: [FRIEND PERK] - When the perk lands: [ON JOIN / ON LAUNCH / ON FIRST PAID] - Proof I have: [QUOTES, COUNT, OR NONE] - Share link placeholder: [SHARE LINK] - Voice: [WARM / DRY] </inputs> <task> Build these sections: 1. Hero that names [PRODUCT] and the give-get pair in plain words, plus an accessible email form 2. Two-column you get / they get cards using [YOUR PERK] and [FRIEND PERK] 3. When the perk actually lands, from [ON JOIN / ON LAUNCH / ON FIRST PAID], no fuzzy later 4. Proof strip or [VERIFY] 5. Share block with [SHARE LINK], copy cue, and a one-line example message I can paste to a friend 6. Short FAQ (is this required, when do they get it) 7. Privacy line </task> <constraints> - Joining does not require a referral. Sharing is the upside, not the door. - Do not invent a friend count or earnings. Mark gaps as [VERIFY]. - Honest about [ON JOIN / ON LAUNCH / ON FIRST PAID]. - One HTML file, accessible form, Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then say how to keep the example share message under 160 characters.

You are a launch marketer who writes milestone referral waitlists in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: email join, then share toward three unlocks I can keep. Not a points game and not a homepage. </context> <inputs> - Product: [PRODUCT] - Audience: [AUDIENCE] - Unlock at 1 share: [UNLOCK 1] - Unlock at 3 shares: [UNLOCK 3] - Unlock at 5 shares: [UNLOCK 5] - What happens if they share zero: [STILL GET] - Proof I have: [PROOF OR NONE] - Share link placeholder: [SHARE LINK] - Vibe: [PLAYFUL / CALM] </inputs> <task> Build these sections: 1. Hero with [PRODUCT], accessible email form, benefit-led button 2. What you get even at zero shares ([STILL GET]) so the form is worth it alone 3. Visual 1 / 3 / 5 unlock ladder using only the unlocks I gave 4. Proof strip or [VERIFY] 5. Share CTAs (copy link, plus a mailto or share-intent placeholder) using [SHARE LINK] 6. Honesty line: unlocks are tracked after I wire the tool, positions on this HTML are placeholders 7. Privacy line and footer </task> <constraints> - Do not invent a fourth unlock or a live progress bar with fake fills. - Form first. Ladder second. - Accessible labels. Do not require sharing to submit. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then list the three unlocks as a checklist I must be able to fulfill by hand if the tool is late.

You are a growth designer who builds waitlist pages with a share card in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: capture email, then make sharing one tap. Include proof I gave. Not a social network and not a multi-page site. </context> <inputs> - Product: [PRODUCT] - Audience: [AUDIENCE] - Early perk: [PERK] - Tweet or post line I approve: [SHARE COPY] - Text-message line I approve: [SMS COPY] - Share link placeholder: [SHARE LINK] - Proof I have: [PROOF OR NONE] - Vibe: [MINIMAL / BOLD] </inputs> <task> Build these sections: 1. Hero, accessible email form, benefit-led button naming [PERK] 2. After-join share card (styled as if it appears after submit, visible on the page as a demo state) using [SHARE COPY] and [SMS COPY] verbatim 3. Copy-link control on [SHARE LINK] with a simple JS or a clearly labeled button 4. Proof strip or [VERIFY] 5. Three early-join bullets 6. Privacy line. Minimal footer </task> <constraints> - Use my share lines. Do not punch them up with hype I did not write. - Vanilla JS is fine inside the single file for copy-to-clipboard. No frameworks. - Do not invent social counts. Mark gaps as [VERIFY]. - Form is still the primary action. The card is the referral teaser. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then note how to hide the share card until the form succeeds once I wire a real backend.

You are a B2B launch marketer who writes teammate-invite waitlists in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: one person joins with work email, then invites teammates. Proof I gave plus a referral teaser. Not a full SaaS homepage. </context> <inputs> - Product: [PRODUCT] - Buyer or champion: [ROLE] - What the workspace unlocks early: [WORKSPACE PERK] - How many teammate invites: [INVITE COUNT OR OPEN] - Capture fields: [WORK EMAIL, NAME, TEAM SIZE] - Proof I have: [LOGOS, QUOTES, OR NONE] - Share or invite link placeholder: [INVITE LINK] - Voice: [PLAIN / SHARP] </inputs> <task> Build these sections: 1. Hero aimed at [ROLE] with an accessible work-email form and a button that names [WORKSPACE PERK] 2. Personal spot vs workspace: one short honesty block 3. How teammate invites work, using [INVITE COUNT OR OPEN] 4. Proof strip from [LOGOS, QUOTES, OR NONE] or [VERIFY] 5. Invite teaser with [INVITE LINK] and a sample Slack or email blurb 6. Privacy and work-email note 7. Footer </task> <constraints> - Do not invent company logos or seat counts. - Keep fields to what I listed. Accessible labels. - Invite is optional. The form must work alone. - One HTML file. Google Fonts only. No site nav. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then say whether team size should stay on the form or drop.

You are a Product Hunt launch marketer who writes pre-hunt waitlist pages in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: collect emails before [PRODUCT] goes live on Product Hunt, show proof I have, and tease a share so supporters are ready. Not a hunt-day upvote page and not a full homepage. </context> <inputs> - Product one-liner: [PRODUCT] - Who should care: [AUDIENCE] - Hunt date if locked: [HUNT DATE OR SOON] - What list members get on hunt morning: [HUNT PERK] - Proof I have: [BETA QUOTES, METRIC, OR NONE] - Maker name: [MAKER] - Share teaser: [SHARE LINE] - Share link placeholder: [SHARE LINK] </inputs> <task> Build these sections: 1. Hero with [PRODUCT], hunt timing from [HUNT DATE OR SOON], accessible email form, button naming [HUNT PERK] 2. What happens on hunt morning in three steps 3. Proof strip or [VERIFY] 4. Short maker note signed as [MAKER] 5. Share teaser so people can bring one friend before the hunt, using [SHARE LINK] and [SHARE LINE] 6. Privacy line. Footer with a Product Hunt mention that does not claim a rank </task> <constraints> - Do not invent a Product Hunt rank, upvote goal, or featured badge. - Do not put a live Upvote button unless I also gave a live PH URL (I did not, so skip the button). - Form first. Share second. - One HTML file. Accessible. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then list the two fields to swap the morning you paste the real Product Hunt URL.

You are a Product Hunt launch designer who writes hunt-morning pages in ChatGPT. <context> Build one self-contained HTML page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Hunt day for [PRODUCT]. Two jobs: send supporters to the real Product Hunt listing, and capture email for people who want the product, not only the upvote. Include proof I gave and a share teaser. Not a homepage. </context> <inputs> - Product: [PRODUCT] - Live Product Hunt URL: [PH URL] - Hunt date: [HUNT DATE] - Email perk for people who want the product: [EMAIL PERK] - Proof I have: [QUOTES, METRIC, OR NONE] - Maker: [MAKER] - Share line: [SHARE LINE] </inputs> <task> Build these sections: 1. Thin hunt-day bar with [HUNT DATE] 2. Hero with [PRODUCT], a Support us on Product Hunt button that is a real link to [PH URL], plus an accessible email form for [EMAIL PERK] 3. What to do in 60 seconds (open PH, upvote, come back if you want the list) 4. Proof strip or [VERIFY] 5. Share teaser with [SHARE LINE] and a copy of [PH URL] 6. Maker thank-you line 7. Footer. No fake #1 badge </task> <constraints> - [PH URL] must be the upvote target. Do not invent a second store. - Do not invent live upvote counts. If I want a count slot, mark it [VERIFY] and label it as a slot. - Email form is for the product list, clearly separate from the PH button so it does not look like a fake upvote. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then say which button should be visually primary on a phone.

You are a maker who writes a Product Hunt waitlist with a real origin in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: email list for [PRODUCT], told as a maker story, with proof I gave and a referral teaser. Not a blog post and not a 12-section homepage. </context> <inputs> - Product: [PRODUCT] - Maker name: [MAKER] - Private origin detail: [PRIVATE DETAIL] - Who it is for: [AUDIENCE] - Hunt timing: [HUNT DATE OR SOON] - Proof I have: [PROOF OR NONE] - Email perk: [PERK] - Share link placeholder: [SHARE LINK] - Voice: [HUMAN / DRY] </inputs> <task> Build these sections: 1. Hero in [MAKER] voice, [PRODUCT], accessible email form, button names [PERK] 2. Short origin that uses [PRIVATE DETAIL] once, then the product job 3. Who this is for 4. Proof or [VERIFY] 5. Hunt timing honesty 6. Referral teaser with [SHARE LINK] 7. Sign-off as [MAKER]. Privacy line. Footer </task> <constraints> - Do not invent biography, funding, or a PH rank. - Keep the origin under a short scroll. This is still a waitlist page. - Form first. Story supports the form. - One HTML file. Accessible. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then name the one sentence that should stay if I have to cut half the story.

You are a Product Hunt maker who writes a hunter briefing page in ChatGPT. <context> Build one self-contained HTML page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Audience: people who will hunt or share [PRODUCT]. Capture their email so you can ping them on hunt morning. Include proof I gave and a referral teaser. Not a media kit PDF and not a homepage. </context> <inputs> - Product: [PRODUCT] - Three repeatable facts: [FACT 1], [FACT 2], [FACT 3] - Hunt date: [HUNT DATE OR SOON] - What you need from them: [UPVOTE / COMMENT / SHARE] - Email perk: [PERK] - Proof I have: [PROOF OR NONE] - Share link placeholder: [SHARE LINK] - Maker: [MAKER] </inputs> <task> Build these sections: 1. Hero: hunter briefing for [PRODUCT], accessible email form (ping me hunt morning), button names [PERK] 2. Three-fact share kit using [FACT 1], [FACT 2], [FACT 3], easy to copy 3. What you are asking for, from [UPVOTE / COMMENT / SHARE], no guilt 4. Proof or [VERIFY] 5. Referral teaser: bring one more hunter, [SHARE LINK] 6. Timing from [HUNT DATE OR SOON] 7. Footer signed [MAKER] </task> <constraints> - Do not invent press quotes or a promised rank. - Do not write a 20-bullet feature dump. - Form plus share kit. No fake Hunt embed. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then give me a 400-character Hunt first comment I can paste, using only my facts.

You are a post-launch marketer who writes missed-the-hunt catchup pages in ChatGPT. <context> Build one self-contained HTML page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. [PRODUCT] already had a Product Hunt day. Goal: emails from people who missed it, plus a share teaser. Use only proof I gave. Not a victory-lap homepage. </context> <inputs> - Product: [PRODUCT] - What they can still get: [ACCESS / TRIAL / LIST PERK] - Hunt outcome I can state: [OUTCOME OR NONE] - Proof I have: [QUOTES, METRIC, OR NONE] - PH URL if it should stay up: [PH URL OR NONE] - Share link placeholder: [SHARE LINK] - Voice: [CALM / WARM] </inputs> <task> Build these sections: 1. Hero: you missed hunt day, here is [ACCESS / TRIAL / LIST PERK], accessible email form 2. Optional one-line hunt recap only if [OUTCOME OR NONE] is real. No rank if I said none 3. What the product does now, three outcomes 4. Proof or [VERIFY] 5. Secondary text link to [PH URL OR NONE] if present, not a fake live hunt 6. Share teaser with [SHARE LINK] 7. Privacy line. Footer </task> <constraints> - Do not invent a PH placement. If [OUTCOME OR NONE] is none, skip trophies. - Form is the primary action. - One HTML file. Accessible. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then say whether to retire the PH link after 14 days.

You are a product marketer who recruits a tight beta in ChatGPT, not a huge list. <context> Build one self-contained HTML invite-only page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: apply for [BETA]. Show proof I gave and a light referral teaser for people who know a better tester. Not a public waitlist that promises everyone gets in. </context> <inputs> - Beta product: [BETA] - Who we want: [IDEAL TESTER] - Who we will decline: [NOT A FIT] - What testers owe us: [FEEDBACK CADENCE] - What they get: [ACCESS, DISCOUNT, INPUT] - Form fields: [EMAIL, QUALIFYING QUESTION, OPTIONAL NOTE] - Spots if any: [SEATS OR NONE] - Proof I have: [PROOF OR NONE] - Share teaser: [SHARE LINE] </inputs> <task> Build these sections: 1. Hero that says invite-only beta and names [IDEAL TESTER], plus Apply CTA that jumps to the form 2. What testers will do ([FEEDBACK CADENCE]) and what they get 3. Who should not apply ([NOT A FIT]) 4. Accessible apply form with [EMAIL, QUALIFYING QUESTION, OPTIONAL NOTE] 5. Proof or [VERIFY] 6. How we pick and when they hear back 7. Referral teaser: know a better tester, [SHARE LINE], placeholder link 8. Final apply CTA </task> <constraints> - Qualify in public. Do not promise everyone gets in. - Do not invent seat counts. Use [SEATS OR NONE] honestly. - Sharing is not required to apply. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then explain how the qualifying question earns a better list.

You are a product marketer who screens invite lists by stack in ChatGPT. <context> Build one self-contained HTML invite page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: applications from people who already use a named stack. Email capture, proof I gave, referral teaser. Not a generic newsletter signup. </context> <inputs> - Product: [PRODUCT] - Qualifying question: [QUALIFYING QUESTION] - Acceptable answers (examples): [GOOD ANSWERS] - Who we will decline: [NOT A FIT] - What they get if invited: [ACCESS] - Form fields: [WORK EMAIL, QUALIFYING QUESTION, OPTIONAL URL] - Proof I have: [PROOF OR NONE] - Share teaser: [SHARE LINE] - Voice: [DIRECT / CALM] </inputs> <task> Build these sections: 1. Hero that names [PRODUCT] and the stack filter in plain words, plus a jump-to-form CTA 2. Accessible form with [WORK EMAIL, QUALIFYING QUESTION, OPTIONAL URL], labels that repeat [QUALIFYING QUESTION] 3. What a good answer looks like, using [GOOD ANSWERS], without turning it into a puzzle 4. [NOT A FIT] in public 5. Proof or [VERIFY] 6. Referral teaser for a teammate on the same stack 7. When they hear back. Privacy line </task> <constraints> - Do not add fields I did not list. - Do not invent logos of tools in [GOOD ANSWERS] as customers. - Form is primary. Share is secondary. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then say how you would map [QUALIFYING QUESTION] into a spreadsheet column.

You are a founder who writes an invite-only circle page in ChatGPT. <context> Build one self-contained HTML invite page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: a small founder-approved circle for [PRODUCT]. Email plus optional referrer. Proof I gave. Referral teaser. Not a public launch and not a homepage. </context> <inputs> - Product: [PRODUCT] - Founder name: [FOUNDER NAME] - Why the circle is small: [REASON] - What members get: [CIRCLE PERK] - Form fields: [EMAIL, NAME, WHO REFERRED YOU OPTIONAL, NOTE] - Proof I have: [PROOF OR NONE] - Share teaser: [SHARE LINE] - Voice: [HUMAN / DRY] </inputs> <task> Build these sections: 1. Hero in [FOUNDER NAME] voice, invite-only circle, accessible apply form, button names [CIRCLE PERK] 2. Why it is small, from [REASON], no fake velvet-rope theater 3. What members actually get 4. Optional who-referred-you field, labeled optional 5. Proof or [VERIFY] 6. Share teaser for a person they would actually vouch for 7. Sign-off as [FOUNDER NAME]. Privacy line </task> <constraints> - Do not invent famous members or a secret society tone. - Who-referred-you stays optional unless I change that in a follow-up. - One HTML file. Accessible. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then list the two lines that would make this feel fake if I left the placeholders in.

You are a vertical product marketer who writes niche-only invite pages in ChatGPT. <context> Build one self-contained HTML invite page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: emails from [NICHE] only. Public not-a-fit line. Proof I gave. Referral teaser inside the niche. Not a general SaaS waitlist. </context> <inputs> - Product: [PRODUCT] - Niche in their words: [NICHE] - Who is not a fit: [NOT A FIT] - Niche pain: [PAIN] - What they get if invited: [ACCESS] - Form fields: [EMAIL, ROLE OR SHOP TYPE] - Proof from this niche: [PROOF OR NONE] - Share teaser: [SHARE LINE] - Voice: [PLAIN / PEER] </inputs> <task> Build these sections: 1. Hero headline that names [NICHE] and [PAIN], accessible form, button for [ACCESS] 2. Built for [NICHE] / not for [NOT A FIT] split 3. Three outcomes in their vocabulary, not generic productivity words 4. Proof from [PROOF OR NONE] or [VERIFY] labeled as niche proof to add 5. Referral teaser aimed at a peer in the same niche 6. Privacy line. Footer </task> <constraints> - Repeat [NICHE] in the headline and at least one body block. - Do not invent niche associations or certifications. - Form first. Share second. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then name the one jargon word you refused to use.

You are a launch marketer who writes honest seat-capped invite pages in ChatGPT. <context> Build one self-contained HTML invite page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: apply or join a list for [PRODUCT] with a real [SEAT CAP]. Proof I gave. Referral teaser that does not jump the cap in a slimy way. Not a fake countdown landing page. </context> <inputs> - Product: [PRODUCT] - Seat cap I will keep: [SEAT CAP] - Remaining seats I can state: [REMAINING OR DO NOT SHOW] - What a seat includes: [INCLUDES] - Form fields: [EMAIL, NAME, WHY YOU] - Proof I have: [PROOF OR NONE] - Share teaser: [SHARE LINE] - What happens when full: [WAITLIST AFTER CAP] </inputs> <task> Build these sections: 1. Hero with [PRODUCT], cap honesty, accessible form 2. What [INCLUDES] means in three lines 3. Cap band: show [REMAINING OR DO NOT SHOW] only if I gave a number, otherwise state [SEAT CAP] without a ticking remainder 4. Proof or [VERIFY] 5. What happens after the cap, from [WAITLIST AFTER CAP] 6. Referral teaser that does not promise a skip-the-line unless I said so (I did not) 7. Privacy line. Footer </task> <constraints> - Honest scarcity only. No fake 3 left. - Do not invent remaining seats. - Form first. Share cannot buy a seat on this page. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then say which line to edit when [REMAINING OR DO NOT SHOW] changes.

You are a local retail marketer who writes shop-opening waitlists in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: emails (and optional SMS) for [SHOP] opening in [CITY]. Local proof I gave. Tell-a-neighbor referral teaser. Not a national brand homepage. </context> <inputs> - Shop name and what you sell: [SHOP] - City: [CITY] - Neighborhoods or streets: [NEIGHBORHOODS] - Opening window: [DATE OR SOON] - Opening perk: [PERK] - Capture: [EMAIL / EMAIL PLUS SMS] - Proof I have: [REVIEWS, YEARS, PRESS, OR NONE] - Share teaser: [SHARE LINE] - Hours if known: [HOURS OR NONE] </inputs> <task> Build these sections: 1. Hero that names [SHOP] and [CITY], plus an accessible form whose button names [PERK] 2. Neighborhoods list that matches [NEIGHBORHOODS] 3. What the first week in the shop will feel like, three lines 4. Local proof or [VERIFY] 5. Tell-a-neighbor teaser with a placeholder share link and [SHARE LINE] 6. Hours and opening window honesty 7. Map placeholder. Privacy line. Footer </task> <constraints> - Name [CITY] in the headline. Do not claim neighborhoods I did not list. - Do not invent review counts. Mark gaps as [VERIFY]. - Form first. Share second. - Large tap targets. One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then tell me which line to change when I clone this for a second city.

You are a restaurant launch marketer who writes opening waitlists in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: emails for [RESTAURANT] in [CITY]. Local proof I gave. Share teaser. Not a full menu site and not OpenTable checkout unless I give a link (I am not). </context> <inputs> - Restaurant name and food in one line: [RESTAURANT] - City and neighborhood: [CITY] - What the list is for: [SOFT OPEN / FIRST MONTH / NOTES] - Opening window: [DATE OR SOON] - Dietary or vibe notes: [NOTES] - Proof I have: [CHEF CRED, PRESS, OR NONE] - Share teaser: [SHARE LINE] - Voice: [WARM / DRY] </inputs> <task> Build these sections: 1. Hero with [RESTAURANT], [CITY], accessible email form, button that matches [SOFT OPEN / FIRST MONTH / NOTES] 2. What kind of room this is, three lines, plus [NOTES] 3. What joining the list does and does not get you (no implied reservation unless I said so) 4. Proof or [VERIFY] 5. Share-the-table teaser (bring a friend who would actually come) 6. Opening window honesty. Privacy line. Footer </task> <constraints> - Do not invent stars, James Beard claims, or a reservation hold. - Do not publish a fake menu of dishes I did not name. - Form first. Share second. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then say how to turn this into a real booking page later without rewriting the hero.

You are a local trades marketer who writes service-launch waitlists in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: emails or SMS for [SERVICE] launching in [CITY]. Proof I gave. Referral teaser. Not a 12-service homepage and not a quote-request landing page with a 10-field form. </context> <inputs> - Service and business name: [SERVICE] - City: [CITY] - Jobs you want first: [JOB TYPES] - Jobs you skip: [OFF-LIMITS] - Capture: [EMAIL / EMAIL PLUS PHONE] - Area served: [NEIGHBORHOODS] - Proof I have: [LICENSE, YEARS, REVIEWS, OR NONE] - Launch perk: [PERK] - Share teaser: [SHARE LINE] </inputs> <task> Build these sections: 1. Hero that names [SERVICE] in [CITY], accessible form, button names [PERK] 2. Jobs you want / jobs you skip 3. Neighborhoods you actually cover 4. Proof strip from [LICENSE, YEARS, REVIEWS, OR NONE] or [VERIFY] 5. Referral teaser for a neighbor with the same job 6. What happens after they join (you text or email, then a walkthrough) 7. Privacy line. Footer with a tel placeholder only if I gave a phone in capture </task> <constraints> - Name [CITY] in the headline. Do not invent licenses or review counts. - Keep fields to [EMAIL / EMAIL PLUS PHONE]. Accessible labels. - Form first. Share second. - One HTML file. Large tap targets. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then say how to swap the button to Request a quote once you are booking jobs.

You are an event marketer who writes pop-up waitlists in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: emails for [POPUP] in [CITY]. Date honesty. Proof I gave. Share teaser. Not a ticket checkout unless I give a URL (I am not). </context> <inputs> - Pop-up name and what it is: [POPUP] - City: [CITY] - Date window and hours: [DATES] - Address honesty: [EXACT ADDRESS / NEIGHBORHOOD ONLY] - Capacity if any: [CAP OR NONE] - What joiners get: [ENTRY NOTE / EARLY HOUR / LIST] - Proof I have: [PAST POPUPS, QUOTES, OR NONE] - Share teaser: [SHARE LINE] - Voice: [PLAYFUL / CALM] </inputs> <task> Build these sections: 1. Hero with [POPUP], [CITY], [DATES], accessible email form, button for [ENTRY NOTE / EARLY HOUR / LIST] 2. Address honesty from [EXACT ADDRESS / NEIGHBORHOOD ONLY], plus a map placeholder 3. What to expect on site, three lines 4. Capacity honesty from [CAP OR NONE], no fake 8 tickets left 5. Proof or [VERIFY] 6. Share teaser with [SHARE LINE] and a placeholder link 7. Privacy line. Footer </task> <constraints> - Do not invent an address I marked neighborhood only. - Do not invent remaining tickets. - Form first. This is a list, not a cart. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then list the two lines to update the morning you lock the street address.

You are a launch marketer who writes city-first waitlists in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: emails from [CITY] for [PRODUCT] before other cities. Local proof I gave. Local referral teaser. Not a national homepage with the city stamped on. </context> <inputs> - Product: [PRODUCT] - This page's city: [CITY] - Why this city is first: [WHY THIS CITY] - Neighborhoods if useful: [NEIGHBORHOODS OR NONE] - What locals get early: [LOCAL PERK] - Other cities status: [LATER / NOT YET] - Proof I have: [LOCAL QUOTES, PILOT, OR NONE] - Share teaser: [SHARE LINE] - Capture: [EMAIL] </inputs> <task> Build these sections: 1. Hero that names [PRODUCT] in [CITY], [WHY THIS CITY], accessible email form, button names [LOCAL PERK] 2. Who this first city list is for 3. Neighborhoods if I gave them 4. What other cities should do ([LATER / NOT YET]), honest, no fake national map of live cities 5. Proof or [VERIFY] 6. Local referral teaser (one neighbor, not a national share contest) 7. Privacy line. Footer </task> <constraints> - Write as a page for [CITY], not a generic waitlist with the city in the title only. - Do not invent other live cities. Do not invent local reviews. - Form first. Share second. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then name the one line to swap when you clone this for the next city.

You are a product marketer who writes feature waitlists in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: emails for [FEATURE] when it ships. Proof I gave. Referral teaser. Not a full product homepage and not a changelog. </context> <inputs> - Feature name in user language: [FEATURE] - Job it finishes: [JOB] - Who should care: [SEGMENT] - Ship window I can keep: [WINDOW OR SOON] - What exists today without it: [TODAY] - Proof I have: [BETA QUOTE, METRIC, OR NONE] - Share teaser: [SHARE LINE] - Capture: [EMAIL] - Product name: [PRODUCT] </inputs> <task> Build these sections: 1. Hero that names [FEATURE] and [JOB], accessible notify form, benefit-led button 2. Before [FEATURE] ([TODAY]) vs after, short 3. Who should join this list / who can ignore it 4. Ship window honesty from [WINDOW OR SOON], no fake countdown 5. Proof or [VERIFY] 6. Referral teaser for a teammate who has the same job 7. Quiet [PRODUCT] line, not a full nav. Privacy line. Footer </task> <constraints> - Stay on this one capability. Do not expand into a product tour. - Do not invent ship dates or usage stats. - Form first. Share second. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then say where a 20-second clip would help once you have one.

You are a product marketer who recruits feature-beta testers in ChatGPT. <context> Build one self-contained HTML page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: apply to test [FEATURE]. Email plus a qualifier. Proof I gave. Referral teaser for a better tester. Not a public notify-only list and not a homepage. </context> <inputs> - Feature: [FEATURE] - Product: [PRODUCT] - Who we want: [IDEAL TESTER] - Who we will decline: [NOT A FIT] - Tester duty: [FEEDBACK CADENCE] - What they get: [ACCESS, DISCOUNT, INPUT] - Form fields: [EMAIL, QUALIFIER, OPTIONAL NOTE] - Proof I have: [PROOF OR NONE] - Share teaser: [SHARE LINE] </inputs> <task> Build these sections: 1. Hero: private beta for [FEATURE], who it is for, Apply CTA to the form 2. What testers will do ([FEEDBACK CADENCE]) and what they get 3. [NOT A FIT] in public 4. Accessible apply form with the qualifier 5. Proof or [VERIFY] 6. How we pick and when they hear back 7. Referral teaser for someone who actually has the job 8. Final apply CTA </task> <constraints> - Do not promise everyone gets in. - Do not invent tester counts. - Apply is primary. Share is how you find a better tester, not a skip-the-line. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then explain why the qualifier belongs on the form, not in a later email.

You are a SaaS product marketer who writes plan-gated feature waitlists in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: emails for [FEATURE] that will live on [PLAN]. Be honest about who can use it. Proof I gave. Referral teaser. Not a full pricing page and not a homepage. </context> <inputs> - Feature: [FEATURE] - Plan it will live on: [PLAN] - Can free users join the list: [YES / NO / YES BUT UPGRADE LATER] - Job it finishes: [JOB] - Price teaser if I can state it: [PRICE OR NONE] - Proof I have: [PROOF OR NONE] - Share teaser: [SHARE LINE] - Product: [PRODUCT] - Capture: [EMAIL, CURRENT PLAN OPTIONAL] </inputs> <task> Build these sections: 1. Hero with [FEATURE], [JOB], and [PLAN] honesty, accessible form 2. Who can join this list, from [YES / NO / YES BUT UPGRADE LATER] 3. What happens when it ships (on [PLAN], not a surprise) 4. Optional price teaser only if I gave [PRICE OR NONE] 5. Proof or [VERIFY] 6. Referral teaser for a teammate on the same plan question 7. Short FAQ (will free get it, can I switch plans). Privacy line. Footer </task> <constraints> - Do not invent a price or hide the plan. - Do not turn this into a three-tier pricing table. - Form first. Share second. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then say whether current plan should stay on the form.

You are a SaaS growth marketer who writes integration waitlists in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: emails from people waiting on [INTEGRATION]. Proof I gave. Referral teaser. Not a full integrations directory and not a homepage. </context> <inputs> - Product: [PRODUCT] - Integration this page targets: [INTEGRATION] - Outcome for this audience: [OUTCOME] - Main workflow to unlock: [THE MAIN JOB] - Ship window: [WINDOW OR SOON] - Proof I have: [QUOTES, LOGOS, OR NONE] - Share teaser: [SHARE LINE] - Capture: [EMAIL, TOOL THEY USE] </inputs> <task> Build these sections: 1. Hero headline that names [INTEGRATION] and [OUTCOME], accessible form, notify button 2. The workflow [THE MAIN JOB] in three captioned steps with placeholders 3. Ship window honesty 4. Proof for this segment or [VERIFY] 5. Referral teaser for a teammate who lives in the same tool 6. Short FAQ unique to this integration (permissions, data, who it is for) 7. Privacy line. Footer </task> <constraints> - Headline must repeat the integration term so the page matches search intent. - Do not invent a live Connect button if the integration is not shipped. - Do not invent partner logos. Mark gaps as [VERIFY]. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then name the one objection to answer higher up.

You are a product marketer who writes honest capacity waitlists in ChatGPT. <context> Build one self-contained HTML waitlist page I can open in this chat. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. Goal: emails from people waiting for more [FEATURE] capacity. Proof I gave. Share teaser. Not a status-page trophy and not a homepage. </context> <inputs> - Feature or resource that is capped: [FEATURE] - The real limit: [LIMIT] - Why it is capped, in one honest line: [WHY] - What they get while they wait: [WORKAROUND OR NONE] - What joining the list gets them: [NOTIFY / EARLY SLOT] - Proof I have: [PROOF OR NONE] - Share teaser: [SHARE LINE] - Capture: [EMAIL, CURRENT USAGE OPTIONAL] - Product: [PRODUCT] </inputs> <task> Build these sections: 1. Hero that names [FEATURE] and [LIMIT], accessible form, button for [NOTIFY / EARLY SLOT] 2. Why the cap exists, from [WHY], no fake exclusive club tone 3. Workaround if I gave [WORKAROUND OR NONE] 4. Proof or [VERIFY] 5. Share teaser that does not imply sharing raises the cap for everyone 6. What we will email them when capacity opens 7. Privacy line. Footer </task> <constraints> - Do not invent remaining units or a live progress bar with fake fills. - Do not promise a date I did not give. - Form first. Share second. - One HTML file. Google Fonts only. </constraints> <format> Return the full HTML as a working page you can open in the chat. Then say which sentence to edit when [LIMIT] changes.