"Automation" sounds like something for big companies with big IT teams. It is not. For a small or mid-sized business, the first automation can be very simple. Often it is just: something that used to need a person to remember, now happens on its own.
The hard part is not the technology. It is knowing where to start. Here is the way I suggest to owners who ask me.
What automation actually means
In plain words, automation is a task that runs by itself, with a record of what happened.
Some examples of the kind of thing I mean:
- An approval goes to the right person, and reminds them if they do not act.
- A follow-up goes out when a payment is late.
- A new enquiry from your website lands straight with your team.
- A shipment deadline gets flagged before it is missed.
- A document is read and its details pulled into a system, with a person checking the result where it matters.
None of these is exciting. That is the point. They remove small daily leaks of time and attention.
Step 1: List what wastes time
Do not start with software. Start with a list.
For one week, write down every time someone in your business:
- asks "where is this order?"
- retypes the same data from one place to another
- forgets to follow up
- phones someone just to get a status
- searches for a document
Ask your team too. They know the pain better than you do. Do not worry about how to fix any of it yet. Just collect.
Step 2: Pick one process, not ten
Look at your list and pick the process that costs you the most. Judge it by time, by mistakes, and by how often it happens.
Some common first choices:
- Manufacturing: job work sent to outside vendors, where diaries and memory are the only record.
- Trading and distribution: orders arriving over WhatsApp, phone and email, with credit limits known by one person.
- Export: shipment tracking and documents after the goods leave.
The urge to fix everything at once is strong. Resist it. One process, done well, teaches you more than ten done badly.
Step 3: Write down how it works today
Before anything is built, draw the process as it really is. Not as it is supposed to be.
Ask:
- Where does the work start?
- Who touches it next, and what do they do?
- Where does it wait?
- Where do mistakes or delays happen?
- What does the owner need to see at the end?
Do this with the people who do the work. A supervisor will tell you things a manager never knew. It can be a rough sketch on paper. It does not need to be pretty.
Step 4: Decide what "better" looks like
Before you start, decide how you will know it worked. Keep it simple and honest.
For example: "I can look up an order status without calling anyone." Or: "Nothing starts on the floor until the material has arrived." Or: "Every shipment has its documents in one place."
Notice these are not big claims. They are things you can check with your own eyes. Be careful of anyone who promises a specific percentage gain before they have seen your business. Real impact is measured after the system is running, using your own numbers.
Step 5: Build small, use it, then adjust
Now build a first version of just that one process. It should be small enough to get into real use within weeks, not months.
A few tips:
- Use it on real work early. A system nobody touches teaches you nothing.
- Design for the person using it. On the floor, that usually means a phone, large buttons and very few fields.
- Keep what already works. If Tally handles GST and invoicing well, keep it and connect to it. If your buyers love WhatsApp, keep WhatsApp.
- Keep a human check where it matters. Automation should take away repeat work, not take away judgement.
After a few weeks of real use, look at what happened. What is better? What is still annoying? Fix that. Then, and only then, move to the next process.
Common mistakes
Starting too big. A huge project delays the first win, and people lose patience.
Copying a template. If the software forces you to change how you work, people will work around it.
Skipping the team. If the people doing the work are not part of the plan, they will not use the result.
Getting locked in. Ask who owns the code and the data. You should own both, and you should be able to take them elsewhere.
Where we come in
At Jugaad Studio, this is how we work. We find the costliest process, build a custom system for it in weeks, measure the real impact, and expand to more modules if it makes sense. No discovery fees. And if an existing product is a better fit than custom software, we will tell you so.
If you have a list, even a messy one, we can look at it together.
Tell us what wastes the most time. Fifteen minutes is usually enough to know whether it is worth building.
[Book a 15-minute call](https://studio.jugaad.sh/contact). No obligation. No pitch deck.
WhatsApp: +91 98300 90897. Email: atish@jugaad.sh.
Atish Kejriwal
Founder, Jugaad Studio