Remote-first · UK right to work
Grounding in reality. Establish the baseline facts first. Construct solely for essential requirements. Track only the metrics that evolve.
Superior software rarely fixes operational friction; identifying the core bottleneck does. Effective architecture accounts for the specific limitations of its environment, rather than mimicking frameworks designed for organisations with infinite resources.
For seven years, I have operated where this precision is mandatory: scaling nascent SaaS startups, navigating rigid logistics regulations, and managing non-profits fuelled by volunteer labour. My fundamental approach remains constant across these sectors — isolate what is objectively true, then engineer upward from that foundation.
Four principles that show up in everything I build — whether it's a CRM schema, a health score, or a Saturday-night events brief.
Every system is a data movement problem.
Before I touch a tool, I map where information comes from, where it needs to go, and what happens if it's late or wrong. The tool is just the last decision.
Build for the person who isn't you.
A system only works if it survives contact with someone who didn't design it — a new starter, a tired CSM, a client filling in a form at 11pm.
Constraints aren't failures — they're requirements.
"We don't have budget for that tool" or "this has to work on a shared spreadsheet" isn't a problem to apologise for. It's the actual brief. The best systems I've built came from taking the constraint seriously, not working around it.
Start simple. Add complexity only when scale demands it.
A system that's too sophisticated for its current scale is its own kind of technical debt — harder to hand over, harder to debug, and usually solving a problem nobody has yet.
On signal extraction, downstream relay, and the architecture behind good customer health scoring.
→The origin essay. How I found the language for work I had always been doing.
→On stakeholder motivation mapping, adoption design, and why systems fail when the people question comes second.
→If you're building something and need someone who builds systems that keep working when you're not watching — let's talk.
I'm actively looking for a mid-level CS Operations or Product Operations role at a remote-first B2B SaaS company. I hold dual UK-Nigerian nationality with the right to work in the UK without sponsorship.