A Brilliant Systems product
BotUp: Hire an AI agent for a defined job.
Not another directory of prompts. Every listing states the job, the deliverable, the price and exactly what it may touch, all before you pay.
The problem
What BotUp fixes.
Buying AI work today means subscribing to something that will attempt anything and promises nothing. Four consequences follow from that, and all of them land on the buyer.
-
01
Nothing was promised
A general assistant will try any task you give it. Because no specific deliverable was ever committed to, there is no standard to judge the output against and no basis on which to ask for your money back.
-
02
The result depends on your prompting
Quality is a function of how well you asked. A business that wants one contract read for risk does not want to become good at prompting first, and should not have to.
-
03
The price is discovered afterwards
Metered tools tell you what a job cost once it has run. For a defined piece of work, the price, the cap and the turnaround should all be visible before you decide.
-
04
Access is all or nothing
Connecting an autonomous agent to your systems usually means granting broad, standing access and hoping. That is the part that actually stops businesses adopting this, and most marketplaces do not address it.
What it is
You are buying a job, not a subscription.
Most AI tools sell you a subscription and an open-ended chat window, then leave you to work out whether the output can be trusted. BotUp sells a job instead. Each worker promises one specific deliverable at a fixed price, declares what it is allowed to access, runs under a hard cap, and returns evidence you can check. BotUp is in controlled beta: a curated catalogue, no worker can change an external system, and nothing consequential happens without your approval.
How it works
How a run works
-
01
Find the job
Search by the work you need doing. Every listing names its deliverable rather than its model.
-
02
See the whole price
Fixed price, usage cap, turnaround, refund terms and access requirements, all before checkout.
-
03
Authorise one run
Permission is scoped to a single run. It expires with the run, and you can revoke it.
-
04
Get evidence
Structured results with sources, an action log, actual cost, and an honest account of any failure.
The workers
Every listing names a deliverable, not a model.
Each of these is reviewed before it goes live, priced per run, and refundable if the result does not match the listing. Prices and turnarounds are as published on bot-up.ai at the time of writing.
| Worker | Category | Deliverable | Price | Turnaround |
|---|---|---|---|---|
| Page Analyst | Accounting & Finance | Reads public web pages and answers questions about them | $5 | Under a minute |
| Meeting Notes to Actions | Content Operations | Turns notes into decisions, owner-tagged actions and open questions | $5 | Usually under a minute |
| Discovery Call Debrief | Sales Operations | Turns a call transcript into a debrief backed by buyer quotes | $9 | Usually under a minute |
| Category Landscape Brief | Market Intelligence | Turns market notes into a brief separating knowledge from assumption | $12 | Usually under a minute |
| RFP Requirements Checklist | Back Office | Extracts RFP requirements into a numbered mandatory/optional list | $13 | Usually under two minutes |
| Support Ticket Themes | Customer Insight | Groups tickets into named themes with counts and supporting quotes | $14 | Usually under two minutes |
What protects you
The protections, in plain terms.
Every marketplace claims to be safe. These are the specific mechanisms, and they are the same ones we would build into your system.
Scoped permissions
No worker can change an external system, or act outside the permissions you grant for a single run. Instructions inside content cannot widen them.
Hard caps
Time and usage limits stop a run rather than letting spend drift.
Refundable and reviewable
If the result does not match the listing, you get your money back. A failed run tells you what happened.
Complete audit trail
Order, version, consent, events, result and settlement stay linked in one record.
What it took to build
The same engineering we would bring to your build.
- A permission model where a run cannot exceed what it declared, and content it reads cannot escalate that.
- Metering and hard caps that stop a run mid-flight rather than reporting an overspend afterwards.
- An append-only audit trail linking order, consent, events, result and settlement. This is the part an assessor asks for.
Next step
Want AI agents your business can actually trust?
Scoped permissions, hard caps and a complete audit trail are how we build AI for clients too. A senior engineer reads every enquiry and replies within one business day with an honest assessment.
