Skip to main content
Introw is building blocks, not a monolith. Use the API to read and write program data, embed the portal in your product or your CRM, and connect AI clients over MCP, so partnerships fit into the stack and the surfaces you already run.

​
The problem it solves

​
Impact

The surface a partner will actually use is the one they already have open. Being able to put your program inside it is what separates a program partners use from one they were merely given.

​
How this area works

The Developer Platform exposes Introw as composable pieces. The public REST API lets you read and write partners, commissions, and payouts with scoped API keys. Embed lets you drop the partner portal into your own product through an iframe, or meet partners inside HubSpot and Salesforce with CRM embeds. MCP exposes your program to AI clients over an OAuth-protected server, so assistants like Claude, ChatGPT, and Cursor can work with your partner data on your behalf. Three building blocks take Introw into your product, CRM, and AI tools. Where this sits in a setup. None of the setup tracks need any of it to go live. This is the surface you reach for once the program works and you want it inside your own systems. Each capability is a way to take Introw beyond its own surfaces, into your product, your CRM, and your AI tools, while the CRM stays the source of truth. Three building blocks take Introw into your product, CRM, and AI tools.

​
Run it from your AI assistant