The MCP Practitioner Course · Lesson 6 of 7

Productizing MCP as a Service

> ~3 hours · three engagement shapes, the pitch deck outline, pricing bands, SOW structure, runbooks, and the renewal motion that pays for the next three years

By the end of this module you'll have a productized service offering you can take to your top ten clients next week. Pricing bands, SOW template, runbook, and the renewal motion. Everything before this module is technical. This is where it stops being a hobby.

---

Discovery audit (1–2 weeks, $5K–$15K). A workflow audit specifically scoped to identifying MCP integration candidates in the client's stack. Output: a written 5-section deliverable with recommended tools, prompts, and a phased rollout plan. This is the entry point. Most clients can't answer "where would MCP help us" on their own; the audit answers it.

Implementation engagement (4–12 weeks, $15K–$55K depending on pattern). Build a specific MCP integration end-to-end. Helpdesk, CRM, finance, or custom. Includes deployment, security review, runbook, staff training, and a 60-day support window.

Ongoing managed service ($2K–$8K/month). Monthly retainer for production operations, incremental tool additions, monthly strategic review, and annual security re-review. This is the recurring revenue.

Most successful firm engagements layer all three. Audit → implementation → managed service → audit (every 6 months) → next implementation. The same $14K–$24K initial implementation produces $50K–$80K in year-two recurring.

---

• Discovery audit: $5K (free for round one, paid round two onward) for a 25–50 person SMB. $10K–$15K for 50–150. The audit fee is credited against implementation.
• Helpdesk implementation: $14K–$22K, usually 4–6 weeks.
• CRM implementation: $18K–$30K, usually 5–8 weeks.
• Finance implementation: $35K–$55K, usually 8–12 weeks. Compliance and testing overhead drives the band.
• Custom integration: $20K–$60K depending on complexity.
• Ongoing managed service: $2,500–$4,000/month for one production server, $4,500–$7,500 for two, $6,500–$10,000 for three or more.

These hold up for small businesses in most regional markets. Adjust by 1.2x–1.5x for major-metro markets. Below those bands you're underpricing the operational work; above them you're competing with enterprise consultancies that aren't doing better work but have a larger sales motion.

---

• The shift. MCP is now a multi-vendor standard. Every model the client uses (or might use) speaks it.
• The opportunity. Their existing systems can become AI-actionable for ~$15K–$25K per integration, not the $200K-enterprise number they're afraid of.
• The three patterns. Helpdesk, CRM, finance — pick the one that fits.
• Before/after for the chosen pattern. Specific to the client's stack and processes.
• The methodology. A diagram of the MCP server, the auth flow, the security boundary.
• The security review checklist. The 21-item checklist from Module 4. Hand it across the table.
• Timeline. 4–12 weeks with named milestones.
• The team. You or your firm, the senior engineer, the ops handoff person.
• The price. One number, no tiers, no "starting at."
• Next step. "Two-week audit, no obligation, audit fee credited against implementation." Close.

---

Every implementation SOW has six sections:

• Scope. Specific tools to be built (named, with descriptions). Specific prompts. The auth provider. The hosting platform. What is NOT included — explicitly listed. Scope creep dies in the explicit not-included list.
• Deliverables. Production deployment, test suite, security review checklist (the 21-item checklist filled in for this client), runbook, training session.
• Timeline. Named milestones with dates: kickoff, alpha, beta, security review, production handoff.
• Acceptance criteria. Specific tests the client runs to accept. Define the threshold: e.g., "passes 95% of the test cases," "completes 30 minutes of supervised live use without incident."
• Pricing. One number. Half on signing, half on production handoff. (Not 1/3-1/3-1/3 — keeps you focused on shipping.)
• Support window. 60 days post-handoff included. Beyond that, the managed-service retainer kicks in or hourly rates apply.

---

Every MCP server you ship gets a runbook. One page. Hand it to the client at handoff. Sections:

• What this server does. Two sentences.
• Tools and scopes. Reference list.
• Where to look at logs. URL + auth.
• How to tell if something is wrong. Symptoms (specific) and where to check.
• Common failure modes and 5-minute fixes. Top 5 issues.
• Escalation contacts. Who at your firm to call (with phone), business and after-hours.
• Rollback procedure. One command.

---

Managed-service retainers don't renew themselves. Build the renewal mechanic into the engagement rhythm:

• Monthly business review (30 min). What's the agent doing, what's it not doing, dollar value of saved time, next thing to build. Document the saved time in dollar terms every month.
• Quarterly security review. Re-walk the 21-item checklist. The CIO sees the discipline; the renewal becomes obvious.
• Annual roadmap. Every March, hand the client a one-page roadmap: what's worked, what's next, budget for next year. Renewal becomes "yes, here's the new SOW."

---

Don't price MCP work hourly. The hour is the wrong unit — the value is in the working server, not the time spent. Hourly billing creates pressure to overbuild (more tools = more hours) and undertest (testing isn't billable in the client's mind). Fixed-price engagements with explicit acceptance criteria align your incentives with the client's: ship the smallest server that passes acceptance, fast.

---

• Days 1–30. Build a referenceable example. Pick one of the three patterns and ship it for your own internal use, your IT partner's helpdesk, or one friendly pilot client at a deep discount or free. The artifact you walk into client meetings with is non-negotiable; you can't sell what you haven't shipped.
• Days 31–60. Run the audit pitch on your top 10 existing clients. Free or $5K depending on relationship. Convert 4–6 to paid implementations. Three weeks per implementation = roll out 2 in this period; queue the rest.
• Days 61–90. Ship the implementations. Convert each to a managed-service retainer at handoff. By day 90: 4–6 audits done, 2 implementations live, 2–3 managed-service retainers signed. Math compounds from there.

---

The MCP server you write is the easy part. The service offering — the audit deliverable, the security review checklist, the runbook, the onboarding rituals, the monthly review cadence, the per-client pricing tier — is what differentiates a productized service from a series of one-off projects.

Anyone can build an MCP server. Few people can sell, deliver, and operate one as a productized service. That gap is where the durable business lives.

---

• Pick the client (real or fictional) for your capstone build
• Pick which pattern (helpdesk, CRM, finance, or custom)
• Block two weeks on your calendar for the build
• Skim the capstone brief in the next module so you know what you're producing

The capstone is the artifact you walk into your first sales meeting holding. Two weeks. Pick well.

Previous: Real-World Integration Patterns for SMBs · Next: Capstone — Ship a Real MCP Integration