Sales emails
AuraScore 81/100

Mid-Market Treasury Solutions Email Sequence Quality Audit

Verify corporate treasury sales emails against CFO pain points, fee transparency, and conversion clarity.

Deploy this template when preparing outbound sequences targeting corporate treasurers and CFOs. It produces a systematic checklist evaluating working capital hooks, software compatibility, and commercial banking trust factors.

Template

Role: Commercial Banking Solutions Director specializing in mid-market treasury and liquidity sales

Context

  • Target executive persona: {{target_cfo_segment}}
  • Core treasury solution: {{treasury_product_focus}}
  • Competitor bank friction: {{incumbent_bank_friction}}
  • Prospect revenue band: {{annual_revenue_band}}
  • Value proof point: {{client_case_metric}}
  • Sequence touchpoint stage: {{outreach_cadence_stage}}

Task

Generate a comprehensive sales email audit checklist that commercial banking relationship managers can use to inspect outgoing cold emails for strategic relevance, financial pain alignment, and response triggers.

Method

  1. Map {{target_cfo_segment}} daily treasury challenges against the proposed {{treasury_product_focus}}.
  2. Diagnose whether the email directly references {{incumbent_bank_friction}} without sounding hostile or ungrounded.
  3. Verify that messaging reflects the operational complexity of {{annual_revenue_band}} enterprises.
  4. Check the presentation of {{client_case_metric}} for executive credibility and lack of jargon.
  5. Evaluate tone appropriateness for {{outreach_cadence_stage}} within an enterprise sales cadence.
  6. Structure actionable checklist items across Hook, Pain Alignment, Operational Proof, and Next Step.
  7. Include specific red-flag indicators for every checklist item.

Constraints

  • Output MUST follow standard Markdown checkbox syntax (- [ ]).
  • Checklist MUST NOT exceed 15 total diagnostic items.
  • Every item must include a designated "Red Flag" symptom indicating failure.
  • Do not use generic B2B SaaS tropes; language must strictly reflect commercial banking operations.

Output format

1. Sequence Stage Validation Overview

[Summary of sequence position: {{outreach_cadence_stage}} for {{target_cfo_segment}}]

2. Stage-by-Stage Email Inspection Checklist

A. Executive Hook & Context
  • [ ] [Item Name]: [Standard] | ⚠️ Red Flag: [Symptom]
B. Working Capital & Treasury Value
  • [ ] [Item Name]: [Standard] | ⚠️ Red Flag: [Symptom]
C. Evidence & Credibility Metric
  • [ ] [Item Name]: [Standard] | ⚠️ Red Flag: [Symptom]
D. Low-Friction Closing Ask
  • [ ] [Item Name]: [Standard] | ⚠️ Red Flag: [Symptom]

3. Readiness Scoring Rubric

[Minimum passing criteria before sending to {{target_cfo_segment}}]

Self-review

  • Ensure the checklist targets treasury and cash management themes explicitly.
  • Verify all 6 context variables are used in the prompt body logic.
  • Confirm every section in the output format contains unambiguous diagnostic checks.
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
financial-services
commercial banking
treasury sales
cfo outreach