Everyone promises ROI. It’s the currency of every boardroom presentation in Singapore, Bangkok, and Sydney. But while vendors sell the dream of efficiency, few will show you the plumbing that actually creates it.

Most transformations fail because they skip the foundation, jumping straight to buying tools without understanding why the current stack is leaking value. I don’t believe in magic; I believe in mechanics. I2I-9 is the method behind the results: a rigorous, three-phase approach for turning stalled projects into growth engines. Here’s how it works.

Phase 1: Insight, find the leaks

The first phase isn’t about technology. It’s about diagnosis. Most audits stop at software licences and integration points. I go deeper.

A deep-dive audit identifies the technical, data and cultural leaks. A “leak” isn’t only lost data; it’s a breakdown in trust between sales and marketing, or the friction that makes a team quietly ignore a new CRM because it feels like surveillance, not support.

If you don’t find the cultural leak first, no amount of code will fix it. This phase gives you the clarity to stop wasting budget on underused tools and misaligned processes, finding the cracks in the foundation before you pour any more concrete.

Phase 2: Action, build the roadmap

Once the leaks are clear, I stop guessing. I define a high-impact architecture and a customised roadmap that aligns your technology with your regional strategy in APAC.

This is where I challenge the “best practice” myth. A roadmap that works in New York often fails in Jakarta on market maturity alone. So I build a “minimum viable stack” that solves the leaks found in Phase 1 rather than adding complexity.

Crucially, this phase establishes a new way of working that bridges technical teams and business leadership, translating tech-speak into business value so your C-suite understands the investment and your marketers understand the capability.

Phase 3: Impact, embed the change and the ROI

This is where most consultants leave: they hand over the deck and walk away. I don’t just advise; I lead the execution, because ROI is made in adoption, not in the recommendation.

I measure success differently, moving beyond vanity metrics like login counts to velocity metrics: how fast is the culture adopting the change, are workflows actually shortening, is data quality improving week over week? By embedding new habits, the stack becomes a high-performance engine for sustainable growth, and by the time the engagement ends, your team is fluent enough to keep the momentum going.

The philosophy: outcomes over outputs

Why does I2I-9 work? Because it prioritises outcomes over outputs. An output is a report, a diagram, a deployed tool. An outcome is revenue growth, reduced churn, empowered teams. In APAC, where complexity is high and patience is low, outputs are vanity; outcomes are survival.

I built this method around a single truth: MarTech transformations fail on culture, not code. I2I-9 is simply the structured application of that truth, people before platform, habits before hardware.

A question for your strategy

Stop guessing where your budget is going. Start measuring what it’s actually buying you.

If your current roadmap looks like a vendor deck rather than a transformation plan, it’s time to change the approach. You can see how I2I-9 translates into specific engagements on the Services page.