02 / DESIGN
Specify how the
capability will operate.
Turn a selected operating route into the requirements, interfaces and responsibilities an implementation team can work from.
The decision is made.
The design needs detail.
A route identifies the approach. Architecture establishes how it will work: the state of a subscription, the authoritative investment record, the system interfaces, the wallet and custody model, and how people resolve exceptions.
We agree the design scope after reviewing your existing material. A completed Operating Route is useful input, but equivalent work from your own team can also be assessed.
The architecture package
- Process and data flows with named owners and authoritative records.
- System and provider responsibilities, interface requirements and operating assumptions.
- Investor journey and exception scenarios.
- Security, access, wallet and custody decisions assigned to the responsible specialists.
- Implementation work packages, acceptance criteria and test approach.
- Cost and dependency register, procurement questions and handover requirements.
Detailed scope, duration and fee depend on the agreed systems, provider participation and available evidence. Legal conclusions and regulated services remain with the appropriate providers.
A design that supports procurement.
The output should make it possible to compare implementer proposals against the same requirements. Unresolved choices stay visible, with an owner and a decision date.
Discuss your architecture ↗
