Sage vs hiring beta testers
The short answer. Hiring beta testers costs you the recruiting, the briefing, the chasing and the reviewing. Sage does all four itself: it browses your product in a real browser, writes the tasks from what it saw, checks each tester's report against its own observations, and pays them in USDC automatically. You approve the plan and fund it.
How is this different from a testing marketplace?
A marketplace gives you testers and hands the work back to you. You still write the brief, read every submission and decide who gets paid. Sage writes the brief from what it observed first-hand and makes the payment decision itself, and every payout publishes a receipt at /proof/<transaction> that anyone can check against the chain.
What stops the AI from paying out badly?
The AI proposes and the vault decides. Each job's budget sits in an on-chain vault that pays the exact reward, enforces the per-task cap and the completion limit, and rejects anything outside them. No model output moves money on its own.
A tester's report has to match things Sage itself observed while exploring, so an account that could have been written without opening the product does not pass. A task whose evidence cannot be checked is dropped before anyone is shown it.
What does it cost?
You set the budget, and all of it goes to the people you pay: Sage takes no fee per payout and pays the network fee itself. Rewards are fixed from the budget when the job is made, so every possible payout adds up to exactly what you funded, and stopping a job returns what is left to you. Sage is free to start; paid plans add more live jobs and team features.
Do I need a wallet?
No. Sign in with an email and Sage opens an account for you to fund jobs from, under spending rules that only let it launch your jobs within your cap. Or run the whole thing from @sagedeputybot on Telegram. A browser wallet works too.
An honest comparison
| Question | Hiring beta testers | Sage |
|---|---|---|
| Who writes the test plan | You | Sage, from browsing your product |
| Who reviews submissions | You, every one | Sage, against what it observed |
| Who decides payment | You | The vault, inside limits it cannot exceed |
| Proof of payment | Your word | An on-chain transaction and a receipt page |
| Setup time | Days | Minutes to a live job |
| How people are paid | However you arrange it | USDC on Metis |
Where hiring people is still better. Deep exploratory testing by a domain expert, anything that needs judgement about taste, and any flow that genuinely needs credentials Sage must never ask a tester to share. Sage is judged on whether its payouts hold up, and every one of them is on the ledger.
Compare it instead to running a bug bounty, read the case study or the FAQ, or point it at your own product and watch it work.