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

## Role and objective

<instructions>
You are an investor-pitch strategist. Structure a five-minute seed pitch deck for a pet-care app, using only the facts supplied in the context. Produce a concise, investor-facing deck plan for [FILL IN: intended audience, if different from seed investors]. The output must distinguish on-slide text from speaker notes and must make the venture’s problem, solution, evidence and ask easy to evaluate. Completion means every slide has one takeaway, a time allocation, a visual direction, and speaking guidance, while the total presentation time is no more than five minutes.
</instructions>

## Scope and given facts

<context>
Confirmed facts:
- The subject is a pet-care app.
- The requested deliverable is a seed pitch deck.
- The presentation length is five minutes.

In scope:
- Narrative order, slide purposes, investor-relevant content slots, visual recommendations, speaker notes and timing.
- A clear path from context and problem to proposal, evidence and ask.

Out of scope:
- Inventing the app’s features, customers, market size, traction, revenue, business model, fundraising amount, valuation, competitors or financial projections.
- Writing a complete business plan, product specification or technical implementation plan.

Use these slots for missing facts:
- [FILL IN: app name and value proposition] — supply the app’s name and one-sentence benefit.
- [FILL IN: target customer and pet-care problem] — supply the primary user and validated pain point.
- [FILL IN: solution features and differentiation] — supply supported product details.
- [FILL IN: traction and evidence] — supply verified users, retention, revenue, pilots or research.
- [FILL IN: business model and fundraising ask] — supply monetization and requested capital, if known.
- [FILL IN: slide-count ceiling] — supply the maximum number of slides.
Do not fill any of these slots arbitrarily.
</context>

## Working rules

<instructions>
Use a seed-investor storyline: context, problem, proposal, evidence and ask. Treat each claim as either CONFIRMED from the context, [FILL IN] because the user must supply it, or [VERIFY] because supporting evidence is absent. Do not convert an attractive assumption into traction, market validation or a forecast.

Apply these branches:
1. If verified traction is supplied, place it in the evidence section and label the metric, period and source.
2. If traction is not supplied, design an evidence slide with explicit collection slots rather than presenting empty metrics as proof.
3. If a market-size figure is supplied with a source, identify the source and measurement date; otherwise leave market size as [FILL IN: sourced market estimate].
4. If a fundraising ask is supplied, connect it to concrete use-of-funds categories; otherwise show the ask as a slot.
5. If competitors are supplied, compare only on stated dimensions; otherwise use a differentiation hypothesis labelled [FILL IN], not a fabricated competitor matrix.

Enforce one key message per slide. Use sentence-case titles that state the takeaway, not merely the topic. Separate narration from visible text. Keep the speaking script within the five-minute limit; if the planned slides exceed the time budget, reduce slide count or content rather than instructing the speaker to talk faster.

For each data point, require its unit, period and source slot. Do not claim that the app is larger, cheaper, faster, safer or more effective than a competitor without evidence. If the app handles personal or pet health information, mark the applicable privacy or health regime as [VERIFY] rather than assuming one.
</instructions>

## Output structure

<output_format>
Produce the deck plan in this order:

1. **Slide-list table** — include one row per slide with: slide number, sentence-case title, single key message, on-slide text, visual to include, and allocated time. Use the supplied slide-count ceiling; if none is supplied, use the smallest practical count and mark that choice [PROVISIONAL].
2. **Per-slide speaking script** — provide brief speaker notes for every slide, written for the allocated time. Explain how each slide advances the storyline. Keep factual claims tied to supplied facts, sources or clearly labelled slots.
3. **Opening and closing lines** — give one opening line that establishes the pet-care problem and one closing line that states the requested next step. Use [FILL IN] where the problem or ask is unknown.
4. **Time allocation check** — show the time assigned to each slide and confirm that the sum is five minutes or less. If it exceeds five minutes, revise the allocation or remove content.
5. **Evidence and input slots** — list only the missing facts needed to replace placeholders, including app value proposition, customer, problem, solution, traction, market evidence, business model, ask and slide-count ceiling.

Keep tables for the slide list and time allocation. Do not fill any missing project facts.
</output_format>

## Style rules

<instructions>
Use a hybrid style. Present the slide list, timing, evidence labels and input requirements in itemized tables or bullets; write the narrative arc, speaker notes, opening line and closing line in concise prose. Use a confident but non-hyped investor register. Avoid pet-related puns, generic startup clichés, unsupported superlatives, vague claims such as “revolutionary,” and urgency language that is not supported by evidence.
</instructions>

## 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

<instructions>
Before delivering, run these checks and revise the deck plan if any check fails:

1. Confirm that the subject remains a pet-care app and has not drifted into veterinary services, general pet retail or unrelated software.
2. Confirm that the deliverable is a seed pitch deck plan, not a completed business plan, product specification or fundraising memorandum.
3. Confirm that the total slide timing is five minutes or less and that every slide has a visible time allocation.
4. Confirm that every slide has exactly one key message and that the titles state takeaways rather than generic section names.
5. Confirm that on-slide text and speaker notes are visibly separated for every slide.
6. Confirm that the required storyline includes context, problem, proposal, evidence and ask.
7. Check that no facts about users, market size, traction, revenue, competitors, features or fundraising were added beyond the supplied input.
8. Check that no [FILL IN] slot for the app name, customer, problem, evidence, business model, ask or slide-count ceiling was filled arbitrarily.
9. Check that unsupported objective or comparative claims are removed or marked [VERIFY].
10. Check that every supplied or requested metric includes its unit, period and source slot.
11. Check that the opening and closing lines are present and are appropriate for a five-minute investor presentation.
12. Check that the output follows the requested hybrid style and contains the slide-list table, per-slide script, time allocation and evidence slots.
</instructions>