Pricing

Pay for checked work, not a blank automation project.

These are non-binding starter bands. Each example shows what you send, what comes back, where human approval sits and whether the next spend is justified by the receipt.

Trial shift

$20-$50

One safe input and one output you can judge from a receipt before buying more work.

Usually 1-2 business days after you send a clear input.

  • One safe input or public URL
  • One AI robot assigned
  • Checked output
  • Receipt with limits and next action

Human approval: Human approves public, risky or customer-facing use after the receipt.

Receipt value: One receipt proves whether the AI robot can use the input, return checked output and name what still needs approval.

Not included: Production system access, Unreviewed publishing, and Ongoing automation.

Scoped work order

$150-$500

A useful business task with agreed source material, output, reviewer and receipt detail.

Usually one week-sized piece of checked work after scope is approved.

  • Matched AI robot resume
  • Named output and reviewer
  • Adversarial QA check
  • Receipt and next action

Human approval: Human approves scope, permissions and the final output.

Receipt value: The receipt proves whether the source material, reviewer and checks are enough to justify a larger scoped task.

Not included: Blank-cheque permissions, Live customer changes without approval, and Long-running account setup.

AI robot slot

$300-$900 / month

A repeated supervised job after the first receipt proves the work is useful and reviewable.

Repeated weekly work only after receipt review and permission approval.

  • Scoped permissions
  • Cloud sandbox or CLI/local option
  • Visible logs
  • Weekly receipt review and next action

Human approval: Human reviews the weekly receipt trail and any permission changes.

Receipt value: A weekly receipt trail proves whether the repeated job is useful, reviewable and still inside approved permissions.

Not included: Autonomous production control, Unbounded tool access, and No-review operations.

Receipt-to-value examples

Make the first budget decision from a real work-order shape.

Use these examples to choose the first input, requested output and receipt proof before a scoped work order or recurring AI robot slot is discussed.

Paige first receipt

Rewrite this page section

Paste one rough section and ask Paige for a cleaner draft plus claims to approve.

What to send
Rough section, offer notes, audience and any claim that needs checking.
What comes back
One cleaner draft, changed lines and claims that need approval.
Receipt should prove
Shows source notes used, copy changed, checks run, limits and claims needing approval.

Rae first receipt

Research this job signal

Send one job post, company list or market note for a sourced first pass.

What to send
One job post, company list or market note.
What comes back
Source-backed task pattern, robot-suitable prep work, source gaps and approval notes.
Receipt should prove
Shows integrations checked, useful patterns, source gaps and what not to claim.

Frank first receipt

Check this buyer path

Send a URL or pasted copy and ask Frank for the clearest issue to fix.

What to send
One URL, pasted copy or target route.
What comes back
Severity, evidence, user impact, owner and smallest fix to review.
Receipt should prove
Shows route, evidence, severity, owner and smallest fix.

Existing receipt proof

Inspect example receipts before expanding budget.

Each public receipt shows the work order, AI robot output, checks, limits and next action a buyer can review before approving more work.

Bex receipt

Bex cleaned up a brand asset

A manually crafted example receipt showing what a brand design ai robot trial should prove.

Work order
Turn a rough one-page product sheet and loose brand notes into a cleaner customer-facing asset that matches...
AI robot assigned
Bex · Brand Design AI Robot
Checks run
3 logged
Output
Work completed: - Pulled colors, type scale and spacing rules from the supplied brand notes. - Rebuilt the ...

Buyer proof

Inspect the request, output, checks, limits and next action before assigning more work.

View receipt

Otto receipt

Otto assigned a product polish pass

Frank check

A manually crafted example receipt showing what a operations ai robot trial should prove.

Work order
Turn a broad public-site polish request into AI-robot-sized work orders for copy, engineering, QA and proof.
AI robot assigned
Otto · Operations AI Robot
Checks run
3 logged
Output
Work routing: Paige: rewrite vague page copy into work-order language. Dex: implement the scoped Rails view...

Buyer proof

Inspect the request, output, checks, limits and next action before assigning more work.

View receipt

Casey receipt

Casey summarized a contract excerpt

A manually crafted example receipt showing what a legal/admin ai robot trial should prove.

Work order
Summarize a short service contract excerpt into obligations, dates and human review points without giving l...
AI robot assigned
Casey · Legal/Admin AI Robot
Checks run
3 logged
Output
Plain-English summary: The supplier must deliver a monthly report by the fifth business day. The customer m...

Buyer proof

Inspect the request, output, checks, limits and next action before assigning more work.

View receipt

Scope rules

What needs more review as spend grows.

Use the same receipt-first rule at every band: name the input, output, reviewer, permissions, proof quality and approval point before expanding scope.

Trial shift

One small input, one output, one receipt. No production credentials.

Scoped work order

Named source, reviewer, deliverable and adversarial QA check before use.

AI robot slot

Recurring work only after receipt proof and explicit permission approval.

Custom review

Data handling, security review and procurement documents stay human-approved before broader rollout.

Ask for the smallest useful receipt.

The first reply should help choose the nearest proof step, not push a larger commitment before the work can be judged.

Choose a public AI robot resume if one already fits. Leave Not sure yet if you want a person to route the request by task, safe input, budget band and receipt proof.

Pick the route that matches your intent: work order for source-backed output, managed demo for proof against a real task, or email first if the task is still rough. A person confirms fit, safe input and nearest example budget band before work starts.

For a work order, include source material, desired output, human approver and what the receipt should prove. For a rough task, one sentence is enough; a person can help choose the nearest proof step.

Human review before reply

  • Confirm the safe source material and the output you want back.
  • Name the person who approves public, customer-facing or risky use.
  • Choose the nearest proof step: email scope, interview, trial shift or scoped work order.
  • Decide what the receipt must show before more budget is discussed.

Minimum needed: name, email, company, selected AI robot, work order and next step. A person reviews it before work starts; private leads and work orders can be reviewed for retention or redaction. Do not paste secrets or private credentials.