Skip to content
AksharAI

How it works

One process, tested on your past cases, then trusted with real work.

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.

BLOCKSTriggerRead documentAsk the modelCheck a ruleAsk a personWrite to a systemVendor registrationDraft v4 · Ritu ShahNew emailvendors@ inbox01Read documentsPAN, GST, cheque02Compare detailsNames and numbers03GSTIN activeRule, no model04ProcurementApproves record05Create vendorDraft in Tally06Test run on last month's vendor filesEach result compared with what procurement actually didReady to publishTesting

In short

How does a first AksharAI agent go live?

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.

Scope
About a week
Build
Typically 1 to 2 weeks
Test set
30 to 50 past cases
Live
With a person in charge

The path

Six stages from idea to daily use

What happens at each stage, roughly when, and who does what on each side.

  1. Stage 1 · Week 0

    A first call about one process

    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.

    Your team
    Bring the person who does the work, as well as their manager.
    Our team
    Show an agent working on a version of your task and give a clear view of fit.
  2. Stage 2 · Week 1

    Scope with real samples

    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.

    Your team
    Share samples and agree the rules and who approves what.
    Our team
    Write a one page scope: inputs, outputs, checks, approvals and what success looks like.
  3. Stage 3 · Weeks 2 to 3, typically

    Build and connect

    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.

    Your team
    Arrange access to systems and review the work each week.
    Our team
    Build the flow, the screens and any custom connectors.
  4. Stage 4 · Before launch

    Test on past cases

    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.

    Your team
    Review the test results and the mistakes.
    Our team
    Run the evaluation, fix failures and report plainly.
  5. Stage 5 · First month

    Go live with a person in charge

    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.

    Your team
    Approve, correct and tell us what feels wrong.
    Our team
    Watch runs, tune rules and fix issues quickly.
  6. Stage 6 · Ongoing

    Daily use and improvement

    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.

    Your team
    Own the agent's rules and decide what comes next.
    Our team
    Support, monitoring and new work on 2good terms when you need it.

Who is involved

Four roles on your side

Small projects need a few hours a week from each. The reviewer matters most, because they know what a right answer looks like.

Process owner

Owns the rules, approves changes and decides when the agent is ready. Usually the head of the team whose work it is.

Reviewer

The person who approves exceptions every day. Often the same person who did the work before.

Builder

Assembles the app in the studio. Can be someone on your team, our team, or both together.

IT contact

Grants access to systems and agrees where the platform runs. Needed for a few hours in total.

Colleagues sitting around an office table discussing a piece of work

Questions

About timing, cost and fit

How long until the first agent is in use?

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.

Do we have to use your team to build?

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.

What does the build cost?

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.

What if the agent does not work well enough?

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.

See it on your work

Bring one slow, repetitive process. We will show you an agent doing it.

A working session with someone who builds these every week.

Or get a ballpark proposal in two minutes

What happens next

  1. Step 1A short call about one process and the systems involved
  2. Step 2A demo of an agent working on a version of your task
  3. Step 3A clear view of fit, approvals and what it would take