Frequently asked questions
How is an agent different from a chatbot?+
A chatbot answers questions. An agent does the work: it reads the situation, decides, then updates the record, drafts the reply, files the document. See the three-way comparison, including when a plain rule is the better answer.
What if the agent gets something wrong?+
That is the design starting point, not an afterthought. Anything that matters goes through a human approval step, low confidence goes to a review queue instead of into your data, every action is logged with its reasoning, and you have a stop switch your own team controls. All seven controls.
We tried an AI pilot last year and nothing came of it. Why would this be different?+
Most pilots fail. The two most common causes are that nothing was measured before the work started, and that the thing was never properly wired into how the job actually gets done. That is why days 1 to 5 are a process map and a baseline, and why the agent is tested against your real historical cases before it goes anywhere near live work.
What will this cost me every month?+
On the model side, less than most people expect: roughly $40 to $350 a month for an agent handling 2,000 support tickets, depending on the model and caching. The vendors’ own published prices, dated, and the assumptions behind that estimate. Every proposal we send carries a cost model built on your real volume, plus a spending cap.
Does our data go to OpenAI or Anthropic to train their models?+
No. We use business API access where your content is not used for training, and where data must not leave your systems at all we use self-hosted open-weight models or on-device processing. Which route is right is part of the audit, because it changes the cost.
Do we have to replace our CRM or ERP?+
No. We connect to what you already run. See below.
What if the audit says we do not need AI yet?+
Then that is what the report says, and it happens. That answer is worth the $750 on its own: it is the reason the audit is paid rather than free.
Do we have to build with you after the audit?+
No. The report is yours either way. The $750 comes off the first invoice only if you do continue.
Who owns the agent, the code, the prompts, all of it?+
You do. Full source code, the prompts and the process map transfer to you on final payment, on accounts in your name. You can take it to another agency or run it in-house.
Is an agent legal for what we want to do?+
Usually, with conditions. GDPR Article 22 restricts decisions made solely by automation about people, and the EU AI Act treats HR, credit and essential-services use as high-risk even when it is purely internal. See how we design for it. This is not legal advice, but it will tell you which questions to take to a lawyer.
Will this replace our staff?+
In practice teams handle more volume rather than shrink, because the work that goes away is the work nobody wanted. We are not going to promise you a headcount reduction we cannot measure, and if that is the only reason for the project, the audit will probably tell you the payback is thinner than you hope.
How long until the first one is live?+
30 days from the start of the build. The week-by-week.
How do we know you actually build agents, and are not just relabelling a chatbot?+
Fair question. Gartner reckoned that of thousands of vendors calling themselves agentic, only about 130 genuinely were. Ask us three things: show me an agent taking an action in a real system, not answering a question; show me the audit log; show me the prompts and rules it runs on. We give all three before you commit anything. Ask every other agency the same.
What if our process changes in three months?+
Then the agent changes with it. You have the prompts and the rules in readable form, so your own team can adjust the simple things, and a monthly plan covers the rest.
