03 Method
The five steps
Measure, rank, agree, build, measure again. The last step is the one most automation projects skip, and it is the only one that turns a claim into evidence.
Step 1: Measure the baseline
Runs per month, minutes per run and error rate, recorded before anything changes. Without this, every later claim about savings is an opinion.
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 here, not bolted on later.
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 just picks one version and makes the other two people 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 here.
They talked us out of two of the four we asked for and showed the arithmetic. The two they built paid back inside a quarter.
05 Compliance
Rules an automation has to respect
Three reach almost every build. None of them is onerous; all of them are cheaper designed in than retrofitted.
- Audit trail. Anything writing to the books is part of the accounting system, so it inherits the logging control an external audit already tests: an unalterable, timestamped record of each entry and each later change, which is control A.8.15 of ISO/IEC 27001.
- Automated messaging. Commercial SMS requires DLT registration of the entity, the sender header and every content template under the Telecom Commercial Communications Customer Preference Regulations, 2018, administered by the the telecoms regulator in your market. Unregistered messages are blocked by the operators.
06 The people
Who do you actually work with?
Four founders, named. The audit is done by the people who will build the thing, so nothing is promised in a report that cannot be delivered.
Automation is a measurement problem before it is an engineering one, which is why two of these four never write a line of code.
-
Dhanush Prabha
Co-Founder, CTO and CMO
Builds the automation, the exception path and the fallback for the day it fails.
-
Sriram Ravichandran
Founder and CEO
Times the process as it actually runs, ranks it by hours and error cost, and agrees what changes.
-
-
07 Cross-border
How do we work with clients in another country?
None of this needs you to be in any particular country. The work is remote either way, so these are the answers a buyer asks for before signing, and they are the same on every engagement we run.
Working hours
Our day runs on UTC+5:30. The overlap window with your team is written into the scope rather than assumed, and everything outside it runs asynchronously.
How we communicate
One written update a day on the channel you already use, a standing weekly call inside the overlap window, and a named person to escalate to. Nothing important is agreed only on a call.
Who you contract with
Synerdyn Private Limited, the company behind IncorpX, named in the agreement with its registration number. The governing law and the forum are agreed before you sign, not after a dispute.
Currency and payment
Invoiced in your currency or in ours, your choice, and settled by bank transfer. Milestones are tied to deliverables you can see, never to elapsed time.
What you own
Copyright in everything built for you is assigned on final payment: source code, design files, prompts, configuration and documentation. Third-party licences are listed by name so nothing is a surprise later.
Where data sits
You choose the region your data is stored and processed in, and the answer is written down before the build starts, with who at IncorpX can reach it and for how long.
Offset from our working day standard time
- London-5:30
- Dubai-1:30
- Singapore+2:30
- Sydney+4:30
- New York-10:30
- San Francisco-13:30
IncorpX is a brand of Synerdyn Private Limited. The contracting entity, the governing law and the invoicing currency are all named in the proposal before you sign anything.
08 Reference
Terms used on this page
- Happy path
- The version of a process where nothing goes wrong. It is 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 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 by nature, 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.
- GDPR
- The EU and UK data protection regime. Article 83 sets administrative fines of up to €20 million or 4% of worldwide annual turnover, whichever is higher, which is why consent, retention and access control are build decisions here rather than paperwork.
09 Questions
Process automation FAQs
Next step
Send us 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. The audit is 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.
