> ## 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.
# Co-selling
> Sell together on shared CRM records - register deals, share pipeline, collaborate on every object, and link partner deals, without giving partners a CRM seat.
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.
}
;
};
> Co-selling is how vendors and partners close together on the same CRM records: partners register deals, both sides collaborate in context, and everything writes back to the CRM, with no partner ever needing a CRM seat.
## What this area does
Channel revenue stalls when the vendor's CRM and the partner's world never meet. Partners cannot see the deal, the vendor cannot see the partner's work, and the two sides reconcile over email. Co-selling closes that gap by making the CRM record the shared workspace. Partners register deals and leads, and comment on and collaborate around deals, contacts, companies, and tickets, while every action syncs back to HubSpot or Salesforce. When a partner runs their own CRM, [Partner Connect](/features/partner-connect) links the two systems on one deal.
Crucially, none of this requires giving a partner a seat in your CRM. Your sales reps stay in the CRM they already use, partners work from the portal or right inside their own tools, and Introw keeps the two in sync. Deal registration protects against channel conflict and routes through the approvals you define, so the pipeline stays clean and trusted. Shared pipelines give both sides one scoped view of attributed deals and a place to collaborate on each record, keeping everyone moving toward close.
## Why it matters
* **CRM-native** - Co-selling happens on the CRM record and writes back to it, so there is one source of truth for partner-attached pipeline and the AE never leaves HubSpot or Salesforce.
* **Time to value** - Joint selling runs on the deals already in your CRM, with partners collaborating without a CRM seat, so co-selling starts immediately with nothing to migrate and no per-partner license to provision.
* **Work where you already are** - Partners can register and collaborate from the portal, their CRM, Slack, email, or an AI assistant.
* **Trust & accuracy** - Deal registration with conflict detection and approvals keeps attribution clean and channel conflict in check.
## How it fits together
Both sides work one CRM record from registration to close:
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
register["Register deal"] --> pipeline["Shared pipeline"]
pipeline --> collaborate["Collaborate on the record"]
collaborate --> tasks["Tasks"]
tasks --> close["Close, synced to CRM"]
```
## Capabilities
Let partners register deals and leads, with channel-conflict checks and approvals, synced to your CRM.
Give both sides one view of attributed deals and collaborate on each record, scoped to who sees and edits what.
Capture and assign the next steps to close on a shared deal.
## Who works in this area
Runs the co-sell motion, keeps deals moving, and protects clean attribution.
Collaborates with partners on shared accounts without leaving the CRM.
Registers and co-sells deals from wherever they already work.
## Headless
## All guides
{/* ROLLUP:START - generated content goes here */}
Open a CRM record for partner collaboration, set the right collaborators, and keep the deal conversation on the record with comments and files.
Link every deal to the partner who sourced or influenced it, so partners see the right deals in a shared pipeline and partner-attached revenue, reporting, and commissions are trustworthy.
Attribute deals to partners, add a scoped pipeline view to a partner experience, and control which deals and properties partners can see and edit - end to end.
Understand the 'No portal yet' and 'No deal embed yet' messages on a deal and take the right action so partners can see and collaborate on it.
Read pipeline org-wide or per partner from Introw.
Add a task to a shared deal, assign it to your rep or the partner with a due date, and turn on the notifications that keep both sides on schedule.