Scalebay’s four-layer framework for handing off users to retention 

Most mobile growth teams have a problem sitting between acquisition and retention. It rarely shows up on an org chart, and it often doesn't appear on any single dashboard, but it shows up in the numbers every time.

Say an app spends €100,000 acquiring users. UA reports installs and CAC. Product reports activation. CRM reports opens and clicks. Monetisation reports revenue. Retention reports D30. Everyone has a dashboard, but nobody owns the full customer journey, and the business keeps acquiring users who never become valuable long-term customers.

And that's exactly where Scalebay approaches this differently, treating mobile growth as one connected system spanning user acquisition, ASO, LTV and monetisation, CRM & retention, and data & KPI analysis, with acquisition strategy tied explicitly to LTV rather than just installs alone.

A model like that only works if it can actually run on something, and that's the part Customer.io provides: the engagement infrastructure that turns behavioural data into automated journeys across email, push, in-app, SMS and WhatsApp.

The important part isn't either piece on its own. It's the handoff between them, and most mobile teams get it wrong in the exact same spot: they treat the install itself as the moment retention begins.

The traditional mobile funnel looks like Ad → Install → Onboarding → Retention. But there's a gap hiding inside that last arrow: a user has to actually experience value before retention means anything, and that might take two minutes for one app and several sessions for another.

The real handoff looks more like Acquisition → Attribution → Behaviour → Activation → Engagement → Monetisation → Retention.

That sounds obvious written out on a slide. The hard part is making data actually flow between those stages, which is exactly the gap Scalebay closes for mobile teams. Rather than judging paid acquisition in isolation, its LTV model separates iOS and Android economics by cohort retention to set target CAC and payback, so the question stops being "how cheaply did we acquire this user" and becomes "how valuable is this type of user likely to become."

That second question only matters if you can act on the answer for each individual user, and most teams hit the wall at exactly that point: they know it in aggregate, but have no way to apply it person by person.

It certainly should. Two users acquired through the same campaign can look identical on a spreadsheet and behave completely differently in the app:

User A: Installed from branded search → Opened twice → Completed registration → Viewed premium content → Returned the next day

User B: Installed from broad audience → Opened once → Did not register → Did not return

Same acquisition timestamp, same campaign, same CAC, yet they shouldn't receive the same lifecycle treatment, and in a system built properly, they don't: acquisition data lands in the profile the moment it's captured, behavioural events keep updating it from there, and segments shift right along with it, moving each user automatically into whichever journey actually fits them. That's the logic that Scalebay defines, and Customer.io's segmentation carries out in real time.

But that still leaves the question every team actually struggles with: what's the first thing that should happen after acquisition? The honest answer is that it's never one thing. It's a sequence of handoffs, each one setting up the next.

The first responsibility after acquisition is activation, and what counts looks different by category: a dating app might define it as sending a first message, a fintech app as linking a bank account, a marketplace as a first purchase. The specific event matters less than the principle behind it, that activation should represent real product value rather than a completed checklist item. Scalebay's onboarding and retention audits examine event attributes, segmentation and funnel stages before any lifecycle programme gets built, so the activation event reflects what the product actually needs rather than a generic template. Getting a user to complete that one action is only the start, though, since a single meaningful moment doesn't guarantee they'll ever have a second one.

Activation isn't retention. A meal-planning app might see 80% of users complete onboarding, but only 35% generate a first meal plan, and just 8% stay active after 30 days. The real opportunity usually isn't onboarding at all, it's the gap between first value and repeated use, and closing it means building a journey that reacts to what a user does next instead of running on a calendar. Get someone engaged, though, and a new question shows up just as fast: how do you know when they're actually ready to pay for it?

This is where CRM data and monetisation data usually sit in separate silos, and where showing the same subscription message to two very different users wastes the opportunity: a user who's used one premium feature five times without starting a trial needs a different nudge than one who logs in weekly but has never touched a premium feature at all. Scalebay's pricing, paywall and LTV analysis supplies the commercial read on which user is which; contextual, real-time messaging supplies the delivery. Even the user who converts here isn't the end of the story, because what happens to them next reveals more about the acquisition channel than anything captured at signup.

This is the handoff most teams miss entirely. A campaign on Meta might bring high volume at low CAC with weak D30 retention, while Google brings higher CAC but stronger retention, and Apple Search Ads brings lower volume but the best trial-to-paid conversion. Optimising for CAC alone pushes budget toward Meta. Optimising for LTV, the anchor Scalebay uses for acquisition decisions, can point somewhere completely different.

Four handoffs, and one recurring failure behind all of them: each stage usually belongs to a different team, with its own dashboard and its own definition of success.

• Layer 1 - media and market: channel, campaign, country, platform, creative, keyword, audience
• Layer 2 - product behaviour: install, open, register, search, view, complete, purchase, subscribe, return
• Layer 3 - lifecycle treatment: onboarding, activation, feature adoption, conversion, reactivation, win-back
• Layer 4 - commercial value: CAC, retention, conversion, revenue, LTV, payback

That split ownership is exactly what keeps most organisations stuck, since none of the four teams behind these layers are working from the same picture. What Scalebay does differently is connect them, so a change at Layer 1 shows up as a measurable outcome at Layer 4 instead of getting lost somewhere in between.

