← All work

Education · Full-stack platform / Case study

Numeracy Coach

From public website to the systems behind every lesson.

Python & FastAPIPostgreSQLPlatform engineering
Numeracy Coach’s rebuilt homepage featuring its educator-led identity, specialist mathematics positioning and founder portrait
The rebuilt Numeracy Coach website, captured from the live public site in October 2026.

A platform for an educator-led business

Numeracy Coach is an educator-led mathematics tutoring business. Its technology needs extend from helping a family find the right specialist to managing the records, payments and communication behind each lesson.

I rebuilt the public website and developed the supporting business platform: an integrated set of purpose-built services for enquiries, educator recruitment, administration, session operations and finance. Alongside those live systems, I built controlled workspaces for developing and reviewing learning tools.

The challenge: connect the whole operation

The earlier implementation used Google Workspace and Apps Script to connect recurring administrative tasks. As the scope expanded, the next step required a more structured backend, clearer ownership of business records and interfaces suited to different users.

The challenge was to make those pieces work together without confusing a website enquiry with an enrolled student, a payment notification with a confirmed receipt, or an AI-generated draft with work an educator has approved.

A new public website and intake journey

The rebuilt site presents the business through its educators, teaching approach and subject expertise. A responsive editorial design brings together mathematics subject pages, service information, leadership profiles, recruitment, educational resources and clear enquiry paths.

The implementation uses Python, FastAPI and server-rendered templates, with lightweight JavaScript where it improves the experience. The migration retained useful articles and assets, mapped legacy URLs and included search metadata, a sitemap and consent-based measurement.

Family enquiries and teacher applications lead into staff review workflows. Administrators can review submissions, track status, record notes and follow up through the existing Admin environment. Applicant documents use private storage, access checks and malware scanning. A content editor supports routine website updates without a code release.

A custom operations and finance backend

The operational platform uses Python services and PostgreSQL business records, with SQLAlchemy models and versioned database migrations. Its scope includes:

  • People and services: student and tutor records, onboarding, enrolments, billing relationships and explicit permissions.
  • Session operations: provider-event intake, session and participant matching, calendar reconciliation and exception review.
  • Billing and payments: invoices, PrePay and Direct Pay workflows, payment recognition, allocation and account history.
  • Tutor earnings: commission obligations, receipt allocation, payout preparation and eligible referral-bonus handling.
  • Communication: AI-assisted session-note workflows, audience-specific information and traceable delivery.
  • Staff visibility: a Finance dashboard, account workspaces, review queues and operational reporting.

The financial workflows separate recognition, confirmation, allocation and settlement. Matching a notification does not silently authorize a financial posting. Retries, reversals and audit history are part of the design rather than afterthoughts added around it.

Learning tools, with a clear release boundary

Tutor, Student and Parent workspaces have been implemented as a controlled internal capability. Approved administrators can inspect role-specific, read-only views or exercise learning workflows in an isolated simulation.

The learning workflow includes assignment drafts and versions, reviewed publication, protected files, student submission attempts, private tutor review, explicitly released feedback and revisions. Role and relationship checks determine what each person can see; household membership alone does not grant educational or financial access.

These workspaces are not presented here as a broadly launched family portal. External account access remains unreleased in the documentation reviewed, and further learner-intelligence work remains under evaluation. Generated suggestions stay separate from educator-approved assignments and feedback.

Delivery that respects the running business

The work included automated regression testing, isolated database and file-scanning checks, responsive browser review, documented releases and rollback planning. Public website, intake, operational finance and learning-preview services retain distinct data and permission boundaries.

The result is a public-facing experience and operational foundation built around the business, with a deliberate path for introducing new learning capabilities.

The connected picture

One business. Distinct systems.

01 / LIVE PUBLIC WEBSITE

Discover & enquire

Subject expertise, family enquiries and educator applications.

Staff-reviewed intake ↓
02 / OPERATIONS BACKEND

Run the business

People, services, sessions, finance and communication workflows.

Explicit records & permissions
03 / CONTROLLED INTERNAL WORKSPACE

Develop the learning tools

Role previews and isolated assignment, submission and feedback simulations.

Educator review before release

Simplified scope overview. Services retain separate data and access boundaries; the learning workspace is not a broadly released family portal.

Next project

Thriving Fries

A good place to start

What could work
better in your business?

Let’s figure it out