Skip to content
Senior web & app development · 20 capabilities
oakstone.digital
Case study / Fieldnote Learning

Making expertise easier to access.

A membership platform turned a dense course catalogue into a confident, guided experience.

Industry
Education
Duration
13 weeks
Division
Websites & Commerce
Year
2025
Fieldnote Learning — education web development project by Oakstone
Websites & Commerce / delivered
2.1×
enrolment conversion rate
−46%
billing support tickets
180
courses restructured
The challenge

Fieldnote had 180 courses and a catalogue page that listed all of them alphabetically. Prospective learners could not tell which course suited their experience level, and the enrolment flow lost roughly two thirds of the people who started it.

Billing was handled by three separate tools, and pausing a membership required a support ticket.

The move

We modelled courses as structured content with level, duration, outcome and prerequisite fields, which made genuine comparison and guided pathways possible for the first time.

Entitlements were rebuilt around a single billing provider with proration, pauses and grace periods defined as explicit rules. The enrolment journey became saveable and resumable across devices.

The result

Enrolment rate from course page to paid membership more than doubled, driven mostly by resumable applications and clearer level guidance.

Support load dropped noticeably once members could pause, upgrade and update payment details themselves.

Stack
Next.jsStripe BillingPostgreSQLMuxResendVercel
Team

One product lead, one designer, two engineers

Constraints
  • 180 courses had to migrate without breaking existing enrolments
  • Three billing tools consolidating into one mid-term
  • Accessibility to WCAG 2.2 AA across the learner journey
What we would do differently

Modelling courses as structured content was the decision that made everything else possible, and we should have insisted on it in week one instead of accepting the existing freeform pages for the first sprint.

Mid-term billing consolidation is genuinely risky. Running both providers in parallel for one cycle cost a little more and removed almost all of the risk.

A better brief starts here

Your next proof point is waiting.

Bring us the hard thing. We will bring a point of view, a senior team and a clear next step.

Start a conversation