Who this is for
An engineering manager, platform lead or security lead who has been asked to deploy GitHub Copilot to somewhere between twenty and a few hundred engineers, and who has to produce an acceptable-use policy, a security review, a content-exclusion decision, an MCP approval process, a rollout plan and a way of measuring it — usually alongside the job they already had.
If you are one person adapting templates for yourself, the Toolkit on its own is the right purchase and this page is not. The difference between the two prices is the engagement, and an engagement only earns its cost when there is a team on the other side of it.
The problem it addresses
The templates that exist for this are either vendor material dressed as a checklist or a generic AI policy that could be about anything. The specific decisions — that content exclusion is not retroactive and so has to be made before the pilot, that an MCP server is a supply-chain dependency running inside an agent loop, that review comments per pull request is the adoption metric almost no dashboard shows — are the ones that get made late, by accident, or not at all.
The Toolkit writes those decisions down. This package works through them with you against your organisation rather than a hypothetical one.
What is included
- Enterprise Deployment Toolkit — organisation licence
- Rollout readiness review of your current state, written up
- Governance and policy review against the toolkit templates
- A 60-minute working session with the people running the rollout
- Implementation recommendations, prioritised and written down
- One follow-up session within 30 days to review what happened
The Toolkit licence is the same organisation licence sold on its own ($299); it is not a reduced or different edition.
What is not included
Stated here rather than discovered later:
- Anything on GitHub's side — seat provisioning, billing, or support tickets
- Writing your internal policy for you; the templates are adapted with you, not delivered as a finished legal document
- Any claim of GitHub affiliation, partnership or certification
- Guaranteed adoption numbers or productivity figures
The Copilot Stack is an independent educational resource. It is not affiliated with, sponsored by, or endorsed by GitHub or Microsoft, and nothing in this package is a certification of anything.
How it runs
- Enquiry. The form below. You hear back within two working days with either a confirmation that the floor price covers your situation or a short note on what would change it and why.
- Readiness review. A written questionnaire, the same one in the Toolkit, completed by you. It has four questions that can return "not yet", and if one does, that is the first thing the session covers.
- Governance review. Your existing policies — or the absence of them — read against the Toolkit's templates, with a written note on each gap and which template closes it.
- Working session. Sixty minutes with the people who will actually run the rollout. Not a presentation: the agenda is the gaps from the two reviews, in priority order.
- Written summary. What was decided, what was deferred and why, and a prioritised list of what to do next, sent within three working days of the session.
- Follow-up. One further session within thirty days to review what happened against what was planned.
Price
From $999. That figure covers a single team or business unit of the sizes listed in the form. Larger, multi-unit or multi-region rollouts are scoped in the reply to your enquiry, and the price stated there is the price — there is no hourly rate underneath it.
Payment is taken by invoice once the scope is agreed, before the first review. The Toolkit licence is delivered at that point, so the templates are in your hands while the reviews are being done.
Enquire
Received. You will hear back within two working days from a person, not a sequence.
Questions
Is this consulting?
A bounded piece of it. Two reviews, one session, one summary and one follow-up, at a fixed price. It is not a retainer and it does not expand into one unless you ask.
Can we just buy the Toolkit and skip the rest?
Yes — here. That is the right choice for a single adapter or a team that already has its governance settled and wants the templates.
Will this get us approved by security?
It will give your security review a set of documents to review instead of a blank page, and a written note on where your current state differs from what the templates assume. Whether that passes is a decision made where you work, by the people accountable for it, and this page does not pretend otherwise.
Do you deal with GitHub on our behalf?
No. Seats, billing, enterprise settings and support tickets are between you and GitHub. This package is about what your organisation writes down and decides; it is not a reseller relationship.
What if the readiness review says "not yet"?
Then the working session is about what "yet" requires, which is usually the most useful hour in the package. Nobody is charged for a rollout that should not happen this quarter.