Impulse Intelligence Platform
Most companies build integrations one at a time. They're about to be buried under their own technical debt.
One auth. One rate limiter. One audit log. One place to govern.
The standard pattern in 2024 was "build a Salesforce integration, then a HubSpot integration, then a Slack integration, then a custom one for the partner that just signed." Each integration had its own auth, its own rate limits, its own observability gap, its own breaking-change risk, its own dedicated maintenance.
That pattern was already getting expensive. In 2026, with AI agents now wanting to call into your kernel from Claude, ChatGPT, Perplexity, internal Breeze workflows, customer portals, partner systems, and a half-dozen other surfaces, the cost has compounded. Companies wiring integrations one at a time are now spending operational headcount on integration debt that should have gone into product or growth.
companyMCP (the Model Context Protocol that connects every interface to one intelligence layer) is what we install instead. Build the interface once. Every agent or tool that speaks MCP can call it.
This is not a productivity argument. It's a survivability argument.
A Model Context Protocol surface, tuned to your specific data model and your governance requirements.
In plain language: we stand up a single, governed interface that lets any caller (your team's AI tools, your customer-facing agents, your partner systems, a vendor's MCP client, your own internal Breeze workflows) ask your kernel a question and get a real, structured answer.
- No prompt-stuffing.
- No hallucinated numbers.
- No prayer.
For most clients, the Kernel underneath is HubSpot — and other CRMs where they're already in place, though HubSpot is our preferred substrate. Depth built since 2007 pays back in protocol design.
Five categories. The exact shape is yours.
A typical companyMCP install includes five categories of endpoint. We design the shape with you in the diagnostic and proof-of-concept moves — not for you in a vacuum.
Read endpoints
- Contact & company queriesLookup by ID, by property, by association. Filtered by the access scope of the calling agent.
- Deal pipeline queriesStage, amount, owner, age-in-stage, custom-object associations. Real-time.
- Custom object queriesWhatever your kernel models. matters, engagements, projects, jobs, cohort records.
- Workflow state queriesWhere this contact sits in onboarding. Whether a deal is stuck.
- Reporting · natural language"How many enterprise deals are open in EMEA, past 30 days in negotiation, no activity in the last week."
Write endpoints
The actions you authorize agents to take.
- Notes · tasks · propertiesLifecycle stage transitions, deal stage moves, custom object creation.
- Always governedBy your write policy. Versioned. Reversible.
Search endpoints
Natural-language search across the kernel.
- Conversational queries"Find me the customer that mentioned procurement issues in their last call."
- Indexed · structuredReturned with structured results, not pasted into a chat.
Resource endpoints
The supporting data your agents need to be useful.
- Brand voice rulesFrom your prompt library.
- Approved messagingBy audience.
- Recent customer conversationsKnowledge base articles. Compliance guidance.
Tool endpoints
The workflows you authorize agents to invoke.
- Real workflows"Send the renewal pitch." "Open a partner deal registration." "Generate the proposal." "Escalate to CSM."
- Arguments · validation · rollbackEach tool wraps a real workflow with all three.
A sales agent. Two real answers. One audit log entry.
A sales agent (running in Claude, or in your CRM, or from a Slack DM, depending on where the rep is working) needs to know which deals are at risk this quarter.
Tool: company.search
Arguments: {
"object": "deal",
"filters": {
"stage": "negotiation",
"days_in_stage": ">30",
"last_activity_days": ">7",
"amount": ">50000"
}
}- 01Authenticate the caller against the rep's scope
- 02Check authorization for this specific operation
- 03Run the query against the kernel
- 04Apply governance output filters
- 05Log the call · return the result
[
{
"deal_id": "1234",
"name": "Acme Renewal",
"amount": 240000,
...
},
{
"deal_id": "5678",
"name": "Beta Expansion",
"amount": 180000,
...
}
]The protocol layer is also where governance lives.
This is the layer that lets you put an agent in front of a customer without losing sleep.
Seven callers. One surface.
Four things, just to save the procurement team time.
Honest read. Two columns.
The diagnostic determines which case you're in. We won't sell you protocol installation you don't need.
- You're deploying multiple agents (your own, your team's, partner-built) and don't want to maintain N separate integrations.
- You have customers or partners who should have agent-mediated access to your kernel.
- You're at L3 or higher on the Maturity Model and ready to move toward L4 Exposed.
- Your governance and compliance posture requires a single audited interface for agent-mediated access.
- You're at L2 or below. Build the Kernel first. The protocol on top of a broken kernel produces broken agent responses faster.
- Your AI use is exclusively single-agent inside HubSpot's Breeze ecosystem. Native Breeze tooling is sufficient for that case.
- Your roadmap doesn't include customer-facing or partner-facing agent surfaces.
Six to twelve weeks. Four moves.
A typical companyMCP installation runs 6 to 12 weeks depending on kernel complexity and the scope of endpoints.
- MOVE · 01Discover1–2 wksThe diagnostic + a focused protocol scoping session. We identify which endpoints matter most, which agents will call them, and which governance requirements apply.
- MOVE · 02Expose2–3 wksA pre-contract proof of concept. We stand up a slice of the protocol surface in a sandbox, with real kernel access if you grant it, so you can see the interface before signing.
- MOVE · 03Wire3–5 wksFull protocol install with all authorized endpoints, governance infrastructure, and observability. Documentation. Training for your team.
- MOVE · 04OperateongoingTuning, endpoint expansion, governance maturation. Most clients keep us close in the months after install while the agent portfolio expands.
Map your company's intelligence in 90 minutes.
We will assess your kernel's readiness for protocol exposure during the 90 minutes. You walk away with a written read on whether MCP installation is the right next move — or whether kernel work has to come first.
Yours to keep — signed or not.