Tuning your ICP corpus
Help-center article "Tuning your ICP corpus" for GTM engineers, covering how to edit the corpus, role-based apply permissions, member proposals, and versioning/rollback.
Your ICP corpus is the editable brain behind Tipoff's account scoring. It's the working definition of who your ideal customer is — a set of example accounts plus the attributes and weights that describe them. Every time Tipoff tiers a company against your ICP, it's comparing that company to your corpus. Tune the corpus well and your A/B/C tiers stay sharp; let it drift and your signal-to-noise degrades. As a GTM engineer, this is one of the highest-leverage controls you own.
What the corpus drives
The corpus feeds tiering and account scoring across your workspace — the signals feed, reveal matches, and any downstream routing to your CRM or sequencer. A change here re-tiers accounts everywhere, so treat it like production config, not a scratchpad.
Editing the corpus
- Open Settings → ICP Corpus.
- Add or remove example accounts that represent your best-fit (and clearly-not-fit) customers.
- Adjust attributes and their weights — firmographics, tech signals, segment markers — to reflect what actually predicts a win.
- Use Preview to see how a sample of accounts would re-tier before anything goes live.
- Save your work as a draft, then Apply to publish the new version.
Who can apply changes
Only admins and users with the corpus manager role can apply a corpus version. Because a single edit re-scores every account and can reshuffle what your whole team works, apply rights are deliberately narrow — this prevents an accidental weight change from silently reshaping everyone's pipeline.
Proposing edits as a member
Members can still contribute without apply rights:
- Make your edits in the corpus editor.
- Choose Propose changes instead of Apply.
- Add a short note explaining the rationale.
Your proposal lands in the review queue, where an admin or corpus manager can preview the diff, then approve and apply it — or send it back with comments.
Versioning and rollback
Every applied change creates a numbered version with the author, timestamp, and a diff against the prior version. Open Version history to compare any two versions side by side. If a change hurts tiering quality, select an earlier version and Roll back — this republishes it and re-tiers your accounts against the restored definition. Nothing is destructive; you can always move forward or back.
Related: How account tiering works, Roles and permissions, and Connecting Tipoff to your CRM.