Case study 02 · EdTech · Wall Street English

Reviving a dead app: from 5 to 2,000+ paid subscriptions in 6 months

Repositioning a failing standalone EdTech app into a core product feature, driving 2,000+ paid subscriptions through UX strategy and ecosystem integration.

Speak+ cover
Speak+, now inside Core
5 paid subscriptions. then 2,000+ :)
ClientWall Street English · Speak+
IndustryEdTech
RoleProduct Designer (sole designer)
PlatformWeb & mobile
Timeline2 + 5 months
(01) Snapshot

Snapshot

Speak+ was a standalone English-speaking-practice app that had stalled at 5 paid subscriptions: decent downloads, almost no conversion. Rather than pour budget into acquiring new users, I repositioned Speak+ as a feature inside Wall Street English's trusted Core Course ecosystem, redesigning its positioning, onboarding and in-app promotion. In six months, paid subscriptions grew from 5 to 2,000+.

5 → 2,000+paid subscriptions in six months
15+countries on the platform
1designer: me
(02) The problem

The problem

Wall Street English is a global English-learning company built on structured courses and speaking practice with real teachers. Speak+ began as a separate B2C app: unlimited small-group speaking classes on a monthly subscription. On paper it worked. In practice it was dying.

PROBLEM 01Unclear value

As a standalone product, Speak+ sat outside any structured learning journey, so new users couldn't see why it mattered.

PROBLEM 02Weak onboarding, dated UI

Little to build trust meant free trials rarely converted.

PROBLEM 03Flatlined at 5

Paid subscriptions simply stopped moving.

a strong feature, trapped in the wrong container: a standalone app.

(03) Goals

What success meant

Business
  • Grow paid Speak+ subscriptions by integrating it into the ecosystem, not acquiring users externally
  • Extend recurring revenue by keeping students engaged beyond course completion
  • Reduce dependency on costly external B2C acquisition
Users
  • Give advanced learners a clear way to keep improving after structured courses
  • Make Speak+'s value obvious within the learning journey
  • Offer flexible, unlimited practice tied to real-life communication
(04) Understanding the users

Understanding the users

The people most likely to convert were already inside the ecosystem: existing Core Course students, a warm and trusting audience who simply weren't upgrading.

Satisfaction surveysAsked learners what they valued and where Speak+ fit (or didn't) in their week.
In-app behaviour analysisLooked at where students dropped off and where upgrade prompts were ignored.
Teacher signalTeachers were already recommending Speak+, and it still saw almost no adoption.
Who I designed for
CCore Course student

Already paying for a structured course; doesn't want to pay twice for practice.

AAdvanced learner

Finishing levels and looking for a way to keep speaking regularly.

AAlumni

Completed the course; at risk of drifting away without a reason to return.

The key insight

The barrier was never awareness or trust. Speak+ was built and priced as a separate product stacked on a course students had already paid for. It wasn't an acquisition gap. It was positioning, placement and pricing.

(05) The question

Asking the right question

Before designing anything I ran qualitative and quantitative research (satisfaction surveys and in-app behaviour analysis) around four questions:

Why weren’t existing Core students upgrading to Speak+?
What actually motivates advanced learners to keep practicing?
What barriers stopped users from paying for speaking practice?
How do trust and structured learning shape a subscription decision?
(06) Design principles

Design principles

01SeamlessIntegrated, not intrusive. Speak+ should feel like a continuation, not an upsell.
02ValuablePractice with purpose. Frame it as an essential fluency builder.
03Trust-ledPromote without pressure. Contextual education, not aggressive upselling.
04ScalableDesigned for growth. Reusable promotion surfaces and flexible entry points.
(07) The solution

The solution

We repositioned Speak+ from a standalone app into a speaking-practice feature embedded directly inside the Core Course experience. Three moves carried the work:

APositioning & messagingPractice-first messaging and flows that framed Speak+ as the natural next step for advanced learners and alumni.
BIn-app promotionContextual, milestone-based prompts across the dashboard, onboarding and level results, right when its value was clearest.
CEcosystem integrationEmbedded into existing subscriptions and alumni flows, so upgrading felt like continuing the journey.
In the product
before and after: standalone Speak+ vs Speak+ in Core
(08) Trade-offs

Trade-offs & decisions

the interesting decisions were about restraint, not features.

Standalone brandvsEcosystem integration

Keeping Speak+ separate would preserve its identity; folding it into Core would cost that visibility. I chose integration.

→ faster adoption and revenue, at the cost of a standalone brand.
Deep feature expansionvsRapid growth

I prioritized integration and in-app promotion over new features.

→ significant growth, while feature work waited.
Hard sellvsTrust-based promotion

An aggressive upsell would convert faster short-term. I chose subtle, context-based education.

→ sustainable adoption without damaging trust.
(09) Impact

The impact

5 → 2,000+paid subscriptions in six months
Recurringrevenue stream, instead of a failing standalone product
Both sidesadoption grew among students and teachers
Longer LTVadvanced learners stayed engaged with flexible, unlimited practice
(10) Reflection

Looking back

“A stalling product rarely needs more. It needs to be in the right place, at the right price.”

Speak+ didn't fail because the practice was weak; it failed because it was framed as a separate purchase instead of a continuation of a journey students already trusted. The fix was distribution and positioning, not features. Next time I'd instrument the promotion surfaces from the start, to see which moment (onboarding, a level-up, course completion) actually drove upgrades.

(11) The setup

The setup

RoleProduct Designer (sole designer)
Team1 Product Manager · 1 Product Designer (me) · 3 Developers
Timeline2 months to integrate into the Core app · 5 months to promote and onboard franchises and users
Next case study
Building trust into a two-sided swimming marketplace →
Swimingo cover
Swimingo