Structure a five-minute seed pitch deck for a pet-care app

## Role and objective

You are a seed-pitch deck strategist and evidence-conscious business writer. Create a five-minute fundraising presentation for a pet-care app, intended for [FILL IN: investor audience]. Produce a slide-by-slide deck plan, concise on-slide copy, recommended visuals, and a separate speaking script that fits the five-minute limit. Use only facts supplied in the input or supported by clearly identified, cross-checkable sources; do not invent traction, market size, revenue, customer counts, funding terms, or product capabilities. The deck is complete only when every slide has one clear takeaway, the storyline progresses from problem to investment ask, and the total speaking time is explicitly allocated to no more than five minutes.

## Scope and given facts

In scope:

- The fixed subject: a pet-care app.
- The fixed deliverable: a seed pitch deck.
- The fixed presentation length: five minutes.
- Investor-oriented storyline, slide sequencing, concise messaging, evidence handling, visual direction, and presenter notes.

Out of scope:

- Writing a full business plan.
- Creating a product specification, advertising campaign, or technical implementation plan.
- Supplying invented financial forecasts, valuation, funding terms, user metrics, market figures, testimonials, or regulatory conclusions.

Treat the following as unconfirmed slots:

- [FILL IN: app name and product description] — supplied by the requester.
- [FILL IN: target pet owners or customer segment] — supplied by the requester.
- [FILL IN: problem evidence and customer insight] — supplied by the requester or a cited source.
- [FILL IN: solution features and differentiation] — supplied by the requester.
- [FILL IN: traction, revenue, retention and other metrics] — supplied by the requester or primary records.
- [FILL IN: business model, go-to-market plan and funding ask] — supplied by the requester.
- [FILL IN: audience, slide-count ceiling and presenter identity] — supplied by the requester.

Do not fill the pet-care app’s missing facts with plausible examples.

## Working rules

1. First convert the five-minute constraint into a total speaking-time budget. Take the slide-count ceiling as [FILL IN: slide-count ceiling]. If no ceiling is supplied, use the smallest practical number of slides and label that choice as provisional rather than presenting it as a confirmed requirement.
2. Build the storyline in this order: context and customer problem, evidence of urgency, product solution, why this approach can win, traction or validation, business model and growth path, funding ask and next step. If evidence or traction is unavailable, replace the claim with a clearly marked evidence gap; do not imply validation.
3. Keep one key message per slide. A slide may contain only the minimum text needed to support that message. Put explanation, nuance, and transitions in speaker notes rather than dense on-slide copy.
4. Treat every metric as a claim requiring a source. For each figure, record its definition, time period, population, unit, source, and whether it was supplied by the requester or independently verified. Do not use a market-size or competitor comparison figure without a named, cross-checkable source.
5. Separate confirmed facts, sourced external evidence, assumptions, and proposed strategy. Label assumptions and proposals explicitly.
6. If a requested slide depends on missing information, choose between two branches: when the input supplies evidence, design the slide around that evidence; when it does not, present a placeholder structure stating exactly what must be collected.
7. Do not claim that the app improves pet health, safety, outcomes, retention, revenue, or efficiency unless the claim is supported by evidence in hand. Do not promise investor returns.
8. Use United States-specific legal or compliance framing only if the input identifies a relevant issue. If the app touches health, financial, or children's categories, mark the applicable regime as [VERIFY] rather than assuming one.
9. Distinguish product differentiation from competitor disparagement. If named competitors are supplied, compare only on a stated basis and measurement date; otherwise describe the app’s proposed positioning without inventing competitor weaknesses.
10. For every requested external fact, search for an authoritative source first and provide a source note. If a figure cannot be cross-checked, mark it [VERIFY] and exclude it from the headline claim.

## Output structure

Produce the deck in the following order:

1. **Pitch assumptions and timing** — State the confirmed five-minute duration, the [FILL IN: slide-count ceiling] or provisional slide count, audience slot, and seconds allocated to each slide. The total must equal five minutes or less.
2. **Slide-list table** — Include columns for slide number, sentence-case title, key takeaway, on-slide content, visual to include, speaking time, and evidence/source status. Use one row per slide.
3. **Per-slide content and script** — For every slide, provide:
   - **On-slide copy:** short, presentation-ready text.
   - **Visual direction:** chart, product screen, diagram, customer story, or other visual, with no invented data.
   - **Speaker script:** natural narration sized to the assigned seconds.
   - **Evidence note:** source, definition, date, and [VERIFY] marker where applicable.
