WEEK ONE ACTIVATION PLAN

Guide the first week.
Build momentum that lasts.

£12,000 | 10 days.

Schedule a call

The first week sets the tone. Get it right, and people build momentum. Get it wrong, and they quietly drift away.

It’s not always drop-off, it’s drift. New users complete the first step but don’t know what comes next. Staff log in once, then slide back to old ways.

The Week-One Activation Plan brings that critical week 1 together. We design a clear, day-by-day journey across product, comms, and support. So the right actions happen, in the right order, for the right reasons.

The first week sets the tone. Get it right, and people build momentum. Get it wrong, and they quietly drift away.

It’s not always drop-off, it’s drift. New users complete the first step but don’t know what comes next. Staff log in once, then slide back to old ways.

The Week-One Activation Plan brings that critical week 1 together. We design a clear, day-by-day journey across product, comms, and support. So the right actions happen, in the right order, for the right reasons.

Choose this if:

Sign-ups look fine, but 7-day retention is flat
Teams can’t agree if “activation” is product, comms, or training
People complete the first step, then stall
Product, Comms, and Support send mixed signals in week one
It's a critical launch where failure it not an option.

If your first-week journey feels scattered, or invisible, this makes it visible, structured, and shared.

Why trust Alterkind

We don’t just add messages. We design systems that build behaviour.

For product teams: outputs are copy-ready, flow-ready, and built on how people actually progress.
For change programmes: we anticipate confidence dips, resistance points, and the social cues that drive adoption.

One plan. One owner. Measurable progress.

What happens next?

Day 1 | Kick-off & journey map (60 mins)
Walk us through your current first-week journey across product, comms, and support.

Days 2–3 | Behaviour scan
We analyse where momentum fades: where people stall, why, and what’s missing.

Days 4–6 | Draft plan
We design a day-by-day week-one plan: in-product steps plus light out-of-product nudges. Ready-to-use copy, timings, and behavioural rationale included.

Day 7 | Team review (90 mins)
Working session with Product, Comms, Design/UX, and or Ops to refine and align.

Days 8–9 | Final plan
We consolidate feedback and deliver a clear, practical playbook that's ready to run.

Day 10 | Handover (45 mins)
Walkthrough of the plan, how to measure it, and hand-off to the named owner.

We build inside your current tools and journeys. No rip-and-replace. Plans are made of small, testable changes you can ship weekly. Decisions stay tight: one plan, one owner, one cadence.

Compatibility & tooling

We’ve built week-one plans using Braze, Customer.io, Iterable, HubSpot, Salesforce, Intercom, Pendo, Appcues, OneSignal, and internal channels like Slack and Teams.
Using something else? We adapt.

We don’t need admin rights. Viewer access or staged exports are enough. Everything fits your existing brand voice and templates.

Who it’s for

Product managers owning activation or adoption
Change leaders rolling out new systems or ways of working
Comms teams who want nudges that support not distract

What we need from you

A named sponsor and day-to-day lead
Access to current week-one flows and messages
Ability to send in-product or channel prompts (or someone who can)
Legal/Privacy contact if consent or AI is in scope
A Loom, Figma, or doc of your current week-one journey
Basic usage data: sign-ups, log-ins, completions, drop-offs (proxies fine)

What success looks like

One clear week-one plan everyone follows
Day-by-day actions that build confidence, not clutter
Higher retention beyond day seven. Measurable, repeatable, reportable

Logistics

Duration

10 working days.

Scheduling

Usually within 2 to 3 weeks, depending on team availability.

Format

Delivered remotely by default. In-person or hybrid sessions can be arranged. We are a UK based team.

Requirements

A Loom or link showing the first-use flow (or rollout steps), plus three numbers: sign-ups, completions, and drop-offs (proxies are fine).

Your current week-one journey (Loom, Figma, or doc) and basic usage data (or best proxies). If you don't have this, product or rollout strategy is enough.

Roughy 7-8 hours commitment from your team across two weeks: one kick-off, one workshop, one review, plus async feedback.