What I can build for you.

Branching scenarios where people make the call and live with it. Built in Storyline, with consequence paths that mirror the real decision.

Self-paced courses that respect the learner's time. Rise for speed, Storyline when the interaction has to be bespoke, WCAG 2.1 AA either way.

The part that decides whether any of it works. Objectives, sequencing, practice and assessment, mapped to what the job actually asks people to do.

Training that holds up when the auditor asks. Scenario-based, evidenced, and traceable back to the regulation it exists to satisfy.

Rehearsal for the conversations that decide revenue. Discovery, objections and pricing practised against realistic buyers before quota is live.

A production workflow with AI inside it, not bolted on. Claude, NotebookLM and ElevenLabs against your source material — half the scripting time.

Conversational practice partners built on your own content. Learners get an interlocutor that pushes back, available at 2am and never bored.

Measurement designed in from the start, so completion isn't the only number you have. Behaviour and outcome tracking, not just xAPI plumbing.

Interface work for learning products and internal tools. Flows, states and edge cases specified properly, not just screens that look right.

Animation that explains a process faster than a paragraph can. Used where a diagram would stall and a talking head would lose the room.

Scripted, shot or generated, then cut for attention rather than completeness. Subtitled and transcript-backed so it survives being watched on mute.

Visual systems for learning products — type, colour, motion and component rules, so a programme still looks like one thing at module forty.

Sites and landing pages built the way this one was — designed, then built in Webflow by the same person, so nothing is lost in the handoff.

What to build, what to retire, and in what order. Usually a shorter list than expected, and usually not the one the request arrived as.

The structure underneath a programme: how tracks relate, what unlocks what, and where a learner goes when they fail. Designed once, before build.

Packaging, testing and deployment into whatever platform you already run. SCORM 1.2, 2004 or xAPI — tested in your LMS, not just on my machine.

Small custom applications where an LMS won't do it — trackers, assessment tools, internal dashboards. Built to be handed over, not rented back.

Legacy courseware brought forward — Flash-era and desktop-only content rebuilt responsive, accessible, and playable on the devices people actually use.