03 Method
The five steps
Measure, rank, agree, build, measure again. The last step is the one most automation projects skip, and the only one that turns a claim into evidence.
Step 1: Measure the baseline
Runs per month, minutes per run and error rate at your Ambala operation, recorded before anything changes.
Week 1Step 2: Rank by hours and risk
Frequency multiplied by time gives the hours; error cost gives the risk. The loudest complaint is often not the biggest number.
Week 1Step 3: Agree the process, exceptions included
A process mapped only in its happy path produces an automation that hands a third of the work straight back.
Week 2Step 4: Build the fallback, then the flow
Retries, an alert to a named owner and a manual path first. Personal data flows and consent are designed in at this point.
Weeks 2 to 4Step 5: Measure again after two cycles
The same three numbers, after the process has run twice in full. Only then does the next automation start.
Week 6
04 Honesty
What we will tell you not to automate
Turning down work is cheaper than delivering an automation that makes things worse. Four cases where we say no.
- A process nobody agrees on. If three people describe it three ways, the disagreement is the problem. Automating it picks one version and makes the other two work around the system.
- A process that runs twice a month. Twenty minutes, twice a month, is eight hours a year. That does not pay back a build, and saying so costs us a sale and saves you a subscription.
- A process where the judgement is the point. Credit decisions, pricing exceptions and hiring calls have humans in them deliberately. Automating the paperwork around them is useful; automating the call is not.
- A process about to change. If the ERP is being replaced next quarter, the automation is being built against a system that will not exist. Sequence matters more than speed.
Rules any automation has to respect
Anything writing to the books falls under the Rule 3(1) audit trail requirement administered by the Ministry of Corporate Affairs. Personal data flows fall under the Digital Personal Data Protection Rules, 2025 from the Ministry of Electronics and Information Technology. Automated SMS needs DLT registration with the Telecom Regulatory Authority of India before a single message is delivered.
05 Reference
Terms used on this page
- Happy path
- The version of a process where nothing goes wrong. Usually two thirds of the volume and almost none of the difficulty.
- Exception queue
- Where a run that leaves the happy path goes, with a named owner and a deadline, instead of failing silently.
- Three-way match
- Checking that the purchase order, the goods receipt and the supplier invoice agree before a payment is released.
- Idempotency
- The property that running the same step twice produces the same result once. Without it, a retry creates a duplicate invoice.
- Robotic process automation
- Written RPA: driving a user interface as a person would. Brittle, and the last resort where no interface exists.
- API integration
- Connecting through a published API or webhook rather than a screen, which is what makes an automation survive a vendor update.
- Data Protection Board of India
- The adjudicating body under the Digital Personal Data Protection Act, 2023. The Schedule to that Act sets fixed rupee ceilings rather than a share of turnover: up to ₹250 crore for failing to take reasonable security safeguards against a personal data breach, up to ₹200 crore for failing to notify the Board and the people affected, and up to ₹50 crore for a breach of any other provision. That is why consent, retention and access control are build decisions here rather than paperwork.
06 Questions
Process automation in Ambala: FAQs
Per process, then per connection between processes, on the same basis everywhere. A single process automated end to end is the unit; connected processes sharing a dashboard are quoted together. The audit that ranks your Ambala team's processes by hours lost comes first, costs nothing and is yours to keep. Every quote states IncorpX professional charges; tool subscriptions and any government fees are billed separately at actuals.
A single well-understood process takes 2 to 4 weeks. Three connected ones take 6 to 10 weeks. The variable is never the build; it is how long it takes to agree what the process actually does, exceptions included.
No. Process interviews, design, build and handover all run over calls and screen shares from our base in Chennai, Tamil Nadu. The one thing that genuinely benefits from being present is a shop-floor or warehouse walkthrough, which is planned and quoted where it applies.
Rank them on runs per month, minutes per run and what an error costs. Order to cash, procure to pay, employee onboarding and approval routing top that list in almost every business we audit in Haryana, because they score high on all three.
In our experience it moves them rather than removes them. What automates cleanly is re-keying, chasing, formatting and forwarding, which is the work nobody wanted. What remains is exception handling and customer contact.
Then fix it before automating it. An automated bad process fails faster and more consistently than a manual one, and it removes the human judgement that was quietly compensating for the design. We will say so rather than take the build.
Because the audit records the before: runs per month, minutes per run and error rate. The same three are measured after two full cycles. Without that baseline, saving is an opinion rather than a number.
Anything writing to the books does. The proviso to Rule 3(1) of the Companies (Accounts) Rules, 2014 has required company accounting software to keep a non-disableable audit trail and edit log since 1 April 2023, and an automation posting entries is part of that system.
It is in scope. The Digital Personal Data Protection Rules, 2025 were notified on 13 November 2025, with the main obligations commencing on 13 May 2027. We map what personal data each automation touches and how consent and withdrawal work, at design time.
Only from a registered sender. Commercial SMS in India requires DLT registration of the entity, the sender header and every content template, and unregistered messages are blocked by the operators regardless of what the automation does.
Next step
Send the three tasks your team complains about most.
You get the hours each one costs a month, what it would take to automate, and what we would leave alone. Free, and yours to keep.
Read by Dhanush Prabha, our CTO, not a form queue. Reply usually within one working day, in your time zone.
Nebin Binoy 
