> ## 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.

# Market Development Funds

> Run your MDF program end to end - allocate budgets to partners, collect requests and claims, and prove ROI, all as CRM-linked records.

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 <div className="group flex items-center justify-between gap-3 px-4 py-3 transition-colors hover:bg-[#FD90FF]/[0.06]">
        <span className="text-sm leading-relaxed text-zinc-700 dark:text-zinc-200">{prompt}</span>
        <button type="button" onClick={copy} aria-label={copied ? "Copied to clipboard" : "Copy prompt"} className={`shrink-0 rounded-md p-1.5 transition-all hover:bg-[#FD90FF]/10 focus:opacity-100 focus:outline-none ${copied ? "text-[#FD90FF] opacity-100" : "text-zinc-400 opacity-0 group-hover:opacity-100 dark:text-zinc-500"}`}>
          {copied ? <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <path d="M20 6L9 17l-5-5" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg> : <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <rect x="9" y="9" width="11" height="11" rx="2" stroke="currentColor" strokeWidth="2" />
              <path d="M5 15V5a2 2 0 0 1 2-2h10" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg>}
        </button>
      </div>;
  };
  return <>
      <p>
        Introw is <strong>headless</strong> by design: run everything here in plain language from Claude, ChatGPT,
        Slack, Teams, or your own CRM through Introw's <a href="/features/developer/mcp">MCP server</a>, with every
        action written straight back to your CRM source of truth. The portal is one surface, never the only one.
      </p>

      {prompts.length > 0 ? <div className="not-prose my-6 overflow-hidden rounded-2xl border border-zinc-200/80 bg-white shadow-sm dark:border-white/10 dark:bg-white/[0.02]">
          <div className="flex items-center gap-2 border-b border-zinc-200/80 bg-gradient-to-r from-[#FD90FF]/10 via-[#FD90FF]/5 to-transparent px-4 py-2.5 dark:border-white/10">
            <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4 text-[#FD90FF]" aria-hidden="true">
              <path d="M12 2.5l2 5.5 5.5 2-5.5 2-2 5.5-2-5.5L4.5 10l5.5-2 2-5.5z" fill="currentColor" />
              <path d="M18.5 14l1 2.6 2.6 1-2.6 1-1 2.6-1-2.6-2.6-1 2.6-1 1-2.6z" fill="currentColor" opacity="0.55" />
            </svg>
            <span className="text-xs font-semibold uppercase tracking-wider text-zinc-500 dark:text-zinc-400">
              Try it from your LLM
            </span>
          </div>

          <div className="flex flex-col divide-y divide-zinc-100 dark:divide-white/[0.06]">
            {prompts.map(prompt => <PromptRow key={prompt} prompt={prompt} />)}
          </div>

          <a href="/headless" className="flex items-center justify-between gap-2 border-t border-zinc-200/80 px-4 py-2.5 text-sm font-medium text-zinc-600 no-underline transition-colors hover:text-[#FD90FF] dark:border-white/10 dark:text-zinc-300">
            <span>See the full headless playbook</span>
            <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <path d="M5 12h14M13 6l6 6-6 6" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg>
          </a>
        </div> : <Card title="See the headless motion" icon="wand-magic-sparkles" href="/headless">
          The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
          from Claude, ChatGPT, Slack, and your CRM.
        </Card>}
    </>;
};

> Market Development Funds is how you put co-marketing money to work: allocate budgets to partners, let them request and claim against those funds, and track the ROI of what they spend, all reconciled to your CRM.

## What this area does

MDF programs usually run in spreadsheets and email, which makes them slow to approve and
impossible to prove out. This area replaces that with a structured program. You create funds with
a budget and period, allocate that budget to partners by segment, and decide whether each
partner gets a fixed amount or draws from a shared pool. Partners then request funds, submit
claims with proof of spend, and report ROI, all through branded forms that write to CRM-linked
records.

Each fund moves through a clear lifecycle: request, approval, claim, ROI, and reimbursement. Your
team reviews submissions in one inbox, marks requests paid, and tracks fund balances and results,
while partners see their allocation and submit from the portal. Because MDF is built on the Forms
platform, the request, claim, ROI, and invoice steps reuse the same review and approval mechanics
your team already knows.

## Why it matters

* **Time to value** - Stand up a full MDF program - budgets, request forms, the claim and approval flow, and ROI reporting - in an afternoon, so funds start driving demand this quarter instead of waiting on a build.
* **Low total cost of ownership** - Partner marketing runs the whole program, from allocation rules to claim approvals, with no engineering.
* **CRM-native** - Requests and claims live as CRM-linked records, so spend ties back to the real pipeline it created and the VP can defend MDF ROI to finance with the numbers already in the source of truth.

## How it fits together

Each fund moves through a clear lifecycle from allocation to proven ROI:

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  allocate["Allocate budget"] --> request["Request"]
  request --> approval["Approval"]
  approval --> claim["Claim with proof"]
  claim --> roi["ROI and reimbursement"]
```

## Capabilities

<CardGroup cols={2}>
  <Card title="Funds & Allocation" icon="sack-dollar" href="./funds-allocation">
    Create funds and allocate budget to partners by segment.
  </Card>

  <Card title="Requests, Claims & ROI" icon="receipt" href="./requests-claims-roi">
    Collect requests and claims, and track the ROI of funded activities.
  </Card>
</CardGroup>

## Who works in this area

<CardGroup cols={2}>
  <Card title="Partner Marketing" icon="user">
    Designs funds and reviews requests and claims.
  </Card>

  <Card title="Partner Operations" icon="user">
    Allocates budgets and configures the request lifecycle.
  </Card>

  <Card title="Finance" icon="user">
    Approves spend and reconciles reimbursements.
  </Card>
</CardGroup>

## Headless

<Headless
  prompts={[
"How much MDF budget does Acme still have available this quarter?",
"Submit an MDF request for Acme: $5k for a regional field event.",
"Show every MDF request and claim still pending approval.",
]}
/>

## All guides

{/* ROLLUP:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="Set up an MDF program" icon="book-open" href="/features/mdf/funds-allocation/guides/set-up-an-mdf-program">
    Stand up a marketing fund end to end: general details, budget allocation by segment, ROI tracking, lifecycle timelines, and a partner-facing overview.
  </Card>

  <Card title="Request funds by email" icon="book-open" href="/features/mdf/requests-claims-roi/guides/request-by-email">
    Let partners request MDF straight from their inbox, with the AI agent filling in the request for them.
  </Card>

  <Card title="Request funds by embed" icon="book-open" href="/features/mdf/requests-claims-roi/guides/request-by-embed">
    Put an MDF request form on your own site or partner page so partners request in context.
  </Card>

  <Card title="Request funds by link" icon="book-open" href="/features/mdf/requests-claims-roi/guides/request-by-link">
    Give partners a shareable link to submit an MDF request in seconds, attributed to the right partner.
  </Card>

  <Card title="Run the MDF request-to-payout flow" icon="book-open" href="/features/mdf/requests-claims-roi/guides/run-the-mdf-request-to-payout-flow">
    Operate the full MDF lifecycle: configure the request, claim, ROI, and invoice steps, then review requests, collect proof of spend, and mark requests paid.
  </Card>

  <Card title="Track ROI on a fund" icon="book-open" href="/features/mdf/requests-claims-roi/guides/track-roi-on-a-fund">
    Measure the return of a marketing fund from partner-reported outcomes and real-time CRM data.
  </Card>
</CardGroup>
