Sandbox quickstart.
Ten minutes. Seeded data. No card. You will see one full run end to end.
The sandbox is a real Paitho instance pointed at a fixed dataset of fifty B2B SaaS companies we have permission to use. You will see exactly what a paying customer sees, except you cannot send to real inboxes and the lead list is not yours.
1. Create a sandbox
Go to paitho.ai/sandbox and enter an email. We send a one-tap magic link. No password to forget.
You land in a workspace that already has a sample run waiting at the qualification stage. We kept the first three stages pre-computed because they take about ninety seconds and we did not want you staring at a spinner on your first visit.
2. Pick a vertical pack
The sandbox defaults to the Devtools & Infra pack. You can switch it from the top-right pack picker. Each pack changes the pain taxonomy, the scoring weights, and the tone profile. The same lead list will produce different drafts under different packs. That is the point.
If you want to know what a pack actually contains, read the packs section first. If you just want to feel the product, leave the default.
3. Run qualify
Click run qualify(). The stage scores each of the fifty leads against five ICP components. About nineteen of them will pass. Click any leadto see the score breakdown. The scoring rule is the pack's icp.yml file. You can read it and edit it in place.
4. Watch a brief get drafted
Pick a passed lead. Hit draft_brief(). Watch the prompt run with the model receipts visible on the right. You will see exactly which signals were used, which were rejected, and what the model produced.
The brief is not the email. The brief is the working document the email is written from. Read it. If the facts are wrong, fix the brief and re-draft. Garbage in, garbage out.
5. Read the email
Hit draft_email(). Six sentences come back. They are tied to one pain signal with a date and a citation. Open the citation. It will be a real URL.
If the email reads like a template, that is the bug we want to hear about. Tell us and we pay a $50 credit per confirmed case.
6. Reject one on purpose
Pick another draft. Reject it with a reason. The reason gets stored in the eval set for the prompt that produced it. Over time, your rejections raise the bar. Read about the eval format here.
Next
The sandbox runs forever. Bring it up when you want to test a new pack, see a prompt change, or show someone what real outbound looks like before they ask for a demo. Talk to sales when you are ready to point it at your own list.