Field note
The Meter Is the Product
Fronte Agents hands a small business owner an AI agent that does the work, and a spending brake that holds.
Where the week goes
Every owner keeps the same list, and it is not a hard one. Answer the mail. Tell the week where it stands. Go get money somebody already owes you. None of it is skilled work. All of it is yours. It arrives in a trickle that does not stop, and by Friday the trickle has eaten the week you meant to spend on the thing you actually started the business to do.
Fronte Agents is built for that owner: the person who loses the week to work they cannot delegate, and who does not want a shell to operate. They want a hand to take the work. The product is one private AI agent per customer. You hand it a job, it does the job on its own, and you see what the job cost. There is no terminal in the loop, and there is no setup homework. If you can send a message, you can run an agent.
Three jobs ship named, because a blank page is a worse product than a filled one. First, the inbox, handled: it connects to your mail, bins the noise, flags the three that matter, and drafts the replies. You approve each one, and nothing leaves the building without your say. Second, the week, briefed: one page of what moved, what is stuck, who is waiting on you, and what is next. Third, the invoices, chased: tell it who owes you, it sends one polite nudge until the invoice is paid, then tells you who paid, and it stops the moment you say stop. If none of those fits, you type your own job in plain English. It will write a small script if you ask it to. Coding is one thing it can do, not the thing it is.
The honest shape: a meter you can trust
The part most products in this category hide is the bill. AI calls cost real money, and the cost moves with the provider, so a flat fee that includes everything is a promise somebody is quietly hoping you will not test. This product does the opposite. It meters the work in dollars while it happens, and it hands you one control: a ceiling you set.
The ceiling is not a warning. It is a stop. Before the agent is allowed to make a call that costs money, the meter checks the cost against your number. If the call would cross it, the call does not happen. The agent pauses and tells you, in plain words, that it has stopped at your ceiling and that nothing was spent past it. The check happens before the work, not after, and it happens again for every call running at the same time, so ten jobs cannot sneak past the cap together. That ordering is the whole trick: reserve the money, do the work, then settle the real amount. The brake sits in front of the engine, not behind it.
Fail closed is the phrase for it. When the meter cannot tell what a call will cost, it refuses the call rather than guess. When the ledger and the meter disagree, it stops and refuses to bill until a person reconciles them. When a model is briefly unavailable, the reservation is released and the state does not change, because a hiccup is not a fault. None of this is glamorous. All of it is what makes a number you can believe.
The wall around your agent
Each customer gets their own agent, not a seat in a shared pool. Own user, own directories, own memory, own token, reachable only from the inside. The tenant is identified by the signed session, never by a value a visitor can pass in, and a new route is closed by default until it is deliberately opened. The memory is snapshotted nightly and restorable in one click, and a restore takes a fresh snapshot first, so undoing a mistake is itself undoable.
That isolation is the own it promise, and it is the reason the promise is worth anything. Your agent is yours alone. It reads only what you connect, and nothing else. Your mail, your documents, and your chats are not used to train anyone's model. Nobody shares your runtime, your files, or your memory. When you leave, you take the thing you built.
The hard parts
Trust is earned in inches and lost in one bad send, so the design assumes the agent will sometimes be wrong. It drafts; you approve. Anything that leaves the building passes a human first. That is slower than full autonomy, and it is the right speed for a tool that speaks in your name.
The failure modes are written down, because a product that hides them is lying about them. Hit your ceiling: the agent pauses and shows you two buttons, raise the ceiling or leave it paused. A card declines: the agent pauses and asks you to fix the card, and your data stays put. A setup step fails: you see an honest retry, not an endless spinner. This is the unglamorous half of the work, and it is the half that decides whether you keep using the thing.
And here is the part the cap does not solve. A ceiling bounds money. It does not bound judgment. It will not stop a bad reply from being drafted; only your approval does that. It will not fix a provider's outage, and it will not make a slow week fast. It will not teach the agent your business, and it will not earn your trust. A meter can tell you what something cost. It cannot tell you whether it was worth it. That stays your call, and the product is honest about leaving it there.
What we are selling
The published price is $19/mo, and the ceiling sits inside that, so the default bill is a number you chose before the work started. One price, one meter, one brake, one private agent. No ceremony, and no pricing page you have to read twice to find out what the tool will cost. You did not start your business to spend Monday in your inbox.