Wealth workflows
Financial products are connected systems.
A financial product is more than a customer interface. We design the connected workflows across customers, financial decisions, transactions, data and operations with deeper expertise across wealth and investment products.

Acquire
Build digital acquisition journeys that connect lead capture, qualification, financial discovery and conversion.

Onboard
Create secure onboarding experiences across identity verification, suitability, KYC/AML, documentation and account opening.

Plan & Invest
Web, mobile, APIs, background work and the integrations that hold the product together.
What sits underneath
Great wealth experiences run on strong systems.
We work across the customer layer, adviser workflows, data and integrations, and the operational tooling required to keep the product moving.

Client experience
Make complex financial information understandable and actionable. - Portfolio & performance - Goals & financial planning - Cash & transactions - Documents & communication

Adviser workspace
Give advice teams the context and controls to serve clients efficiently. - Client 360 - Planning & recommendations - Tasks & reviews - Portfolio actions

Investment workflows
Connect decisions to the investment process. - Model portfolios - Allocation & rebalancing - Orders & execution - Performance & attribution

Data & integrations
Work with the ecosystem rather than pretending it does not exist. - Custodians & brokers - Market & reference data - CRM & planning systems - Identity & document providers

Operations
Build the internal product alongside the customer product. - Exceptions & approvals - Reconciliation - Case management - Audit trails & reporting

Intelligence
Use AI where it improves a real financial workflow. - adviser assistance - Document intelligence - Portfolio insights - Human-reviewed automation
When partnering with Gunpowder Innovations, your digital initiatives meet the highest quality, security and regulatory standards without slowing down the work.
ISO 9001
Ensures consistent quality management and reliable banking software delivery.

PCI DSS
Protects payment card data and secures financial transactions.

ISO 27001
Strengthens information security and reduces cybersecurity risks.

GDPR
Protects customer data and ensures privacy regulation compliance.

ISO 20022
Standardizes financial messaging between banks and payment systems.
PSD2
Enables secure open banking and regulated third-party integrations.
What sits underneath

01. App entry and onboarding start
A person arrives from a store listing, a deep link or a web page, and a session, a device record and a partial application come into existence before anything is verified. Breaks when onboarding is resumable in the design but not in the data, so someone who closes the app at step four comes back to step one and does not come back again.

02. Identity and eligibility
Document capture, liveness, sanctions and PEP screening and eligibility rules run against your provider, and each returns an outcome the product has to hold. Breaks when a check returns refer rather than pass or fail and the flow has no state for it, so a real customer sits in limbo and no agent has a screen to move them from.

03. Account and ledger creation
An account is opened with the partner or core, an entry is written to the ledger, and identifiers, limits and entitlements are assigned. Breaks when the partner call succeeds, the local write fails, and the retry carries no idempotency key, so the customer ends up with two accounts and one of them holds money.

04. Funding
The first money arrives by open banking initiation, card top-up or inbound transfer, and it settles on a timeline the interface has to represent honestly. Breaks when the balance is served from a local cache after card authorisation but before settlement, so a customer spends against funds that later fail to settle.

05. Money movement
A payment is initiated, checked against limits, scored for fraud, sometimes stepped up for authentication, then submitted to the rail. Breaks when the step-up fires after the interface has already shown success, so the customer reads confirmation and then a hold, and support hears about it first.

06. Status, notifications and reconciliation
Callbacks return from processors and partners, are retried and occasionally duplicated, and drive both the customer notification and the internal reconciliation. Breaks when callbacks arrive out of order and a stale earlier state overwrites the terminal one, so a settled payment reverts to pending on the customer screen.

07. Support, dispute and the record
An agent opens the case, reads what happened, answers the customer, and the exchange becomes part of the complaint and dispute record. Breaks when the console shows current state but not the sequence of events, so nobody can tell the customer why the payment failed rather than that it failed.
Fixed scope
Focused delivery
One workflow, end to end
Take one high-value journey onboarding, portfolio review, investment proposal or another critical flow from discovery through production.
Ongoing
Dedicated product team
A cross-functional team across product, UX/UI and engineering working against your roadmap and existing technology ecosystem.
Questions financial teams ask
Clear answers to the questions that come up before a project starts.
Can you work with our existing wealth technology?
Can you design for both investors and advisers?
Do you build the investment infrastructure itself?
How do you approach security and access?
Can you take a new wealth product from idea to launch?























