The White-Label Delivery Capability Pack

This pack is for MSPs, software vendors, resellers and consultancies deciding whether to put Systech behind their brand. It covers what we deliver, how the engagement is structured, the terms that protect your client relationship, and how a job runs from first call to handover. It is deliberately specific, because a partner choosing a subcontractor needs terms, not adjectives.

1. Three situations, and they are not the same purchase

2. What we deliver under your brand

Broadly, the service lines we already run for our own clients, delivered by the same engineers with your name on the output.

Hands-on delivery

• Managed IT, with service desk cover by arrangement, depending on the partner
• Microsoft 365 and Azure project work: tenant builds, migrations, SharePoint and Teams structure, security hardening
• Security delivery: managed firewall, EDR and XDR rollout, Conditional Access design, Cyber Essentials preparation
• Backup and recovery design, and restore testing
• Application packaging and MSIX, including App Attach image builds
• Azure Virtual Desktop and Windows 365 design, build and cost optimisation
• Legacy Windows and Windows Server migrations
• Legacy application capture and repackaging where the original install media has gone

Advisory, delivered as material you can put your own cover on

• A second opinion on an approach before you commit to it
• A design review of something a client's previous supplier built
• A technical response to a tender question, including named, credentialed answers where a tender asks for evidenced expertise
• Sizing and cost modelling behind a proposal you are about to submit
• An independent technical assessment of an estate's licensing position, security posture and technical debt, for example before acquiring a book of business

For software vendors specifically: the deployment and integration layer around your product. That means getting it packaged, delivered and supported cleanly in a customer's Microsoft estate, answering the identity, device and virtual desktop questions your support team is not staffed for, or standing behind a proof of concept in an enterprise environment.

What this bench is not for: volume first-line service desk work, general body-shopping, and anything outside the Microsoft cloud, security, virtual desktop and application space. Service desk cover is available by arrangement on a white-label engagement, depending on the partner, but if you need volume rather than depth, a provider built for scale will serve you better and cost you less.

3. Engagement models compared

Fully white-label, co-branded and overflow capacity compared

	Fully white-label	Co-branded	Overflow capacity
Who the end client sees	Your brand only; we never appear	Your brand, with us introduced as your named specialist partner	Your brand; we work inside your existing processes
Who owns the client relationship	You, entirely, including all client communication	You, entirely; we are introduced, not handed the account	You, entirely; we never leave your queue
What the gap is	A skill you do not hold in-house	A skill the client wants to see evidenced by name	Capacity, not capability
Where our engineers work	Behind your delivery team, in your tooling and templates	Alongside your team, including client sessions where you want us	In your ticket queue, project board and change process
Typical trigger	A won contract that needs one thing you cannot staff	A governance or procurement process that asks who is doing the work	A peak, a holiday period, a backlog or a project running hot
Handover at the end	Documentation in your templates, issued as yours	Documentation in your templates, with our input attributed if you want it	Tickets and changes closed in your system, so nothing needs migrating
Best for	Vendors and MSPs protecting a single supplier relationship	Engagements where the specialism is part of what was bought	Established teams absorbing short-term demand without hiring

4. Confidentiality, non-solicitation and ownership

5. How a job runs

1. NDA. Mutual, before any detail is shared.
2. Scoping conversation. Within a day or two of you getting in touch. It establishes what the client actually needs, what you have already committed to in writing, and what your own team is keeping.
3. Written scope. Deliverables, exclusions, the assumptions the estimate depends on, who owns each part, and how the work will be handed back. The quote is itemised, so you can price your own margin on top and compare it line by line with anyone else's. We give you a date we believe; if we cannot hold your date, we say so at this point rather than in week three.
4. Access. Granted only after the scope is agreed, limited to what the work requires, and documented so both sides know exactly what we hold.
5. Delivery. Through one agreed channel with a named owner on each side, usually a shared Teams channel or your own ticketing system, in your tooling and following your naming and change conventions where you want us there.
6. Handover. Documentation as a defined deliverable, in your templates: reports, run books, design documents, handover notes and diagrams.
7. Access removal. A defined step at the end, with confirmation back to you, so you have the record.

A scoped piece of work usually starts within a fortnight, sooner where the work is well defined and the discovery has already been done.

6. Incidents and escalation

Through you, always. You own the client relationship and therefore the client communication, so our job in an incident is to give you an accurate technical picture fast enough that you can be the one telling them something useful.

The mechanics are agreed per engagement and belong in the contract:

• What counts as an incident, as against a routine request
• Who is called, and on what number
• What our engineers may do without waiting for your approval, and what always needs your sign-off
• What happens when the named contact on either side is unavailable

We do not publish response targets for partner work. They depend on what is covered, during what hours, and what you have promised your client. Tell us your commitment and we will tell you plainly, in writing, what we can stand behind and what we cannot.

7. Commercial structure

8. What sits behind the delivery

The team. Senior engineers rather than a rota of first-line staff, which matters on partner work: you are putting your name on what we deliver, and you do not get to supervise it. Support is 100% UK-based.

Independently audited process.

• ISO 27001 for information security, certified by NDC Certification Services
• ISO 9001 for quality management, certified by NDC Certification Services
• Cyber Essentials, with a certificate you can verify online
• Microsoft partner status, with team certifications kept current

Named expertise. Where a bid needs a named credential, the team includes Ryan Mangan, Systech's founder: a Microsoft MVP for Azure Virtual Desktop and Windows 365, a Chartered Fellow of the BCS, and the author of Packt's Mastering Azure Virtual Desktop. That is what the co-branded model is for.

No logos, by design. We do not quote a partner count or show other partners' names. White-label work is confidential by definition, and a firm willing to show you its other partners is showing you how it would treat yours.

9. Where our scope ends

• We do not hold your client contract, and we do not carry your obligations under it. Your client's commercial terms, service commitments and regulatory accountability stay with you. We can build to a standard you have committed to, and give you the evidence that it was built that way.
• Our certifications are ours and do not transfer. ISO 27001, ISO 9001 and Cyber Essentials cover how Systech operates, so they are a fair statement about the processes your delivery runs through, not a certificate you can present as your own.
• Systech holds Cyber Essentials and helps clients prepare for it. We are not a certification body.
• Independent penetration testing is delivered with our CREST-approved partner, Punk Security. That approval is theirs, so it is disclosed rather than absorbed into anyone's brand.
• If a scope has been sold that cannot be delivered as described, we will tell you during scoping, not after you have taken the money.
• If the same skill gap keeps appearing, hire for it. We will tell you when the pattern suggests that, rather than quietly taking the work each time.

Where this leaves you

• Specialist work, unlikely to recur often enough to hire for

  Subcontract it and keep the client relationship entirely your own. That is what this is built for.

• The same skill gap keeps appearing

  Hire for it. We will tell you when the pattern suggests that, rather than quietly taking the work each time.

• You need volume rather than depth

  A provider built for scale will serve you better and cost you less. Service desk cover is by arrangement, depending on the partner, and we will say so on the first call.

• A scope has been sold that cannot be delivered as described

  We will tell you during scoping, not after you have taken the money.

If the work is specialist and unlikely to recur often enough to hire for, subcontract it and keep the client relationship entirely your own. That is what this is built for. Tell us what you have won, what is missing and when it has to land, and we will come back within a working day with whether we can help, and say so plainly if we cannot.