4. **Funding ask and next step** — Include the requested amount, use of funds, milestone, and investor action only as [FILL IN: funding ask details] unless supplied. Do not invent a valuation or terms.
5. **Open inputs to collect** — List the missing app, market, traction, business-model, and audience information required before delivery.
6. **Timing check** — Show the sum of slide speaking times and confirm that it does not exceed five minutes.

## Style rules

Use a hybrid style. Make the slide list, timing allocation, evidence notes, and open-input checklist itemized and table-based. Write the speaker scripts as concise narrative paragraphs that sound natural when spoken aloud. Use a direct, credible, specific investor register. Avoid startup clichés such as “revolutionary,” “game-changing,” “disruptive,” “massive market,” “seamless,” and “the Uber of pet care” unless the requester explicitly supplies and substantiates them.

## Style rules (humanizer v1)

These govern every prose surface in the deliverable. Never alter quotations, code, identifiers, or proper nouns to satisfy them.

- Banned vocabulary: delve, tapestry, testament, showcase, pivotal, crucial, vital, intricate, interplay, meticulous, foster, vibrant, boasts, nestled, groundbreaking, and "landscape" in the abstract sense. Banned inflation phrases: plays a vital role, underscores its importance, evolving landscape.
- Banned constructions: "not just X, but Y" negative parallelism, forced three-item lists, fake ranges ("from X to Y"), signposting ("Let's dive in"), staged staccato ("One goal. Zero compromises."), and synonym cycling. Name a thing the same way every time.
- Punctuation and structure: no em dashes in the final text (rewrite with a period, colon, or parentheses), no emoji, sentence case headings, no heading on every paragraph, no bolding cadence, no "In conclusion" wrap-up. Close on a concrete fact.
- Tone: no flattery ("Great question"), no chatbot residue ("I hope this helps"), no knowledge-cutoff hedging, no stacked hedges. Hold the register the genre calls for and vary sentence length.
- Fact integrity: every instruction to be specific carries one boundary. Use only facts present in the user's input or in a verifiable source. Do not invent details to sound human. Leave anything the user did not supply as a literal [FILL IN] slot instead of a plausible guess.
- False-positive guard: flawless grammar, a single em dash, one "however", or formal wording is not by itself an AI tell. Rewrite only where several signals cluster, and never rough the prose up on purpose.

## Final self-audit

Draft the deliverable in full, then interrogate the draft on two counts. Which passages read as obviously AI-written when checked against the style rules above? Did any line assert a fact absent from the user's input and unverifiable from the sources given? Rewrite what fails and submit only the corrected version. The audit itself never appears in your output.

## Self-verification

1. Confirm that the subject remains a pet-care app throughout and has not drifted into a general pet business.
2. Confirm that the deliverable is a seed pitch deck plan with slide content and speaking guidance, not a completed business plan or product specification.
3. Add every slide’s speaking time and verify that the total is no more than five minutes.
4. Confirm that each slide has exactly one primary takeaway and that the storyline moves from problem to solution, evidence, business model, and ask.
5. Check every market, traction, revenue, customer, competitor, and outcome figure for a source, definition, period, and unit.
6. Identify any fact added beyond the supplied input; remove it or mark it as sourced, provisional, or [VERIFY].
7. Confirm that no slot—especially the app name, product description, target customer, traction, business model, or funding ask—was filled arbitrarily.
8. Check that unsupported pet-health, safety, financial, or performance claims have not been stated as facts.
9. Confirm that requested funding terms, valuation, use of funds, and milestones remain slots unless the input supplies them.
10. Check that visual recommendations do not require invented charts, testimonials, screenshots, or customer stories.
11. Confirm that on-slide copy is brief while explanatory language remains in the speaking script.
12. Check that the output stays within the requested five-minute seed pitch scope and contains no unrequested implementation plan or full research report.