SprintTSP-SPR-01

Two weeks to get one workflowrunning without a person in the middle.

We pick the one repetitive job that eats the most hours, build the automation on your own documents, and hand it over live in your accounts.

₹60,000₹75,000one-time

All prices exclusive of 18% GST. GST invoice issued against every payment.

  • Launch price holds until 31 December 2026.
The cost

The work is not hard. It is endless.

Somebody on your team spends half of every day reading the same kind of document and typing what it says into another screen. Nobody at that desk lacks skill. They lack hours, and the pile grows with your order book.

  • Purchase orders arrive as PDFs and WhatsApp photos, then get typed into the system by hand.
  • One person reads every incoming email and decides which of four teams it belongs to.
  • The same weekly report is rebuilt in Excel every Monday, from the same three exports.
  • Quotations get written from scratch because nobody can find the last one for a similar part.
  • Vendor bills are checked against the GRN line by line, and the odd one still slips through.
What you get

One automation, live in your account.

The workflow is chosen with you on day one, built against your real documents, and switched on before we leave. You hold the keys and the code.

  • One workflow automated end to end, chosen with you on day one
  • Prompts, rules and pipeline code in a repository you own
  • The automation running in your own cloud account, on your own API keys
  • A confidence threshold, with everything under it routed to a human review queue
  • Per-run logging of errors, cost and volume, readable without a developer
  • Connections to wherever the work already sits: an email inbox, a shared drive, an ERP export, a WhatsApp Business number
  • Accuracy measured on a sample of your own documents and written down before go-live
  • A one-page runbook for whoever operates it after we leave
  • One 60-minute handover call with the people who will use it
Delivery
14 working days
Post-handover support
In-scope fixes free for 30 days
How it runs

Fourteen days, kickoff to handover.

Booked as one block. Four of those days are spent running the automation beside the person who does the job today, because that is where the real errors show up.

  1. Days 1–2 — Pick the workflow

    We watch the job get done once, on a call, with live documents. Then we write down what the automation must handle and what it must escalate.

  2. Days 3–7 — Build on your data

    Built against a sample of your own files, including the messy ones from last month. Accuracy gets measured on those before anything goes live.

  3. Days 8–11 — Parallel run

    The automation runs alongside your team while a person still does the job. Every disagreement between the two gets logged and fixed that week.

  4. Days 12–14 — Handover

    Keys, code and runbook move to your side. One hour on call with whoever operates it, then the workflow is yours to run.

Fit

Who should take this.

Take this if

  • One workflow eats hours every week and the rules behind it can be written down
  • The documents already exist as PDFs, emails, exports or scans, in a place someone can point at
  • You have taken the Operations Audit, or you already know which job to attack first
  • Somebody on your side can give two hours a week and answer questions about how the work is really done
  • You want the automation running under your own keys, in your own account

Skip this if

  • You want a chatbot demo for a board meeting. That is a slide, not a system, and it will not survive contact with your data.
  • There is no clean set of past examples to work from. Take the Operations Audit and start with what to capture.
  • The knowledge lives in one person and handwritten registers nobody has photographed. Digitise the last three months first.
  • You need it live in under two weeks. The sprint is booked as a block and we will not cut the parallel-run days.
  • You want the automation to make the final call on money, safety or anything legal. A person keeps that seat.
  • You want three workflows at this price. Three workflows is three sprints, or a retainer.
Pricing

What it costs, and what moves it.

One price, one workflow, fourteen days. Scope is written down on day two and signed, so nothing drifts on either side after that.

₹60,000₹75,000one-time

All prices exclusive of 18% GST. GST invoice issued against every payment.

  • Launch price holds until 31 December 2026.

What moves the price

  • More than one workflow in the same sprint
  • Handwritten input, or documents in more than two languages
  • A source system with no API and no export, where we have to read the screen
  • Data that cannot leave your premises, so the model has to run on your own hardware
  • Volumes past a few thousand documents a month, where inference cost stops being small

Included

  • Workflow selection, build, accuracy testing and the parallel run
  • Prompts, pipeline code and deployment scripts, in your ownership
  • The handover call and the runbook
  • A one-page runbook for whoever operates it after handover
  • A GST invoice against payment

Quoted separately

  • Model and API usage, billed by your provider straight to your own account
  • A second workflow, or a second language
  • Changes to the source systems the automation reads from
  • Tuning after your documents or your rules change
Questions

Before you ask.

What changes the price?

Three things: how many workflows, how clean the source documents are, and where the model has to run. One workflow with digital documents sits inside the fixed fee. Handwriting, a second language, or data that cannot leave your premises is quoted before we start. The launch price applies to any sprint booked while it still shows on this page.

How long does it take?

Fourteen days from kickoff. Two days to pick the workflow and write the rules down, five to build against your own documents, four running in parallel with the person who does the job today, three to hand over. The clock starts when we have sample documents and access, not when you pay.

What happens after handover?

The automation runs in your account, on your keys, from day fifteen. You keep the repository, the prompts and a one-page runbook. Anything that stops behaving the way we agreed is fixed free for thirty days. New document types, new rules or a second workflow are quoted separately, or picked up on a monthly retainer.

Which models run it, and where does our data go?

We build on the Anthropic API by default, the same stack behind the municipal waste platform above, and we will use whichever provider your policy names instead. Everything runs in your cloud account under your own key, so documents travel from your storage to the model and back. We store nothing on our servers, and under the standard API terms your data is not used to train models.

Do you invoice with GST?

Yes. We are GST registered and every payment gets a proper tax invoice against our GSTIN, issued the same day the payment lands. Every price on this page is exclusive of 18% GST. Payment is by bank transfer or UPI against the invoice. Model usage after handover is billed by your provider straight to your own account.

What do you need from us?

Three things. Real examples of the documents the workflow handles, the messy ones included, and the more you can send the better it gets. One person who does the job today, for roughly two hours a week. Read access, or an export, from wherever the data sits. If those examples do not exist yet, the sprint is early. Start by capturing them.

Ready when you are

Two weeks from now, one job leaves your team.

Send a message with the workflow you have in mind and roughly how often it runs. We will tell you within a day whether it fits a sprint or needs a build.