FinTech Embedded Banking Integration Pitch
Craft a B2B sales email pitching modern core banking API infrastructure to regional financial institutions.
Apply this prompt when enterprise FinTech sales reps need to initiate contact with credit union or regional bank executives. It emphasizes core modernization, compliance speed, and new non-interest fee revenue.
Role: VP of Enterprise FinTech Sales specializing in core modernization, embedded finance, and regulatory infrastructure.
Context
- Target bank or credit union: {{financial_institution}}
- Executive recipient: {{executive_title}}
- Current legacy pain point: {{core_banking_bottleneck}}
- Solution capability: {{api_infrastructure_benefit}}
- Financial upside: {{projected_deposit_growth}}
- Deployment speed: {{integration_timeframe}}
Task
Generate a compelling B2B partnership email to {{executive_title}} at {{financial_institution}} that contrasts their existing {{core_banking_bottleneck}} with {{api_infrastructure_benefit}}, validating the business case via {{projected_deposit_growth}}.
Method
- Target the operational impact of {{core_banking_bottleneck}} on {{financial_institution}}'s customer retention.
- Present {{api_infrastructure_benefit}} as an overlay solution that prevents expensive core replacement.
- Quantify the revenue upside using {{projected_deposit_growth}} to anchor the business case.
- Highlight {{integration_timeframe}} to de-risk implementation anxiety for IT and compliance leaders.
- Draft a frictionless call to action offering a technical feasibility walkthrough.
- Produce two subject lines tailored to executive leadership priorities.
Constraints
- Body text MUST remain between 130 and 170 words.
- MUST NOT disparage legacy core vendors by brand name.
- You MUST quantify the implementation timeline accurately based on {{integration_timeframe}}.
- Maintain an authoritative enterprise partner tone.
Output format
- Subject Line Options (2 options)
- Salutation
- Hook (Legacy core constraint & market pressure)
- Value Proposition (API layer, speed, and deposit growth)
- Implementation Assurance (Timeframe & security compliance)
- Closing Call to Action
Self-review
- Does the copy emphasize an overlay approach rather than a risky rip-and-replace?
- Are the projected numbers from {{projected_deposit_growth}} realistically framed?
- Is the tone suitable for a senior {{executive_title}} in commercial banking?
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.