Digital products ·
An online school needs a continuous learner journey
“Build an online school website” can describe several different jobs. One team needs a course storefront and payments; another needs accounts, schedules, assignments and tutor workflows. The useful starting point is the learner's journey from discovering a course to completing it.
Separate discovery from learning
A public website explains the programme, introduces its author and terms, answers doubts and helps a person choose. The learning environment has a different job: grant access to paid content, record progress and connect learners with tutors. They may be one system or two, but the handoff must be clear.
Draw the route: find a course, compare options, pay, gain access, start the first lesson, ask a question and complete the programme. Mark who owns each transition. A list of screens without this route misses the real product.
When a hosted platform is enough
A hosted platform is a sensible choice when its sales and teaching model match yours. Compare real scenarios rather than feature counts: pricing tiers, timed access, feedback, tutor roles, refunds and moving between cohorts. Test them with one of your own courses.
Check who controls the domain, content and learner data, how exports work and what happens if you leave. Speed of setup matters, but dependency and the cost of future changes belong in the same decision.
When to build a site or service
A custom public website can be valuable when the offer, brand and buying journey do not fit a template. It may still pass paid learners into a hosted learning platform. This gives the team control over the course presentation without rebuilding lesson delivery.
A custom learning service makes sense when distinctive teaching rules are central to the product: unusual roles, learning paths or integrations that a ready-made system repeatedly obstructs. Test configuration options before funding a new platform; otherwise infrastructure may consume resources better spent on teaching and support.
Test the payment-to-access handoff
After paying, a learner should know where to go. What if payment succeeds but a notification is delayed? Which account receives the purchase? Who helps if an email does not arrive? A break here feels like a broken promise even when each individual service is healthy.
Run test purchases across different states: new learner, existing account, cancelled payment, repeat payment and cohort transfer. Check the order record, access to the correct lesson and a clear support route, not just a success screen.
Use data to improve learning
Registration totals do not show whether someone could begin. A team may need to see failed access, abandonment at the first lesson or unanswered questions. Choose a small set of events that leads to a responsible action, and explain what data is collected and why.
An elaborate dashboard cannot help a stranded learner if nobody owns the response. Metrics become useful when they change a decision or a support process.
Choose the journey before the platform
For a first release, define one course, one payment route and the path to the first lesson. Walk it as a learner and as support staff. That test will show whether a hosted platform is enough, a separate sales website is needed, or a custom service is justified.
I can help design and build the public website, learner account or integration with a learning platform. The scope follows the learner journey and the school's actual rules rather than a technology label in a quote.
From an idea to a digital product
If the task calls for a service or internal tool, we can define the first complete journey and a path to a working release.