Systems review
A clear view of what is working, what is fragile, and where focused technical effort will make a difference.
For UK independent schools
Technology that gives your school room to think.
Independent software and systems engineering for schools that need their digital estate to work harder, not become another thing to manage.
Tell me what you are trying to fixThe practical bit
Your systems should support the school day, not interrupt it.
When platforms, data and processes do not quite join up, staff carry the burden. The result is duplicated work, fragile workarounds and less time for the people and work that matter.
Code Fandango brings an experienced, independent engineering perspective to the knotty technical work behind the scenes—especially when the problem does not fit neatly into a supplier’s usual offering.
Where I can help
Make the complicated manageable.
Integration and automation
Connect the systems your teams already rely on and reduce repeatable, manual work.
Bespoke software
Purpose-built internal tools and services when an off-the-shelf product does not fit the job.
Technical delivery
Pragmatic engineering support for reporting, legacy applications, Linux, servers and unusual technical projects.
A little reassurance
Familiar with the particular mix of school systems.
Neil has long-standing experience of school IT and the unusual collection of administrative systems, infrastructure and home-grown tools that schools accumulate. In an earlier school role, he developed interconnected web applications for booking, assets, stock, support, network management and remote access as needs emerged.
A sensible first step
How work usually begins.
- 01
Tell me about the slightly unusual problem, including the systems and people around it.
- 02
We establish the practical constraints and whether an investigation or focused project would help.
- 03
If it is not a sensible fit, you will get an honest answer rather than a sales process.
Questions, answered
A few things people reasonably ask.
No. Code Fandango is not trying to replace an MSP or compete for commodity support. It is for the unusual project or problem that needs focused technical work.
Yes. Code Fandango can work alongside internal teams and existing suppliers where roles are clear.
Potentially. Older software is not automatically bad software; the first step is to understand what it does and what needs improving.
Yes. An investigation or bounded improvement is often the most sensible way to begin.
Remote work is the usual starting point. On-site time can be discussed when it is genuinely useful for the work.
Next step
Start with the problem, not the platform.
You do not need a completed specification. A short email explaining the context and constraints is enough to establish whether I can help.
Start with an email