Freight Routing Sales Deck Wireframe and Narrative Email
Outline visual slide architecture and scripting for commercial logistics software pitches.
Use this template when sales leaders need a clean, slide-by-slide visual layout and messaging flow before building a freight customer pitch. It generates a concise email detailing screen compositions, callout cards, and proof points.
Role: Principal Presentation Designer & Freight Tech Storyteller specializing in enterprise B2B sales collateral.
Context
- Commercial lead: {{sales_lead_name}}
- Solution provider: {{freight_company}}
- Prospect profile: {{target_client_tier}}
- Primary performance metric: {{core_metric_gain}}
- Deck length limit: {{slide_count_limit}}
- Visual tone: {{design_system_tone}}
Task
Draft a comprehensive email to {{sales_lead_name}} detailing a high-converting visual wireframe and slide narrative plan that showcases {{freight_company}}'s routing capabilities to {{target_client_tier}}.
Method
- Establish the overarching narrative arc matching {{target_client_tier}}'s supply chain pain points.
- Translate {{core_metric_gain}} into a central visual hero metric that recurs across the deck.
- Map out each slide from 1 to {{slide_count_limit}}, pairing slide title, layout archetype, and visual focal point.
- Specify UI callout placements to display routing map software without visual clutter.
- Detail the layout for the proof-of-concept slide using split-screen before-and-after route density diagrams.
- Define visual hierarchy rules matching the {{design_system_tone}} aesthetic.
- Provide concrete guidance on negative space to ensure the slides remain scannable during live sales calls.
- Add clear presentation speaker notes to guide verbal delivery for each visual anchor.
Constraints
- Output MUST be structured as an email sent to {{sales_lead_name}}.
- MUST NOT exceed the total slide count designated in {{slide_count_limit}}.
- Visual descriptions MUST emphasize diagrammatic storytelling over text bullet points.
- Layout terminology MUST be precise (e.g., 3-column container, KPI stat card, full-bleed map).
Output format
- Email Subject line formatted for internal handoff
- Brief contextual introduction (under 50 words)
- Slide-by-Slide Layout Blueprint (Numbered list from 1 to {{slide_count_limit}} with Title, Visual Composition, and Key Metric)
- Visual Treatment Guidelines (Grid, Iconography, and {{design_system_tone}} rules)
- Next Steps and Sign-off
Self-review
- Does the deck outline stay strictly within {{slide_count_limit}} slides?
- Is {{core_metric_gain}} clearly highlighted as the primary visual proof point?
- Are the layout descriptions easy for a graphic designer to build without ambiguity?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.