Skip to content

§00Pricing

Early access

Priced like software, not like a project.

You pay for integrations in production — not for the project around them.

PartnerMCP is in early access. Pricing is set per workspace, from the systems you connect and the volume your integrations carry.

What you’re billed forOne integration
What you’re billed for, per integration: discovery workshops, specification documents, change requests and overtime are not billed. Integrations in production are billed.
§01—Stages

Start with one integration.

Prove it on your systems, run it in production, then govern every integration across the company.

  1. Stage 01Sandbox

    Pilot

    Prove one integration on your systems.

    • Two of your systems, through their supported APIs
    • Discovery, a plan and a field mapping you review
    • Sandbox tests before anything reaches production
    • A readable, versioned spec of the integration

    Goes live when you approve it

  2. Stage 02 Production

    Production

    Run it. Change it by talking.

    • Integrations in production — what you pay for
    • Monitoring, retries and repairs within your policy
    • Changes in plain language — tested, versioned, reversible
    • Approvals, versions and an audit log on every change
    • Answers to “what failed, and why?”

    Add integrations as you need them

  3. Stage 03Governed

    Enterprise

    Govern every integration.

    • SSO with your identity provider and custom roles
    • Multi-approver policies and per-system approvers
    • Edge Agent for systems behind your firewall (architecture concept)
    • Data residency controls and security review support

    Terms set in your agreement

§02—Questions

Pricing, plainly.

How is PartnerMCP priced?

By the systems you connect, the integrations you run in production and the volume they carry. Discovery, planning, mapping, testing and changes are part of the product — not separate line items.

Why isn’t there a price list?

PartnerMCP is in early access. Pricing depends on your systems and volumes, so we set it per workspace once we’ve seen what you want to connect. Describe your systems in Start Building and we’ll follow up with pricing by email.

What counts as an integration in production?

A deployed integration running against your production systems — for example, Salesforce opportunities becoming Priority sales orders, with status flowing back. Plans, drafts and sandbox runs are how an integration gets there.

Do changes cost extra?

There are no change orders to price. You describe the change in plain language; PartnerMCP plans it, tests it in a sandbox and applies it with your approval — as a new version you can roll back.

Can our systems integrator work with PartnerMCP?

Yes. PartnerMCP is built to work alongside integrators: it takes on the repetitive integration work so their expertise goes where it matters, while your team approves every change.

§03Next step

Name your systems. Get a price.

Tell us which systems should connect and what should happen. We’ll review them and follow up with pricing.