The shape
One company, read two ways.
The org is a grid. Read it across and you see the business domains we sell into; read it down and you see the four craft chapters that build everything. Every person sits at one intersection — a domain and a craft.
Reads down ↓
Four craft chapters
Growth
Win and expand the business — turn interest into signed, growing revenue.
Discovery
Define the product in detail — journeys, requirements, design, and the why. Runs ahead of engineering.
Engineering
Build it to standard — owns architecture, quality, and the technical veto.
Delivery
Get clients live and keep them live — go-live plus run & SRE.
The base · serves all
Foundation
The shared core every domain reuses across all crafts — common standards, a design system, reusable services, templates and playbooks — so nothing is built twice.
The pivot
Every business domain (reads across →) is delivered by the same four craft chapters (reads down ↓) — one delivery lifecycle applied across all domains.
People belong to both a chapter (their craft) and a domain — that intersection is where the work happens.
Reads across →
Four business domains
Business Ops — P&L · pipeline · coordination & admin: the connective tissue above all four.
Enterprise AI & Automation
Generic and enterprise AI plus workflow automation — cost saved internally, revenue earned externally.
Digital Banking & Processing VAS
Bank-facing products and value-added services, delivered per segment.
Money Movement & Financial
Payment rails and regulated financial services.
Ecosystem & Bespoke
Partners, open APIs, and custom builds.
Labs Leader
Owns the Labs vertical's P&L. Every domain and shared function rolls up here.
This is the shape. Use Full matrix to see who does what, or How to read for the decisions behind it.
Foundation
Shared reusable core · standards · design system · integration — the base every team builds on. Serves all BUs.
Enterprise AI & Automation
Workflow automation + enterprise AIDigital Banking & Processing VAS
Bank-facing products + VASMoney Movement & Financial
Rails · regulated financeEcosystem & Bespoke
Partners · APIs · custom buildsBusiness Ops
P&L · pipeline · coordination · admin.
Cross-cuttingWorkflow Automation
Internal · cost-saving. Automating our own operations · applied AI · MLOps.
Enterprise AI
External · revenue. AI products sold to customers.
Retail
Card mgmt + core-banking journeys.
Merchant
Acceptance, settlement, VAS.
Corporate
Enterprise journeys, B2B.
IPN & Remittance
Instant payments, cross-border.
Non-Banking Financial
FRA-regulated services.
Ecosystem
Partner / open APIs.
Bespoke
Custom client builds.
Growth
Acquisition · presales · pricingDiscovery
PM + Design · runs aheadEngineering
Standards · QA · quality vetoDelivery
Go-live · run-ops · support · uptimeFaded column (Non-Banking Financial) is postponed, not yet staffed. Hue = domain · top-bar weight = level · left-accent cell = a craft seat.
Foundation
Shared reusable core — architects & platform.
Enterprise AI & Automation
Workflow automation + enterprise AIDigital Banking & Processing VAS
Bank-facing products + VASMoney Movement & Financial
Rails · regulated financeEcosystem & Bespoke
Partners · APIs · customBusiness Ops
Cross-cutting · serves every domain.
Workflow Automation
Cost-saving automation.
Enterprise AI
Revenue product.
Retail
The consumer app.
Merchant
Acceptance, VAS.
Corporate
B2B journeys.
IPN & Remittance
Rails, cross-border.
Non-Banking Financial
FRA-regulated · postponed to 2027.
Ecosystem
Partner / APIs.
Bespoke
Custom builds.
Growth
Acquisition · presalesDiscovery
PM + DesignEngineering
Standards · QADelivery
Go-live · run · support- Domain
- A top-level grouping — Foundation · Enterprise AI & Automation · Digital Banking & Processing VAS · Money Movement & Financial · Ecosystem & Bespoke. Reads across the top.
- Business line
- A box inside a domain (e.g. Retail, Enterprise AI, Ecosystem). The unit with its own market and, where relevant, its own P&L.
- Product
- A product or app a business line ships — shown as tags inside each line box (e.g. Retail: Banking App · Card App · AI PFM). One line can carry several.
- Chapter
- A craft function shared down every column — Growth · Discovery · Engineering · Delivery. People belong to a chapter (their craft) and serve a line.
- Cell / seat
- A chapter × business-line intersection — the actual work that craft does for that line.
- Business Ops
- The cross-cutting corner team. Serves every domain and chapter.
- Colour
- One hue per domain — slate = Foundation, blue = Enterprise AI & Automation, purple = Digital Banking, teal = Money Movement, amber = Ecosystem & Bespoke.
- Weight
- deep tint + thick bar = domain header · soft tint + thin bar = business line · faded + left accent = a craft seat.
- Faded column
- Planned but not yet staffed (currently Non-Banking Financial and Bespoke).
Digital Banking vs Retail — what's the difference?
Domain = the technology. Business line = the market.
Foundation owns the reusable core; the segment lines only configure it — they never own their own stack. That org boundary is what prevents three divergent codebases.
Why is Business Ops in the corner?
It's cross-cutting — it sits at the origin, not inside a domain.
Why merge Delivery and Reliability?
One chapter — Delivery — spanning go-live and run/SRE.
Reliability survives as a named SRE track inside Delivery, owning the uptime SLOs — the same "quality veto" pattern Engineering uses — so the stability voice isn't drowned by go-live pressure. Re-split when the SRE track alone needs a full on-call rotation.
Where does integration work live?
Split by commodity-vs-specialized, and inbound-vs-outbound.
The need often surfaces from a line (e.g. SMS for the Retail app), but the owner is Foundation if it's reusable — trigger ≠ owner. That's what keeps "same technology" true across every line.
Why is AI its own domain?
Enterprise AI & Automation — two lines: Workflow Automation + Enterprise AI.
The same scarce ML/MLOps people serve both, so they share one home (standards, tooling, hiring). Keeping the missions as separate lines protects two different scorecards — and builds in the internal→external path: automation proven on our own ops graduates into bespoke bank automation.
Two bosses — who's actually accountable?
Accountability follows the outcome — one name per result.
| Result | Accountable |
|---|---|
| The outcome — shipped, works, sells | Business line |
| Built well — quality, safety, scale | Engineering |
| On time / as promised | Delivery |
| Priority tie-break | Product |
Tip — click any title for its role scope, responsibilities & KPIs.
From heroics to a
scalable operating system
Modupay Labs works today because talented people stretch across too many roles. That is a strength — and a compounding risk. This is the operating model that trades heroics for structure, without losing startup speed.
The goal
Startup speed and execution discipline
Speed without discipline is chaos — missed commitments, reactive leadership. Discipline without speed is bureaucracy — stalled growth, frustrated talent. The model is built to hold both at once.
The core idea
Two owners for every piece of work
Business ownership — what we serve — runs down the markets; each business line owns its P&L. Functional ownership — how we execute — runs across the crafts; shared standards, shared people. Every initiative sits where a market meets a craft.
When the two owners disagree
The line owns the outcome; the craft owns the standard
Two managers, no tug-of-war. Your line / squad (solid) sets priorities, owns the outcome and writes your review; your craft chapter (dotted) owns the standard, the hiring bar, calibration and a quality veto. The line owns what, whether, when & the money; the craft owns who & how-well — real authority over outcomes, without letting delivery pressure erode the bar.
How ownership becomes visible
Every initiative names an owner at each step
Where it’s heading
Every craft, augmented by AI agents
Engineers already build with agents by default — there is no “engineering agents” box. The named role sits in Delivery: an AI delivery manager (agent orchestrator) who runs a workstream end-to-end — discovery to delivery — by directing a fleet of agents, with Foundation reviewing the output. Designing the org around this shift, rather than bolting it on later, is the advantage.
What it removes
The hidden risks of a people-dependent model
Multi-hat employees · tribal knowledge · vacant roles · leadership overload. On the Staffed view, the ★ (multi-hat) and +hire markers are exactly these gaps — surfaced so they can be closed, not carried indefinitely.
What it delivers
Five pillars
Isn’t this over-built for today?
Lean now, layered later
Today one person wears several hats — that is what the ★ marks on the staffing view. The chart is the destination, not day one: it fills in on triggers, not a calendar, so every hire and promotion already has a place to land.
The shift
What changes
From
Informal coordination. Individual heroics. Leadership memory.
To
Structured ownership. Scalable engines. System-driven accountability.
Not proposed: new VP layers, big-bang reorganisation, mass hiring, or process for its own sake. Proposed: clear ownership at every level, a phased transition, and a structure that grows with us.