PITCH LANDING PAGE BUILDER — Polymorph ========================================= This prompt takes three inputs — a discovery call transcript, your notes/feedback, and the pre-filled product description below — and outputs a single, self-contained HTML pitch landing page designed to be walked through live during a pitch call. The page follows the "Oscar-Winning Solution" method: every section maps directly to something the prospect said during discovery. Nothing generic. No boilerplate company history about Polymorph. The entire page is about the prospect's problems, solved. The output is a single .html file you can open in any browser and screen-share during the pitch meeting. HOW TO USE ---------- 1. Copy the entire prompt below (everything inside the START/END markers) 2. Paste it into your LLM of choice — ChatGPT, Cursor, Claude, or any tool that can generate code 3. Replace the placeholders: - [PROSPECT_COMPANY] — the prospect's company name - [DISCOVERY_TRANSCRIPT] — full transcript from the discovery call - [SELLER_NOTES] — your notes, observations, or strategic feedback 4. Run the prompt. The LLM will output a complete HTML file. 5. Save the output as pitch-[prospect-name].html and open it in a browser. 6. REVIEW BEFORE PRESENTING. Walk through each section. Adjust any language that doesn't feel right. Make sure the problems, impact, and solution mapping are accurate. This is your pitch — own it. ---START PROMPT--- You are a sales strategist and front-end developer. Your job is to analyze a discovery call transcript and build a bespoke pitch landing page that a salesperson will screen-share and walk through during a live pitch meeting. The page follows the "Oscar-Winning Solution" method: every single section connects directly to something the prospect said during the discovery call. If a section can't be tied to a real discovery insight, it gets cut. Nothing generic. Nothing about the seller's company history. The entire page is about the prospect — their problems understood, their outcomes delivered. --- INPUTS Prospect company: [PROSPECT_COMPANY] Seller company: Polymorph Discovery call transcript: [DISCOVERY_TRANSCRIPT] Seller's notes and feedback: [SELLER_NOTES] Product/service description: Polymorph is a South Africa–based custom software studio. The commercial path is: Discovery → diagnostic pitch → paid concept design (scope/UX/technical blueprint) first. The embedded product director / specialist + longer build is a second pitch after concept proves fit — do not let the HTML lead with the long engagement; this page sells concept. Reference positioning (adapt, don't paste verbatim): Polymorph Growth Engine narrative — https://the-polymorph-growth-engine-486905238426.us-west1.run.app/ Do not invent fixed ZAR/EUR pricing in the HTML unless the seller provides numbers in [SELLER_NOTES]. Use ranges or "scoped after discovery" if needed. STEP 1: ANALYZE THE DISCOVERY TRANSCRIPT Before writing any code, analyze the transcript and extract: 1. Core Problems (3–5): The real problems the prospect described. Quote their language. Separate symptoms from root causes. 2. Commercial Impact: For each problem, what is the business cost? Revenue lost, deals missed, time wasted, margin eroded, growth stalled. Quantify where the transcript gives you numbers. 3. Emotional Impact: For each problem, what is the human cost? Stress, frustration, distraction, burnout. 4. Decision-Makers & Concerns: Who was on the call? Who else influences the decision? What did each person seem most concerned about? 5. Budget Signals: Any mention of current spend, past investments, budget range. 6. Timeline & Urgency: Is there a deadline? A trigger event? What happens if they delay? 7. What They've Already Tried: Previous solutions, agencies, hires, tools. Why those didn't work. 8. Success Vision: What does success look like in 90 days? In 12 months? Use their words. 9. Language & Tone: Note specific phrases, metaphors, or framing the prospect used. --- STEP 2: BUILD THE HTML PITCH LANDING PAGE Create a single HTML file with embedded CSS and JavaScript. The page has six sections: SECTION 1: PROBLEM PLAYBACK Purpose: Prove you listened. Build trust before you sell. - Open with: "Here's what we heard" - 3–5 bullet points summarizing their core problems - Use their language — don't sanitize it - No solutions in this section SECTION 2: IMPACT & URGENCY Purpose: Make the cost of inaction concrete. - For each problem, show downstream impact - Revenue left on the table, time lost, opportunity cost, risk, stress - Mix numbers and narrative - Frame as "This is what's already happening" SECTION 3: TAILORED SOLUTION Purpose: Map solution to problems. One problem, one solution. Outcome-led. - For each problem: the problem (one line), the specific Polymorph approach (e.g. concept design artefact or build slice), the outcome - Lead with the outcome, not the feature - If something is outside scope, say so honestly SECTION 4: VALUE → PRICE Purpose: Anchor price to value so the number feels inevitable. - Re-anchor on value before showing price - Show the recommended commercial path (typically paid concept design, then scoped build) and investment framing the seller confirmed - Frame as investment relative to return - Calm and confident — no "just" or "only" SECTION 5: PROOF & CONFIDENCE Purpose: Reduce risk. Show you've solved this before. - 2–3 proof points matched to their specific problems - Pattern recognition: "We keep seeing this pattern — and we know what fixes it" - No logo walls — proof that speaks to their situation SECTION 6: CLEAR NEXT STEPS Purpose: Remove ambiguity. Make the path forward obvious. - 3–4 concrete steps after a yes - Specific: "60-minute kickoff within 48 hours" not "We'll get started" - End with a single, clear call to action --- STEP 3: DESIGN & TECHNICAL REQUIREMENTS - Single HTML file with all CSS and JS embedded (no external files except Google Fonts) - Each section: min-height 100vh - Smooth scrolling, minimal fixed nav (dots or short labels) - Responsive: desktop 1440px+ and tablet 768px+ - Google Fonts: DM Serif Display for headings, Figtree (400, 500, 600) for body - Background: #001428 or #0a1628 (Polymorph navy family) - Primary text: #FFFFFF or #F5F5F5 - Accent: #3E85FF (Polymorph blue) — used sparingly; optional highlight #EF413D for key CTAs only - Secondary text: #999999 or #AAAAAA - Scroll-triggered fade-in animations (IntersectionObserver) - Staggered delays for list items (100–150ms between) - Duration: 600–800ms - Premium, bespoke, cinematic feel - Prospect's company name in page title and hero - Polymorph appears only subtly in footer --- RULES 1. Every section maps to discovery. No filler. 2. Use the prospect's language. Don't upgrade "a mess" to "suboptimal." 3. No jargon. No feature dumps. Lead with outcomes. 4. No "About Us" section. Credibility comes through proof and quality. 5. No fluff. Every word earns its place. 6. Price is never isolated. Always anchored to value. 7. End with clarity, not politeness. 8. Self-contained single HTML file. 9. Quality bar: This should look like a boutique agency spent a week on it. --- OUTPUT Output the complete HTML file. Nothing else — no explanation, no commentary, no markdown. ---END PROMPT---