How I got here
- Age 9, the first buildsModding games, hosting servers, breaking things on purpose
It started with games. Modding them, hosting little servers for friends, figuring out why something crashed and how to make it not crash again. Nobody told me it was engineering. It just felt like the most interesting puzzle in the room, and it has been ever since.
- Age 14, the wiring problemTook everything apart to see how it actually worked
Computers, networks, locks, systems. If something had moving parts, I wanted to know why it moved that way. Most kids learned a tool. I learned to look at any system and ask where does this break, and who's the weakest link? That instinct never left.
- Age 18, inside one of the biggest names in techCybersecurity and application development at scale
Walked into a role at one of the world's largest tech companies, working across application development and cybersecurity. Security thinking forces a discipline most engineering doesn't: assume failure, design for the worst case, leave nothing held together by hope. That became the bar everything we build now gets held to.
- Five years of shipping, across industriesHealthcare, finance, real estate, energy — real systems, real stakes
Over five years I've helped win, shape and deliver production systems across some of the most demanding sectors there are, healthcare, finance, real estate, and energy & utilities, for large organisations and private clients alike. Regulated, high-stakes environments where "mostly working" gets someone hurt or sued. That's the bar. It doesn't drop just because a business is smaller, it's the exact standard every Chigzio build gets held to.
- The pattern, on repeatBrilliant operators, capped by their back-end
Outside the day job, I started looking at small and mid-sized businesses the same way I looked at systems. Same finding, every time. The people running them weren't being held back by their offer or their hustle. They were being held back by an operational layer that nobody had ever actually built.
- Today, ChigzioA small team building the operational layer properly
Chigzio exists to build that missing layer. Client acquisition, internal operations, and the systems that let a business scale without scaling its chaos. A founder-led studio with a tight team of engineers behind it, treating every build like production software, because that's what it is. Built for the result, not the demo. Yours to keep on day one.
What I hold every build to
Outcomes, not tech
You don't care how it's built. You care that the diary fills and the chaos stops. I lead with the result, always.
Production-grade, always
Proper error handling and security on everything. Built to run in the real world, under real load, not just look good in a demo.
Built to be yours
Full handover, documented. No black boxes, no being held hostage. The system belongs to your business.
Honest about fit
If I can't see a clear win for you, I'll tell you on the first call. A pass costs you nothing. A wrong build costs you everything.
