MOMENTUM AMP • COHORT 1 • 2026
The Certified Integration Partner Program
Build on the Momentum platform. Publish your tools, workflows, and AI agents directly to ~4,500 independent insurance agencies. Get certified. Get distribution.
2,000+
4,500+
ECOSYSTEMS
6
SURFACES
May 1
TARGET
April 1
ABOUT THE PROGRAM
Built for builders. Backed by distribution.
The CIP program is Momentum AMP's structured pathway for technical integration partners to publish tools, workflows, and AI capabilities directly to the Momentum platform — and optionally, to become certified consultants for third parties who want to integrate.
Why this exists
Demand from agents to connect, automate, and build workflows has far exceeded what Momentum's internal team can directly support. The CIP program addresses this by creating a small, curated network of certified partners who specialize deeply, adhere to quality standards, and become the primary delivery team for integration work.
The "rising tide" model
Partners make money. Momentum makes money. Agents get better tools. The commercial model is consumption and transaction-based — similar to in-app purchases. Partners set their own prices, Momentum takes a platform margin, and Momentum actively drives agent adoption toward high-quality, high-value work.
This program is being built alongside you. The partners in this cohort are helping establish the foundation — the standards, the tooling, the curriculum — that every future cohort will benefit from. You are shaping this from the ground up.
Weekly cadence calls are twice per week to accommodate different schedules. Expect to participate, provide feedback, and help define what "done right" looks like. The program goal: 2–3 certified partners with live, functional integrations by May 1, 2026.
THE PROCESS
How it works
From this kickoff to a live, published integration — here's the path.
Sandbox
Kayden
INTEGRATION SERVICES
Where your work shows up
You're not limited to a single delivery method. The Phase I goal is to take
your strongest capability and deploy it across as many of these surfaces
as possible — "carpet bomb the platform" with one thing done well.
The Toolbox
A UI-wrapped marketplace of plug-and-play tools with transactional, credit-based pricing. How agents consume your capabilities without touching an API.
Automation Center (MAC)
A Kafka-powered, real-time workflow engine. Publish automations as steps inside agency workflows — trigger-based, event-driven, seamless.
AMPs
AI prompt packages — similar to GPTs or Gems — with preset instructions and tool access. Build and publish purpose-built AI workflows for agents.
insuranceagency.ai
The new three-panel AI platform launching April 1. Partner-built templates, tools, and workflows featured in the marketplace from day one.
Agentic Agents
Named, purpose-built agents that perform a single function or series of functions — a loss-run expert, a voice agent, a planning agent. Emerging delivery mechanism.
API / MCP / Webhooks
Direct integrations for partners building their own connectivity or integrating third parties. REST API, MCP (live), webhook support, and A2A connectivity.
PARTICIPATION OPTIONS
Two ways to participate
Both paths require the same initial training and time commitment. The difference is what you choose to do after you're certified.
Let Steve know which path fits your model
KICKOFF RECORDINGS
Watch all three sessions.
All three kickoff calls are recorded. If you attended one session, the others cover the same core material plus additional Q&A. Recordings are linked below once hosting is confirmed.
SESSIONS 1, 2 & MAKEUP CALL · MARCH 4, 6 & 11, 2026
CIP Program Kickoff — Complete Recording
All three kickoff sessions combined into a single video: program overview, platform walkthrough, partner value proposition, integration surfaces, the two participation paths, and Q&A from all cohort attendees. If you attended one or two sessions, everything covered across all three is included here.
Note: The combined recording will be available on this page once video hosting is confirmed. Contact sanderson@momentumamp.com with any questions.
-
What is the CIP program and why is Momentum launching it now?
- Momentum AMP has close to 4,500 agencies in its ecosystem, with roughly 2,000 using the AMS as their core operating system. For years, Momentum has published open APIs and told the market: come partner with us. The problem was that great partners would show up with real capabilities, and Momentum didn't have the internal bandwidth to properly support them — to answer questions, manage integrations, hold weekly calls, and benchmark performance.
- The CIP program — Certified Integration Partner program — is the solution to that bottleneck. It is a small, selective, curated network of technical integration partners who go through a defined onboarding process, commit to service standards, and get real support from the Momentum team in return. The goal is to build something that mirrors what Microsoft and Apple did with their partner and app store ecosystems: make it possible for outside builders to extend the platform in ways Momentum can't do alone.
- The timing comes from what the team heard directly at the Indie Tech conference earlier this year. The sentiment from agents has shifted from 'this sounds interesting' to 'I need this right now.' The demand is there. The CIP program is how Momentum meets it.
-
What are the integration delivery mechanisms — where can my integration actually appear?
- There are six primary delivery mechanisms where CIP partner integrations can appear within the Momentum ecosystem:
- 1. Toolbox — A marketplace-style interface inside the AMS where agents can browse, access, and interact with partner-built tools. Momentum wraps partner API functionality in a user-friendly front end so agents don't need to manage API credentials themselves.
- 2. Automation Center (MAC) — Momentum's workflow builder, powered by Kafka for real- time event processing. Partners can publish workflows, trigger from webhooks, and integrate as steps within automation sequences. The goal is for Toolbox tools and MAC workflows to be interoperable.
- 3. AMPs — Momentum's equivalent of GPTs or Gems. Custom AI agents that users configure for specific tasks. Partners can publish their own AMPs or contribute to existing ones.
- 4. insuranceagency.ai — Momentum's forthcoming AI platform, launching in beta April 1. A three-panel interface (channels, AI conversation, UI) where agents interact with AI in natural language. Partners will be able to publish integrations and tools into this environment.
- 5. Agentic Agents — Named, purpose-built agents that can execute multi-step workflows autonomously. Momentum is launching five agentic workflows in the first phase; partners can contribute to and extend this layer.
- 6. API, MCP, Webhooks, and A2A — Direct connection methods for technical integrations. Momentum has open APIs, a recently launched MCP, agent-to-agent (A2A) capability, and webhook support. These are the underlying rails that power all delivery mechanisms above.
-
What is the difference between a CIP Partner and an Individual Contributor?
- This distinction came up directly during the calls and is worth understanding clearly.
- A CIP Partner is a company or team that goes through the full certification process — onboarding, legal agreements, SLA commitments, and accountability standards. CIP Partners can build and publish integrations under their own brand, charge for their tools, and take on integration work for third-party vendors who want to connect to Momentum but don't want to build the integration themselves. Think of CIPs as the approved contractors in the ecosystem.
- An Individual Contributor is someone who wants to publish a tool, workflow, prompt, or AMP into the Momentum platform without becoming a full CIP. They can do this through a more streamlined, self-service process. They won't be listed as approved integration partners for hire, but their published content can still appear in the Momentum marketplace.
- You do not have to be a CIP to participate. Michael was clear: some people on the calls may be better suited as individual contributors, and that is a completely valid path. The CIP designation is for those who want to take on the broader role of building for Momentum's customer base and potentially servicing other vendors.
- CIPs can also be player-coaches — meaning they can both hold CIP status and publish their own tools as individual contributors. If you've already built 40 workflows, bring them. You'll be the publisher and you'll set the price.
-
Are there any types of integrations or products that would be off-limits?
- Very few, if any. The spirit of the program is openness. If you can build it, pitch it, and there is demand for it among independent agents, Momentum wants to see it.
- With roughly 4,500 agents across the ecosystem, even a specialty niche like parametric weather coverage is likely relevant to a meaningful percentage of the base. The guidance from Michael: think singles and doubles first — build for the 80% use case — but if you have a creative or niche concept, take a chance. The bar for 'off-limits'; is high.
- Momentum will give honest feedback on fit and relevance, but they are not going to arbitrarily close doors. If you have an idea, bring it forward.
-
Can Momentum's platform work across other AMS systems so CIP partner tools reacha broader market?
- This is a directional vision, not a confirmed arrangement — but it is one Momentum is actively working toward. Momentum has made a significant investment in the Indie Tech show and sees that organization as a potential neutral connector: if Indie Tech can establish itself as a bridge between AMS platforms, CIP-built tools routed through Momentum's infrastructure could reach agents on other systems as well.
- That said, Momentum is not interested in building cross-AMS standards committees or waiting for industry alignment. The approach is: build the best open platform, make it easy for partners to connect, and let the market come to us. If other AMS vendors want to participate in what Momentum is building, the door is open.
- Note: Multi-AMS connectivity through Indie Tech is a vision, not a confirmed commercial arrangement. Watch for updates from Steve as this develops.
-
Can we start building and connecting before the legal agreements are signed?
- Yes. Do not wait. If you do not already have API credentials and sandbox access, reach out to Alex Wilhelm at alex.wilhelm@momentumamp.com right away.
- The NDA and other legal agreements are in process and will follow shortly. But the goal is for partners to be building, testing, and giving feedback now. Go try to build a workflow, connect to the MCP, and push data back and forth — then tell the team what works and what does not. That feedback is exactly what the program needs at this stage.
- The partners who get the most out of this program will be the ones who jump in early.
-
Can a Toolbox tool be added as a step inside the Automation Center workflow?
- Yes — that is explicitly the goal. The Toolbox is designed as a manual, human-triggered interface where an agent takes a specific action. The Automation Center is designed for automated, rules-based workflows that run without requiring a human at each step. The intent is for every part of the Momentum system to connect to every other part.
- If you build a tool or integration as a Toolbox item, the roadmap includes making it available as a step inside the Automation Center as well — and vice versa. Anyone with an API, MCP connection, email address, or RPA/agentic browsing capability can participate in this connected layer.
-
Is everything we need to know about the program and next steps in the Charter document?
- Yes — the Charter is the controlling document and it is detailed. That said, it is a living document and is actively being updated. Now that you have seen the platform walkthrough, reading or re-reading it with that context will be valuable.
- The next major workstream being developed is the legal agreements — NDAs, SLAs, Partner Program Agreement, and related documents. These will be coming to partners for review. Feedback on the Charter itself is welcomed; send it to sanderson@momentumamp.com.
INTEGRATION SERVICES
Open items — no answer yet
These topics came up during the calls but do not have finalized answers. Watch for updates from Steve as they're resolved. This list will be updated as decisions are made.
Commercial model & revenue share percentages
The framework is defined directionally. Specific rates are still being finalized and will be communicated before any partner goes live.
PENDING
Formal legal agreements
NDA is in draft. MSA, Partner Program Agreement, SLA, and API Terms to follow in sequence.
IN PROGRESS
Integration approval authority
Who has final sign-off on partner-published integrations before they go live to customers.
PENDING
insuranceagency.ai partner publishing timeline
April 1 beta is Momentum-managed. CIP partner publishing timeline on the platform is TBD.
TBD
Multi-AMS / Indie Tech connectivity
Directional vision for reaching agencies on other AMS platforms. No confirmed arrangements with other AMS vendors yet.
DIRECTIONAL
Get API credentials & sandbox
Contact [email protected] now if you don't already have access. Don't wait.
Sign up on Momentum AMP
Create an account at momentumamp.com and add a payment method. Email Steve — no billing for 90 days.
Read (or re-read) the Charter
The Charter is the controlling program document. Read it with the platform walkthrough in mind. Send feedback to Steve.
Pick your ONE superpower
Identify the single capability you'll deploy across all delivery mechanisms first — one thing done well across every surface is the Phase I goal.
Sign the NDA when it arrives
NDAs are being drafted and will be distributed shortly. This is the first formal legal step — required before credentials are formalized.