CHAPTER 01 · LAUNCH
DEFINE THE PRODUCT, ROUTE AND DELIVERY MODEL
Launch
Before anything is built, we define how the product will work, who performs each activity and what has to be true for it to go live.
WHAT YOU RECEIVE
- 01Customer journey
- 02Roles & responsibilities
- 03Product structure
- 04Control & evidence model
- 05Dependencies
- 06Implementation roadmap
STANDARD SPRINT
COMMERCIAL BASELINE
€7,500excl. VAT
For one defined product, journey and jurisdiction.
Target: ten working days once the agreed required inputs are available. This is not a promise to obtain a licence or launch a product in ten days.
1 · CUSTOMER JOURNEY
2 · ROLES
| activity | client | partner | normexa |
|---|---|---|---|
| onboarding policy | A | R | |
| journey design | A | R | |
| control testing | R | C |
3 · CONTROLS & EVIDENCE
4 · ROADMAP
- aThe journey, with the regulated decision point marked.
- bWho is accountable, responsible, consulted, informed.
- cEach control has an ID and an evidence owner.
- dDependencies sequenced into a delivery roadmap.
SERVICE ANATOMY
INPUT →
Opportunity, feasibility outcome, client decisions and required documents.
WORK →
Product architecture, flows, RACI, controls, technology and operating model.
DELIVERABLE →
The launch blueprint and delivery roadmap.
ACCEPTANCE
Launch acceptance gate — accept, revise or stop.
CHAPTER 02 · BUILD
IMPLEMENT THE AGREED SCOPE UNDER A SOW
Build
We implement what Launch defined — workflows, systems, integrations and the operating setup — and prove it works.
- 01
Product workflows
- 02
Systems and integrations
- 03
Testing and evidence
- 04
Operating readiness
ENTRY PRICE
€12,000from
For a bounded milestone under an agreed statement of work.
Complete engineering and external costs are scoped separately.
| item | test | evidence |
|---|---|---|
| onboarding flow | passed | filed |
| partner API | passed | filed |
| limits control C-02 | passed | filed |
| reconciliation C-03 | open | pending |
| reporting export | passed | pending |
| runbook | n/a | filed |
Every item in the agreed scope is tested and evidenced before the release gate. Open items block release — they are not waived.
SERVICE ANATOMY
INPUT →
Accepted blueprint and an agreed statement of work.
WORK →
Engineering, integrations, testing, evidence and operating setup.
DELIVERABLE →
Implemented and tested agreed scope.
ACCEPTANCE
Build acceptance & release gate — release, or remediate and retest.
CHAPTER 03 · OPERATE
RUN THE AGREED OPERATING MODEL
Operate
Contractually agreed ongoing operational support: the Operating Core, plus the modules your product actually needs. The authorised entity keeps its regulated activities.
Product Operations
- Customer journey and product support
- Product changes and releases
- Operational controls evidence
- Product performance reporting
Technology Operations
- Monitoring of agreed systems
- Vendor and integration management
- Release and environment management
- Access administration
Partner Operations
- Partner interface management
- Agreed reporting to the authorised entity
- Onboarding and offboarding coordination
- Oversight evidence packs
EXAMPLE SCOPE · O0 Operating Core + O1 Product Operations + O3 Partner Operations
Module scope, pricing and service levels are agreed per contract. No universal all-inclusive operating promise.
CORE BASELINE
€3,000setup
and from €2,500 / month for a bounded Core scope.
Additional modules and complex operations are scoped separately. Module prices and service levels are not published.
SERVICE ANATOMY
INPUT
Released product and an agreed Operate contract.
WORK
Operating Core plus selected modules: monitoring, coordination, reporting, change.
DELIVERABLE
The accepted contractual operating service.
REVIEW
Continuous review — continue, change or exit.
Not sure which service you need?
Most engagements start with Qualify — a conversation that scopes the opportunity before anything is priced.