Let AI do the work for your users

It embeds inside your SaaS, reads the real data in the product, and finishes the task for the logged-in user, in one message, inside the product they are already in.

You can, and the first working version is a weekend now. The part that takes months is everything after the model call: making each action run as the signed-in user rather than an admin key, showing a confirmation with the real values in it, keeping an audit trail that names a person instead of a service account, and a sandbox to test in. That is the work that decides whether it ever leaves your staging environment, and it is the part you are buying.

Inside your product, in the browser, the place your users already are. Not a separate tab, not another login to remember, and not inside somebody else's chat window where your users have to go looking for it.

The multi-step ones a menu cannot be: look something up, reason about an exception, then act. Creation, assignment and access management are the sweet spot, because those are the requests that span several screens and need a judgement call in the middle.

No. It reads your product's live state at the moment of the question, not a cached answer from last month and not a training copy of your docs.

Nothing to install alongside your product, no rewrite, no migration, no new service to run. If you remove Verb tomorrow, your product is exactly what it was.

About five minutes from signing in for read-only questions. Actions that change things take longer, because they run against your backend, and we would rather you wired that up deliberately than quickly.

It loads as one small script with no framework inside it, styled in isolation from your product’s own styles both ways. It opens as a side panel or a popup, you choose whether the side panel pushes your page aside or covers it, it goes full-screen on a phone, and it never opens itself.

Yes. Its name, greeting, opening suggestions and colour are set from your dashboard, and contrast is worked out for whatever colour you pick so the text stays readable.

It only acts through capabilities you have described. Anything outside them gets an honest “that isn’t something I can do”, not a guess dressed up as an answer.

No. Anyone on your site can ask read-only questions from the moment the assistant is there. Signed-in users get whatever their sign-in already permits them inside your product.

When it opens it suggests things it can genuinely do, drawn from the capabilities you turned on. You edit those suggestions from your dashboard, because a feature nobody knows about may as well not exist.

You would know, not wonder. If something on your side stops it loading, usually a strict content-security header, the failure is reported in your dashboard rather than staying silent.

Building is free: the Dev plan is your site and its test site, working on your own computer, for good. When your users can reach it, Starter is $39 a month for 3,000 requests and 1 site, Pro is $99 a month for 8,000 requests and 3 sites, Max is $249 a month for 20,000 requests and 10 sites. The actions it takes are never counted. Every number is on the pricing page.

No. No card, no call, no invite code. You are in the dashboard in under a minute, and building on Dev stays free. A card comes in only when you pick a plan to go live.

It stops answering until the month starts again, and your visitors see a calm "temporarily unavailable", never an error. You can add more requests from your dashboard, and you are never billed for anything you did not choose.

No. There is nobody to wait for and nothing to request. Sign up, point Verb at your site, and it starts answering.

No. Plans are priced on requests and sites. Your team is not what costs anything, so it is not what you pay for.

Yes. Each product is a site with its own tools and script tag. Pro includes three and Max ten, and any plan can add one for 15 a month.

The assistant on this page is the real product. Open it, top right, and ask it anything about Verb. It answers with the same discipline it would bring to yours.

Every site comes with a test site alongside it: its own key, its own log, and a Test badge on the widget. Its key only answers on localhost, so it runs inside your app on your own computer, against your development data, and never reaches your users. Anything that changes data still asks for a yes first.

No. Everything you and your team try in the sandbox is free and never counted. It is there to be leaned on.

Your live site stays free until 30 October 2026, and you will hear it from us directly before that date. Choose a plan before then and it keeps answering without a break. Everyone who was here during the beta gets a founding offer: just ask.

The people who built it. There is no ticket queue and nobody reading from a script. The contact on this page reaches us directly.

Because you should see it work on your own product, with your own data, before paying anything. The test site only answers on your own computer, so it cannot carry a real product, and nobody is on a clock while they wire it up.

No. Verb has no way to sign in as anyone: no passwords, no sessions, no cookies of ours inside your product. It works through the access your product already grants.

No checkout, no payments, no card data. Not a setting you switch off. It is simply not something Verb does, and it never will be.

Anything that edits or deletes shows the user exactly what is about to happen, in plain language, with the real details. They confirm, or it does not happen.

It says so. Your user gets an honest “that didn’t work” instead of a confident lie, and you hear about it before they do.

Every action is on the record: what was done, who asked for it, when, and whether it actually worked. Crucially the record names the person, not a service account, so your log never reduces to “the AI agent did this”, which is the line that makes an audit useless and stops an in-house build being signed off.

The person who asked, and the record says so by name. Verb never holds a credential of yours, it cannot do anything the person asking could not already do themselves, and anything that writes stops for a confirmation showing the real values. There is a security page on this site written for whoever will actually ask these questions.

It helps: your existing tools wire in as they are. It is entirely optional, though: if that means nothing to you, it changes nothing.

The same team runs TradePilot, a trading copilot with 170+ tools live in production, software people rely on for decisions about their own money. Verb is that discipline, packaged for your product instead of ours.

No. It acts as the logged-in user, through the access your product already grants them, and your backend remains the authority. If a user could not do the thing themselves, neither can the assistant on their behalf.

You and your team, in your dashboard. Conversations are kept until you ask us to delete them, and you can export them whenever you like. Each user appears as a pseudonymous reference rather than a name. The model provider processes a conversation to produce the reply. Nobody else sees it.

A domain serves no answers until you have proven you own it. Requests coming from any unverified origin are refused outright, so a copied page gets nothing.

The real details, not a generic “are you sure”. If it is about to cancel an order, you see which order, whose, and what changes. Confirm, and it happens; close it, and nothing does.

Minutes. Any credential is issued by your own backend, short-lived, treated by Verb as opaque, and never stored beyond the request it came with.

From your dashboard: read-only questions or everything you have described, one switch apart, with per-tool control in between. Even at full access, anything that writes still asks first.