Business Automation & RPA

Common questions

Frequently asked

Do we need UiPath or Power Automate licences before engaging?

No. The discovery phase decides the toolset — many processes are better served by lightweight Python on a scheduled VM than by a full RPA licence. Where UiPath, Power Automate, or Make.com is the correct fit, we procure on your behalf or against your existing Microsoft 365 or Azure entitlements. For most SMEs, the licensing footprint ends up under ₹1 lakh per year. We never lock clients into a specific vendor — every build is documented so it can be migrated.

How long does a typical automation take to go live?

A single, well-bounded process — bank reconciliation, vendor bill OCR, dunning workflow — takes four to six weeks from kickoff to production cutover. Larger programmes covering five to eight processes run as a 12 to 16 week engagement with sprint-level releases. We deliberately avoid big-bang deployments; every bot ships independently and earns its keep before the next one starts.

What happens when a process changes — for example, GST schema updates or a new ERP version?

All builds ship with a maintenance contract option. Statutory changes such as GST rate revisions, IRP schema updates, or e-way bill rule changes are absorbed under the retainer at no incremental fee. ERP version upgrades and material business-rule changes are handled at a fixed change-request rate. Critically, every script and bot is documented and version-controlled in your repository — you are never hostage to a single engineer.

Will the bots replace our finance team?

Almost never, and that is the wrong frame. The objective is to remove transactional work — keying invoices, downloading bank statements, building Excel pivots — so the team you already have can move into reconciliation review, vendor management, and analysis. In practice, clients redeploy one or two roles upward into FP&A or controller-track work rather than reducing headcount. The cost saving is in not hiring the next three clerks the growth would have required.

How is this different from buying off-the-shelf software like Zoho or Tally add-ons?

Off-the-shelf tools work for vanilla workflows. Custom RPA earns its keep when the process spans three or more systems, requires judgement-style exception handling, or involves data sources that have no API. Bank reconciliation against a non-standard ERP, OCR for handwritten vendor bills, multi-subsidiary consolidation in mixed currencies — these are the cases where a generic add-on stalls. We use off-the-shelf where it fits and build custom where it does not.

How is data security handled — bots have access to bank statements and our ERP.

Bots run on infrastructure you control: an Azure tenant, AWS account, or on-premise VM under your administration. Credentials are stored in a secrets vault (Azure Key Vault, AWS Secrets Manager, or HashiCorp Vault), never in source code. Read-only access is preferred wherever the workflow permits. Every bot run produces an immutable audit log of what was accessed, what was changed, and by which credential. We sign mutual NDAs and, on request, provide a SOC 2 controls memo for your auditor.