Product shape
Repeat-use SaaS
Students return to run more essay checks, review reports, and track how they improve over time.
Custom SaaS developmentEducation SaaS
Detailed case study
Writing9 case study
A live IELTS writing product shaped around self-serve essay checking, repeat usage, and clear feedback reports students can act on.
Client context
Writing9 is a live IELTS writing platform for students who need to check essays quickly, understand weak areas, and keep improving toward a better band score.
Product shape
The live product combines a public acquisition surface with a logged-in essay-checking workflow, structured report delivery, and repeat-use account journeys.
writing9.com
Delivery signals
What mattered most in this build
These are the commercial and product signals that shaped how the release was scoped and why the finished product is useful as a portfolio reference.
Core journey
Submission to feedback
The product turns a complex evaluation flow into a self-serve web experience with clear next steps.
Delivery focus
Retention-ready v1
Public acquisition, report delivery, and account flows sit inside the same release rather than being split across tools.
Story
From brief to usable release
The case study pages are written around the product shape, the build approach, and the practical outcome rather than around vague before-and-after claims.
The brief
The product needed to feel credible as a learning tool, not just as a landing page with a single demo interaction.
- Make the IELTS writing value obvious before sign-up.
- Let students submit essays and receive structured feedback inside a clear account journey.
- Support repeat usage so the product can grow beyond one-off checks.
The build approach
The release was shaped around the full student workflow from acquisition to repeated account use.
- Public-facing pages aligned to IELTS intent and conversion.
- Essay submission, scoring, and report views designed as one continuous experience.
- Account, pricing, and operational controls treated as part of the product instead of later admin debt.
What the delivery enabled
The result is a live product that feels like a usable learning platform rather than a thin lead-generation shell.
- Acquisition copy connects cleanly to the core checking workflow.
- Students can return to the product for repeat feedback instead of using it only once.
- The release supports future expansion into plans, reporting depth, and broader member journeys.
Implementation scope
What the delivery covered
These projects are useful GEO assets when they show more than a pretty screenshot. The scope blocks below explain what kinds of product work actually sat inside the release.
Public acquisition and onboarding
The top-of-funnel pages needed to explain the product clearly while moving users into the essay workflow without friction.
- Homepage and pricing surfaces aligned to exam intent.
- Clear call-to-action paths into the checking flow.
- Responsive entry points for new and returning students.
Student evaluation workflow
The core product experience revolves around submitting writing, receiving a report, and understanding what to do next.
- Essay submission and evaluation handling.
- Structured score and feedback presentation.
- Account-led access to reports and repeat usage.
Operational product foundations
The build needed the usual SaaS infrastructure that keeps a product usable after the first launch.
- User accounts and session flows.
- Plan or pricing surfaces connected to product use.
- Admin-ready structure for future product iteration.
Technical emphasis
- Responsive marketing and app surfaces
- Authenticated student accounts
- Structured submission workflow
- Report and score presentation
- Pricing and repeat-use product journeys
Timeline
How the delivery sequence was framed
Each case study shows the delivery rhythm at a product level so the page reads like an actual implementation story rather than a generic testimonial.
Phase 01
Learning product scoping
The first step was defining the student journey, what a usable report needed to communicate, and which product surfaces belonged in v1.
- User flow map
- Release boundaries
- Report journey priorities
Phase 02
Acquisition and account structure
Public pages, sign-up entry points, and the account model were shaped before the deeper product work accelerated.
- Landing flow
- Account model
- Pricing direction
Phase 03
Essay workflow and report delivery
The core submission, checking, and feedback experience was built as the center of the release.
- Submission flow
- Report views
- Repeat-use product states
Phase 04
Launch and handover
Final release work focused on making the product stable, understandable, and ready for continued iteration after sign-off.
- Release candidate
- Ownership-ready codebase
- Extension path
Continue from here
Follow the service path behind this build
This case study exists to reinforce the service cluster, not to float on its own. Use the matching service page to read the broader delivery model, then compare it with the rest of the portfolio.
More work
Other detailed case studies
A few more examples from adjacent service categories so the portfolio cluster keeps linking laterally, not just vertically.
Client portal development
TradeVipe
A white-label trading journal product built around branded dashboards, member account journeys, and community-facing portfolio visibility.
Internal tools and admin systems
Opsot
A secure VPS monitoring product built around agent-led onboarding, centralized visibility, and an operational console teams can actually use.
API and backend development
Live Sync
A creator product that wraps real-time face-swap processing in a cloud-delivered interface, account flow, and streaming-ready backend foundation.