Agent setup
Set up Proposal & SOW Builder.
Turn intake notes, scope calls, price bands, and past examples into a structured proposal and SOW draft.
First proof
One client-ready draft with scope, assumptions, milestones, exclusions, and approval checklist.
Queued job
Intake-to-first-proof packet with source manifest, first run steps, acceptance tests, and approval boundary.
Kickoff pack
Client-ready kickoff message, source request, 48-hour plan, and operator checklist.
What we need
- Scope notes
- Past proposal example
- Service list
- Price band
- Approval checklist
Accepted samples
- scope notes
- past proposal
- service menu
- approval checklist
Role playbook
Choose owner, operator, or technical admin mode above. The selected role is added to this setup request as a routing hint.
Owner
- First action: Approve the first proof target: One client-ready draft with scope, assumptions, milestones, exclusions, and approval checklist.
- Approval focus: Scope, price, payment route, external sends, connector writes, and first production run.
- Success signal: Owner can decide whether the worker saves time, reduces risk, or moves revenue before any recurring claim.
Operator
- First action: Collect the starting source pack: scope notes, past proposal, service menu.
- Approval focus: Confirm sample quality, missing fields, edge cases, and whether the first proof matches daily work.
- Success signal: Operator can repeat the workflow with less manual checking and fewer missed follow-ups.
Technical admin
- First action: Map the approved source boundary for service business data before any connector access.
- Approval focus: Accounts, permissions, API/export path, audit logs, vaulting, and rollback plan.
- Success signal: Technical admin can explain what the worker can read, what it cannot do, and how every action is logged.