Skip to main content

Enterprise MCP Pilot

A complete, evidence-backed MCP pilot for one enterprise use case — discovery to handover, with the documentation security and procurement actually ask for.

Suitable for

  • Organisations that need MCP evaluated and piloted properly: architecture, identity, governance and evidence — not a demo.
  • Teams whose security and procurement functions must sign off before production use.
  • Organisations that want enterprise engagement from day one, without a mandatory sales call to see pricing.

Before we start

What you provide

Fixed-scope work needs defined inputs. This is everything the engagement requires from your side.

  • An executive or platform sponsor and a nominated technical lead.
  • Discovery access: the systems, teams and constraints relevant to the pilot use case.
  • Sandbox or staging environments under your control; production access only if required and explicitly authorised in writing.
  • Your security, compliance and procurement requirements up front, so the evidence pack matches what your reviewers need.

Scope

What is included — and what is not

Included

  • Discovery: current state, integration targets, constraints and success criteria for one pilot use case.
  • Target architecture for the pilot, including transport, session and scaling design.
  • Security and identity review covering authorization boundaries, credential handling and audit trail design.
  • Pilot implementation of the agreed MCP integration in your environment.
  • Client interoperability testing against the named clients agreed in scope, with recorded conditions.
  • Deployment and rollback planning, exercised at least once in a non-production environment.
  • Operational evidence: runbooks, logging and monitoring guidance, and the procurement-facing documentation set.
  • Structured handover to your engineering and operations teams.

Excluded

  • Organisation-wide rollout beyond the agreed pilot use case.
  • Third-party platform fees, licences and hosting costs.
  • Ongoing managed operation of the pilot after handover.
  • Scope changes follow the written change-control process; customer responsibilities (access, environments, reviewer availability) are set out in the engagement terms.

What you receive

Deliverables

  • Discovery report and agreed success criteria.
  • Target architecture document.
  • Security and identity review with findings and resolutions.
  • Working pilot implementation in your environment.
  • Interoperability test record for the named clients.
  • Deployment runbook and tested rollback plan.
  • Production Evidence Pack (enterprise edition) — see contents below.
  • Handover sessions with your engineering and operations teams.

Production Evidence Pack — enterprise pilot edition

  • Architecture and design documentation.
  • State and authorisation data-flow summary.
  • Security and identity review record.
  • Interoperability and acceptance test records with conditions.
  • Negative authorisation test record: wrong issuer, wrong audience, expiry, replay and insufficient permission.
  • Requirements, findings and acceptance traceability matrix.
  • Residual-risk register: what remains open, who owns it and what would close it.
  • Deployment runbook and rollback exercise record.
  • Directory metadata and ownership readiness checklist — readiness assistance only, with no directory-acceptance promise.
  • Operational guidance: logging, monitoring and incident basics for the pilot.
  • Procurement appendix: scope, dependencies, data handling, subprocessors and specialists, support boundaries and exclusions.

Timetable

Expected timetable

  1. Discovery begins after intake and scope validation.
  2. The implementation milestone and overall timetable are fixed in the written scope, because enterprise environments and review gates differ.
  3. Acceptance follows the criteria agreed in writing at discovery.

Acceptance

How success is accepted

  • All deliverables listed in the written scope are provided.
  • The pilot meets the success criteria agreed at discovery.
  • The rollback plan has been exercised in a non-production environment.
  • Handover sessions have been held and the evidence pack delivered.

After payment

What happens after you pay

  1. TrustOps confirms the reservation and opens enterprise intake.
  2. Discovery sessions are scheduled. Delivery start is confirmed after intake and scope validation.
  3. The implementation milestone (30%) is invoiced only at the milestone defined in the written scope; the final 30% only on acceptance.
Start the enterprise pilot — £2,600

You'll review your order on TrustOps (trustops.ecocitizenz.com) before any payment step. Purchase starts your engagement and written intake; your delivery schedule is confirmed during intake.