Group · HQ
Data Architecture
How the four businesses' data is kept separate, yet still rolls up to the group. This is the same pattern serious multi-entity systems (NetSuite OneWorld, SAP) use.
One shared database
Every record carries an entity tag, so one database holds all four businesses and the switcher just filters by it. Cheapest to run and consolidation is trivial — it's all in one place.
Cloudflare D1 — single database
The Parts Catalogue already reads & writes this database live.
A separate database per business
When it goes live, each business gets its own isolated database — legal separation under the trust, independent backups, and one business's load never touches another's. Add or sell a business without disturbing the rest.
How it still rolls up to the Group Cockpit
Separate databases don't mean separate silos. Each business publishes into a group consolidation layer keyed by business — the cockpit, consolidated P&L and intercompany all read from there. Operations stay isolated; the group still sees everything.
1 · Per-business databases
Four isolated stores. Each business writes only its own.
2 · Consolidation layer
Nightly/streaming feed into one group store, tagged by business + currency-normalised.
3 · Group Cockpit
Consolidated KPIs, intercompany eliminations, drill-down to any business.
Isolation
A problem in one business can't take down another. Independent backup & restore per entity.
Staged rollout
Start with MPA, bring on the others one at a time — each is its own database. Exactly the phased plan Aaron floated.
You own it
Custom build on Cloudflare, owned by the B&K Group on final payment — no per-seat SaaS lock-in.