Tools · onboarding
New client kickoff packet assembler
Assemble once; everyone opens one doc.
What's stuck?
Type A
AI already sitting in the source tool
Fits when: most of the truth for “pull kickoff answers into a single shared packet” lives in one place.
Skip if: inputs live in four places that do not agree.
Type B
A connector that builds the pack
Fits when: the hour goes to assembly, not judgment.
Skip if: nobody will keep the connections alive.
Type C
A writing or structuring layer on finished inputs
Fits when: inputs exist; the hour is the first draft.
Skip if: inputs are still screenshots.
Say the stuck step out loud
If you cannot finish this sentence, pause buying: pull kickoff answers into a single shared packet.
Start with a map, not another tab.
For / Not for
For
- Kickoff lives in five threads and a forgotten form
- You can point at last week’s version of this work
- A human still owns judgment, exceptions, and the send button
Not for
- You do not have a kickoff questionnaire yet
- You have not named an owner for the workflow
- You want a ranking list more than a Tuesday that ends on time
- The current process is unclear to you
- You are shopping to avoid naming an owner
- You already have AI in a paid tool and never pointed it at: pull kickoff answers into a single shared packet
- The pitch is a ranking list
- Someone wants you to rip out a working habit for a platform you will not administer
This week plan
How to choose
- What is the output? Buy for the artifact you already send, not the demo.
- Where does truth live? If systems disagree, AI will disagree louder. Name the source of truth first.
- What should a human still do? Keep judgment; automate gather and first draft.
- Will this run if you are out Thursday? If no, you bought a personal helper, not a workflow.
Named stuck step: pull kickoff answers into a single shared packet.