Segmentation boundary
A segmentation boundary is an enforced rule that assigns an account to exactly one segment and governs which motion, pricing and coverage model applies to it.
Segments are useful only when they are boundaries rather than descriptions. A boundary is testable from data the system already holds, employee count, contract value band, industry code, deployment model, and it is enforced at the point of record creation, not applied retroactively in a report.
Boundaries determine routing, quota, coverage ratio, pricing tier eligibility and success model. When they are soft, the same account is enterprise in the marketing model, mid-market in the sales comp plan, and SMB in the support entitlement, and every cross-functional number derived from segment is unreconcilable.
Where it breaks
Segment is a free-text field maintained by whoever last edited the account.
Related terms
- Ideal customer profile (ICP)
- An ICP is a testable specification of the accounts a company can serve profitably and repeatably, expressed in attributes the revenue system can actually evaluate.
- Routing
- Routing is the deterministic assignment of a record to an owner based on registered rules, segment, territory, coverage, and existing account relationship.
- Coverage model
- A coverage model specifies how many accounts of what type each seller or team is responsible for, and what level of attention each account tier receives.
- Revenue architecture
- Revenue architecture is the structural definition of how a company produces revenue: what it sells, to whom, under what constraints, and through which economic logic.
Field notes on this
- Your pricing is a list, not a logic
A price list says what things cost today. It cannot say what to charge the deal in front of you, which is why realised price drifts and nobody owns the drift.