Kickoff Doc Creation — discovery-prefilled KO docs in the client folder
The KO doc is waiting in the client's folder before anyone asks for it.
What was getting in the way.
Every new client needs a kickoff document — services recap, goals, a long access checklist, discovery notes. Building one meant an account manager copying a template, hunting facts across the CRM, and retyping discovery details; docs arrived late, half-filled, or inconsistent between account managers.
Context
Every new client; recent examples include a therapy practice and a dog-training company.
How the work runs.
- 01
Trigger
"create a KO for " in the client's channel (or automatically via the pre-kickoff pipeline, Entry #19).
- 02
Agent builds from the canonical
Agent builds from the canonical KO outline (standing format — no template hunt needed).
- 03
Prefills from the CRM with
Prefills from the CRM with verified facts only: contact name, email, phone, deal terms; anything inferred goes in as an explicit "(confirm)" placeholder, never as fact.
- 04
Adds niche-specific verification flags (e.g
Adds niche-specific verification flags (e.g., for a therapy practice: local-services-ads eligibility, business-profile rules for virtual practices, health-privacy considerations on tracking).
- 05
Creates the doc directly in
Creates the doc directly in the client's shared-drive folder (never in a personal drive where the team can't move it).
- 06
Outcome
a call-ready kickoff doc; discovery notes are folded in on request from CRM call records.
Evidence from the workflow.
Each system has a role.
Intake (verified facts)
CRM
Record of truth / action
Shared drive (docs)
Intake / signal
Team chat
Why this is Coworker.
Takes assignments and reports back. You hand it work, it prepares and returns a result.
Only CRM-verified facts enter as facts; everything inferred is marked for human confirmation.
Effects / Outcomes
KO docs went from an hours-long manual chore to a minutes-long automated build in the right folder.
Every doc follows the same canonical outline — consistency across account managers.
Verified-fact discipline is structural: inferred values are visibly flagged for confirmation, so bad data can't silently become "fact" on a kickoff call.
Find where a workflow like this fits.
Start with the systems, work, constraints, and authority already present in your operation.