Enterprise Treasury Infrastructure Outbound Sales Script
Generate a multi-touch B2B outbound email script targeting corporate treasurers and CFOs.
Use this template when launching a cold email sequence to financial decision-makers regarding payment rails and liquidity optimization. It builds a metrics-driven value proposition focused on interchange fee reduction and settlement speed.
Role: Principal Enterprise FinTech Sales Specialist targeting Fortune 1000 treasury teams.
Context
- Target executive persona: {{prospect_title}}
- Target enterprise: {{target_company}}
- Incumbent infrastructure or gateway: {{current_settlement_provider}}
- Estimated annual merchant volume: {{annual_payment_volume}}
- Identified operational friction: {{latency_or_fee_friction}}
- Proposed modern rail solution: {{proposed_rail_architecture}}
Task
Produce an enterprise outbound sales email script sequence that exposes inefficiencies in {{current_settlement_provider}} and positions {{proposed_rail_architecture}} as the optimal mechanism to eliminate {{latency_or_fee_friction}} across {{annual_payment_volume}} in annual throughput.
Method
- Target the strategic priorities of {{prospect_title}} regarding treasury yield and working capital management.
- Highlight industry benchmarks for {{latency_or_fee_friction}} without making defamatory claims against {{current_settlement_provider}}.
- Quantify potential annual savings and working capital velocity gains based on {{annual_payment_volume}}.
- Articulate the technical differentiation of {{proposed_rail_architecture}} in simple, executive terms.
- Construct Email 1 as a problem-agitation script contrasting batch processing against real-time settlement.
- Construct Email 2 as a financial model teardown offering a customized ledger impact assessment.
- Construct Email 3 as a peer benchmarking script referencing enterprise treasury transformations.
Constraints
- MUST maintain an enterprise corporate tone focused on risk mitigation, capital efficiency, and security.
- MUST NOT make explicit settlement uptime guarantees without qualified disclaimers.
- Word count per email script MUST be between 120 and 190 words.
- Call to actions MUST request a 15-minute introductory alignment call, not an immediate product demo.
Output format
Format the output into three structured components:
- Sequence Strategy Note (1-2 sentences on sending cadence)
- Cold Email Scripts (Email 1: Cold Open, Email 2: Business Case, Email 3: Peer Benchmark, each with 2 Subject Line variants, Body, and Call to Action)
- Objection Pre-emption Appendix (2 common treasury pushbacks and 1-sentence rebuttal hooks)
Self-review
- Confirm {{target_company}} and {{prospect_title}} variables are properly contextualized.
- Validate that all calculations or references to {{annual_payment_volume}} sound commercially realistic.
- Ensure each script clearly contrasts {{current_settlement_provider}} with {{proposed_rail_architecture}}.
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.