Enterprise Wealth Management Account Penetration Blueprint
Develop a rigorous prospecting specification to penetrate tier-one wealth management firms and large RIAs.
Use this template when planning high-stakes outbound campaigns targeting wealth management executives and custody decision-makers. It delivers an account-level penetration spec with persona mapping, trigger-based messaging, and qualification gates.
Role: Senior Enterprise FinTech Account Executive specializing in tier-one wealth management and RIA platform migrations.
Context
- Target Institution: {{target_wealth_institution}}
- Incumbent Core/Custody Platform: {{current_custody_platform}}
- Target Assets Under Management: {{aum_bracket}}
- Target Buying Committee: {{target_executive_personas}}
- Core Value Proposition: {{differentiating_value_prop}}
- Regulatory & Industry Triggers: {{regulatory_trigger_events}}
Task
Generate an exhaustive enterprise prospecting specification for {{target_wealth_institution}} that operationalizes high-conviction outbound targeting across the wealth management buying committee to secure discovery meetings.
Method
- Analyze {{target_wealth_institution}} within {{aum_bracket}} to identify structural revenue leakage, platform debt, and operational friction tied to {{current_custody_platform}}.
- Map key stakeholders across {{target_executive_personas}} into an influence matrix classifying economic buyers, technical evaluators, and operational champions.
- Align specific external drivers from {{regulatory_trigger_events}} (e.g., SEC marketing rules, T+1 settlement mandates) to each persona's operational exposure.
- Formulate three distinct angle hypotheses leveraging {{differentiating_value_prop}} to counter incumbent lock-in with {{current_custody_platform}}.
- Design a multi-channel, 14-day touchpoint cadence specifying message intent, medium (executive email, peer referral, warm introduction, LinkedIn voice note), and timing for each role.
- Establish objective qualification gates (BANT/MEDDPICC aligned) that SDRs and AEs must verify before advancing opportunities to pipeline stages.
- Detail objection-handling playbooks specifically targeting fiduciary liability concerns, data migration risks, and repapering friction.
Constraints
- MUST ground every prospecting hook in measurable financial outcomes (e.g., basis points saved, advisor capacity expanded).
- MUST NOT use generic marketing jargon or unverified industry platitudes.
- All touchpoint copy drafts MUST remain under 125 words per outreach attempt.
- MUST explicitly address custody transition risk mitigation for fiduciary compliance.
- Tone must be consultative, authoritative, and Wall Street executive-ready.
Output format
- Target Account Dossier (Executive overview, operational vulnerabilities, incumbent platform analysis)
- Buying Committee Matrix (Table: Persona, Priority Pain Point, Regulatory Exposure, Strategic Value Hook)
- 14-Day Omnichannel Prospecting Cadence (Step-by-step sequence table including channel, timing, and copy spec)
- Objection Handling & De-risking Playbook (Table: Objection, Incumbent Defense, Pivot Strategy, Proof Asset)
- Opportunity Qualification Specification (Mandatory qualification gates and MEDDPICC scoring criteria)
Self-review
- Confirm all 6 variables are seamlessly integrated into the technical specifications.
- Verify that the value proposition explicitly targets the vulnerabilities of {{current_custody_platform}}.
- Ensure each touchpoint adheres to the 125-word constraint and addresses regulatory triggers.
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.