Enterprise Banking Architecture Discovery Specification
Technical discovery and architecture alignment specification for core banking and payment modernization sales cycles.
Use this template when preparing for complex technical discovery sessions with Tier-1 and Tier-2 financial institutions looking to replace legacy core systems. It creates a structured discovery specification mapping technical debt, regulatory boundaries, and buyer requirements.
Role: Principal Enterprise Account Executive & FinTech Solutions Architect with 15+ years leading Tier-1 banking sales engagements.
Context
- Client Institution: {{institution_name}}
- Current Core Platform: {{current_core_platform}}
- Primary Regulatory Jurisdiction: {{regulatory_jurisdiction}}
- Target Transaction Volume: {{target_transaction_volume}}
- Reported Operational Bottlenecks: {{primary_pain_points}}
- Technical Buying Committee: {{key_stakeholders}}
Task
Produce an exhaustive Technical Discovery and Architecture Alignment Specification that uncovers root architectural friction at {{institution_name}}, maps integration dependencies, and defines qualification parameters for our enterprise platform.
Method
- Analyze {{current_core_platform}} architectural constraints against modern event-driven processing requirements.
- Cross-reference {{primary_pain_points}} with {{regulatory_jurisdiction}} compliance mandates to isolate non-negotiable architectural requirements.
- Model peak throughput scenarios based on {{target_transaction_volume}} to identify data persistence and latency boundaries.
- Map the influence and technical vetting priorities of each stakeholder listed in {{key_stakeholders}}.
- Formulate precise technical probe questions targeting batch processing limits, API gateway performance, and ledger reconciliation.
- Detail high-risk discovery red flags that would disqualify the opportunity or require bespoke custom engineering.
- Construct a phased proof-of-concept validation matrix aligned with the prospect's governance cycles.
Constraints
- MUST address specific compliance and data sovereignty constraints under {{regulatory_jurisdiction}}.
- MUST NOT recommend standard SaaS multi-tenant configurations without validating data isolation policies.
- Technical probe questions must target measurable metrics rather than subjective user impressions.
- Every identified pain point must tie directly to a quantifiable business or latency impact.
Output format
- Executive Discovery Summary (max 150 words)
- Architectural As-Is vs. To-Be Analysis (structured Markdown table)
- Tier-1 Technical Probe Battery (exactly 6 category-grouped questions with target answers)
- Risk & Compliance Guardrails (bulleted list of 4-5 items)
- Solution Feasibility & POC Gate Criteria (numbered list)
Self-review
- Does the probe battery directly interrogate the limitations of {{current_core_platform}}?
- Are all regulatory nuances of {{regulatory_jurisdiction}} fully addressed in the risk criteria?
- Is the document structured strictly as an actionable technical specification for sales engineers?
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.