Connecting four layers on paper is one thing. Running them as live, automated journeys across every user in real time is another problem entirely, and it's not one Scalebay solves alone.

Customer.io takes the behavioural signals Scalebay defines and turns them into automated engagement for each user. Native mobile SDKs for iOS, Android, React Native, Expo, and Flutter send installs, screen views, and in-app events into the platform as they happen. Identity resolution merges anonymous activity from before registration into the profile created afterward, so a user who skipped sign-up on day one still has a complete history when they return.

The platform connects to the rest of a typical mobile stack. Salesforce and HubSpot can feed in CRM data, reverse ETL brings in first-party data from your data warehouse, and APIs and webhooks cover anything custom. Data also flows back out to analytics tools like Mixpanel and ad platforms like Google Ads, which puts retention and conversion results in front of the acquisition team. Email, push, in-app, SMS, and WhatsApp all read from the same profiles and events, so Scalebay’s four layers reach the user without a separate integration project for every channel.

Scalebay's engagement with Microids on Home Design 3D is a useful example of the model in action. Over 12 months, Scalebay combined ASO, UA and CRM rather than treating acquisition and retention as separate programmes, building the CRM layer in Customer.io: onboarding journeys, a reactivation engine, a free-trial workflow and an in-app rating flow.

The programme delivered more than 500,000 push notifications through lifecycle and broadcast campaigns, with a 20.1% open rate on the in-app rating flow. But the results that actually matter sit downstream: average sessions per user rose from 2.9 to 5.6, a 90% increase; trial starts rose from roughly 6.7% to 9.7%, a 45% increase; and account creation rose from 47% to 64%.

The success here wasn't "500,000 push notifications got sent". It was that the CRM system became an owned engagement channel connected to real user progression and commercial intent, which is what the handoff looks like when it's working. None of it happens, though, if the team running CRM never talks to the team running acquisition, and that disconnect usually starts with something simple: nobody ever agreed on who's responsible for what.

Here's how it should split: UA owns acquisition efficiency, channel performance and CAC; ASO owns store conversion and organic acquisition; CRM owns lifecycle orchestration, segmentation and testing; product owns activation and feature adoption; monetisation owns trials, subscriptions and churn; growth leadership owns LTV, payback and overall profitability.

Each of these functions can run well in isolation and still add up to a broken system, because none of them individually owns the full customer journey. That's the real role Scalebay plays: giving every one of these teams a shared customer model instead of five separate ones. Without that shared model, the same handful of failure patterns show up again and again: sending identical onboarding to every user regardless of source, judging CRM by opens and clicks instead of downstream revenue, tracking dozens of events with no clear purpose, keeping UA and CRM data in separate systems, and treating lifecycle work as a one-time project instead of an ongoing practice.

Naming what goes wrong is the easy part. Turning that into something repeatable is harder, and it comes down to six steps.

1. Define your value event: the action that predicts long-term retention, not just onboarding completion.
2. Connect acquisition data: know where each user came from and what you paid to acquire them.
3. Implement behavioural tracking: the events that indicate activation, engagement, monetisation and churn.
4. Build lifecycle segments: meaningful behavioural audiences, not just demographic ones.
5. Automate journeys: use Customer.io to move users between onboarding, activation, monetisation, retention and win-back automatically as behaviour changes.
6. Feed retention back into LTV and acquisition: compare cohorts by channel, country, platform and campaign, and let that reshape the next round of media spend.

This is where the system becomes self-improving. Scalebay brings the acquisition strategy, mobile growth expertise and commercial analysis; Customer.io provides the lifecycle orchestration underneath it; the customer journey is what connects the two. A self-improving system is only worth building because of what it improves, and that brings the whole framework back to one number.

The acquisition-to-retention handoff gets talked about as a CRM problem. It's really a unit economics problem. Improving CAC by 10% on a €500,000 acquisition budget saves €50,000. Improving retention by 10% can lift the value of the entire acquired cohort. Increasing sessions per user by 20% can move both retention and monetisation at once. That's why CRM needs to sit much closer to the growth model than it usually does, which is the position Scalebay's approach takes by design, connecting acquisition, ASO, LTV, retention and analytics around the commercial value of the user rather than treating installs as the end goal.

The acquisition-to-retention handoff gets talked about as a CRM problem. It's really a unit economics problem, and the numbers make the case on their own. Improving CAC by 10% on a €500,000 acquisition budget saves €50,000, a real number, but a small one next to what's possible downstream: improving retention by 10% can lift the value of the entire acquired cohort, and increasing sessions per user by 20% can move both retention and monetisation at once. Efficiency at the top of the funnel is worth chasing, but the bigger gains sit further down, which is exactly why CRM needs to sit much closer to the growth model than it usually does. That's the position Scalebay's approach takes by design, connecting acquisition, ASO, LTV, retention and analytics around the commercial value of the user rather than treating installs as the end goal.

Put into practice, that design becomes a continuous loop: acquire better users, understand their behaviour, guide them toward value, personalise the next action, convert more of the right users, retain them longer, measure their LTV, and use those results to improve the next round of acquisition.

That loop, not any single tactic inside it, is the handoff most mobile teams are actually missing. It was never a transfer from one team to another. It's one connected growth system, with Scalebay designing it and Customer.io running it.