> ## 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.
# Requests, Claims & ROI
> Run the full MDF lifecycle - partners request funds, submit claims with proof, and report ROI, all reviewed in one place.
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.
}
;
};
> Requests, Claims & ROI is the working lifecycle of your MDF program: partners request funds, submit claims with proof of spend, and report results, and your team approves and reimburses, all as CRM-linked records.
## What it does
Every fund runs through a lifecycle: a partner requests budget, you approve it, the partner spends
and submits claims with proof, reports the ROI of the activity, and gets reimbursed. Each step is a
branded form, and submissions land in the same review inbox your team uses for all forms, so
approving MDF works exactly like approving any other submission. You can configure timelines for
each step, so partners know the deadline to claim or report.
ROI is built in. Partners report results through a form, and funds can track real-time ROI from
CRM data, counting objects or summing a property, so you can show the return each fund produced.
When a request is fully reimbursed, you mark it paid, closing the loop with a complete,
CRM-connected record of the spend and its impact.
## The problem it solves
MDF spend without structure is impossible to govern or justify:
* **Requests and claims arrive by email** → Partners submit through branded forms into one inbox.
* **Approvals are inconsistent** → Each step uses the same review and approval mechanics.
* **Deadlines slip** → Configure timelines for request, claim, ROI, and invoice steps.
* **ROI is never proven** → Track ROI from forms and real-time CRM data.
## From problem to solution
Requests, Claims & ROI gives MDF a governed lifecycle. Partners request, claim, and report through
forms; your team approves and reimburses in one place; and ROI ties back to CRM data. The program
becomes auditable and defensible instead of a spreadsheet of receipts.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
request["Request"] --> claim["Claim with proof"]
claim --> reimburse["Approve and reimburse"]
reimburse --> roi["ROI tied to CRM"]
```
## Use cases
Partners request budget through a branded form.
Collect expense claims and documentation.
Track results from forms and CRM data.
Approve, reimburse, and mark requests paid.
## Impact
* **Low total cost of ownership** - Partner marketing runs the lifecycle with no engineering.
* **CRM-native** - Requests and claims are CRM-linked, so ROI ties to real pipeline.
## Who it's for
Reviews requests and claims and proves ROI.
Approves spend and reconciles reimbursements.
## Works with
{/* CONNECTS:START - generated content goes here */}
Claims draw down allocations.
Capture requests and claims as forms.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Integration surface and code.