Skip to content

Business automation

Built on what you already run

The work nobody was hired to do.

Every business accumulates tasks that exist only because a system does not. We find them, and we build the thing that does them instead.

What we automate

Typical return

Build time

Payment and collection follow-up

6–11 hrs/wk

2–3 wks

Recurring reports and dashboards

3–5 hrs/wk

2–4 wks

Onboarding and internal checklists

4–6 hrs/wk

2–3 wks

Lead capture and routing

2–4 hrs/wk

1–2 wks

Customer messaging and nurture

3–6 hrs/wk

2–4 wks

Ranges from systems we have built. Yours comes out of the audit.

18–32 hrs/wk

Typical total

What automation actually buys you

And what usually happens instead

A business that keeps running correctly on the days you are not watching it.

What you actually want

What happens instead

Follow-up that happens whether anyone remembers

A task that gets done when someone has time for it

Numbers that are already right when you open them

A report rebuilt by hand every Monday morning

One person freed for the work you hired them for

Two salaries spent on re-typing what is already there

That is what we build. Not software you have to adopt, but a system that runs on the tools your team already opens.

The stack

Nothing new to learn

We build on the tools your team already opens. Nobody is asked to learn a new screen, and nothing is ripped out.

Tool

What it does here

n8n

The workflow engine. Reads, decides, sends.

WhatsApp

Where your customers already reply

Tally

Read from, never written to

Excel and Google Sheets

The input your team already maintains

Amazon SES

Bulk email at a fraction of the usual cost

If you run something else, we read from that instead. The engine does not care.

The audit

Before anything is built

01

We sit with the people doing the work

Not with you. With the two or three people who actually do the task every day, because they know where it breaks.

1 day

02

We map it as it runs, not as it should

Written down, step by step, including the workarounds nobody mentions in a meeting.

2–3 days

03

You get a written proposal

What we would build, in what order, what it costs, and what it returns. You own the document either way.

1 week total

How a system works

One reading, four outputs

Nothing is ripped out. One workflow reads the data your team already enters, and everything downstream happens without anyone remembering to do it.

BEFORE · MANUAL, EVERY MORNING

Rep opens Tally and reads the ageing report

Rep types the WhatsApp message

Rep remembers to follow up, or does not

Three people. Every day. Nobody measured it.

AFTER · AUTOMATIC

Tally and ExcelREAD HOURLY · UNCHANGEDn8n workflow
  • Payment reminder on WhatsApp
    Daily 09:00
  • Outstanding dashboard for the owner
    Live
  • Escalation email to the sales owner
    On 45 days overdue
  • Monday collection report
    Weekly

Example: the ARB Bearing collection system

Case studies

Systems running in production

ARB Bearing

Bearings distributor, three states

Payment follow-up now happens every morning at nine, whether anyone remembers it or not.

Instead of

  • Two reps chasing customers from memory
  • Outstanding sitting in Tally where nobody looks
  • Collection time nobody had ever measured

What we built

A workflow that reads the daily ageing report and sends the reminder on WhatsApp, email and SMS, from the account the customer already replies to.

Each rep gets their summary, the owner gets one for the whole business. Tally was never written to.

Paramount Wires and Cables

Manufacturer

A new joiner is fully onboarded before their first Friday, and the manager can see exactly where it stands.

Instead of

  • Paperwork moving desk to desk on paper
  • Nobody able to say which step was pending
  • A week lost before anyone noticed a form was missing

What we built

A checklist that runs itself, step by step, chasing the person who owes the next action.

The manager sees where it is stuck without asking anyone. Nothing sits in an inbox waiting to be remembered.

0

Dabur, via Dentsu

FMCG campaign systems

Every campaign message, reply and drop-off lands in one sheet, as it happens.

Instead of

  • Replies counted by hand across three phones
  • A reporting day at the end of every campaign
  • Numbers that were already old by the time anyone read them

What we built

A tracker that captures every outbound message and every response into a single live sheet, with drop-off visible per stage.

The reporting day disappeared entirely.

What it costs

Ranges, not quotes

We do not publish a price list, because the build depends on what the audit finds. These are the ranges systems of each size have actually landed in.

System size

Build time

Typical range

One process, one output

1–2 wks

₹40,000 – ₹90,000

One process, several outputs

2–4 wks

₹90,000 – ₹2,00,000

Several processes, connected

4–8 wks

₹2,00,000 – ₹5,00,000

Ranges shown so you can rule us out without a call.

Ongoing support and changes are billed monthly, or not at all if the system runs untouched. Most do.

Who this is for, and who it is not

Read this before you book

This is for you if

Book the call

  • You run a service or manufacturing business, 20 to 200 people
  • Your operations already run on Tally and Excel, and they mostly work
  • The same manual task is repeated every week by someone you pay well
  • You want one person accountable, not a team of five on a call
  • You have been burned by an agency and want to see the thing working first

It is not for you if

Do not book

  • You want ad campaigns run and reported on
  • You sell D2C on Shopify
  • You need a logo or a landing page
  • Your business is under ten people
  • You want the cheapest quote in the room

Book the call

Fifteen minutes, and you will know whether there is anything here for you.

Bring one process that annoys you every week. We will tell you what it would take to stop it, or tell you it is not worth doing.

Or on WhatsApp

+91 99535 67826

Reply time

1 working day