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

# Deal Registration

> Protect partner-owned deals end to end - resellers register opportunities, edit CRM fields they own, and share credit with distributors via multi-tier.

export const Headless = ({children, intro = true}) => {
  const [copied, setCopied] = useState(null);
  const copy = event => {
    const row = event.target.closest("li");
    if (!row) return;
    const text = row.textContent.trim();
    try {
      navigator.clipboard?.writeText(text);
    } catch {}
    setCopied(text);
    setTimeout(() => setCopied(null), 1600);
  };
  return <>
      {intro ? <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> : null}

      {children ? <div className="not-prose" data-prompts="block">
          <div data-prompts="head">
            <span>{copied ? "Copied" : "Try it from your LLM"}</span>
          </div>
          <div data-prompts="rows" onClick={copy}>
            {children}
          </div>
          <a href="/headless/prompts" data-prompts="more">
            See all prompts
          </a>
        </div> : <Card title="See the headless motion" icon="wand-magic-sparkles" href="/headless">
          The agentic motion - lifecycle deep dives and a Claude Code skill library that run your partner program from
          Claude, ChatGPT, Slack, and your CRM.
        </Card>}
    </>;
};

export const Rail = ({children}) => <div className="not-prose" data-overview="rail">
    {children}
  </div>;

export const Impact = ({children}) => <div className="not-prose" data-overview="impact">
    {children}
  </div>;

export const Personas = ({children}) => <div className="not-prose" data-overview="personas">
    {children}
  </div>;

export const Pains = ({children}) => <div className="not-prose" data-overview="pains">
    {children}
  </div>;

> Deal registration is how partners who own the sale protect their investment in a deal. Resellers register to lock in conflict-free credit, work the fields they own on the live CRM record, and where a distributor sits above them, both tiers share attribution and visibility on the same opportunity.

## The problem it solves

<Pains>
  | Without Introw | With Introw |
  | - | - |
  | Partners fear losing their deal | Registration locks the claim |
  | Registering is too slow to bother | Seconds, from wherever they are |
  | Approvals are opaque | Configurable steps, with AI |
  | Partners would need CRM seats | They work the deal without one |
</Pains>

## Impact

A reseller decides where to put their sales capacity. Being the vendor whose registration actually protects their deal is the reason they put it with you.

<Impact>
  for your business

  * **Trustworthy**
    Conflict checks and approvals run before the deal is credited, so a reseller's margin is protected up front
  * **In your CRM**
    Registration, field edits and multi-tier credit all live on the HubSpot or Salesforce record, reconcilable like any deal
  * **No new tool**
    Partners register and update from the portal, their own CRM, email, chat or an AI assistant

  for your partners

  * **Self-serve**
    They register, edit the fields you open, manage line items and quote, without a CRM seat
  * **Enabled**
    The claim is what makes investing in the deal rational, and they can see it was honoured
  * **Efficient**
    No email to the vendor for a field change, because the field is theirs to change

  [A day in the life of a reseller](/days-in-the-life/reseller)
</Impact>

<Personas>
  * **Partner Managers** - the rules that protect resellers
  * **Partner Ops / RevOps** - multi-tier credit that holds up
  * **Resellers** - deals they can claim and run
</Personas>

## How this area works

Deal registration is the motion where the partner, not the vendor, closes the deal. A reseller registers an opportunity to claim it, which checks for channel conflict and routes through your approvals so their margin is protected from the direct team and other partners. Once a deal is shared, resellers can edit the specific fields you allow on the CRM record, manage line items, and create quotes, all without a CRM seat.

The pieces chain from the partner's claim to a credited, shared deal.

**Where this sits in a setup.** Registration is the first thing most partners actually do, so it lands early. The [reseller](/tracks/reseller), [co-sell](/tracks/co-sell) and [distributor](/tracks/distributor) tracks sequence it with attribution and conflict checks.

<Rail>
  * ![A deal registration form in the builder, with the fields a partner fills in on the canvas and, for the selected Deal amount field, the HubSpot deal property it writes to.](https://assets.introw.io/docs/features/deal-registration/registration/shots/form.png)

    [**Deal Registration**](./registration)

    Claim the deal, checked and approved.

    [How to · 4 guides](./registration/technical)

  * ![The channel conflict check on a deal registration form, screening every submission against the CRM for an overlapping deal before the registration is accepted - here against every deal that is not Closed Lost.](https://assets.introw.io/docs/features/deal-registration/channel-conflict/shots/analysis.png)

    [**Channel Conflict**](./channel-conflict)

    Screened against direct and partner pipeline.

    [Read more](./channel-conflict)

  * ![A registered deal open from the shared board, with its CRM properties, the attributed partner, and the thread both companies work in.](https://assets.introw.io/docs/features/deal-registration/shared-pipeline/shots/deal.png)

    [**Shared Pipeline**](./shared-pipeline)

    Give resellers a CRM-drawn view of every deal they own.

    [How to · 2 guides](./shared-pipeline/technical)

  * ![The Quotes & Line Items controls on a deal embed: whether partners see line items and pricing, may edit them, and may create and publish quotes, plus which segments may quote, the HubSpot template used and whose company heads the quote.](https://assets.introw.io/docs/features/cpq/quotes/shots/config.png)

    [**Self-serve quoting**](/features/cpq/quotes)

    Let resellers assemble line items and build quotes on their deal.

    [How to · 1 guide](/features/cpq/quotes/technical)

  * ![A partner record, whose tier, owner and attributed deals are what a two-tier program routes a registration through.](https://assets.introw.io/docs/features/deal-registration/multi-tier/shots/partner.png)

    [**Multi-tier Attribution**](./multi-tier)

    One deal, a reseller and a distributor.

    [How to · 1 guide](./multi-tier/technical)
</Rail>

For two-tier channels, the same deal can carry both a reseller and a distributor through multi-tier attribution in your CRM. Both partners get credit, and the visibility they need on the same opportunity. Everything writes back to HubSpot or Salesforce, so partner-owned pipeline stays real and reconcilable.

The pieces chain from the partner's claim to a credited, shared deal.

## Run it from your AI assistant

<Headless>
  * Register a deal for Acme: \$120k ARR, closing end of Q3, contact [jane@acme.com](mailto:jane@acme.com).
  * Show every deal registration pending approval or in channel conflict.
  * Approve the registration from Globex and link it to the existing CRM deal.
</Headless>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.