Work
The work starts where the neat diagram stops
These case studies cover delivered systems, ongoing platform work, and product concepts. The categories vary. The job is consistent: understand what is actually happening, then make it clearer, safer, and easier to operate.
Multi-screen build environment, awards in view, and live systems under construction.
The work usually arrives as a screen, a call, a spreadsheet, or a process everybody understands differently. I start by finding the system connecting it.
Delivered and ongoing work
Responsibility carried in live environments
These case studies cover delivered systems and current technology ownership. The detail varies because some work remains confidential. The status does not.
Long-running delivery portfolio
Company and independent delivery portfolio
500+ Websites and Digital Experiences
More than 500 websites and digital experiences delivered through Register Event, Symbiometry and independent freelance work, with approximately 98 per cent of the company portfolio personally designed and built.
Problem
Event websites arrive with fixed dates, changing programmes, several audiences and no tolerance for the registration journey failing when attention peaks. Treating each build as a fresh emergency creates slow delivery, uneven quality and a growing pile of one-off fixes.
Outcome
A repeatable operating model for producing branded event experiences quickly without losing sight of the attendee journey, the platform underneath it or the team responsible for running it.
Live platform delivery
Major international medical congress
World Muscle Society Congress Platform Work
A major international medical congress had registration, communications, programme changes, apps and data moving at once. I connected the EventsAir configuration, attendee journeys, front-end and operational workflows so the delivery team could see and manage the congress as one system.
Problem
A congress is not one journey. Registration, communications, programme changes, apps, data, and live support all move at once. When those parts drift apart, attendees see the gaps and the delivery team inherits the repair work.
Outcome
Registration, communications, and platform touchpoints operated as a more coherent system, giving the delivery team clearer visibility across the attendee journey and the work behind it.
Ongoing engagement
Long-running work outside the events industry
Aviation Business Technology Ownership
An aviation business needed ongoing hands-on technology ownership rather than another disconnected project. I provide the senior technical thread across its systems and decisions through a long-running relationship.
Problem
Operational technology decisions need continuity. Without a senior owner who understands the business as well as the systems, platforms, suppliers and short-term fixes can drift in different directions.
Outcome
The engagement is ongoing, so this account focuses on the shape of the work rather than confidential operational detail or unapproved outcomes.
Delivered front-end work
Constrained enterprise event platform environments
EventsAir Front-End Customisation
Attendees were meeting a constrained enterprise platform at the point where clarity and trust mattered. I used HTML, CSS, Bootstrap, JavaScript and careful DOM work to improve hierarchy, responsiveness and brand coherence without breaking the EventsAir platform underneath it.
Problem
Event platforms often expose just enough front-end access to be dangerous: enough to improve the experience, not enough to rebuild it cleanly. That makes detail work matter.
Outcome
Clearer hierarchy, more responsive layouts, and a more intentional attendee experience inside a platform that was never designed to hand over the whole front end.
Concepts and internal work
Useful thinking, labelled before it pretends to be delivery
These are concept architectures, research and internal strategy. They show how I frame a problem and design a credible operating model, but they are not presented as completed client outcomes.
Concept architecture
Concept design for conference review operations
AI Abstract Management Concept
Concept architecture for an AI-supported abstract review system combining triage, vector search, visible confidence, dashboards, and reviewer oversight.
Problem
Abstract review pipelines are usually held together by inboxes, spreadsheets, volunteer judgement, and rushed categorisation. The challenge is improving the workflow without flattening expert nuance.
Outcome
A prototype-ready blueprint for making abstract review more visible and consistent while keeping expert reviewers responsible for the decision.
Company positioning
Company repositioning and product strategy
Symbiometry Systems-Partner Repositioning
Repositioning Symbiometry as the specialist systems partner for MICE businesses, with one method and three connected delivery toolkits.
Brand system
Symbiometry
Problem
Symbiometry's range had grown wider than its story. EventsAir expertise, workflow automation, and practical AI belonged together, but describing the company as AI-first made one toolkit sound like the whole business.
Outcome
A clearer company story: start with one live event, find where time and margin are leaking, fix the systems underneath delivery, then keep improving the loop.
Ongoing exploration
Ongoing research and interface exploration
Personal AI Assistant and Vox Concepts
Ongoing research into assistant architecture, personal knowledge systems, memory, automation, voice and chat interaction, and orchestration.
Problem
Most assistants still feel like single-turn tools. The harder challenge is building something that understands context, retains useful memory, and fits around the reality of day-to-day work.
Outcome
A growing body of concept work around assistants that behave less like gimmicks and more like inspectable, practical working systems.
If your project does not fit a neat case-study category, that is normal.
Bring me the technical problem, the delivery state and what the organisation needs to be able to do next.