Systems
LiveIn development
A student recruitment and education operations platform: one student record behind many applications, a 140-university course catalogue, evidence documents, GDPR consent signing, and agent onboarding and commission — across three operational roles.
- Backend modules
- 24
- Page components
- 89
- Automated tests
- 1,879
- Universities
- 140
Source: Repository and live-system audit, September 2026.
Architecture, from the case study 
A multi-branch retail operations platform: storefront, point of sale, branch inventory, attendance, commission and payroll, on one codebase and one database.
- API route handlers
- 210
- Page routes
- 72
- Database models
- 64
- Automated test files
- 146
Source: Repository and deployment audit of the live system, September 2026.
Architecture, from the case study 
A full-stack e-learning platform: course discovery, checkout, enrolment, secure lesson delivery, learner progress, quizzes, certification and public certificate verification.
- Domain modules
- 11
- Admin resources
- 12
- Database migrations
- 41
- Automated tests
- 547
Source: Repository audit of the source monorepo, September 2026.
Architecture, from the case study 
A CRM for a property and investment business: public enquiries triaged into contacts, opportunities tracked through their own approved stage sequence for each of four investment routes, and every read and write decided by the database.
- Database tables
- 38
- Row-level policies
- 92
- Permissions
- 49
- Roles
- 6
Source: Repository audit of the CRM source, September 2026.
Architecture, from the case study A case-management platform for a regulated advisory practice: stages, statutory deadlines, tasks, document control and an internal fee ledger.
The operating system for my own software company: public website and internal CRM in one application, from lead through proposal, project, invoice and payment.
AI editorial tooling inside a news publishing platform: the model drafts the excerpt, SEO title and meta description, the editor approves or rewrites them, and the generation endpoint is guarded so it cannot become someone else’s API bill.
Architecture, from the case study A scheduling workflow that turns meeting instructions sent in a team chat into Google Calendar events, with the trigger narrowed and the date handling pinned so that the automation acts only on the messages it should.
Architecture, from the case study