Business building · Growth · Operations · Technology
I build businesses and the systems that run them.
For more than two decades my work has been one thing in different materials — from buildings to markets to software. Understand the real problem, bring the right people together, and stay close until it works.
What brought you here?
- 01Understand my workFour businesses and systems, and what connects them.
- 02Explore how I thinkEssays and field notes from work in progress.
- 03Consider a leadership or advisory conversationScope, selected outcomes and how to reach me.
- 04Read what I am learningWhat I am building and puzzling over right now.
One practice, five systems
On paper the chapters look unrelated — insurance, buildings, trade, software. They are the same practice in progressively more abstract materials: learning to build systems where the joints between disciplines hold.
The systems I build
- 2000
People & commercial systems
Sales & financial services
The first system was other people: how organisations sell, train and decide. It taught me that every system is really a set of incentives.
- 2010
Physical spaces & infrastructure
Synchronos
One accountable team for everything in a building that has to work together — automation, AV, security, interiors. The joints between trades are where projects fail.
Explore - 2024
Markets, trade & partnerships
T57
The commercial architecture a global trade platform needs before it launches: which markets, at what price, through which partners.
Explore - 2025
Enterprise software & AI
NxSync
Software that starts from the business problem, not the feature list — an AI-native ERP, secure collaboration, built in reviewable stages.
Explore - 2025
Decisions & continuity
Spine
The most abstract material of all: the reasoning behind decisions. Spine keeps it from disappearing between sessions and handovers.
Explore
These overlap rather than replace each other. Commercial experience shaped how I built Synchronos; coordinating trades on real sites shaped how I lead product work; that product work produced NxSync, and its own friction produced Spine. Several run in parallel today.
Built and operated
Founded and ran a smart-infrastructure company for more than a decade, with founder-level accountability for the outcome.
Entered and developed markets
Shaped international commercial strategy and market entry across India and MENA.
Delivered multidisciplinary systems
Coordinated design, automation, AV, security, networking and interiors across thousands of real projects.
Conceived and advanced products
Directs an AI-native enterprise-software portfolio, from secure collaboration to delivery governance.
How the work actually goes
Not a process diagram — one real example. This is how Spine, the tool that keeps AI-assisted work traceable, went from a problem I noticed to something in daily use.
- 01
Learn
I watched our team move faster with AI tools — and quietly lose the reasoning behind decisions.
- 02
Understand
The real problem was not the tools. It was the joint between sessions, where context disappeared.
- 03
Design
Define what "finished" means before starting. Work in bounded, reviewable pieces. Record why each decision was made.
- 04
Build
We adopted the habits by hand first — then turned them into a product, Spine, so the discipline was a system, not a resolution.
- 05
Improve
Watch it in real use — including on this website — keep what works, and carry the lesson into the next project.
Still curious
I am always glad to compare notes on building businesses, entering new markets, or making AI-assisted work dependable. If something here overlaps with what you are working on, write to me.