How it works
From pipeline opportunity to delivered project.
A straightforward process built around the way MSPs and agencies actually sell work.
The process
A typical project engagement
You spot an opportunity
A client asks about Azure migration, wants a CI/CD pipeline, or is asking "can you do anything with AI?" You know there's a deal here - you just need the delivery capability.
Brief us (15 minutes)
Send us a brief or jump on a quick call. Client context, what they're trying to achieve, any constraints. We'll ask the right questions to scope it properly.
We scope and price it (48 hours)
You'll receive a fixed-scope, fixed-price proposal you can put in front of the client. Add your margin, present as your own quote. No attribution to us unless you want it.
Client signs, we start
Once the SOW is executed, we kick off with a delivery plan and milestone schedule. You always know what's being built and when.
Asynchronous build and delivery
We do the engineering work outside your business hours where possible, structured around milestones. No disrupting your daily client management.
Handover and documentation
Final deliverable includes documentation your team can use to support the solution. We're available for a structured handover call if needed.
What makes a good engagement
We work best when the brief is clear.
You don't need to know exactly what needs to be built - that's what the scoping conversation is for. But the more context you can give us, the faster and more accurate the proposal.
Client context
Industry, size, current environment. On-prem, hybrid, cloud-native? What do they have today, what are they moving to?
The outcome they're buying
Not the technical spec - the outcome. "They want to stop managing their own servers" or "they need their developers to deploy faster" gives us more to work with than a list of technologies.
Timeline and constraints
Hard deadlines, budget ceiling, any existing infrastructure we need to work with. Regulatory requirements (IRAP, ISO 27001, healthcare) are important to flag early.
How you want to present it
Do you want to handle all client communication and present us as internal? Do you want us on a scoping call? No right answer - we adapt to what works for your relationship.
The Engineering Reserve retainer
Some MSPs want guaranteed capacity rather than a project-by-project engagement. The Engineering Reserve is a monthly block of senior engineering time - pre-paid, pre-allocated, available when you need it.
It works like insurance for the technical questions your team can't answer. Architectural review before a client meeting, a Tier-3 escalation on a complex Azure issue, a quick Bicep template review - the retainer covers it.
Pre-agreed capacity
A fixed monthly block of hours means you don't have to re-engage us every time something comes up. We're already on-standby.
Faster response
24–48hr SLA compared to standard project enquiry turnaround. Good for Tier-3 escalations and architectural reviews that need a quick answer.
Use-it-or-lose-it
Unused hours don't roll over. This keeps the arrangement simple and protects your planning - you know what you're paying, we know what to be ready for.
Got something in your pipeline?
Tell us about it. We'll be straight with you about whether there's a fit.