ClientE-MusicMaestro

What I did for E-MusicMaestro

Over roughly two years I worked across the E-MusicMaestro platform - a subscription site serving music academies and individual students with aural test practice (ABRSM, Trinity), sight-reading material, and a books shop. The codebase already had momentum and a committed owner; my job was to land features and fix the harder pieces he didn't have time to dig into himself.

Notable areas of work:

• Aural test administration and randomisation - opened up the higher-grade ABRSM admin pages and rewrote the Trinity test randomisation logic to use a per-user "last played" tracker, so students cycled through the full bank before any repeats.
• Student statistics dashboards - added per-student usage stats (last login, aural-test packages, recent question counts) for academy administrators managing large student rosters. Optimised the page so the detail table loaded on demand rather than blocking the initial render.
• WorldPay payment integration - hardened the WorldPay callbacks so subscription activations completed reliably, and resolved an authentication issue between the site and WorldPay so order-detail emails generated correctly for book purchases.
• Order emails and admin view - built out the order-detail email pipeline so confirmation emails carried full itemised line items, and added an admin transactions view so purchases could be audited without database access.
• General maintenance - kept sight-reading subscription access working, handled contact-form deliverability through a Mailgun migration, and added a "check the live site after deploy" step to the workflow.

How it helped

E-MusicMaestro is the work of a dedicated independent developer who built and runs the product himself, so he already had clear instincts about what the site needed; the work I took on was the kind that needs focused dev time rather than ongoing brand or content attention. Each engagement was scoped tight (2-3 hour blocks for individual pieces; small project commitments for the bigger features) and he could trust I'd diagnose properly before touching anything.

Payment integration in particular needed a careful hand - WorldPay's callback model is unforgiving, and getting it solid protected subscription revenue. The pattern I built up helped him see which signals to watch and which logs to read if a payment question came up.

How I would describe working together

This was a genuine collaboration with a developer who is deeply invested in his own project, and I valued that. There's a particular energy to working alongside someone maintaining something they care about that much, and I learned a lot from the processes and the enthusiasm behind it. Communication was over email and Slack, scoping was honest on both sides, and I could deliver on the smaller pieces quickly because I already knew the codebase from the bigger ones.