Ask Is the Gift
Ask first. They'll be glad.
The story in one paragraph
Tandem Steps needs 100,000 downloads and 40% of them still active at day 30. The beta says only pairs get there: 46% of paired users stayed active against 18% of solo users. Most walking apps lose people in the first two weeks because they ask you to keep a promise to yourself, and that's easy to break. Our audience (30-55, dependable, quietly guilty about the last app they quit) would happily say yes to a walk with a friend. What stops them is the asking. Accepting an invitation is easy, and sending one feels like imposing. So we flip it. Being asked is a compliment, and asking is a generous thing to do. Ask Is the Gift gives people permission and the words: a plain note, "I'd like to walk with you," sent in one tap. It also tells them something they've never been told, that the person on the other end has probably been hoping you would. A shared streak then turns that one small ask into a promise worth keeping.
Manifesto
Somewhere, someone has been meaning to see you.
They haven't said so. It felt like too much to ask.
You've felt it too. The message you typed and didn't send. The "we should catch up" that stayed a sentence.
Here's what nobody tells you: being asked is lovely.
It means you were the one they thought of.
So ask. Keep it small. Walk with me this week?
No plan. No pace. No score.
Ten minutes, two people, one streak.
You don't keep it for a goal. You keep it for them.
Ask first. They'll be glad.
How it comes to life
Assumption: the invite is a single shareable link that opens straight into pairing, with a pre-written note. If it isn't, fix the flow before spending media; every piece below depends on it.
Assumption: week 1 starts Wed 21 Oct 2026, with a public launch around Mon 14 Dec. Weeks 1-4 are build and pre-launch, so "Tease" is mostly seeding and testing.
Phase 1: Tease (weeks 1-4, to mid-Nov, low spend)
Goal: Prove the idea before the big spend. Test the notes and the invite flow, collect real "I was hoping you'd ask" stories, and build a waitlist of askers.
| Channel | Execution | Role |
|---|
| Beta community (1,200 users) | Ask beta pairs to share the real note that started their pairing, with permission. Collect "I was hoping you'd ask" replies. | Gives us proof and real stories for launch, and fills the beta data gap. |
| Instagram, TikTok, Facebook | Organic "Waiting to Be Asked" teasers: one-line posts spoken as the invitee, "Someone you know is hoping you'll ask." Link to a waitlist. | Plants the idea cheaply. |
| Micro-creators (about 20 across SG/MY, plus a smaller group in JP and AU) | Each posts a real, filmed moment of sending or receiving an ask, in user-style video. No scripts, no app tour. | Gives credible faces to the idea before paid media. |
| Message testing | A/B test three invite notes and three poster lines in small paid bursts. | Picks the winning words by invite-sent rate, not by opinion. |
| Waitlist page | One page, one action: "Choose who you'll ask first." Collect the friend's name, not just the email. | Starts pairing before launch. |
Phase 2: Launch (weeks 5-6, 14 Dec onwards, heaviest spend)
Goal: Reach people at the moment of year-end catch-up and get the first invite sent within days.
| Channel | Execution | Role |
|---|
| Film: "The Unsent Invitation" (30s, 15s and 6s cutdowns) | Ordinary people with a thumb over "send", while someone across the city is plainly hoping it will arrive. Cut to delight. No hugging. Adapted per market by casting, setting and pace. | Carries the emotional idea. Runs on social video, YouTube and Meta. |
| Out-of-home: "Waiting to Be Asked" | Posters speaking as the invitee, always showing two people, each with a QR code that opens the invite flow. Placed at transit stops, school gates and office lifts in Singapore and Kuala Lumpur, with smaller placements in Tokyo and Melbourne. | Reaches people where they pause with a phone in hand. QR means one tap to the invite. |
| Paid social and short video | Two audiences: askers ("Ask first") and the asked ("Someone's hoping you'll ask"). Target friends of existing users through lookalikes and share-link retargeting. | Brings in both halves of every pair. |
| In-app: The Asker's Note | Three plain, translatable notes (e.g. "Walk with me this week?"), then a first screen for the invitee that shows the sender's note, not a tutorial. | The conversion moment, and the product proof of the idea. |
| Creators | Mid-size creators film themselves asking a friend they haven't seen in a while. The friend's real reaction is the content. | Social proof, with real stories. |
| PR and community | A short, honest piece on "the ask we all keep avoiding", with local spokespeople who are not fitness figures. | Earned reach without health claims. |
| App store | Screenshots that lead with the note, not the step count. | Turns the ad's interest into a download. |
Phase 3: Sustain (weeks 7-8, to mid-Jan, moderate spend)
Goal: Keep pairs walking through the January surge and turn the first ask into a habit that goes both ways.
| Channel | Execution | Role |
|---|
| In-app nudges | Day 3: "Say thanks for the ask." Day 7: a prompt to ask a second friend, or send a note back. Streak messages talk about "you two", never rankings. | Retention, and a second pair from every pair. |
| User stories | The best replies ("I was hoping you'd ask") become short posts and ads, with permission. | Cheapest, most credible creative we have. |
| Retargeting | Solo users get a gentle "Who would you ask?" prompt. Not guilt, just permission. | Moves the 18% solo group toward pairing. |
| New-year moment | Instead of "new year, new you," run "Ask someone first this year." Light OOH and social, with the same two-person visuals. | Rides the January surge without resolution tropes. |
| Market tuning | Move spend toward the markets and notes with the best pair-up rate. | Makes the budget accountable to the lead metric. |
Creative direction
Key visual idea: A thumb over "send", and a second person visibly waiting. Every image has two people, or a clear trace of the second. We never show one person alone with an app.
Film and content approach:
- User-style, shot on phones or look-alike cameras, in real homes, streets and offices. Light production, which also suits the budget.
- Quiet and observational. The humour comes from recognition, never from mocking someone for having quit before.
- One moment per film, one emotion: the small surprise of delight.
- Market adaptation is through casting, setting and pace only:
- Singapore and Malaysia: quicker, a little funnier.
- Japan: gentler and slower, letting the ask be quiet and considerate.
- Australia: dry and understated.
Tone of voice:
- Plain words, short sentences. "We", "you and a friend", "walk with".
- Never use "earn", "beat", "crush", "goals", "results", and never mention health, weight or fitness gains.
- No local slang or dialect, as the campaign must travel. Brief translators on the feeling, not the words.
- Warm, never preachy. The invitee is flattered, the inviter is generous, and no one is accused of being out of touch.
Brand codes:
- The note: a plain, handwritten-feeling message as the recurring graphic device.
- Warm natural light, ordinary clothes, normal walking pace.
- A single shared streak number, shown as "ours".
- Nothing from the category: no route maps, orange lines, sweat, leaderboards or medals.
Timeline
| Weeks | Dates (approx.) | Focus |
|---|
| 1-2 | 21 Oct - 3 Nov | Confirm the invite flow. Brief creators. Write and translate the notes. Set up tracking. |
| 3-4 | 4 - 17 Nov | Beta stories, message tests, waitlist, creator seeding. Shoot the films (user-style, 2-3 days per market). |
| 5 | 18 - 24 Nov | Select winning notes and lines. Locked edit, approvals, store assets, OOH production. |
| 6 | 25 Nov - 1 Dec | Soft-launch in Singapore and Malaysia to check pairing flows and support. Fix what breaks. |
| 7 | 2 - 8 Dec | Final tune. Pre-book the heaviest media. |
| 8 | 9 - 15 Dec | Public launch from about 14 Dec, all four markets. |
| Post-launch | mid-Dec - mid-Jan | Launch burst, holiday catch-up moment, then the January surge. |
Note: the brief says 8 weeks from today with launch in mid-to-late December. This timeline therefore puts the public launch at the end of week 8, and the "Launch" and "Sustain" phases above run just past it. If the client wants the full 8 weeks of live activity, the launch date has to move earlier, or the live window has to be treated as weeks 8-14. Please confirm which.
Budget allocation
Assumption: USD 150,000, covering media, creative and influencers, split 60% Singapore and Malaysia, 20% Japan, 20% Australia.
| Item | % | USD | Reasoning |
|---|
| Paid media (social, video, search, app store) | 45% | 67,500 | The main engine. Split for both askers and the asked. |
| Out-of-home (transit, school gates, office lifts) | 12% | 18,000 | Concentrated in Singapore and Kuala Lumpur, with token presence in Tokyo and Melbourne. |
| Creators and influencers | 18% | 27,000 | Real stories matter more than reach. Mix of micro and mid-size. |
| Creative and production | 15% | 22,500 | User-style film in four markets, cutdowns, notes and translation. |
| Testing, measurement and tools | 5% | 7,500 | Attribution, A/B tests, pairing funnel analytics. |
| Contingency | 5% | 7,500 | Reserve for what the tests tell us to scale. |
Market split of the 60/20/20:
- Singapore and Malaysia: $90k, the priority.
- Japan: $30k, with a separate tone and likely a smaller volume.
- Australia: $30k, focused on the pre-resolution and January window.
Phase weighting: about 15% Tease, 60% Launch, 25% Sustain. Hold back at least 10% of media until the first two weeks of data show which note and which market pair up best.
Reasoning: a large share goes to formats that carry the invite (video, OOH with QR codes, creators), not to broad awareness. With a $150k budget, we can't buy reach everywhere, so we buy it where it converts to pairs. The numbers are indicative and need a media plan.
Measuring success
Lead metric: the pair-up rate. At beta rates, about 80% of users need to be paired for 40% active overall.
| Objective | KPI | How measured | Indicative target (estimate) |
|---|
| Pairing | Share of new users who send an invite in week 1 | In-app events | 60%+ |
| Share of invites accepted | In-app events | 65%+ |
| Overall pair-up rate by day 14 | Paired users ÷ all downloads | 60-80%, with 80% the stretch needed for the 40% target |
| Retention | Day-7 active rate | Step logs | 55%+ for paired users |
| Day-30 active (any step logged in the week around day 30) | Step logs, all downloaders | 40% target. Realistic range 25-40%, given published benchmarks. |
| Downloads | Total installs | App stores and attribution | 100,000 target. Planning range 60,000-100,000. |
| Cost per paired user | Media spend ÷ pairs formed | Set after the soft launch |
| Communication | Share who say "walking with a friend" is why they use the app | In-app prompt or short survey | Baseline then improve |
| Creative response | Completion, shares, replies using "I was hoping you'd ask" | Track by market |
Honest caveat: published day-30 averages for fitness apps run from about 3% to 12%, so 40% is a very ambitious target. The 46% beta result came from 1,200 users who may have been self-selected. I'd report the paired and solo rates separately, plus the blended number.
Risks & how we'll handle them
-
The invite flow isn't smooth. If the link doesn't open straight into pairing, the idea collapses at its key moment.
Mitigation: test the flow end to end in week 1-2 and again in the soft launch. Don't release heavy media until the invite takes under a minute and works on iOS and Android.
-
"Someone's waiting for you to ask" lands as guilt. It could read as an accusation of being out of touch, which our audience already feels.
Mitigation: test every line with real pairs. Keep the tone warm and the invitee flattered. Retire any line where testers feel judged.
-
Pairing and retention fall short of the beta. The beta may have been self-selected, and the holiday period is busy, so pairs may form but fade.
Mitigation: track pair-up rate and day-7 retention daily. Shift budget to the best-performing note and market, and run post-launch nudges so the streak survives past the January spike. Agree with the client now that a pairing-led result below 100,000 downloads may still be a success.
Next steps
- Confirm the invite flow. Is it a single link that opens straight into pairing, with the pre-written notes? Test it on both platforms this week.
- Share any beta invite data (how many invites were sent, how fast, and what people said) so we can see if the insight holds.
- Confirm the launch window. Decide whether public launch is about 14 Dec (as scheduled) or earlier, and whether the 8 weeks include the post-launch period.
- Approve the budget split and the notes. Sign off the 60/20/20 split and the three first-draft invite notes for translation into Japanese, Malay and, for Singapore, Mandarin.
- Brief creators and production partners for the beta stories and the four-market user-style shoot, starting with Singapore and Malaysia.