Journey Intake and Scope Lock (Onboarding)

Journey Intake and Scope Lock (Onboarding)

1. 01

   Inventory every journey the client expects to run before quoting a build fee

   List each lifecycle motion by name (welcome, abandoned cart, win-back, renewal nudge) and mark which already exist in the incumbent platform. Scope disputes almost always trace back to a journey nobody wrote down at kickoff.

2. 02

   Map each journey to its trigger source and confirm the event actually fires

   A behavioral trigger is only as reliable as the data event behind it. Pull a sample of real records through the source system and verify the event timestamp exists before promising a nurture sequence built on it.

3. 03

   Count integrations, approval gates, and maintenance owners per journey

   A five-step journey touching a payment tool, a support desk, and a legal review is not the same delivery load as a five-step journey inside one platform. Price the count, not the channel list.

4. 04

   Confirm CRM field ownership and pipeline-stage definitions with the client's sales lead

   Scoring models and sales handoff rules break when marketing and sales disagree on what a qualified lead is. Get the stage names and required fields signed off in writing during intake.

5. 05

   Set the attribution window and reporting baseline before launch

   Record current conversion rates, list sizes, and revenue per channel for the 90 days prior. Without a pre-launch baseline, every later performance claim becomes an argument instead of a measurement.

6. 06

   Classify each planned automation by autonomy level and place human review where it touches client-facing messages

   Goal-driven agents that send, reply, or write to CRM records need a checkpoint before production. Tag anything customer-facing as review-required and document who approves.

7. 07

   Publish a scope document listing journeys in, journeys deferred, and the change-order rate

   State the per-journey rate for additions after sign-off. Deferred items belong in a visible backlog so the next phase has a starting point rather than a renegotiation.