Question 1

How is pricing worked out?

Accepted Answer

Every engagement is quoted after a scoping conversation, based on the scope and complexity of the work, how many systems it touches, and your delivery timeline. We don't publish a rate card because those three variables change the number too much for one to be useful. You get a written quote before anything is billed.

Question 2

Why start with an Automation Audit instead of going straight to a build?

Accepted Answer

The audit tells you which opportunities are worth building, in what order, and what each one is likely to cost and pay back. Going straight to a build without that means guessing at scope and often building the wrong thing first. The audit fee is credited in full against a build started within 60 days, so it isn't a sunk cost if you proceed.

Question 3

Can we skip the audit and go straight to a Fixed-Scope Build?

Accepted Answer

Yes, if you already have a clear, written scope and know what you want built. Most engagements start with the audit because that clarity is usually what's missing. If you skip it, we'll still confirm scope in writing before any build work starts.

Question 4

What happens after the audit?

Accepted Answer

You get a written roadmap: a prioritised backlog of opportunities, an effort and payback estimate for each, and a build-vs-buy call on every item — with no obligation to build with us. If you do start a build within 60 days, the audit fee is credited against it.

Question 5

How is a Fixed-Scope Build paid?

Accepted Answer

In three milestones: 40% at initiation, 40% at staging, and 20% at go-live. Each milestone has its own acceptance criteria agreed in writing before the build starts, so payment is tied to delivered, accepted work rather than time elapsed.

Question 6

What does a Retained Capacity engagement include, and is there a minimum term?

Accepted Answer

A committed number of engineering hours each month, used for ongoing iteration, fixes, and new work as priorities shift. Unused hours roll over up to 20% of that month's commitment, and billing is monthly. The minimum term is three months.

Question 7

Do we need to already have UiPath, LangChain, or other specific tools in place?

Accepted Answer

No. We work across UiPath, LangGraph, LangChain, CrewAI, AutoGen, and the major LLM platforms, and we'll recommend what fits your environment during scoping. Where it reduces your licensing cost, we build on self-hosted or open-source stacks instead.

Question 8

Who owns the code and IP once the engagement ends?

Accepted Answer

You own everything built specifically for your engagement — the deliverable-specific code, configurations, and documentation. Nyarro retains ownership of its pre-existing accelerators, frameworks, and reusable components, and licenses them to you for continued use as part of the deliverable. In practice, this means you're never blocked from using or extending what was built.

Question 9

How do you handle our data, and are you GDPR compliant?

Accepted Answer

Data handling is aligned with GDPR and India's DPDP Act, and an NDA is available on request before any data changes hands. Your data is never used to train models — ours or any third party's. Where the engagement involves production data, access is scoped to what the work requires.

Question 10

How do engagements start, and what's the lead time?

Accepted Answer

Everything starts with a call to scope the work. From there, you get a written quote, and once you accept it, we confirm a start date based on current capacity — there's no long procurement process on our end.

Three ways to work with us

Not ready to talk pricing yet?

Automation ROI Calculator

Automation Readiness Assessment

Engagement Models

How pricing is set

What every engagement includes

Frequently asked questions

Ready to find out what this costs for you?