TalonInsights
Three clients. Real artefacts.
Three engagements documented properly beats ten described vaguely. Everything below shipped, and everything below can be shown working.
Case study 01 — Manufacturing
David Jackson & Son.
The situation
A Shropshire joinery firm where production was planned on paper and in people's heads, and the website no longer reflected what the business had become. Both needed doing — by someone who would still be there afterwards.
What I built
- A rebuilt website, designed and written from scratch.
- An eight-stage drag-and-drop production scheduler with automatic breach detection, used to plan real jobs on the factory floor.
- A written strategy deck taking the findings to the people who make the decisions.
How it was run
Scoped in writing before a line of code. Delivered in milestones against fixed dates. Handed over with the client owning the domain, the code and the content outright.
Engineering detail
- Eight production stages, drag-and-drop rescheduling, automatic breach detection against stage deadlines.
- Migrated from
localStorageto aSupabasebackend — the plan survives the browser and is shared by everyone. - Sign-in protected by two-factor authentication, so the plan and the customer names behind it stay private.
- Autosave on every change, with one-click backup and restore — nobody loses an afternoon's planning to a closed tab.
- GitHub →
Vercelpipeline: every change reviewable, every change reversible.
The website rebuild — drag to compare
Left: the site the business had. Right: the rebuild — same workshop, told properly. Drag the handle or use arrow keys.
Case study 02 — Automotive
WulfTek Tuning.
The situation
A performance tuning business whose product is invisible until the bonnet opens. A brochure site would have said "trust us"; the business needed the website itself to demonstrate the standard of the work.
What I built
- A Three.js interactive engine-bay renderer — the customer's own engine bay, explorable in the browser.
- Vehicle-registration lookup wired to the renderer, so entering a plate configures the view.
- A fallback chain for when the lookup comes back empty — the page still works when the data doesn't.
Engineering detail
Three.jsscene tuned for mid-range phones — the audience checks sites from the driver's seat.- Registration lookup with a graceful degradation chain: live data → cached → generic model.
- Interactive moment used where it earns its place — the rest of the site stays fast and plain.
Case study 03 — Marketplace / strategy
Alive Network.
The situation
A national entertainment marketplace weighing a turnaround decision — the kind of call that deserves better evidence than opinion.
What I built
- A Monte Carlo turnaround model run over ten million iterations.
- A twenty-two slide strategy deck translating the distribution into decisions the business could actually take.
Engineering detail
- Ten million simulated scenarios — the recommendation ships with a probability distribution, not a single hopeful number.
- Sensitivity analysis showing which assumptions actually move the answer.
- Presented as a decision document, not a data dump: what to do, what it costs, what could go wrong.
Get started
Book a Groundwork Visit — I'll come to you.
No jargon, no pressure, and a written scope you keep whether or not you go ahead. I reply within one working day.