The team
Chris Evans and Matt Collier lead Node. Both are known in UK hosting and managed services, and both still work on the platform: hardware, identity, the app estate, the AI gateway, billing, the awkward integration that has to go out on a Thursday.
They are not the whole firm. The core in-house team is five engineers and developers. Around that is a standing roster of freelancers and partner development houses we have used for years, which is how we take on a migration, a custom integration or a burst of build without turning into a generalist consultancy.
There is still no account-management layer and no ticket roulette. When you email us, an engineer with access to the systems answers, usually someone who has already touched your tenant. How the company is put together.
Chris Evans
Chris leads the firm with Matt and still builds and runs the platform day to day.
Matt Collier
Matt leads the firm with Chris and still builds and runs the platform day to day.
Engineers, freelancers and partners
The other three of the five are in-house engineers and developers on the same estate: apps, integrations, automation, the unglamorous work that makes a catalogue tenant actually fit a business. We have not put individual bios here yet. That is a gap on this page, not a gap in the team.
When a job is bigger than the core five (a cutover, a custom interface, extra frontend or mobile around a platform app), we bring in people from a roster of freelancers and partner houses we already know. They work on our stack and to our documentation. You are not handed to a stranger with a different way of doing things.
How we work
We answer our own support queue. There is no first line to get past. Questions go to the engineers, and the reply you get is the actual answer, not a holding pattern.
We run what we sell. Our files, CRM, e-signing, automation, email and helpdesk all run on the platform, behind the same single sign-on we give customers. Operating our own business on it is our first and harshest test environment.
We automate the routine and document the rest. A specialist core can run a platform properly only with discipline: everything repeatable is scripted, everything deployed is monitored, and every change is written down. That is also how extra hands can join a job without making a mess.
We say no when the honest answer is no. If an app is not ready for self-serve deployment, we call it managed setup. If a feature is not built yet, we say so. We cannot afford the debt that comes from overpromising.
Want to talk before signing up? Book a meeting. You will get Chris, Matt, or another engineer on the tenant, not a sales queue.