Framework

The map

Business Functions Framework

v1.1 · 98 leaves · A sector-neutral map of the functions every business runs, built to map AI automation onto. Three primary-flow boxes, three enabling boxes, and one substrate — the capability floor everything else runs on.

AI-MODE A Automate Au Augment O Optimise shell C Context-dependent Right code = work-type: I information · P physical · R relational · + mixed

Green leaves are the automate-first targets. Colour = AI-mode; right-edge code = work-type. Systems (7) is the floor every other box runs on, not a seventh peer — AI is a lens passed over boxes 1–6; Systems holds the shared plumbing the automations run on.

Edge cases

Seams to watch

Live adjacencies where one function touches two boxes — the places a mapping pass can misfile work.

Value prop ↔ Offer positioning

What the offer is (Make) vs. how it’s framed against alternatives (Sell). The tightest remaining adjacency.

Renewals ↔ Account growth

Keeping and growing an account is split by intent: the sales motion lives in Sell, the service-side outcome in Deliver.

Pricing’s three touch-points

Set in Make as offer design; informed by Sell; executed through Money’s invoicing. One function, three touch-points.

Reporting: content vs. pipe

Each box owns its reporting content; Systems owns the infrastructure — dashboards and the data pipe.

Two onboardings

Customer onboarding (Deliver) vs. Staff onboarding (People). Different objects, kept distinct by prefix.

The website seam

The website is an asset held in Systems 7a, but its work — attracting, capturing, converting — lives in Sell. Mirrors the Reporting seam.