> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.
# CRM
> Run your partner program on HubSpot, Salesforce, or Pipedrive without changing your RevOps setup - Introw adapts to how you already store partners and attribute revenue, works with any object including custom ones, and keeps partners, contacts, deals, and attribution in two-way sync.
export const Headless = ({prompts = []}) => {
const PromptRow = ({prompt}) => {
const [copied, setCopied] = useState(false);
const copy = () => {
try {
navigator.clipboard?.writeText(prompt);
} catch {}
setCopied(true);
setTimeout(() => setCopied(false), 1600);
};
return ;
};
return <>
Introw is headless by design: run everything here in plain language from Claude, ChatGPT,
Slack, Teams, or your own CRM through Introw's MCP server, with every
action written straight back to your CRM source of truth. The portal is one surface, never the only one.
{prompts.length > 0 ? :
The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
from Claude, ChatGPT, Slack, and your CRM.
}
;
};
> Your CRM is the source of truth, and Introw runs on top of it - not beside it. You don't restructure RevOps to adopt Introw. It plugs into how you already store partners and attribute revenue, works with any object including custom ones, and keeps partners, contacts, deals, and attribution flowing both ways.
## Why revenue teams love Introw
Most PRMs make you rebuild your partner data in a second system and reconcile it forever. Introw does the opposite: it reads your CRM as it is today, mirrors it live, and writes the partner context back. There is no migration and no parallel database.
It helps to see the CRM integration as **one connection with four jobs**, not three separate products:
Authorize HubSpot, Salesforce, or Pipedrive once. Records flow in on a schedule and through webhooks; key Introw data flows back. Nothing to migrate.
Every partner account and its contacts are pulled live, so access management and segments stay current without a second list to maintain.
Introw matches whichever method you already use to link deals to partners - property, association, lookup, relation table, or custom object.
Reps see partner context, register deals, and collaborate on the HubSpot or Salesforce record itself - no second tool to learn.
## What makes it different
### You don't change your RevOps structure
Introw adapts to the most common attribution methods **out of the box - no extra configuration or code**. However your team already records partners on a deal - a custom property, an association label, a lookup, a relation table, or a dedicated partner object - Introw reads it and attributes correctly. Sales keeps working exactly as they do today.
### It works with any object, including custom objects
Partners don't have to live on the standard Company/Account object. Point Introw at whatever object you use to model partners - including a **custom object** built for a large program - and attribute **any** object (deals, opportunities, contacts, companies, tickets, or custom objects) back to those partners. Object and field labels sync from the CRM, so Introw always speaks your terminology.
### Partners and contacts are pulled live, so access management is trivial
Introw pulls in **all your partner accounts and their contacts** straight from the CRM and keeps them current. New contact in the CRM → it appears in Introw. A field flips → portal access is granted or revoked automatically. Because the same fields sync for accounts *and* contacts, you can build [segments](/features/partners/segments) dynamically on CRM data (tier, region, lifecycle stage, contact role) and target onboarding, content, and notifications without maintaining a separate list. See [Sync partners & contacts from your CRM](./guides/sync-partners-and-contacts).
### Two-way by design
The CRM stays authoritative, but Introw writes context back: partner tiers, partnership managers, team roles, contact portal access, and partner engagement events all flow into the CRM so your revenue team sees the partner story on the records they already trust.
## The problem it solves
* **"We'd have to redo our RevOps setup"** → Introw reads your existing attribution model; nothing changes for sales.
* **"Our partners live on a custom object"** → Any object works, standard or custom, on both sides of attribution.
* **"Managing who gets portal access is a chore"** → Contacts sync live and access is driven by a CRM field.
* **"Partner data drifts between tools"** → One connection, two-way sync, CRM as the single source of truth.
## Use cases
Keep your current deal-to-partner model; Introw matches it.
Use a dedicated partner object at scale.
Let a CRM field grant and revoke portal access.
Build dynamic segments from account and contact data.
## How it connects to the rest of Introw
The CRM connection is the foundation other features build on - they read and write the same synced data, so you configure attribution once and everything downstream stays accurate.
* **Forms** map directly to CRM fields: a partner submission can prefill from and write back to the same properties Introw syncs, so deal/lead registration lands in the CRM with the right partner attribution already attached. See [CRM field mapping for forms](/features/forms/crm-field-mapping).
* **Shared pipelines** are the synced deals/opportunities, presented to partners. You choose which objects, pipelines, and fields partners see, rename fields and stages for a partner-friendly view, decide what they can edit, nudge or notify on changes, and sync the resulting activity back to CRM notes/chatter. See [Shared pipelines](/features/co-selling/shared-pipelines).
* **Commissions** calculate on the revenue Introw attributes from the CRM, so payouts trace back to the original record. See [Commission plans](/features/commissions/commission-plans).
## Impact
* **CRM-native** - HubSpot, Salesforce, and Pipedrive stay the system of record, two-way synced.
* **Time to value** - Connect once and the program populates itself from records you already have, with no middleware to build and nothing to migrate.
* **Low total cost of ownership** - RevOps configures everything in the UI, no engineering or code.
* **Work where you already are** - reps work from the CRM record; partners are reached in their own channels.
## Who it's for
Connects the CRM and owns attribution and sync.
Manages partners, contacts, access, and segments.
Co-sells with partners from the CRM record.
## Works with
{/* CONNECTS:START - generated content goes here */}
Partners are pulled live from your CRM records.
Segment partners and contacts on any synced CRM field.
Forms read and write the same CRM fields.
Co-sell on the deals already synced from the CRM.
Commissions run on attributed CRM revenue.
## Headless
## Going deeper
Connect, store, filter, import, and attribute - with every how-to guide.
Every way to link deals to partners in HubSpot and Salesforce, and how each is configured.
Live partner and contact sync, access management, and dynamic segments.
Programmatic access to the same data.