What we answer for

Your name on it. We answer for it.

The work goes out under your firm's name. Here is exactly what we answer for, in writing, before you have to ask.

Signed by Eashan Gupta Founder, Agentec. He signs every agreement, and he is your escalation.

01
Our mistake is never your person's.
Your person's yes covers what the screen showed them. The AI's work behind it is ours to answer for.
02
Nothing leaves until your person says yes.
They say it in two ways. Once, as rules: inside your prices, your limits and your hours, a reply goes at once. Or one at a time: anything outside those rules comes to their phone as one tap, ready to send.
03
If we stop, it is all still yours.
Every account is in your name from day one. Your files, rules and log come to you as plain files within 14 days.

Your yes covers what you saw. We answer for the rest.

Your person's yes means they checked what the screen showed them. We answer for the AI's work behind it: the rates it gathered, the sums it did, what it flagged and what it missed.

If our agent got it wrong, the mistake is ours, never your person's. Your rules decide what the agent may send on its own. Everything outside them waits for one tap from a named person at your firm.

When something goes wrong: stop, tell, fix.

Agents get things wrong. That is why every one of ours can stop itself, and why this is written down before you sign anything.

At once It stops
An agent that fails three times stops itself, and your team does that job the old way until it is fixed. At night and at weekends it stays stopped, and we pick it up at 09:00 on the next working day, unless your agreement includes weekend cover. You can stop any agent yourself, any time, in one tap.
At once You are told
Your own system tells your named person at once, at any hour, and Eashan writes to you with what happened and what we are doing about it. If your data is involved and we notice first, we tell your named person what we know within six hours of noticing, any day.
Before it runs again We fix it
The fix is proved on the case that failed and on twenty of your past jobs before the agent runs again. Fixing it is on us.
Within five working days We write it down
A short review: what happened, why, what we changed, and what you need to do, which is usually nothing.

India's CERT-In directions give a company six hours from noticing an incident to report it. That is why the alert comes from your own system, at once, and never waits for a message from us.

The day it goes wrong, we say so.

With your yes, we publish a short note when one of our agents gets something wrong: what happened, that it was ours, what we fixed and what changed. Your firm is never named without your written yes, and nothing about your clients is ever shown.

We never write "the AI did it". It was our agent, so it was our error.

People, by name.

Who works on your system: Every person who works on your system is named in your proposal, with what each has built. Nobody else is given access to it.
Who signs, and who you escalate to: Eashan Gupta, founder. He signs the agreement and every note that needs an answer, and he is your escalation.
Support hours: 09:00 to 19:00 India time, Monday to Friday. At night and at weekends your own system still stops a failing agent and tells your named person at once. Weekend cover is by arrangement, written into your agreement.
If we cannot be reached: Nothing unsafe waits on us. A failing agent stops itself, a working agent keeps working with your person approving, and you hold your own stop switch. Every account, file and log is already in your firm's name.

How we use AI ourselves.

Our own AI policy, in six lines. It binds the agents we run for you and the ones our own company runs on. As it stands on 13 October 2026.

What an agent may do alone: Read, sort, draft, check and file, inside the rules its owner set. Those rules are written down, and a person can read them.
What always waits for a person: Spending money, signing, filing with an authority, deleting a record, and any message outside the rules its owner set.
How we test: Before an agent touches live work it runs on past jobs with known answers. Any change to its rules or its model runs the same jobs again first.
How we disclose: An agent that writes to a person outside the firm says it is AI at the start of every conversation. When one of ours gets something wrong, we say so in writing, as our error.
Your data: Your data trains only your own model, with your written yes, and never anyone else's. Nothing reaches another client. Where a model outside your own machine reads anything, it is named in writing before we build.
Who answers for it: A named person answers for every agent we run, ours and yours. The log shows what it read, what it did and who said yes.

The terms, in plain words.

AI, said plainly: Agentec's AI drafts our notes and receipts and always says it is AI. An agent that speaks to people outside your firm says it is AI at the start of every conversation, in your firm's name.
The price, in writing: One fixed price, in writing, before any work. After the session you get a written proposal with the scope, the test it has to pass, who works on it and the price, and nothing starts without your yes. How we work
If you stop, or we do: Every account and every line of code is in your firm's name from day one. Your data, rules, prompts, templates and log come to you as plain files with a runbook any developer can use: at the end of the month you choose if you stop, within 14 days if we do. The machine in your office is yours.
Your files: Where they sit, what leaves the building and what is encrypted. Your files and security

Bring us the problem, and hold us to this page.

The session comes first: 45 minutes on a video call with our founder, nothing to sign. You leave knowing what we would build first, and why. The written proposal that follows names who works on your system, and this page comes with it.

Book the session Your files and security

A person reads everything you send.hello@agentec.cloud Agentec on LinkedIn