Inclusions
Grouped by area, written as things we do rather than capabilities we have. Your agreement itemises the same list against your actual environment.
Security is part of the service you buy, not a tier sold after something goes wrong. Server and virtual infrastructure is in scope where you run it — how it is counted and priced for your estate is set out in your proposal.
Exclusions
Published plainly, because a dispute about scope eighteen months in is worse for both of us than an awkward paragraph now.
We specify, procure, supply, build and deploy it — desktops, laptops, servers, mobiles and tablets. Only the purchase price of the equipment sits outside the monthly fee.
Supplied and managed under Software, billed separately from the support fee.
Anything beyond maintaining the existing environment is quoted in advance as Consult work.
Operating systems and applications past vendor support cannot be secured or patched, so they sit outside the covered service.
We cannot be accountable for something we are not permitted to manage or monitor.
Vendor-specific systems are not supported at application level. We act as liaison with the vendor on your behalf.
Structured cabling, containment and building works are arranged and quoted separately.
Outside your covered hours unless your agreement expressly provides for it, in which case it is specified and priced.
Travel, parts and third-party attendance, recharged at cost with your agreement first.
If it is not in the agreement, do not assume it is covered — ask, and we will either add it or quote it.
Coverage and Cost
The definition of a covered user matters, because it is what the bill is built from.
A named person who uses your systems and can raise support requests — counted per person, not per device. One person with a laptop, a desk phone and a mobile is one covered user.
Shared terminals, warehouse scanners, meeting-room kit and similar are covered as devices rather than users, and listed individually in your proposal so nothing is counted twice.
In scope where you run them, scoped and priced against your actual environment — hosts, guests and their backup requirement are itemised in the proposal rather than absorbed into a per-user figure.
The fee follows the covered count. Joiners and leavers are reflected at the next billing cycle, so growth is not a renegotiation and a quiet quarter is not a fight.
Invoiced monthly, with payment terms and method set out in your agreement. Licensing appears on the same invoice as a separate line, so you can always see what is service and what is subscription.
Quoted before it starts, at the rate stated in your agreement. Where work is charged by effort, you receive an effort log evidencing the time against the invoice.
No rates are published on this site. You receive a costed proposal after the review, with the charging model stated in full and nothing added afterwards that was not in it.
Onboarding
Switching provider is the objection at this stage, so here is the shape of it. For context, BIG FULFILMENT's full migration completed in three weeks and Chrysalis Supplies had core systems live within 48 hours.
Environment review, user and device inventory, licence position, access arrangements, and what we need from the incumbent.
Management tooling deployed, security baseline assessed, documentation started, gaps identified and prioritised.
Support routes communicated to your staff, monitoring and backup verified, remaining access resolved.
Service live, onboarding findings presented with any recommended remediation, and your first review scheduled.
Support transfers on an agreed date with both providers aware of it. Nobody is left unsure who to call on the morning it changes.
If the incumbent is uncooperative — it happens — we tell you early and work around it rather than letting it stall the date.
Contract and Exit
A twelve-month initial term, then ninety days' notice at any point. No automatic multi-year rollover, and no notice period that quietly outlasts the reason you wanted to leave.
The covered count moves with headcount without reopening the agreement. A material change in shape — a second site, an acquisition, a server estate appearing — is scoped and priced as a variation you approve.
Your Microsoft tenant, your data, your licences and the documentation we built. They always were.
On exit we hand over administrative access, asset and licence records and the environment documentation, within the period stated in the agreement.
The handover of access, records and documentation is part of the agreement. Where an incoming provider wants significant additional support, that is quoted — and we would rather quote it than obstruct it.
A customer who stays only because leaving is difficult is not a customer we want.
Questions
Yes. Macs are supported and managed alongside Windows under the same agreement and the same security baseline. Mobile devices are covered for access, security policy and email rather than as full managed endpoints.
Yes, and often that is the better arrangement. We agree who owns what in writing, so nobody is standing on anyone else's work and nothing falls between the two of you.
Servers and virtual infrastructure are in scope. They are itemised and priced against your actual environment rather than absorbed into a per-user figure, so you can see exactly what the server estate costs to support.
Yes. Each site is listed in the agreement with its own onsite terms, since a Leicester office and a site two hundred miles away are not the same commitment.
Tell us the end date and notice period. We will plan the transition around it — and if the sensible answer is to wait three months, we will say so rather than push you into paying twice.
Not to start. We audit what you have and prioritise. Anything that works stays; anything genuinely unsupportable gets a replacement plan with dates and costs, not an ultimatum.
No. It works better together, because assignment and reclaim then happen inside the support process, but it is not a condition of the support agreement.
We tell you, in plain terms, and we tell you what we are doing next — vendor escalation, a third-party specialist, or a workaround while we wait. What we do not do is go quiet.
POLARIS engineers. Nothing is offshored, and you are not passed to a call centre reading your history for the first time. Where a specialist third party is needed we tell you who and why.
Email service@ptgtech.uk or use the portal at any time — it is logged immediately and picked up when cover resumes. Extended cover, where you need it, is specified and priced in your agreement rather than implied.
Next Step
Tell us what you are running and what is not working. You will get straight answers and practical recommendations — whether or not you go on to work with us.
Ask for the service description document instead. It is this specification in a form you can circulate to a colleague or a finance decision-maker — note it in the message field and we will send it over.
Raise a support request at service@ptgtech.uk or call the number above. Please don't use this form — it goes to the sales team.
Four fields. We reply within one working day.
Related
The tenant this service administers — set up, secured, migrated and supported properly.
Learn MoreBusiness broadband, leased lines, networks and secure remote access.
Learn MoreA costed 12 to 24 month plan, reviewed quarterly.
Learn MoreNamed customers, described carefully — what the situation was and what changed.
Read Them