Segmenting the account base
A segment is a reusable audience that campaigns, plays and reporting all draw on, which is why a loose definition costs more than it looks like it should.
Product walkthrough
See it in RevTech
See how RevOps defines a usable account segment and gives agents a precise population to work instead of a vague market description.
What a segment actually is here
A segment is a reusable account audience — the set of accounts you want a motion to apply to. It is defined once and consumed in several places: campaigns enrol from it, plays target it, and reporting slices by it. That reuse is the whole value, and it is also why segments deserve more care than a saved filter.
The tell that they are operational rather than descriptive is that the same audience builder that defines a segment powers campaign creation. You are not labelling accounts for a chart; you are declaring who a motion will reach.
Building one
Create Segment opens the audience builder, which answers exactly one question: which accounts belong to this segment? Pick an account property, choose an operator valid for its type, enter a value, and add as many conditions as the definition needs. Include and exclude logic is both available and worth using. Most real segments are better described by what they leave out than by another qualifying clause.
The audience preview counts matching accounts as you build. Watch it. A segment that resolves to four accounts is a list, and a segment that resolves to most of your database is a filter you have not finished writing.
- Industry, size, geography, technologies — the properties are your CRM's, not a separate taxonomy
- Each segment card summarizes the criteria behind it, so a definition is readable without opening it
- Search matches name and description — which is a reason to write a real description
The one-sentence test
Before saving, state what the segment is for in one sentence, out loud, in terms of a motion: "mid-market manufacturing accounts we have not touched since the pilot" is a segment. "Enterprise" is a field value.
Segments that fail this test do not cause an obvious problem on the day they are created. They cause one later, when someone enrols a campaign against a segment whose name suggests a motion and whose definition does not support it.
Keeping definitions honest
The accounts inside a segment change continuously even when the definition does not. Companies grow into a headcount band, a territory gets redrawn, an industry field gets cleaned up. A segment that was right in January can be quietly wrong by April without anybody editing it.
Review segment counts on the same rhythm you review targets. If a segment's size has moved substantially and nobody changed the definition, that is information about your account base worth knowing before a campaign discovers it for you.
What to take away
- A segment is an operational object, not a reporting label. Campaigns and plays enrol from it.
- Build against real CRM properties with include and exclude logic — and watch the audience preview count as you go.
- A segment nobody can state the purpose of in one sentence is a filter, not a segment.
- Re-count your segments on a rhythm. Definitions do not drift; the accounts underneath them do.
Try the demo.
See agents carry the repeatable work of GTM across sales, marketing, customer success, and RevOps. Every action prepared, reviewed, and recorded. Fictional data, real product.
Explore the demo