> ## 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.
# Tiers
> Build tier programs with clear requirements and benefits, show partners how to level up, and keep every partner's tier synced to your CRM.
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.
}
;
};
> Tiers give your program a ladder: every partner can see what their tier unlocks and what it takes to reach the next one, and their status stays in sync with your CRM.
## What it does
Tiers let you build one or more tier programs, each a set of levels like Gold,
Silver, and Bronze. For every tier you spell out two things partners care about most:
the **requirements** to reach it and the **benefits** it unlocks. Requirements can be
simple statements, checklist items, or goals tied to real progress, and benefits make
the value of leveling up concrete.
Each tier gets its own identity, with a name, color, and downloadable badge a partner
can show off. Partners are assigned to a tier individually or in bulk, and because
Introw sits on your CRM, a partner's tier syncs to a CRM property, so the rest of your
go-to-market motion can see and act on it. The result is a transparent ladder that
motivates partners to invest more in the relationship.
## The problem it solves
Tiering often exists on a slide but not in a way partners can act on:
* **Partners do not know how to level up** → Published requirements and benefits make the path to the next tier obvious, so partners know exactly what to do.
* **Tier status is invisible to the rest of the business** → Each partner's tier syncs to the CRM, so sales and ops can see and act on it without asking.
* **Tiering is a static label, not a motivator** → Goal-based requirements tie tiers to real progress, so the ladder actually drives behavior.
* **Maintaining tiers is manual work** → Partner ops configures programs, tiers, and benefits with no-code and assigns partners in bulk.
## From problem to solution
Tiers turn a tiering policy into a working program. Partner ops builds the levels and
their requirements and benefits once, partners see a clear ladder to climb, and every
partner's tier flows back to the CRM so the whole revenue team works from the same
status. The program motivates partners instead of just labeling them.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
build["Build tiers, requirements, benefits"] --> qualify["Partner meets requirements"]
qualify --> assign["Tier assigned"]
assign --> sync["Synced to CRM"]
```
## Use cases
Show partners the requirements and benefits for each tier so leveling up is clear.
Set up separate tier programs for different partner types or motions.
Make tier requirements measurable with goals that track real progress.
Sync each partner's tier to a CRM property for the rest of the business.
## Impact
* **Low total cost of ownership** - Partner ops builds and maintains tier programs, requirements, and benefits with no-code.
* **CRM-native** - Each partner's tier syncs to the CRM, so partner status is visible everywhere your team already works.
## Who it's for
Builds tier programs and keeps tier assignments and CRM sync consistent.
Tracks their tier status and what it takes to reach the next level.
## Works with
{/* CONNECTS:START - generated content goes here */}
Set discounts by tier.
Tiers organize the partner list.
Sync tier to a CRM property.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Integration surface and code.