Skip to content

Independent software and systems consultancy

Practical technology for awkward problems.

I build, improve and untangle software, systems and infrastructure when the usual products or suppliers do not quite fit.

Tell me about the problem

Familiar territory

The awkward bits tend to accumulate.

That spreadsheet everyone relies on. The systems that almost join up. The important old application nobody wants to touch.

01

Manual work that has outstayed its welcome

Reduce copying, re-keying and fragile workarounds with a proportionate tool or automation.

02

Information scattered across systems

Connect the useful systems you already have so that people can find and trust what they need.

03

A problem that does not fit a product brochure

Investigate the options, then build, adapt, integrate—or decide that doing less is wiser.

What I do

Useful systems, not a grand transformation programme.

Software is one part of the job. Understanding how people actually work is the other.

01

Bespoke software

Focused internal tools, workflows, reporting and applications for a real job.

02

Existing systems

Thoughtful maintenance, extension and modernisation for systems that still matter.

03

Systems and infrastructure

Practical work across services, servers, data, deployment and integration.

04

Technical consultancy

A clear-headed view when the problem is known but the right next move is not.

Explore the ways I can help

Software and projects

Useful things, released with character.

Code Fandango is also the name behind independently released software and experiments.

Software project

SeaMist

A simple API layer that turns files and directories into a headless CMS.

Read about SeaMist

Explore software and projects

Particular experience

Technology should serve the organisation, not the other way round.

Code Fandango works broadly, with particular familiarity in charities, NGOs and independent schools—organisations where systems tend to grow around real work rather than a neat diagram.

A sensible first step

Start with the problem, not the platform.

You do not need a formal specification, a technology stack or a fully formed plan. An imperfect explanation of what is getting in the way is enough to begin.

Start with an email