Story · 2 min
Over a Pint
I should probably tell you how this actually started, because it wasn't in a boardroom and it definitely wasn't in a strategy deck.
Read
Rhizel Systems
Every business is different.
The patterns aren't.
We build practical, AI-powered software that removes operational friction — so teams get back to doing what they do best.
Scene two
A wall of things
people actually say.
Collected quietly from hundreds of businesses. Different industries. The same sentences.
We still print this every Friday.
Nobody trusts this report.
Only Sarah knows how this works.
We enter this twice.
Systems don't talk to each other.
Managers spend hours chasing information.
We need something that doesn't exist.
We've always done it like this.
The spreadsheet broke again.
Half the fields are left blank.
Everyone has their own version.
It only works if you know the trick.
Scene three
These aren't isolated frustrations.
They're recurring patterns.
Once you've seen them a hundred times, they stop being surprises. They start being the shape of the work.
01
Duplication
Work happening twice, in two systems, by two people.
02
Trust
The numbers exist. Nobody quite believes them.
03
Knowledge silos
The business runs on what one person happens to remember.
04
Disconnection
Systems that were bought separately and never spoke since.
Scene four
Patterns become
solutions.
Each one started as a frustration we kept hearing. None started with the word "software".
Forecasting
01- The pattern
- Decisions made from stale spreadsheets, gut feel, and last month's numbers. Nobody trusts the forecast enough to act on it.
- The solution
- A quiet layer over the systems you already run. It reads what's actually happening and shows the week ahead in plain language.
- The outcome
- Ordering, staffing, and stock decisions stop being arguments and start being conversations.
Feedback
02- The pattern
- Signals arrive from six directions — reviews, emails, complaints, staff comments — and none of them meet in the middle.
- The solution
- One place where every voice lands, is understood in context, and is routed to the person who can actually fix it.
- The outcome
- Recurring issues surface in days rather than quarters, and the team stops relearning the same lesson.
Compliance
03- The pattern
- Expensive platforms bought to satisfy an auditor, then quietly abandoned because nobody wants to use them.
- The solution
- A lightweight layer built around your existing routines — checks happen where the work happens, not in a separate world.
- The outcome
- Audits become boring. Which is the point.
Operations
04- The pattern
- The same fifteen small tasks every day, done slightly differently by whoever is in that morning.
- The solution
- A calm operational spine that everyone works from, with room for the human judgement that makes the business good.
- The outcome
- New starters get up to speed in weeks, not months, and the founder stops being the bottleneck.
Integrations
05- The pattern
- Five systems that don't speak to each other, held together by copy-paste and a person who's been there long enough to remember.
- The solution
- A quiet translator between the tools you already own — nothing to rip out, nothing new to learn.
- The outcome
- Data moves on its own. The person doing the copy-paste gets their afternoons back.
Workflow
06- The pattern
- Approvals stuck in inboxes. Handovers lost between shifts. Work waiting on someone who's on holiday.
- The solution
- A workflow shaped like your business — not a generic template — that keeps things moving without needing to be nagged.
- The outcome
- Cycle times shrink. The team stops chasing and starts finishing.
Custom Applications
07- The pattern
- The thing you actually need doesn't exist. The nearest software costs more than it saves and doesn't quite fit anyway.
- The solution
- A small, considered application built around the way you work — practical, quick to ship, easy to change.
- The outcome
- The tool becomes part of the business rather than something the business works around.
Scene five
Organised by pattern.
Not by industry.
03Read
Integrations · Restaurant group finance
We stopped Finance being a human pipe between two systems.
Scene six
How we work.
Simply, in five steps.
- 01
Listen
Before anything else. To the business, not the brief.
- 02
Recognise the pattern
The same knots show up everywhere. We name them.
- 03
Design around the business
The software adapts. The team keeps what makes it good.
- 04
Build quickly
Weeks, not quarters. Rough in use beats polished in a deck.
- 05
Improve continuously
Every fortnight. Forever.
Scene seven
A living library of
operational thinking.
Philosophy · 4 min
Why Now? The Great Software Misunderstanding
I've become slightly obsessed over the last couple of years with constraints, in the way you become obsessed with something once you've noticed a pattern and then start seeing it everywhere.
ReadMethod · 4 min
Start With the Work
One of the strangest realisations I've had over the last few years is that I don't think I work in technology anymore.
ReadFinal scene