Amish R. Shah

All entries

Latest notes and writing.

Many startup founders have spent years inside large organisations before starting out on their own.

So when they build their companies, they consciously avoid the things they disliked most: layers of approvals, slow decisions, and processes that get in the way of execution.

In the early days, that works brilliantly.

But growth changes the equation.

As teams expand, customers increase, and responsibilities multiply, startups inevitably need systems and processes. The challenge is no longer whether to introduce them, but how to do so without slowing down innovation.

The founders who seem to navigate this transition best understand that processes shouldn't create bureaucracy. They should create clarity, accountability, and the ability to scale.

Interestingly, we've seen a very similar pattern in SMEs once they cross certain growth milestones. Different businesses, different contexts - but often the same underlying questions:

  • How do you build an organisation that is structured enough to scale, yet agile enough to keep evolving?
  • At what stage did formal systems and processes become necessary in your organisation?
  • And what worked - or didn't work - during that transition?

No tool - machine or software - can fix a broken process.

We’ve been solving the wrong problem.

Transactional systems remove redundancy - for efficiency.
Data warehouses add it back - for insight.

Two systems. Two truths.
Neither complete.

AI doesn’t bridge this gap.
It exposes it.

If data can’t move from transaction to insight to action,
it’s not a data problem.

It’s an architecture problem.

The “Rule of Three” is simple.

Do the three most important tasks before accessing email or WhatsApp.

It forces focus.

That’s how good businesses operate too.

They don’t optimise for activity - they prioritise outcomes, and systemise the rest.

Process automation and ERP systems do exactly that.

Focus on what matters.
Automate everything else.

The first time I remember seeing a drone in action was at a friend’s wedding in Ahmedabad, back in January 2015. It was being used for photography - and for most of us, it felt novel, almost futuristic.⁣
⁣
Over time, drones became common in photography. Today, they’re used routinely by creators and influencers. We’ve seen them deliver critical supplies to remote terrains.⁣
⁣
More recently, I saw one being used casually at a family outing.⁣
⁣
And then, of course, there is the other side - their role in modern warfare, from Ukraine to West Asia.⁣
⁣
Same technology.⁣
Completely different outcomes.⁣
⁣
That’s how most technologies evolve.⁣
⁣
What starts as novelty becomes utility.⁣
What becomes utility eventually becomes infrastructure.⁣
⁣
AI is somewhere between novelty and utility today.⁣
⁣
Its impact may be overestimated in the short term.⁣
But over time, like the internet, like drones - it may reshape far more than we currently imagine.⁣

Businesses often overestimate what technology can achieve in the short term,⁣
and underestimate what it delivers over the long term.⁣
⁣
Technology evolves rapidly.⁣
Human behaviour adapts slowly.⁣
⁣
Real transformation happens when the two align.⁣
⁣
The internet is a good example.⁣
It didn’t change everything overnight - but over time, it reshaped how we work, communicate, and build businesses.⁣
⁣
AI won’t change everything overnight - but it may leave very little unchanged.

Most people collect data.
Few understand the context that turns it into value.

I don’t know how things work in Silicon Valley - I’ve never been to any place west of London.⁣⁣
⁣⁣
But here in India, across acres of the software support and systems maintenance ecosystem - call it IT services, outsourcing, offshoring, or GCCs - the most respected people are the ones who can debug.⁣⁣
⁣⁣
Not the ones who write the most code.⁣⁣
The ones who can fix what breaks.⁣⁣
⁣⁣
These are professionals who have seen so many systems fail, behave strangely, and recover that they’ve internalised how technology really works. Give them a problem and, within minutes, they can trace the root cause and suggest a fix.⁣⁣
⁣⁣
Early in my career, I worked with one such professional.⁣⁣
⁣⁣
The probability of finding him at the sutta-tapri outside the office was often higher than finding him at his desk. But when something broke, someone would walk up to him, explain the issue, and he would calmly point to the exact place in the system where things had gone wrong.⁣⁣
⁣⁣
And, he was almost always right.⁣⁣
⁣⁣
That’s the beauty of real technology expertise - people who have seen systems behave in the messy complexity of real-world environments.⁣⁣
⁣⁣
Will AI replace such experts?⁣⁣
Maybe. Maybe not.⁣⁣
⁣⁣
But will AI create the need for many more such experts?⁣⁣
I would say - yes.
Someone will still have to debug the future.

Every factory visit teaches me something new. Every warehouse reveals something most reports don't.

I've had the opportunity of spending time on shop floors and navigating through pallet racking across many facilities - and what strikes me, every single time, is how much a physical space reveals about the health of a business.

The layout of a warehouse. The rhythm of a production line. The way material moves - or doesn't.

You notice things that never make it into dashboards or MIS reports. Where bottlenecks quietly form. Where workarounds have become routine. Where a small process fix could unlock something much larger downstream.

These aren't just operational details. They are the story of how efficiently a business truly runs - told not in numbers, but in motion, space, and the behaviour of people doing real work.

And that story is almost always more honest than any presentation in a boardroom.

For anyone serious about manufacturing or supply chain - or about building systems that actually serve these environments - there is no substitute for time spent on the ground.

Observe first. Then design.

The AI conversation in tech feels increasingly polarised.⁣
⁣
One camp believes AI is the end game - that software engineers, analysts, designers, maybe even founders, will soon be optional.⁣
⁣
The other camp dismisses it - citing non-determinism, hallucinations, and the lack of long-term proof.⁣
⁣
Both positions, in my view, are intellectually lazy.⁣
⁣
AI is neither apocalypse nor illusion.⁣
⁣
It is a tool - a powerful one. It accelerates some tasks dramatically. It performs brilliantly in narrow contexts. It is unreliable in others. And like every tool before it, it will evolve.⁣
⁣
History offers perspective.⁣
⁣
When Canva emerged, it didn’t eliminate designers - it expanded the design market. When Figma accelerated collaboration, it didn’t reduce opportunity - it increased the velocity of product creation.⁣
⁣
Tools reduce friction.⁣
Reduced friction expands ambition.⁣
⁣
AI will likely democratise information processing and lower the barrier to building. But building systems is not the same as generating outputs.⁣
⁣
Architecture. Accountability. Trade-offs. Long-term consequences. Context.⁣
These are not prompt-level decisions.⁣
⁣
The real question isn’t “Will AI replace us?”⁣
It’s “What becomes more valuable when execution gets cheaper?”⁣
⁣
That’s where the real debate should be.