First run workflowParse intake notesMap scope to servicesDraft proposalCreate SOW checklistQueue owner approval
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.