Forget the Goal. Design the Process.

I’ve always had a strong belief that most people get the sequence wrong.

They fixate on the goal — the revenue number, the distributor count, the market share — and then scramble to figure out how to get there. The goal becomes the obsession. The goal becomes the stress. And paradoxically, that obsession is often what gets in the way.

Here’s what I’ve come to believe, built from two decades of building things: if you design the right process with enough care, the goal becomes almost inevitable. You don’t have to chase it. It finds you.

How I first understood this

It’s not a new idea. Athletes talk about it. Coaches talk about it. But it took building two companies to really internalize what it means in practice — when there’s money on the line, a team looking to you for direction, and no playbook to follow.

When we pivoted Cotton Candy Station into full-scale distribution, I knew we were entering territory I’d never navigated before. Consumer distribution in India is a beast — fragmented, relationship-driven, logistically complex, and deeply regional in ways that can catch you off guard. There was no version of me winging this and hoping the numbers worked out.

So instead of staring at a distributor count target and trying to hustle my way to it, I asked a different question: what does the process need to look like for this to work consistently, at scale, without depending on heroics?

That question changed everything.

What we actually built

I designed the distribution channel almost like a system engineer would design a software architecture — thinking in layers, dependencies, and failure points.

It started with the sales team: how to structure it, who to hire, how to train them, and critically, how to design an incentive structure that aligned their daily decisions with what the business actually needed. Incentive design is underrated. Get it wrong and your team optimizes for the wrong thing. Get it right and the system practically runs itself.

Then came the tools. A sales performance dashboard so I could see, at any point, who was doing what, where deals were in the pipeline, and where things were slipping. An order tracker so we had full visibility from the moment a distributor placed an order to the moment it hit their shelf. An inventory management system and demand forecasting model — AI-driven — so we weren’t either overstocking and bleeding cash or understocking and losing distributor confidence.

And then I built what I’d now call the distribution playbook: a documented, repeatable system for onboarding distributors, managing them, resolving disputes, and scaling the relationship over time. Every step of the process had an owner, a tool, and a standard.

None of this was glamorous. Most of it happened quietly, in the background, while the visible metric — distributor count — was being watched by everyone.

What happened when the process ran

Here’s the part that still strikes me: once the process was running and the tools were live, the growth became almost automatic.

We crossed 150 distributors within 7 months. Distribution revenue grew 6x within 6 months of launch. And the process kept going — without me having to push it forward every single day.

As I write this, the network has crossed 185+ distributors pan-India. I’m no longer running the day-to-day. But the system I designed is still running. That’s the real test. Not whether it works when you’re there — but whether it works when you’re not.

That’s what a good process does. It outlasts your direct involvement.

A process needs maintenance, not worship

One trap is thinking a process is something you “set” once and walk away from.

It isn’t.

A process is alive. It needs observation, tweaking, and ruthless simplification. The first version will be wrong in specific ways — that’s expected. What matters is whether you’re watching it closely enough to catch where it’s breaking, and whether you’re disciplined enough to keep improving it rather than just accepting the output.

Every improvement compounds: one less manual step, one clearer metric, one better handoff, one faster feedback loop. Over time, the machine becomes stronger than the individuals inside it. And that’s when scaling stops being about motivation and starts being about engineering.

The role of AI in all of this

Here’s something I want to be specific about, because I think it’s underappreciated.

AI didn’t just help me run the distribution process. It helped me design it.

When I was thinking through how the system should work — what signals to track, how to structure the incentive model, where the feedback loops should sit — AI was a thinking partner. I could stress-test assumptions, explore edge cases, and pressure-check the logic of the process before committing to it. That alone saved weeks of trial and error.

And then, when it came to building the actual tools — the performance dashboards, the order tracker, the demand forecasting system, the distributor analytics — AI was the engine behind a lot of that. Tools that would have taken months to build properly, or required a dedicated engineering team, came together faster and with more capability than I could have managed otherwise.

But the part I find most valuable is what happens after the tools are live: using data and analytics to continuously refine the process. Every week, the system tells you something. A bottleneck that wasn’t visible before. A metric that’s moving in the wrong direction. A part of the process that’s creating friction. AI makes it much faster to make sense of that data and translate it into a concrete tweak.

That’s the loop: design the process, build tools to support it, let data surface what needs improvement, refine, repeat.

For any founder or builder reading this — AI is not a shortcut that replaces good thinking. But when you combine it with a solid process, it becomes a force multiplier. Capabilities that previously required larger teams and heavier infrastructure are now genuinely accessible. If you’re not actively exploring how to weave AI into your operations, you’re working harder than you need to.

What I want you to take from this

I’m not writing this to say I have all the answers. I don’t. But here’s what I know with conviction, earned the hard way across 14 years and two very different industries: design the process with care, and the goal becomes a byproduct. It sounds simple. It isn’t easy — especially when there’s pressure to just move fast and figure it out as you go. But the times I’ve resisted that urge, slowed down to design the machine properly before running it, the results have been consistently better. And the times I haven’t, I’ve paid for it.

I’m glad I was able to stay true to this principle and actually execute it with Cotton Candy Station. And I want to keep writing about the lessons that helped me build across two industries — the things you rarely see written down, and the stuff you usually learn the hard way.

This website is a reflection tool for me. But if you’re a founder or builder, I hope it also becomes something you learn from, something that saves you time, or even just a reminder of what you already knew — but weren’t giving enough importance to.

More coming soon.

— Sri