AI-powered study planner for competitive-exam aspirants.
A mobile-first study planner that adapts to each aspirant — built on Flutter for cross-platform reach, with a Frappe backend that lets the founder iterate on content and structure without redeploying the app for every change.
What the founder came to us with.
Competitive-exam preparation is intense, personal, and almost entirely mobile. Off-the-shelf coaching content doesn't adapt — every aspirant gets the same pace, the same revision schedule, the same diagnostic — and the founders running the next generation of study products know exactly how blunt that feels to a serious candidate.
The founder needed two things at the same time: a mobile-first product that worked on day one across iOS and Android, and a backend that let a non-engineering content team push new tracks, syllabi, and tests without an engineering ticket per change.
How we built it.
We chose Flutter as the mobile platform — one codebase, two stores, a sane release process for a small team, and a UI toolkit that doesn't fight us on dense educational layouts. iOS and Android shipped together.
Frappe Framework on the backend gives the founder real CMS-like power for structuring exam content, study tracks, and adaptive logic — the content team works in a UI, not in JSON checked into Git.
The adaptive layer is small but real: the planner reads where the aspirant is in the syllabus, what they struggled with this week, and what's coming up in the live calendar, and produces a plan that changes when reality changes. AI here is doing scheduling, not magic.
We invested early in the boring parts of mobile — analytics, crash reporting, deep links, push, version-gating — so the founder can ship weekly without breaking users on older OS releases or older app versions.
What shipped, and what it means.
The platform launched on both stores with a content backend the team can actually run. The founder can now run real product experiments — adapting plans, content order, revision cadence — against real users, and iterate on the loop that decides whether the product wins or doesn't.
More fundamental: an architecture that lets the small team feel large. Content updates ship without app releases. The Flutter app handles the experience layer. The backend is one Frappe install. There's no microservice tax.
Engagement facts.
The shape of this engagement, summarised. Items marked TBC are still being confirmed and will be filled in once the founder has approved disclosure.
What it was built on.
Boring choices for the load-bearing parts; the inventive choices live where they earn their keep.
Pillars and engagements that pair with this one.
If this engagement resonates, these are the next places to look — the underlying service pillars and another engagement that ran a similar play.
Product Engineering
Ship MVPs and production systems that don't need a rewrite at series A.
Read more →Data & Analytics
Decisions from data, AI where it earns its keep.
Read more →AI travel itinerary builder
AI grounded in real inventory — same playbook, different sector.
Read story →Got a similar problem? Tell us where you are.
A 30-minute call. We listen, we ask, we tell you whether the play we ran here would work for you — or whether you need something else first.
Book a discovery call