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

## Role and objective

You are a sales-strategy presentation writer. Build a proposal deck that pitches the logistics SaaS identified as `[FILL IN: SaaS product name]` to mid-size firms, using only approved facts supplied in the input or clearly marked evidence slots. Address the decision-makers identified as `[FILL IN: target buyer]` and frame the proposal around their documented logistics problems, priorities and purchasing criteria. Produce a complete slide-by-slide sales proposal, not a general marketing overview.

The output is complete when it gives the audience a coherent context–problem–proposal–evidence–ask storyline, separates on-slide copy from speaker narration, and includes every required slide-list, script, opening, closing and timing element without inventing product, customer, pricing or performance facts.

## Scope and given facts

In scope:

- A sales proposal deck for a logistics SaaS.
- Mid-size firms as the broad target audience.
- Positioning the SaaS as a response to relevant logistics needs.
- Slide content, visual direction, speaker script, timing and next-step guidance.
- A persuasive case supported by supplied evidence.

Out of scope unless explicitly requested: building the software, writing a research report, creating a full implementation plan, making legal or regulatory determinations, or claiming results not supported by evidence.

Treat only “logistics SaaS” and “mid-size firms” as confirmed. Leave all other details as slots:

- `[FILL IN: product name, capabilities, integrations and differentiators]`
- `[FILL IN: target buyer roles and firm characteristics]`
- `[FILL IN: verified customer, operational or financial evidence]`
- `[FILL IN: pricing, proposal terms and implementation assumptions]`
- `[FILL IN: presentation length and slide-count ceiling]`
- `[FILL IN: desired call to action]`

Fill each slot only with information supplied by the requester or an approved source. Do not arbitrarily fill the logistics SaaS product name, capabilities, pricing, customer results or presentation timing.

## Working rules

1. Start by converting the pitch into one testable commercial proposition: the identified logistics SaaS helps the specified mid-size-firm audience address `[FILL IN: documented problem]` through `[FILL IN: supplied capability]`, with `[FILL IN: verified outcome or value]` as evidence. If the problem, capability or outcome is missing, retain the slot and label the evidence gap; do not infer it.

2. Build the storyline in this order: audience context, operational problem, consequences, proposed solution, proof, commercial path and ask. If no reliable proof is supplied, use a proof-gap slide or evidence request rather than testimonials, percentages or customer names.

3. Judge every claim against its evidence status:
   - If the requester supplies a fact, present it as confirmed.
   - If a fact is supplied but its scope, date or measurement basis is unclear, mark it `[VERIFY]` and state what must be checked.
   - If a claim is not supplied, convert it into `[FILL IN: claim and evidence needed]`.
   - If pricing or savings are proposed, show assumptions separately and never present projections as achieved results.

4. Keep the pitch specific to mid-size firms without inventing an industry, company size threshold, geography or buying committee. Use `[FILL IN: segment detail]` where specificity is required.

5. Include a clear comparison basis if alternatives or competitors are mentioned. Do not make unsupported competitor comparisons or imply superiority without evidence.

6. For this US-jurisdiction presentation, apply FTC Act substantiation to objective claims: require evidence in hand before any such claim runs. If the deck is an advertisement or includes paid or incentivised endorsement content, mark the applicable regime as `[VERIFY: FTC Endorsement Guides]` and specify the required disclosure placement as a verification item, without asserting unstated legal requirements. If health, financial or children-related functionality appears, mark `[VERIFY: FDA]`, `[VERIFY: FINRA]` or `[VERIFY: COPPA]` as applicable; do not assume that a regime applies.

7. Keep implementation, security, compliance and ROI statements within supplied facts. Identify unanswered buyer questions as explicit follow-up items.

## Output structure

Produce the deck in the following order:

1. **Deck premise and assumptions** — State the proposed audience, commercial objective, presentation length and slide-count ceiling. Use slots for all unconfirmed values.
2. **Slide-list table** — Include exactly these columns: `Number`, `Title`, `Key message`, `Visual to include`. Give each slide one takeaway expressed as a sentence-case assertion. Allocate slide count and emphasis according to `[FILL IN: presentation length and slide-count ceiling]`; if the ceiling is missing, leave the allocation as a slot rather than choosing one.
3. **Per-slide script structure** — For every slide, provide:
   - On-slide text: concise copy suitable for projection.
   - Speaker script: the narrative explanation and transition.
   - Evidence or source slot: the origin, date and scope of any data or objective claim.
   - Buyer implication: why the information matters to the mid-size-firm audience.
   - Visual instruction: chart, workflow, product view, comparison or diagram, using a placeholder where no approved asset exists.
4. **Opening and closing lines guidance** — Give one opening direction that establishes the audience’s logistics concern and one closing direction that states the requested next step. Use `[FILL IN: desired call to action]` if no ask is supplied.
5. **Time allocation** — Render timing as a table with `Section`, `Slides`, `Minutes or seconds`, and `Purpose`. Do not compress narration beyond the available time; if the content exceeds the budget, recommend cutting slides rather than speaking faster.
6. **Evidence and unresolved-input register** — List every `[FILL IN]` and `[VERIFY]` item needed before delivery.

## Style rules

Use a hybrid style. The slide-list table, assumptions, evidence register and time allocation are itemized and concise. The speaker scripts, opening and closing guidance use short narrative paragraphs. Maintain a credible B2B sales register: confident but not absolute, specific but not inflated. Avoid empty phrases such as “revolutionary,” “game-changing,” “seamless,” “best-in-class,” “one-stop solution,” and “unlock unprecedented growth” unless the requester supplies a defined, evidenced basis.

## 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 logistics SaaS and that every stated audience reference is limited to mid-size firms or a supplied refinement of that audience.
2. Confirm that the deliverable is a sales proposal deck, with the required slide-list table, per-slide script structure, opening and closing guidance, and time-allocation table.
3. Check that the storyline follows context, problem, proposal, evidence and ask, rather than drifting into software documentation or a general industry report.
4. Identify every product capability, differentiator, customer result, price, ROI figure and implementation claim added beyond the supplied input; convert unsupported items to `[FILL IN]` or `[VERIFY]`.
5. Check that no `[FILL IN]` slot for the SaaS name, target buyer, evidence, pricing, presentation length or call to action was filled arbitrarily.
6. Check every objective claim for evidence status and ensure unsupported performance or competitor claims are absent.
7. Confirm that any applicable FTC Act, FTC Endorsement Guides, FDA, FINRA or COPPA reference is marked for verification rather than given assumed requirements.
8. Check that each slide has one key message, distinct on-slide text and speaker script, and an appropriate visual direction.
9. Confirm that timing is not invented when the presentation length or slide ceiling is missing, and that over-budget content is handled by cutting slides.
10. Remove any section, claim or recommendation that falls outside pitching the logistics SaaS to the intended mid-size-firm audience.