From fundraising to post-merger integration: the commercial backbone of every transition.

The CFO had been telling the board the company had 18 months of runway. Technically true. What she suspected, and couldn't easily prove, was that a meaningful chunk of the burn was money nobody would miss if it disappeared. Post-Series B, every department had submitted a budget by taking last year's number and adding 15%. No justification, no trade-off, no challenge. She'd approved it all because she didn't have bandwidth to question every line item alone. That nagging feeling that they were paying for things they'd forgotten they had had been sitting with her for months.

Zero-Based Budgeting is not popular because it requires people to justify things they've always taken for granted. We ran 22 structured sessions across six departments over six weeks. The conversations that produced the most uncomfortable moments were consistently about software subscriptions: tools four teams were paying for separately, tools no one had cancelled after switching vendors the previous year, tools three people were using and forty were paying to license. That work found ₹1.4 Cr of recurring spend that could be cut without touching a single salary.

Three VC conversations, three polite rejections. The founding team had iterated the pitch deck twelve times. The problem wasn't obvious to them, which is always the harder problem to fix. The deck was technically impressive: detailed product architecture, deep market analysis. What it was missing was the financial narrative that institutional investors actually read. Investors were being shown what the product did and asked to imagine the return. That doesn't work.

We rebuilt the investment narrative from the investor's perspective, starting with the return thesis, not the technology thesis. A 5-year model was built with three scenarios, and a use-of-funds section that showed exactly where the ₹12 Cr would go and what milestones each rupee was buying. The deck went from 47 slides to 22. The founding team ran ten mock investor conversations before the next real one, with the aggressive questions that never come up in internal prep but always come up in VC meetings.

When two companies merge, the paperwork makes it look manageable. What the paperwork doesn't capture is 280 people across four cities who woke up on day one wondering whether their job still existed, whether their manager still had authority to approve their expenses, and what tools they'd be using next week. The merger agreement required a unified operating model within 90 days. There was no playbook. Both leadership teams were managing perception rather than reality, and both knew it.

Our PMI lead embedded from day one. Their first action was not a Gantt chart, it was listening. Three cities in week one. What they heard was that both organisations had the same fear: that the other side's way of doing things would win. That shaped the integration design more than any spreadsheet. The 90-day playbook covered 120 workstreams. Technology was the most visible: six overlapping tools rationalised to two. But the harder work was the org structure conversations that no one wanted to have on record.