> ## 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.
# Partner Analytics
> Understand each partner's revenue and engagement, spot who needs attention, and give partners their own performance view in the portal.
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.
}
;
};
> Healthy programs catch silent failure early. Partner analytics shows you each partner's revenue and engagement so you can see who is thriving, who is going quiet, and act before it shows up in a QBR.
## What it does
Partner analytics gives you a per-partner view of performance. On a partner's overview you see their
revenue, engagement, top deals, and goal progress; the analytics tab shows a dashboard scoped to just
that partner. Engagement metrics highlight who is active and who is going quiet, so you can intervene
before a partner stalls.
Partners get their own view too. In their portal you can surface a partner-scoped dashboard, a
collaboration dashboard with deal metrics like total revenue, deal count, average deal size, and
sales cycle, plus goals and embeds. All of it is sourced from your CRM and locked to the partner, so
each partner only ever sees their own numbers.
## The problem it solves
Without per-partner visibility, problems surface too late:
* **Silent failure is invisible** → Engagement metrics flag partners going quiet.
* **Performance is buried in the CRM** → A per-partner view surfaces revenue and engagement.
* **Partners have no self-serve view** → A portal dashboard shows them their own numbers.
* **Reviews start from scratch** → Partner overviews give you the picture before a QBR.
## From problem to solution
Partner analytics turns raw CRM activity into partner-level insight. See who needs attention, act
early, and give partners a scoped view of their own performance, all from trustworthy CRM data.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
activity["CRM activity"] --> insight["Partner-level insight"]
insight --> act["Act early"]
act --> surface["Scoped view for partners"]
```
## Use cases
Spot declining engagement early.
Open a partner's overview before a QBR.
Show them their own dashboard.
Surface revenue and cycle in the partner portal.
## Impact
* **CRM-native** - Metrics are computed from live CRM deals and activity.
* **Work where you already are** - Analytics show up in the portal and the CRM, not a separate tool to open.
## Who it's for
Monitors partner health and performance.
Surfaces analytics to partners.
## Works with
{/* CONNECTS:START - generated content goes here */}
Analyze partner-attached pipeline.
Report earned commissions.
Feed the home dashboard.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Integration surface and code.