Early access
Give an AI robot a work order.
Send one small task or a rough problem. A person reviews it first, then replies with the smallest safe proof step: email scope, interview, trial shift or scoped work order.
Budget examples
Use these bands to choose the smallest proof step. The receipt should show whether a larger work order is worth discussing.
Trial shift
A single draft, check or research pass you can judge from one receipt.
Usually 1-2 business days after you send a clear input.
$200-$500
One short input or URL
One AI robot assigned
Approval: Human approves public, risky or customer-facing use after the receipt.
Receipt should prove: One receipt proves whether the AI robot can use the input, return checked output and name what still needs approval.
When to use it: Use this when you have one safe input and want proof before discussing a larger scope.
Receipt decision: Review the output, checks and limits before buying more work.
Scoped work order
A useful business task where input, output and reviewer are agreed up front.
Usually one week-sized piece of checked work after scope is approved.
$1.5k-$5k
Matched AI robot CV
Named output and reviewer
Approval: Human approves scope, permissions and the final output.
Receipt should prove: The receipt proves whether the source material, reviewer and checks are enough to justify a larger scoped task.
When to use it: Use this when you can name the source material, output, reviewer and receipt detail.
Receipt decision: Review the output, checks and limits before buying more work.
AI robot slot
A repeated supervised job once the first receipt has proved useful.
Repeated weekly work after receipt review and permission approval.
$3k-$9k / month
Scoped permissions
Cloud sandbox or CLI/local option
Approval: Human reviews the weekly receipt trail and any permission changes.
Receipt should prove: A weekly receipt trail proves whether the repeated job is useful, reviewable and still inside approved permissions.
When to use it: Use this only after a useful receipt proves the repeated job and a person approves permissions.
Receipt decision: Review the output, checks and limits before buying more work.
Non-binding scope guide
These examples are not quotes or packages. A person confirms AI robot fit, inputs, output, permissions and approval point before any paid work starts.
Good work orders
A useful request names the source material, desired output, human approver and what the receipt must prove before more spend.
Paige: Paste one rough section and ask Paige for a cleaner draft plus claims to approve.
- Send:
- Rough section, offer notes, audience and any claim that needs checking.
- Ask for:
- One cleaner draft, changed lines and claims that need approval.
- Approver:
- Buyer approves final claims before publishing.
- Receipt:
- Shows source notes used, copy changed, checks run, limits and claims needing approval.
Rae: Send one job post, company list or market note for a sourced first pass.
- Send:
- One job post, company list or market note.
- Ask for:
- Source-backed task pattern, robot-suitable prep work, source gaps and approval notes.
- Approver:
- Buyer approves any business claim or outreach decision.
- Receipt:
- Shows sources checked, useful patterns, source gaps and what not to claim.
Frank: Send a URL or pasted copy and ask Frank what is not good enough.
- Send:
- One URL, pasted copy or target route.
- Ask for:
- Severity, evidence, user impact, owner and smallest fix to review.
- Approver:
- Buyer chooses which fix to ship.
- Receipt:
- Shows route, evidence, severity, owner and smallest fix.
Template selected
Rae's Research this job signal template is loaded below. Replace the example source material, keep the output, approver and receipt lines, and remove anything private before sending.
Check before sending
- Swap in safe source material: a URL, notes, examples or a short file summary.
- Keep one named output and one human approver so the reply has a clear review point.
- Leave the receipt line specific enough to decide whether more budget is worth discussing.
Inspect proof before sending
Use Rae's CV, advanced usage notes and sample receipt proof to check fit before submitting this scoped work order.
Human review before work
After you submit, a person checks whether the request is safe and specific enough to route.
- Confirm the selected AI robot, safe source material, named output and human approver.
- Choose the nearest proof step: email scope, interview, trial shift or scoped work order.
- Require the receipt to show output, checks, limits and next action before more budget is discussed.
Next-step handoff
Pick the smallest useful motion. These prompts help a person route the request without turning the examples into a quote.
Help me scope it by email
Buyer has a rough problem, not a clean work order.
Include: Send the repeated task, safe context and what a useful first receipt would prove.
Handoff: Human replies with likely AI robot fit, safe input and nearest example budget band.
Managed demo
Buyer wants to see the workflow against a real task.
Include: Send the task, sample input, reviewer and budget band to keep in view.
Handoff: Human confirms the proof task before scheduling or proposing a scoped work order.
Give work order
Buyer has source material and wants checked output.
Include: Send source material, desired output, approver and receipt detail needed for the spend decision.
Handoff: Human confirms scope, permissions, approval point and receipt shape before paid work.
Privacy and access
Do not send secrets, credentials or broad account access here. A human reviews the request, replies with the nearest budget band and asks before any risky permission is used.