A WenBuidl business runs five agents: Sales, Marketing, Ops, Support and Finance, plus Buidlr, the agent you talk to. Each one has its own job, its own records and its own limit. Four of the five produce drafts that wait for you. Only Finance acts on its own, and only if you switch that on.
Naming software after a job title is easy. The useful part is saying what each one reads, what it produces, and what it cannot do.
So that is what this page is. No agent below does anything that is not in the product today.
In the order most businesses switch them on.
Drafts answers to what your customers ask, from your lean map, your services and your prices. You are handed a set of drafts to approve rather than a blank page, and you step in only where you disagree. The guardrail is approval, not authorship.
Watches your own records for what quietly goes wrong, and turns each finding into a task. Detection is deterministic, so every finding is a rule you can check and change. It is also the agent that notices the other agents, including drafts nobody has approved.
Decides which quiet leads deserve a follow-up and writes it. Choosing is by rule, wording is by model. The drafts land in the outreach queue as pending approval, which already had delivery and failure handling built around it. Nothing here sends.
Proposes what the business should put out: the post, the page, the lead magnet, and the angle each should take. It never publishes. A piece of content is a public statement in your name and there is no guardrail that makes doing that unattended safe.
Raises invoices, sends them inside the guardrails you set, and closes them when the money arrives. Stablecoin invoices settle themselves against the chain. Auto-send is off unless you turn it on, and even then only for invoices that clear your rules.
The agent you actually talk to, and the one that builds the business before any of the others have anything to work with: the blueprint, the services, the prices, the page. Afterwards it works your contacts, deals, invoices and tasks through the same tools you use.
The column that matters is the last one.
| Agent | Produces | Acts without you |
|---|---|---|
| Support | Draft answers to customer questions | No, answers are drafts until accepted |
| Ops | Tasks, from deterministic findings | No, a task is a thing to work or dismiss |
| Sales | Follow-up messages to quiet leads | No, drafts wait in the outreach queue |
| Marketing | Content proposals and angles | No, and it never publishes at all |
| Finance | Invoices, and settlement against the chain | Only if you turn auto-send on |
| Buidlr | The business itself, then day to day work | It acts through tools, in front of you |
Each agent runs per business in draft mode or auto mode, with a cap on how much it may raise in one run.
Draft means propose and wait. Auto means act inside the guardrails and tell you afterwards. There is no third setting, because nothing in the product behaves differently at a level between those two, and inventing one would only make the setting harder to reason about.
None of these agents need a new system kept up to date before they are useful. Sales reads the leads in your business, Ops reads your deals and invoices, Support reads your services and prices.
That is why they are worth switching on in the first week rather than after a month of setup.
The agents have nothing to work with until the business exists. Building it is the first thing Buidlr does.