> ## 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.
# Report Builder
> Answer any question about your partner program by building custom reports from CRM and Introw data - no SQL, no BI project, no engineering.
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.
}
;
};
> When someone asks "how much pipeline did partners source last quarter?", you should be able to answer in minutes, not wait on RevOps. The report builder lets you build that report yourself from live CRM and Introw data.
## What it does
The report builder lets you create custom reports without code. You pick a data source, from CRM
objects like deals, contacts, and companies, to Introw-native sources like partner engagement,
assets, certifications, commissions, and MDF, then choose how to aggregate and group it. You select a
visualization, a bar chart, line chart, pie chart, or single number, and apply filters, date
properties, and grouping to shape the answer.
Reports respect partner access, multi-currency, and your fiscal year, so the numbers are correct and
scoped. You can save reports, control who can view or edit them, export the raw data to CSV, and use
saved reports as the building blocks for dashboards and portal embeds.
## The problem it solves
Partner reporting usually means waiting on someone else or wrestling with a BI tool:
* **Every question is a RevOps ticket** → Build the report yourself in minutes.
* **The data lives in two systems** → Report on CRM and Introw data together.
* **BI tools need specialists** → No code, just a guided builder.
* **Numbers are hard to trust** → Reports respect access, currency, and fiscal year.
## From problem to solution
The report builder puts answers in the hands of the people who run the program. Pick a source,
shape it, visualize it, and you have a trustworthy report ready to share or drop into a dashboard.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
source["Pick a data source"] --> shape["Shape metric and grouping"]
shape --> filter["Filter the audience"]
filter --> chart["Pick the chart"]
```
## Use cases
Build a report in minutes.
Report across both sources.
Respect access and currency.
Reuse reports as building blocks.
## Impact
* **Low total cost of ownership** - Partner ops builds reports without engineering.
* **CRM-native** - Reports are computed from live CRM data.
## Who it's for
Builds and shares reports.
Defines metrics and data sources.
## Works with
{/* CONNECTS:START - generated content goes here */}
Reports power dashboards.
Export to Power BI.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Integration surface and code.