Delivering clarity, precision, and control to complex financial services programmes
Financial institutions need flawless business analysis to deliver regulatory, operational, and systems change successfully. Poor requirements lead to rework, failed UAT, and budget overruns. I provide Tier-1 quality BA services that keep programmes on track.
Is this you?
- β Missing or unclear requirements causing confusion and rework
- β Failed UAT because requirements weren't clear or testable
- β Budget creep and overruns due to scope changes
- β Production defects from incomplete functional specifications
- β Stakeholder misalignment - everyone has a different understanding
- β Low-quality documentation that doesn't pass audit or governance
If these sound familiar, you need expert business analysis support.
What I deliver
Business Requirements Documents (BRDs)
- Business context - Why this change matters
- Stakeholder needs - What each group requires
- Success criteria - How we measure delivery
- Dependencies - What relies on what
Functional Requirements Documents (FRDs)
- Detailed functional specs - Exactly what the system must do
- Process flows - How the solution works end-to-end
- Business rules - Logic, calculations, validations
- Integration requirements - How systems connect
Non-Functional Requirements (NFRs)
- Performance - Volume, speed, latency targets
- Security & access control - Who can do what
- Audit & compliance - Regulatory needs
- Data retention & archiving - How long data lives
User Stories & Acceptance Criteria
- Agile-ready stories - "As a [user], I need [capability], so that [benefit]"
- Acceptance criteria - Clear pass/fail conditions
- Story mapping - Prioritization and release planning
Requirements Traceability Matrix (RTM)
- Full traceability - Business need β requirement β test case
- Impact analysis - What changes affect what
- Regulatory mapping - Which requirements meet which regulations
Gap Analysis (Current vs. Future State)
- As-is analysis - What exists today
- To-be design - What's needed
- Gap identification - What must change
- Solution options - Build vs. buy vs. configure
Stakeholder Workshop Facilitation
- Requirements elicitation - Uncovering the real needs
- Consensus building - Aligning conflicting stakeholders
- JAD sessions - Joint Application Design workshops
- Show & tell - Demo and feedback loops
Test Strategy, UAT Approach & Test Scripts
- Test strategy - SIT, UAT, regression approach
- UAT test scripts - Scenario-based, traceable to requirements
- Test data requirements - What data is needed for testing
- Defect triage - How to prioritize and resolve issues
What this solves
Missing or Unclear Requirements
Capture complete, unambiguous requirements that developers can implement confidently.
Rework, Overruns & Budget Creep
Get it right the first time with clear, testable, traceable requirements.
Failed UAT or Production Defects
Write acceptance criteria that ensure the solution meets business needs before go-live.
Low-Quality Documentation
Deliver audit-ready, governance-compliant artefacts that regulators and stakeholders trust.
Deliverables
You receive Tier-1 bank quality BA documentation:
β
Business Requirements Documents (BRDs)
β
Functional Requirements Documents (FRDs)
β
Non-Functional Requirements (NFRs)
β
User Stories & Acceptance Criteria
β
Requirements Traceability Matrix (RTM)
β
Gap Analysis (Current vs. Future State)
β
Functional/Data Mapping Specifications
β
Test Strategy & UAT Scripts
All in Confluence, Word, Excel, JIRA, or your preferred format.
Who this is for
- Investment Banks - Trading platforms, risk systems, regulatory reporting
- Commercial Banks - Payments, core banking, digital channels
- Asset Managers - Fund accounting, order management, compliance systems
- Broker-Dealers - Trade processing, settlement, reconciliation platforms
- Regulatory Programmes - ECB, PRA, FCA change initiatives
Typical engagement
Week 1-2: Discovery & Requirements Elicitation
- Stakeholder interviews (business, operations, IT, risk)
- Current state analysis
- Requirement workshops
- Documentation of initial requirements
Week 3-6: Requirements Documentation
- BRD, FRD, NFR creation
- User story development
- Requirements traceability matrix
- Review cycles with stakeholders
Week 7-8: UAT Preparation & Handover
- Test strategy and UAT approach
- UAT test script creation
- Requirements sign-off
- Handover to development/testing teams
Pricing
BA Engagement (Project-Based): Β£18k - Β£55k
Duration: 4-10 weeks
Scope: Full BA lifecycle (requirements β UAT)
BA Resource (Time & Materials): Β£850-Β£1,200/day
For ongoing programme support
BA Sprint Support: Β£6k-Β£10k/sprint
For agile programmes needing BA capability
Real results
Tier-1 Investment Bank (Risk Platform Upgrade)
Challenge: Unclear requirements causing rework, 3-month delay, failed SIT
Delivered: Complete FRD, NFRs, RTM, UAT scripts, stakeholder alignment
Result: Successful go-live on revised timeline, zero critical defects
European Commercial Bank (Payments Hub Migration)
Challenge: Missing requirements for regulatory reporting, audit concerns
Delivered: BRD with full regulatory mapping, data lineage, test strategy
Result: Regulatory requirements met, audit approval, smooth migration
Start here
Free: Requirements Quality Review
Send me your current requirements document (BRD, FRD, or backlog). I'll send back a 10-minute Loom with:
- What's missing or unclear
- Key risks and gaps
- Quick wins for improvement
Paid: Choose Your Engagement
Requirements Sprint (Β£15k-Β£25k, 3-4 weeks)
- BRD or FRD for a defined scope
- User stories with acceptance criteria
- Requirements traceability
- Stakeholder workshops
- Review and sign-off
Full BA Programme (Β£35k-Β£55k, 8-10 weeks)
- Complete BA lifecycle
- BRD, FRD, NFR documentation
- User stories & RTM
- Gap analysis
- Test strategy & UAT scripts
- Stakeholder facilitation
- Sign-off and handover
BA Resource (Day Rate) (Β£850-Β£1,200/day)
- Embedded BA support
- Requirements analysis
- Documentation
- Stakeholder management
- Daily/weekly availability
Why work with me
β
Tier-1 bank experience - Delivered BA on major transformation programmes
β
Regulatory expertise - Understand ECB/PRA/FCA requirements
β
Agile & Waterfall - Comfortable with any methodology
β
Audit-ready quality - Documentation that passes governance reviews
β
Fast delivery - Clear requirements in weeks, not months
What makes great BA work
Bad BA work:
- β Vague "nice to have" statements
- β No acceptance criteria or testability
- β Missing non-functionals (performance, security)
- β No traceability to business needs
- β Stakeholders still confused
Great BA work:
- β Clear, unambiguous, testable requirements
- β Full traceability (business need β requirement β test)
- β Comprehensive NFRs (regulatory, performance, security)
- β Stakeholder consensus and sign-off
- β UAT scripts that validate delivery
- β Developers know exactly what to build
Next steps
- Free Review - Send me your current requirements doc
- Discovery Call - 30-minute discussion of your programme
- Proposal - Scoped BA engagement with clear deliverables
- Kick-off - Start requirements analysis in week 1