This case study is password-protected. Please enter the password to continue.
The Challenge
AuthFlow is how schools authorise third-party apps to access their MIS data. Every partner needed to complete this flow before our products could connect — making it a critical gateway to adoption. The existing journey claimed 3 steps but actually required 6 separate screens, with content before and after the stepper that wasn’t tracked. Schools were dropping off mid-setup, raising support tickets, and falling back to manual onboarding because the self-install path felt too uncertain.
The knock-on effect was significant: failed self-installs meant the support team had to walk each partner through setup manually, costing the business an estimated £45,000 per year in onboarding overhead alone. This wasn’t just a UX problem — it was a revenue bottleneck that needed a fast solution.
The Redesign
The new design consolidates the entire journey into a single modal wizard with a persistent sidebar stepper. Every screen is accounted for.
| Old | New | |
|---|---|---|
| Steps shown | 3 (but 6 screens) | 4 (all inside one wizard) |
| Transitions | Full page reloads | Single modal, no reloads |
| Progress | Missing before & after stepper | Sidebar visible on every screen |
| Install step | Untracked, after stepper ended | Step 4, fully integrated |
| Legal consent | Toggle switches (wrong pattern) | Checkboxes (correct pattern) |
| Booking | Inline calendar, cut off on scroll | Modal overlay, centred calendar |
| Support | None | “Having Trouble?” always visible |
| Branding | Generic, inconsistent | App-specific at every step |
Try It
Walk through the authorisation journey — from data selection to install.
Metrics
200%
Increase in partner self-onboarding
-60%
Reduction in support tickets
0
Manual onboarding fallbacks
“Partners are completing authorisation on their own now — we’re not walking them through it anymore.”
Get in touch