Case study 01 · Flagship · AI product · Growth & iteration
AI Extractor
Helping tutors bring their own content into the platform in minutes instead of the better part of an hour.
- My role
- Product owner: discovery, requirements, customer validation, prioritisation and release coordination
- Built with
- A prompt-engineered backend using Google Gemini, implemented by our engineering team
- Paper trail
- 7 PRDs
North Star
Reduce the time and effort required for tutors to bring their own content into the platform.
01Problem
Getting content in was the bottleneck
Tutors bringing their own content into the platform had to get every question into the live product manually, which took roughly 45 minutes per question.
02Baseline
45 minutes down to 3–5
≈ 89–93% less time per question
03Discovery → redesign
From a rough beta to a first real release
Discovery
The team began by collecting many different PDF structures and talking with customers about the materials they had and what they needed simplified. Customer calls, support tickets, newsletters and direct conversations surfaced the recurring problems.
Beta
I joined when the first version could already output extracted files in a suitable format, but had no polished interface. I didn't assume that first version was right.
Customer validation
I had 5–7 customers use the beta, collected their feedback, identified the problems and made changes.
First release
Those changes went into the first proper release.
UX redesign
The team expanded with a designer, and we redesigned the UI/UX to simplify the extraction workflow.
04Product decisions
What we noticed, and what changed
- Exam expansionStarted with one exam type and expanded to multiple exam types.
- Page selectorUsers were extracting whole PDFs even though only around 80% of the extracted content was ultimately useful. I proposed page selection to cut unnecessary processing and token consumption.
- Exam-type UXUsers were confused by the exam-type choices, so we simplified that part of the UI.
- Completion notificationsUsers reported long waits. The deeper problem was that they believed they had to stay on the loading page, so we added notifications to let them leave and come back when processing finished.
- Background queueingAdded background processing for multiple folders, one after another.
- Intelligence ExtractAdded AI answers/solutions and tagging of questions to the relevant skills and exam domains.
- Landing pageVibe-coded the product landing page at extract.edisonos.com.
- Customer loopSent biweekly newsletters, joined customer calls and reviewed support tickets continuously.
05Scale
From a handful of customers to 50+
When I took over
- customers
- ~5customers
- questions extracted
- 4–5Kquestions extracted
Now
- customers
- 50+customers
- questions extracted
- 80K+questions extracted
- PDFs processed
- 700+PDFs processed
06Quality
Accurate enough to come back to
All observed current customers are repeat users: they keep updating content for new exams and cohorts.
- extraction accuracy
- 98%extraction accuracy
- customer satisfaction
- 4.9/5customer satisfaction
07Learnings
What I took away
A useful AI feature is not just about model capability. The surrounding workflow, user confidence, error handling, history, notifications, and export options can determine whether users actually adopt it.