Process owner
Owns the rules, approves changes and decides when the agent is ready. Usually the head of the team whose work it is.
How it works
Every agent we build follows the same path, whether your team assembles it in the studio or ours does. It starts with one task, gets tested on what your team actually did last month, and goes live with a person approving everything that matters.
In short
It starts with a call about one process. Scoping takes about a week, using thirty to fifty real past cases. Building and connecting typically takes one to two weeks. The agent is then tested on those past cases, and it goes live with approvals switched on for everything that matters, while a named person on your side reviews exceptions daily.
The path
What happens at each stage, roughly when, and who does what on each side.
Stage 1 · Week 0
Bring one task that wastes time every week. We ask who does it today, where the inputs come from, how you know the answer is right and who approves. If it is not a good first candidate, we say so and suggest a better one.
Stage 2 · Week 1
We collect thirty to fifty real past cases, such as last month's invoices or support chats, with what your team did on each. We write down the rules, the tolerances and the approval points together.
Stage 3 · Weeks 2 to 3, typically
The app is assembled in the builder and studio, connected to the systems it needs, with access limited to the task. Your team can watch it take shape in a shared workspace and change wording and rules as it goes.
Stage 4 · Before launch
The agent runs against the past cases you shared, and its answers are compared with what your team actually did. We fix what it gets wrong and agree with you whether it is ready.
Stage 5 · First month
The agent starts on real work with approvals switched on for everything that matters. A named person on your side reviews exceptions daily, and we watch the logs with you.
Stage 6 · Ongoing
Once the agent has a track record, you decide whether any approvals can relax. Most teams then pick the second process, often in the same department, and reuse what they built.
Who is involved
Small projects need a few hours a week from each. The reviewer matters most, because they know what a right answer looks like.
Owns the rules, approves changes and decides when the agent is ready. Usually the head of the team whose work it is.
The person who approves exceptions every day. Often the same person who did the work before.
Assembles the app in the studio. Can be someone on your team, our team, or both together.
Grants access to systems and agrees where the platform runs. Needed for a few hours in total.

Questions
It depends on the process and the systems. A focused agent on clean inputs and one system often reaches testing within a few weeks. Old systems without APIs take longer, and we tell you that in the first call.
No. Many teams build on the platform themselves after a short handover. Others prefer our AI team to build the first one and train them along the way.
Platform plans are on the pricing page. Custom build work by our team is INR 199 or USD 2 an hour, with a 150 hour minimum, no advance and payment after you accept the work. The cost to build estimate gives a rough range.
Then the test on past cases shows it before anyone relies on it. We either fix it, narrow the task, or tell you it is not worth doing yet. On 2good terms, you pay only for work you accept.
Guide
How to test an agent on past cases and decide whether it is ready.
Learn moreFree tool
An indicative range of hours and cost for a custom build on 2good terms.
Learn moreBuild with us
INR 199 an hour, 150 hour minimum, no advance, pay after you accept the work.
Learn moreSee it on your work
A working session with someone who builds these every week.
Or get a ballpark proposal in two minutesWhat happens next