Connect Claude to your business systems in two weeks.

Production-grade Model Context Protocol integration for UK SMEs. Fixed scope. Fixed price. £10,000.

The problem

You've watched your team experiment with Claude or ChatGPT in the browser. Useful — but cut off from the systems that actually matter. Your ERP. Your CRM. Your data warehouse. Your ticketing system. The moment someone asks "can the agent actually do something in our systems?" the project stalls.

Anthropic's Model Context Protocol (MCP) is the open standard that closes that gap. It's also new enough that almost no one on the UK SME market has shipped one to production. Most consultancies will quote you six months and £60k+. Some will tell you to wait for a vendor to do it for you. Neither helps you ship this quarter.

The Sprint

Two weeks. One production-grade MCP server. Deployed to your cloud. Connected to one of your internal systems.

You choose the system:

• Finance / ERP — Xero, Sage, NetSuite, Unit 4 ERPx, Dynamics, SAP B1
• CRM — HubSpot, Salesforce, Dynamics 365, Pipedrive
• Data warehouse — SQL Server, Postgres, Snowflake, BigQuery
• Ticketing / ops — Jira, ServiceNow, Zendesk, Freshdesk
• Any internal REST or SQL-accessible system

What you walk away with

• One MCP server, written in C# / .NET, deployed to your Azure or AWS environment
• A defined toolset (typically 5–10 tools) Claude can call safely with scoped permissions
• Full audit logging of every tool invocation
• Authentication wired to your existing identity provider (Entra ID, Okta, Auth0)
• Source code in your repository, with a CI/CD pipeline
• A runbook your team can operate without me
• Two hours of recorded handover walking your team through the integration end-to-end

The two-week shape

Week 1 — Discovery and design. Half a day on site (or video) with your team to scope the toolset. Architecture document, security model, and the agreed list of tools — all signed off by your CTO or Head of Engineering before a line of code is written.

Week 2 — Build, test, deploy. Daily progress updates. End-of-week handover session. Code merged to your repo, integration running in production.

No surprises in week three. If there is a week three, it is free.

What this is not

• Not a proof-of-concept that gets binned six weeks later. This is production code with logging, tests, error handling, and operational documentation.
• Not vendor lock-in. The MCP server is yours — yours to extend, fork, audit, or replace.
• Not Claude-only. MCP is the open standard. Any MCP-compatible agent — Claude Desktop, Claude Code, your own Anthropic SDK build, or any future client that adopts the protocol — can use the same server.
• Not a consultancy engagement that scope-creeps. One integration, one price, two weeks.

Who delivers it

John Fitzgerald. 30+ years UK contracting, senior .NET / C# architect. Currently shipping production MCP and Anthropic SDK work at Haven Holidays — Lambda generation, agentic pipeline diagnostics, MCP patterns against AWS services. Domain background across financial services (HSBC, Old Mutual, Sarasin, Threadneedle, Liberum, AmTrust at Lloyd's), government (DEFRA, CQC, TfL), utilities (Anglian Water, RWE), and hospitality (Haven, Premier Inn).

I write all the code myself. There is no offshore team, no junior I'm reselling, no agency margin.

What it costs

£10,000 + VAT. Fixed price. 50% on signature, 50% on delivery.

Included: everything above.
Not included: third-party licence and hosting costs (Azure / AWS / Anthropic API), and integrations beyond the one defined in week 1. Want a second integration? £8,000 each, booked within 90 days of the first.

When you should not book

• You haven't decided which system to connect first. Book the free 30-minute call instead — we'll work it out.
• You don't have an Anthropic API account, or you're not willing to set one up.
• You need formal procurement approval taking three months or more. The Sprint is for teams that can move at the speed they say they can.

FAQ

Why two weeks? Because the work fits in two weeks when the scope is fixed. Longer engagements exist to absorb scope-creep, not to do better work.

Why .NET? Because that is the stack I write production code in every day. The MCP protocol is language-agnostic; the implementation is .NET because it is the fastest, lowest-risk path for me. If your environment requires Python or Node, say so on the call — I will either adapt or refer you on.

Do you offer ongoing support? Yes. Optional £1,500/month retainer covers minor changes, monitoring, and on-call response. Most clients run it for 60 days then bring it in-house.

Can we sign an NDA? Yes. Standard mutual NDA on request before discovery.

Are you VAT registered? Yes.

What is your IR35 status? Outside IR35. This is a defined-deliverable contract, not a time-and-materials role.

Next step

20-minute call. We talk about which system to connect first, whether the Sprint fits, and whether we are a good fit for each other. No pitch deck, no sales theatre.