<aside>
📋 Frequency: Trigger-Based | Time: 45 min | Trigger: When a signed contract is received
</aside>
Without a structured intake, you enter your first client meeting without the information you need to run a clean kickoff. The engagement starts reactive — you're diagnosing on the fly instead of confirming a hypothesis — and the client's first impression is disorganization, not expertise.
Prerequisites
- Signed contract received and filed
- Your project management system (Notion, spreadsheet, or equivalent) with a new client record created
- Your intake questionnaire template ready to deploy
Procedure
- Open your project management system and create the client record. Populate all known fields: contact info, engagement type, SOW reference, kickoff date.
- Run the Client Intake Questionnaire Builder skill with the client's industry, engagement type, and primary stated constraint as inputs.
- Send the generated questionnaire to the client with a 48-hour response window. Flag it as a prerequisite for the kickoff meeting.
- Review returned responses before proceeding. If the questionnaire is incomplete, follow up directly — don't move to kickoff prep with gaps.
- Run the Client Onboarding Welcome Sequence skill with the client's name, engagement start date, and primary constraint as inputs.
- Send the welcome sequence. Confirm the kickoff date is locked and aligned with the Engagement Kickoff Prep SOP trigger (3 business days prior).
Expected Outcome
A complete client record in your project system, a sent and returned intake questionnaire, and a welcome sequence delivered — all before the first working session begins.
<aside>
⚠️ Common mistakes:
— Sending a generic intake questionnaire — you get generic answers. Calibrate the questions to the engagement type or you'll spend the first session asking things the questionnaire should have already covered.
— Treating the welcome sequence as optional — it isn't. The gap between signed contract and first session is when buyers experience doubt. A structured welcome sequence holds the relationship during the handoff.
</aside>