Technology. Business. Mastery.
Ideas are cheap until they're built. When you have an ambitious concept, I help you figure out what actually needs to exist, architect the system from first principles, and turn it into real, production-ready software.
I like building things from the inside out.
I care about how the system works, but also why it needs to exist in the first place. Good engineering isn't just writing code that works. It's making decisions that leave the product stronger than you found it.
A product can be beautifully built and still be a bad business.
I've learned to look beyond the code — who needs this, what problem are we solving, what should we build first, and does any of it actually make sense?
Because building the wrong thing really well is still building the wrong thing.
The hardest thing I've had to learn how to manage is myself.
Building companies, products and anything ambitious will test your discipline, your patience and your ability to keep going when things aren't going your way.
Talent helps. But eventually, your standards, consistency and ability to execute matter more.
“Excellence is not an accident!”
~ Harry Zahavi
I don't just like ideas. I like figuring out how to make them work.
I've spent more than a decade learning how to build software, products and businesses from the ground up. Sometimes that means writing the code. Sometimes it means deciding what shouldn't be built. Sometimes it means looking at a messy problem and figuring out where to start.
I care about the whole thing — the idea, the product, the technology, the business and what happens after launch.
Have the idea. Figure out what matters. Build the thing. Make it useful.
Read The Full ProfileWhat I Work Across
I’ve built products of my own, helped businesses turn ideas into software, and spent years working inside the messy part between an idea and something people can actually use.
Event Technology · Ticketing · Payments · Infrastructure
Events are still run across too many disconnected tools. rigitiX brings ticketing, payments, access control, promoters, vendors and audience engagement into one system.
I started rigitiX from the problem, shaped the product, designed the technical architecture and built the systems behind it.
High-throughput ticketing, payment infrastructure, organiser tools, verification systems, dynamic pricing and the infrastructure required to run events at scale.
Game Engine · Match Simulation · Closed-Loop Economy
Sports management games often collapse under clumsy interfaces and broken in-game economies. VFM was designed to simulate realistic tactical football while maintaining a balanced, closed-loop token economy.
Lead Systems Architect & Developer. I modeled the match simulation mathematics, designed the relational database schemas, and built the interactive 2D pitch visualizer.
Mathematical Poisson match engine, double-entry transactional ledgers, escrow-backed player transfer marketplace, and real-time HTML5 canvas matchday rendering.
Financial Technology · Personal Finance · Product Engineering
Managing money becomes difficult when the numbers are scattered across accounts, debts, income and everyday spending.
I worked on the product and engineering behind a financial command centre that brings those pieces together and makes the user's financial position easier to understand.
Product engineering, system architecture and implementation.
FinTech · Crypto Trading · Utility Settlement Platform
The client ran a growing trading community across fragmented channels: VIP signals on Telegram, video courses on external tools, and bank payments reconciled manually with high error rates.
A unified platform combining a multi-currency digital wallet, automated subscription gating for VIP signals, a structured course academy, and a 15-category utility bill settlement engine.
Lead Full-Stack Architect. Commissioned through CodeRigi to unify the business into one cohesive architecture and build the end-to-end web and mobile applications.
“An idea doesn’t come to life by simply believing in it. It comes to life when you develop the discipline, creativity, and technical ability to build it.”
I talk about the things I spend my time actually doing — building technology, starting businesses, making difficult decisions, figuring things out when there’s no obvious answer, and becoming better at carrying the weight that comes with ambition.
No motivational theatre.
Just real ideas, hard lessons, and things worth thinking about.
Ideas are cheap when they never leave your head. I talk about what happens after the excitement — figuring out the problem, learning what you don't know, making the first version, and staying with it long enough to make it real.
The playbook doesn't always fit. Infrastructure, payments, trust, access, talent, regulation — sometimes the environment you're building in is part of the problem you're trying to solve. Here's what I've learned from building anyway.
The best products I've worked on needed both. Someone has to imagine what could exist. Someone has to understand how to make it work. And sometimes, those need to be the same person.
A product can be beautifully built and still be a bad business. I talk about pricing, demand, distribution, unit economics, positioning and the uncomfortable decisions that determine whether something actually survives.
You can build a company and still be terrible at managing yourself. Discipline, consistency, emotional control, standards, focus — these aren't separate from the work. Eventually, the person running the system becomes part of the system.
The wins make good stories. The uncertainty, the wrong decisions, the people who leave, the money that doesn't come, the things that break at the worst possible time — that's where most of the real education happens. I talk about that part too.
The things I’m building usually start with a question.
I write about technology, business, building, discipline and the lessons that only become obvious after you’ve lived through them.
Discipline should make your life bigger, not smaller. There’s a difference between having standards and being trapped by them.
The code is rarely the first problem. A lot of products are already in trouble before the first line is written — because nobody has properly figured out what they’re building or why.
A good product still needs a business behind it. Someone has to pay for it, someone has to sell it, and the numbers have to make sense.
Founders, executives, engineering partners, and operators who built, scaled, and solved complex problems with me.
When you have an ambitious idea for a software product, I help you figure out what to build, architect the platform, and execute it with commercial excellence.
Software Product Builds · Architecture Sessions · Fractional CTO · Keynotes & Advisory
