Contents

Business operations design

The operating model behind the licence: how the business runs every day, who does what, and which controls prove it — designed before go-live, not after the first finding.

Who this is for

  • Applicants that need an operating model to describe in their licence file
  • Newly licensed firms preparing to go live
  • Established companies launching a regulated or digital line of business
  • Firms scaling quickly whose processes have outgrown the team

1From the operating model to the first day of business.

No.AreaWhat we help you prepare
1.1Target operating modelHow the business creates and delivers its serviceOperating model blueprint, capability map, in-house vs outsourced decisions
1.2ProcessesEnd-to-end flows from onboarding to settlementProcess maps, procedures, handoffs and service levels
1.3ControlsHow each risk in a process is prevented or detectedControl matrix with owners, frequency and evidence
1.4Organisation and rolesWho is accountable for whatOrganisation chart, role descriptions, key-person responsibilities
1.5Systems and vendorsThe platforms and providers the model depends onRequirements, selection support, outsourcing documentation
1.6Go-live readinessProof that the business can operate as describedReadiness checklist, dry runs, open-items log
01Licence condition
02Policy clause
03Process step
04Control
05Evidence
06Inspection
Client assets must be kept separate from company assets
Client asset policy sets segregation and daily reconciliation
Operations reconcile client wallets against the ledger each day
Reconciliation reviewed and signed off by a named owner
Signed daily reconciliation reports, kept on file
The inspector samples days and gets the same answer
One example row. We build this chain for every condition, so nothing in the file depends on a promise alone.

Figure 6Every commitment in the application can be traced to evidence.

2An operating model that matches what you told the regulator.

  1. 2.1

    Operating model blueprint

    Capabilities, flows, in-house and outsourced components, and how they connect.

  2. 2.2

    Process and procedure set

    End-to-end processes with procedures written for the people who run them.

  3. 2.3

    Control matrix

    Risks per process, the controls that address them, owners and evidence.

  4. 2.4

    Organisation and role design

    Structure, role descriptions and key-person responsibilities for hiring and handover.

  5. 2.5

    Go-live readiness review

    Every commitment in the licence file checked against what is actually in place.

3Indicative durations — set in your assessment.

01 Assess
02 Design
03 Build
04 Go-live

4Go-live checklist · preview

  • Every process in the licence file has an owner and a procedure
  • Control matrix covers each key risk with evidence defined
  • Key persons appointed and briefed on their responsibilities
  • Outsourcing agreements signed with oversight in place
  • Dry run completed for onboarding, transactions and complaints
  • + the full checklist, shared after your assessment

5Straight answers, before the first meeting.

5.1Why design operations before the licence is granted?
Because the licence file describes how you will operate, and the regulator will test that description. Designing it once avoids rewriting both later.
5.2Do you implement systems?
We define requirements, support selection and document the arrangements. Implementation stays with your technology team or vendor.
5.3Can this work for a non-regulated digital business?
Yes. The same method applies to any business that needs clear processes, controls and accountability before it scales.
5.4What do you need from us to begin?
Your business model, current organisation and the systems you use or plan to use. A 30-minute call is enough to set the scope.

Design the business you will operate — before you have to explain it.