Licensing and tenant readiness
The licences already in place, the proposed users, environment setup, permissions and policies that could enable or block a build.
Copilot Studio readiness assessment
A review of whether Copilot Studio is worth building on your Microsoft 365 tenant.
We look at the tenant, the documents and the work people repeat. You get a written recommendation on what is worth building, what would get in the way, and whether to proceed at all.
Book a 30-minute call
- Agreed scope
- Documents, people and access settled before we start
- Fixed fee
- Covers the scope and the written report
- No obligation
- The report can say do not build
What it is
A review with an agreed scope and a fixed fee. Before it starts, we agree which document set and processes to examine, who needs to be involved, and what access is available. The purpose is to decide whether a build is worth doing on this tenant.
What happens
We review the evidence with the people who know the work and the tenant. The assessment covers:
The document set
Where the documents live, who owns them, how they change, who can read them, and whether they contain clear answers to the questions being asked.
The questions staff repeat
Examples of the questions people answer by hand, where the answers come from, and which questions need judgement or information outside the documents.
Where automation would and wouldn’t hold
The process, its exceptions and the systems it depends on. We look for places where automation can hold up in daily use, and places where it would leave someone repairing the result by hand.
What we need from you
- A named contact who understands the process, and time with the person responsible for the Microsoft 365 tenant.
- A representative document set, examples of recurring staff questions, and examples of exceptions or failed handoffs.
- An agreed way to review the relevant licensing, settings and permissions, such as an administrator walkthrough.
- A clear account of what a useful result would change for the team, along with constraints the recommendation must respect.
What you get
A written report naming the two or three highest-value candidates, or explaining why none is ready to build. For each candidate, it sets out:
- The problem it addresses, who would use it and what a useful result looks like.
- What it would cost to build, as an estimate with the scope and assumptions made explicit.
- What would block it: licensing, permissions, document quality, missing process ownership or dependencies.
- A plain recommendation on whether to build, address prerequisites first, or leave it alone.
“Don’t build anything yet” is a valid recommendation. If the documents or process cannot support a dependable result, we will say so and explain what would need to change.
What it costs
The fixed fee covers the agreed assessment scope and written report. The amount is to be confirmed before the assessment is booked.
What it doesn’t include
- Building or deploying an agent, automation or connector.
- Rewriting the document set, migrating content or changing production tenant settings.
- A tenant-wide security or compliance audit.
- Microsoft licences, service consumption charges, ongoing monitoring or support.
If a build follows
If the assessment identifies a worthwhile build, we can propose a separate engagement with a defined deliverable, acceptance checks, a fee and an agreed delivery window. Documentation and handover are part of that scope.
There is no obligation to continue with us. You can use the report to make the next decision with your own team or another provider, or decide not to build.
Book a 30-minute call
Tell us what the team is trying to do, where the documents live and what keeps going wrong. We’ll use the call to work out whether an assessment is a useful next step.