Sales emails
AuraScore 81/100

Freight Forwarding Outbound Campaign Specification

Architect a structured, multi-touch sales email sequence specification targeting shippers for freight forwarding and carrier RFP inclusion.

Use this template when establishing an outbound email cadence to capture contract freight volume from mid-to-large cargo shippers. It maps value hooks, proof points, and structural constraints across primary and follow-up touchpoints.

Template

Role: Senior Freight Business Development Director specializing in enterprise logistics procurement

Context

  • Target shipper sector: {{shipper_industry}}
  • Buyer seniority and persona: {{target_job_title}}
  • Estimated cargo scale: {{annual_freight_spend}}
  • Primary route corridors: {{core_trade_lanes}}
  • Primary shipper vulnerability: {{primary_pain_point}}
  • Key operational moat: {{differentiating_capability}}

Task

Produce a comprehensive, technical sales email sequence specification document that equips enterprise logistics sales reps to prospect shippers across {{core_trade_lanes}}, positioning {{differentiating_capability}} to secure upcoming RFP bidding slots.

Method

  1. Analyze {{shipper_industry}} supply chain dynamics to identify trigger events that force a carrier review.
  2. Frame {{primary_pain_point}} in the context of cost volatility, spot exposure, or dwell times on {{core_trade_lanes}}.
  3. Establish specific message architecture for a 4-touch sales sequence (Initiation, Metric Proof, Case Study, RFP Soft-Close).
  4. Define subject line engineering rules, including length constraints, dynamic tokens, and spam avoidance criteria.
  5. Draft exact body copy specifications for Touch 1 through Touch 4 incorporating {{target_job_title}} decision criteria.
  6. Detail evidence requirements for each touch, integrating quantifiable efficiency claims tied to {{differentiating_capability}}.
  7. Map explicit behavioral branching logic (e.g., unopened, opened without reply, clicked lane data) for follow-up timing.

Constraints

  • MUST write exact email copy templates alongside the structural specification parameters.
  • MUST NOT use generic freight buzzwords such as 'seamless logistics', 'trusted partner', or 'end-to-end visibility' without operational definitions.
  • All touchpoints MUST state explicit calls to action centered on lane benchmark audits or RFP list inclusion.
  • Tone must be direct, commercially authoritative, and tailored to {{target_job_title}}.

Output format

Provide the specification in markdown using the following sections:

  1. Campaign Strategic Blueprint (Persona alignment, Lane economics, Trigger analysis)
  2. Sequence Cadence Matrix (Touch number, Day offset, Primary angle, Call-to-action)
  3. Touchpoint Specifications (For touches 1 to 4: Subject line variants, Body copy specification, Copy text, Variable requirements)
  4. Objection Handling & Branching Rules (3 common buyer deflections with pivot templates) Total word count must be between 700 and 1100 words.

Self-review

  • Verify that {{annual_freight_spend}} and {{core_trade_lanes}} directly inform the financial stakes in the copy.
  • Check that every email body contains fewer than 125 words of copy.
  • Ensure each touchpoint includes at least two subject line options.
  • Confirm the absence of prohibited buzzwords.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

emails
emails-sales
transport-logistics
freight
outbound
cadence