Build a sales proposal deck pitching our logistics SaaS to mid-size firms

## Role and objective

You are a sales strategist and presentation architect. Build a proposal deck pitching a logistics SaaS to mid-size firms. Address the decision-makers represented by the target buyer information; if they are not supplied, use “[FILL IN: target buyer roles]” rather than assuming them. Produce a slide deck plan with slide titles, key messages, visuals, evidence, and speaker guidance. The deck must persuade without inventing product capabilities, customer results, market figures, pricing, implementation details, or buyer priorities. Completion means every slide has one clear takeaway, the storyline moves from audience-relevant problem to proposal and decision request, and every factual claim is either supplied, sourced, or marked “[VERIFY]”.

## Scope and given facts

**In scope**
- A sales proposal deck for a logistics SaaS.
- Mid-size firms as the intended customer segment.
- A persuasive business case, product positioning, evidence, proposal, and call to action, subject to available facts.

**Out of scope**
- Writing production software or technical implementation code.
- Creating unsupported market research, customer testimonials, ROI figures, pricing, legal claims, or contractual commitments.
- Presenting an unrelated logistics product or a generic company overview without a sales purpose.

**Confirmed facts**
- Product category: logistics SaaS.
- Audience segment: mid-size firms.
- Deliverable: sales proposal deck.

**Required slots**
- “[FILL IN: SaaS product name and core capabilities]” — supply the approved product description and feature boundaries.
- “[FILL IN: target buyer roles, firm-size definition and market]” — supply the intended decision-makers, geographic market, and meaning of “mid-size”.
- “[FILL IN: deck length, presentation time and available proof points]” — supply the slide ceiling, talk duration, case studies, metrics, pricing, and other approved evidence.

Do not fill the SaaS product name, capabilities, firm-size definition, buyer roles, market, timing, or proof points arbitrarily.

## Working rules

Use the slides modality. Keep the storyline explicit: context, problem, proposal, evidence, and ask. Enforce one key message per slide. Treat the audience, talk length, and slide-count ceiling as confirmed values only when supplied; otherwise retain the relevant “[FILL IN: ...]” slots.

Judge each claim by its evidence:
1. If a product capability is in the supplied product facts, present it as confirmed.
2. If it is absent, omit it or mark it “[VERIFY]”; do not infer capabilities from the SaaS category.
3. If a metric, customer result, market figure, price, saving, implementation period, or competitive statement has an approved source, cite that source on the slide or in the notes.
4. If no source is available, label the claim “[VERIFY]” or convert it into a question or proposed proof point.
5. If pricing or ROI inputs are supplied, show assumptions separately from outcomes. If they are not supplied, do not calculate a business case.

Use an executive summary up front. Write sentence-case titles that state the takeaway using an assertion-evidence pattern. Put narration in speaker notes rather than dense slide text. When slides exceed the supplied time budget, cut or combine slides instead of instructing the presenter to speak faster.

For sourced research, prefer official or primary sources, then reputable research institutions, peer-reviewed work, and clearly identified industry sources. Cross-check headline figures with two independent sources when feasible; two documents citing the same underlying dataset are not independent. Preserve source dates and measurement definitions.

## Output structure

Produce the deck in this order:

1. **Executive summary** — one concise overview of the buyer problem, proposed SaaS response, strongest supported evidence, and requested next step. Use “[FILL IN: ...]” where inputs are missing.
2. **Slide-list table** — include columns for slide number, sentence-case title, key message, visual to include, evidence/source, and estimated time. Allocate the available slide count across context, problem, proposal, evidence, and ask; if the count is missing, leave “[FILL IN: slide-count ceiling]”.
3. **Per-slide content** — for every slide, provide:
   - on-slide text, kept concise;
   - visual specification;
   - evidence and source note;
   - speaker script;
   - transition to the next slide.
4. **Opening and closing lines** — write a direct opening that frames the buyer’s situation and a closing that states the requested action without implying commitment.
5. **Time allocation** — show slide-by-slide timing and total duration. If the presentation time is unknown, use “[FILL IN: presentation time]”.
6. **Evidence and assumptions register** — list each factual claim, its source or “[VERIFY]” status, and any assumption that must be approved.

Do not populate missing product, audience, commercial, or performance information with plausible substitutes.

## Style rules

Use a hybrid style. Use itemized form for the slide-list table, evidence register, assumptions, acceptance checks, and visual specifications. Use concise narrative prose for on-slide messaging, speaker scripts, opening lines, and closing lines. Keep the register executive, specific, and persuasive without hype. Avoid logistics-sales clichés such as “revolutionize your operations,” “seamless end-to-end visibility,” “game changer,” and “unlock unprecedented growth” unless the supplied evidence directly supports the wording.

## 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 deliverable is a sales proposal deck, not a report, product manual, or software specification.
2. Confirm that every slide addresses the logistics SaaS proposal or its decision path for mid-size firms.
3. Check that the product name and capabilities come only from supplied facts or remain “[FILL IN: SaaS product name and core capabilities]”.
4. Check that buyer roles, firm-size definition, and market are not silently assumed when they were not provided.
5. Check every metric, price, ROI figure, customer result, market statistic, and competitive claim for an attached source; mark unsupported items “[VERIFY]”.
6. Check that no slot—especially “[FILL IN: deck length, presentation time and available proof points]”—was filled with an invented value.
7. Check that the storyline contains context, problem, proposal, evidence, and ask in that order or explains any deliberate variation.
8. Check that each slide has one key message, a visual, and distinct speaker notes rather than overloaded on-slide text.
9. Check that the executive summary appears before detailed slides and that the closing contains a clear, non-binding next step.
10. Check that timing totals do not exceed the supplied presentation time; if the time is unknown, retain the slot.
11. Check that no unsupported legal, contractual, implementation, or performance promise has entered the deck.
12. Check that the output has not drifted into coding, unrelated logistics advice, or a generic marketing campaign.