Manual6.1
MissionCut the unbillable hours: status reporting, deliverable assembly, and client-portal drudgery.
SegmentOne Bot per client, one per function
Bots
- Chief · Routing across clients and functions
- Account (one per major client) · That client's work; duplicate the profile and rescope
- Reporting · Status packs and reconciliation
- Reviewer · Rejects anything failing the standard
Connect
- Project tool
- Drive
- Slack
- The client portals you click through weekly
Routines
- Monday status pack per client
- Thursday deliverable QA against the brief
- Monthly hours-versus-scope reconciliation
First taskTeach-by-demonstration on the single ugliest client portal you touch every week.
Red lines
- Never emails a client
- Never uploads to a client system
- Client data goes on the shared computer, so one client's Bot can technically reach another's files: segment by Cursor user, and use scoped per-client service accounts (section 5.3), if that is unacceptable