Days 1–3 · Audit
Churn Signal Audit & Validated Signals
We separate real churn signals from normal product noise. Login drops, feature abandonment, support spikes, failed activation steps, and renewal timing are checked against your own cancellation history. You leave with typically between 3 and 6 validated signals depending on what your data can prove.
- Churn history, usage data, Chameleon data, and support context reviewed together
- Thresholds defined only where your data supports the signal
- Signals with weak evidence flagged instead of turned into fake precision
Days 1–3 · Design
Behavioural Trigger Map
This is the operating map for the whole system: which behaviour fires which flow, who sees it, who is excluded, and when CS should be alerted instead. It prevents the classic Chameleon failure mode where flows exist, but nobody trusts the targeting logic.
- Signal-to-flow mapping for every approved intervention
- Audience rules, exclusions, escalation paths, and fallback behaviour documented before build
- A clear handoff artifact your team can extend after the sprint
Days 4–7 · Build
Live Chameleon Flows with Copy
These are not wireframes that your team has to build later. The flows are written, configured, and deployed inside Chameleon. Most engagements produce between 3 and 6 live interventions depending on your churn signals and account volume.
- Tooltips, modals, banners, or checklists selected based on the user situation
- Copy written for the specific risk signal, not generic re-engagement language
- Flow QA completed against real user states before launch
Days 4–7 · Targeting
Targeting Logic, Frequency Caps & Analytics
At-risk users should not be spammed just because multiple signals fire. The targeting rules define who sees what, how often, in what order, and what success looks like per flow. Your team can inspect the system instead of guessing what Chameleon is doing.
- Audience rules, display conditions, and suppression logic configured inside Chameleon
- Frequency caps to prevent over-messaging at-risk accounts
- Per-flow analytics so weak interventions are visible after launch
Days 8–10 · Documentation
Flow Architecture, Copy Library & Admin Training
Your team gets the logic, copy, and admin steps in a form they can actually use later. If a new churn signal appears next quarter, they are not starting from a blank Chameleon account or reverse-engineering someone else’s setup.
- Flow architecture diagram showing triggers, audiences, exclusions, and escalation paths
- Copy library with every modal, banner, tooltip, checklist, and fallback message
- Admin training so your team knows how to pause, edit, duplicate, and extend flows
Days 9–10 · Optimisation
30-Day Monitoring, Review & Support
The sprint does not end with unmonitored flows sitting in Chameleon. We track early performance, review what moved and what did not, and make one round of optimisation recommendations after the first month of data. Direct support is included while your team takes ownership.
- Performance monitoring focused on the churn signal each flow is meant to change
- Day 30 optimisation review with specific recommendations
- Direct support for questions, handoff, and early implementation issues
