Three lines of work.
One team behind all three.
Everything we take on is one of three: an agent inside a workflow, the first version of a product, or the internal tooling a business already runs on. The table below is how most people work out which one is theirs.
Most people know which column is theirs by the second row
Five dimensions, three lines. If two columns both look right, the smaller scope first is almost always the better answer — and we will tell you which one that is.
| Dimension | AI agents & automation | MVP & product builds | Internal tools & ops |
|---|---|---|---|
| You come to us when | AI agentsa repeatable task is eating a team’s day | MVP buildsthe product does not exist yet | Internal toolsthe operation runs on one person’s spreadsheet |
| The unit of work | AI agentsone workflow, one queue, one measurable outcome | MVP buildsthe first real version, end to end | Internal toolsone process, first slice first |
| What lands in your repository | AI agentsthe prompts, the orchestration and the evaluation set | MVP buildsthe running product and the decision notes | Internal toolsthe system, the migrated data and a runbook |
| How you know it works | AI agentsscored against a test set of your real cases | MVP buildsyou pull it and run it every week | Internal toolsone workflow in real use before the second is built |
| The failure it exists to prevent | AI agentsa demo that only works on ten clean examples | MVP buildsa rebuild in year two | Internal toolsa workbook nobody can audit |
| Full detail | AI agentsHow we scope it: AI agents & automation | MVP buildsHow we scope it: MVP & product builds | Internal toolsHow we scope it: Internal tools & ops |
Whichever line, four things do not change
Code in your repository as it is written, scope agreed in writing, support in business hours IST Monday to Friday, and the person who built it on the call.
- Code in your repository as we write itThere is no handover event at the end, because you already had everything.
- Scope agreed in writing before we startAnd a written note the moment something we find changes it.
- Support in business hours, Monday to Friday ISTThe response window for anything critical is agreed in writing. We do not advertise a blanket SLA a team this size could not hold.
- You talk to the person building itNo account manager between the question and the answer.
Three cases where the honest answer is no
We would rather lose the work on the first call than take it on badly and tell you in month three.
- You want an open-ended retainerWe scope in writing and stop when the scope is met. Billing hours indefinitely is not a shape we work in.
- You need cover outside business hoursSupport is Monday to Friday IST. If your operation needs someone awake at 3am, that is a real requirement and we are not it.
- A tighter spreadsheet would actually solve itSometimes it would, and we will say so on the call rather than after the invoice.
36 builds — and we tell you which ones actually run
Delivered for clients under NDA, so what is public is our own reference build of each: 9 are runnable applications you can open, 27 are navigable screen sets with no live backend. Every card says which it is before you click.
Still between two columns?
Tell us where you are in a sentence or two. We'll point you at the right line — and if we're not the right team, we'll say that instead.
Start the conversation