1982 – today
For forty years, the screen has asked you to feed it.
Type. Copy. Paste. Re-key. Reconcile. Repeat.
There's another way down here ↓
What if your software grew back?
Not a database you feed. A living structure that every person, and every agent, adds to. Something that compounds.
Layer 1 · Bedrock · Group
It starts with what's true.
Companies, ownership, directors, the filing calendar, pulled from Companies House. The bedrock every business already has, finally made solid.
| Company | Ownership | Next filing |
|---|---|---|
| HoldCo | Owned by the founders | 2027-01 |
| PropCo | 100% HoldCo | 2026-12 |
| OpCo – Pendle | 100% HoldCo | 2027-03 |
| OpCo – Burnley | 100% HoldCo | 2027-04 |
Layer 2 · Places & assets
Then the places come alive.
Clubs, courts, opening hours, price cards. Every change is previewed, then approved. Nothing moves without a yes.
Current: £18 per court-hour.
Layer 3 · Memory
The reef remembers. And it shows its working.
Every fact has a source and a date. Club, property, people, systems, money, rules. Memory you can check, not a black box.
Court 3 is floodlit until 22:00.
- Source
- Club handbook (illustrative)
- Date
- 2026-02
Layer 4 · Workflows — "object algorithms"
This is where the work starts doing itself.
Each workflow is a living branch. It starts by suggesting. Earn trust, and it acts on a yes. Earn more, and it acts and reports back. But every branch has a ceiling it will never pass, and a named human who approves it.
Pendle Padel: 44 workflows defined. 7 built. The reef is just getting started.
Touch a branch
- Suggest
- Acts on a yes
- Acts and reports
- Ceiling
Workflow list (text version)
| ID | Workflow | Status | Ceiling | Approver |
|---|---|---|---|---|
| WF-05 | Booking log | Built | Acts and reports | Owner |
| WF-06 | Court closure | Built | Acts on a yes | Club manager |
| WF-36 | Group memory | Built | Acts and reports | Owner |
| WF-41 | Court register | Built | Acts and reports | Club manager |
| WF-42 | Opening hours | Built | Acts on a yes | Club manager |
| WF-43 | Price card | Built | Acts on a yes | Owner |
| WF-44 | Cancellations | Built | Acts and reports | Finance |
| — | Gap finder | Defined | Acts on a yes | Owner |
| — | Fill-the-four | Defined | Acts on a yes | Club manager |
| — | Win-back | Defined | Acts on a yes | Club manager |
| — | Leagues | Defined | Acts on a yes | Club manager |
| — | Playtomic payout check | Defined | Acts and reports | Finance |
| — | Intercompany rent | Defined | Acts on a yes | Finance |
| — | Marketing calendar | Defined | Acts on a yes | Owner |
| — | Site finder | Defined | Suggest | Owner |
| — | Venue pipeline | Defined | Acts on a yes | Owner |
| — | Burnley FC partnership | Defined | Acts on a yes | Owner |
| — | 27 further workflows | Defined | — | — |
Everyone who touches it makes it stronger.
The owner sets the rules. The accountant's knowledge sets the books straight once, for good. The coach, the marketer, the landlord, the players, and the agents working beside them. Every contribution becomes a polyp. Every polyp compounds.
Tend the reef: press a participant, or drag one onto the reef. Each can be added three times.
An illustrative Tuesday
One empty court. Seven moves. Zero data entry.
- 19:00 Tuesday. Court 3 is empty.
- Gap finder spots it. Playtomic, bookings in
- Player agent offers it to four suitable players. WhatsApp, out
- Booked and paid. Playtomic / Revolut
- Reconciled automatically. Xero
- Highlight clip posted. Court cameras → Instagram
- Demand data feeds next week's pricing. And next Tuesday, it starts smarter.
Illustrative journey. Based on workflows defined for Pendle Padel, not live data.
One ocean floor. Every industry.
The bottom layers don't change: group, places, memory, record, feeds. Only the top is industry-specific. So every new reef grows faster than the last, and every builder who adds a vertical makes the whole floor richer.
Build vertical tooling on infrastructure that's already alive.
Padel and Fashion are built examples. Gym, Salon, Café and Farm diversification are illustrative concepts. The bars compare time to first workflow: shorter is sooner. No units.
Under every reef
Built on Generative Objects
Every reef starts as a living model of a business: its companies, assets, rules, permissions and workflows. Generative Objects compiles that model into a working platform, producing the same result every time. Anyone who works with the business can add to it, from the owner to an accountant, a supplier or a customer. Each addition is a small, checked change that a person approves, so new layers never break the ones underneath.
- Privacy
- Your data is never used to train someone else's AI.
- Security
- Access rules are built into the model, so people only see and do what they're allowed to, and every action can be traced back to who did it.
- Data sovereignty
- Small local models run on your own infrastructure, so your data stays where you put it.
- Business sovereignty
- The code is open and you own it outright, with no vendor lock-in and no platform taking a cut.
AI grows the reef, people approve it, and the business owns it.
Built by everyone. Owned by you.
Your harness runs on your GitHub and your Cloudflare. Your data, your workflows, your reef. Value stays with the people who grow it, not with a platform taking a rake.
Don't feed the machine. Grow the reef.
Or write to hello@verticalreef.example