About
How We Work
No discovery phases that run for six weeks. No proposals that describe what you already told us. Infrastructure work with a clear scope and a clear handover.
The approach
How an engagement actually runs
The first call
45 minutes. We ask about what you're running, what's breaking, and what you're trying to accomplish. You ask about how we work and what we'd actually do. By the end of the call, we should both know whether this is the right fit — and if it's not, we'll say so.
No NDA required for the first call. We don't take notes to repurpose as a sales proposal. We take notes to understand your situation.
Infrastructure audit
Most engagements start with a fixed-scope infrastructure audit (£950). We review your current setup: architecture, tooling, access controls, monitoring, and the parts that haven't been touched in 18 months. The output is a written report — what's working, what's risky, what we'd prioritise.
The audit is useful on its own. You can take it to your own engineers, to another firm, or use it to decide whether to continue with us. We don't treat the audit as a lead-gen step.
Scoped proposal
Based on the audit (or on a well-described situation), we write a scope document: what we'll do, what we won't do, what the deliverable looks like, what we need from your team, and what it costs. One page, not thirty.
We don't start work until the scope is agreed. We don't change scope without discussing it. If something unexpected comes up mid-engagement, we tell you what it is and what it adds — not at the invoice stage.
Build phase
We work in your existing tools — your git repos, your Slack, your ticketing system. You see commits, you see pull requests, you can review what's changing. No black-box delivery where infrastructure appears at the end.
Weekly check-ins during active engagements. If something is taking longer than expected, you know before it affects the timeline. If we find something during the engagement that changes the picture, we tell you as soon as we find it.
Handover
Handover is part of the scope, not an afterthought. We produce documentation that your engineers can actually use: runbooks, architecture diagrams, decision records explaining why things are set up the way they are. A walkthrough call with the relevant members of your team.
After handover, we're available for questions for 30 days. We want the handover to stick — if there's something unclear, we'd rather fix it then than have it become a support ticket six months later.
The team
Engineers, not account managers
NodeFlow Cloud was started in 2023 by engineers who'd spent years building infrastructure for product companies — and noticed that most DevOps agencies communicated through account managers rather than the people doing the work. The firm is built around the opposite.
How we think
A few things we believe about this work
Boring infrastructure is good infrastructure
The goal is a system where nothing interesting happens. Alerts fire only when something actually needs attention. Deploys are routine. The on-call rotation does not feel like a second job.
Documentation is not optional
Infrastructure that only the person who built it understands has a single point of failure. We write documentation that a new engineer can use on their first week, without asking anyone for help.
Complexity should be earned
Kubernetes is the right answer sometimes. So is a single managed database and a simple deployment script. We recommend what fits the actual situation, not what's most impressive to put in a proposal.
Bad news travels fast
If something goes wrong, or is taking longer than expected, or we've found something that changes the scope — you hear about it from us before you hear about it from the system.
Ready to start
Start with a 45-minute call
No slides. No generic questions. Tell us what you're running and we'll tell you what we'd look at first.
Book a call