Target Market Market

It defines where Oliv is best positioned to win. Accounts outside this zone can still buy, but they should not consume priority sales, CS, or implementation capacity unless a leader approves the exception.

---

Winning Zone

Attribute	Ideal	Good	Rejected
Company size	200 to 5,000 employees	50 to 200 employees with mature RevOps	Under 50 employees
Revenue Motion	Mid-market, enterprise, or hybrid	High velocity with strong volume	Pure self-serve only
CRM	Salesforce or HubSpot actively used	CRM with accessible API	No CRM discipline
Stack	CRM plus calls, email, warehouse, engagement tools	CRM plus at least one major signal source	Data trapped in manual notes
Pain	Forecast, CRM hygiene, handoff, prospecting, renewal risk	One clear workflow bottleneck	No owned revenue process
Buyer	RevOps, CRO, VP Sales, VP CS, CFO	Founder-led with budget	Individual user only
AI Readiness	Wants agents inside current workflows	Exploring AI this quarter	AI blocked with no sponsor

Priority Segments

Segments	Primary Pain	Best Starting Point
RevOps-led Mid-Market	CRM is dirty and process changes faster than systems.	Oliver + CRM Manager
Sales-led Growth Team	Pipeline coverage is inconsistent.	Prospector + Researcher
Forecast-Sensitive Team	Commit is inspected manually and still slips.	Forecaster + Deal Driver
CS-Led Account Base	Renewal risk appears too late.	Portfolio Manager + Retention Forecaster
Enterprise Workflow	Complex stakeholders, POC, legal, and procurement.	Researcher + MAP Manager + Case Builder

Disqualification Signals

• No CRM owner
• No current revenue process to improve
• Buyer wants a chatbot instead of workflow execution
• Customer expects Oliv to replace the CRM
• Procurement blocks all useful data access
• Team wants a cheap note taker only

Owner Notes

Oliver should review target market rules quarterly and whenever win or loss patterns change. Prospector should use these rules before ranking accounts or preparing outreach.

Segment-Specific Notes

Segments	What makes it attractive	What to watch
Mid-Market Revenue Teams	Enough process complexity for agents to matter, but still fast enough to deploy in weeks.	Buyer may want broad transformation before choosing first workflow.
Enterprise Teams	High value workflows, clear need for auditability, strong forecast and handoff pain.	Procurement, security, and technical access can slow deployment.
CS Heavy Businesses	Renewal and expansion data lives across calls, tickets, usage, and CRM.	Page and demo language must avoid sales-only framing.
RevOps Lead Teams	Strong owner for process, fields, rules, and reporting.	RevOps may be overloaded and need a narrow first launch.

Trigger Events

Events	Why it matters	Recommend angle
New CRO, VP Sales, or RevOps	New leader is likely reviewing operating cadence.	Your process can update faster than your systems.
Forecast Miss	Leadership is ready to inspect pipeline quality.	Forecast risk is usually a context and data problem.
CRM Cleanup Project	RevOps already feels the data pain.	Clean records automatically from real activity.
CS Segmentation Project	Team is trying to cover more accounts without more headcount.	Agents can run the digital motion and escalate exceptions.
Tool Consolidation	CFO or RevOps wants fewer vendors.	Keep the stack, remove the manual work between tools.

Agent Behavior

• Prospector: Rank accounts and reject poor-fit companies before outreach
• Researcher: Tailor account briefs to the segment and trigger
• Deal Assistant: Explain why the account is worth pursuing
• Portfolio Manager: Identify whether a customer belongs in scaled, mid-market, or enterprise CS motion
• Oliver: Propose ICP updates when win/loss or adoption patterns shift

How This Page Gets Used In Practice

This page should be the first stop before any account list is worked. A good target account is not just a company that matches firmographics. It has a process problem Oliv can actually operate inside.

When Prospector receives a new account list, it should make three decisions before suggesting outreach:

1. Is the company in the winning zone?
2. Which workflow pain is most likely to exist?
3. Which persona should be contacted first?

If the answer to the second question is unclear, the account should not be pushed into a high-touch motion yet. It can stay in nurture or light research until a trigger appears.

Working Rule

We would rather work 50 accounts with a real operating reason than 500 accounts that only match company size.

How This Page Gets Used In Practice

Strong Fit

Acme Systems is a 900-person B2B SaaS company using Salesforce, Gong, Outreach, and Snowflake. They recently hired a VP RevOps and are recruiting three Sales Ops roles. The likely wedge is CRM Manager plus Forecaster because the team is scaling process control.

Weak Fit

BrightDesk is a 22-person startup with founder-led selling and no dedicated CRM owner. They may like the idea of agents, but there is not enough operating structure for Oliv to improve yet.

Change Log Guidance

Oliver should propose an update to this page when the same pattern appears in three or more wins, losses, or stalled deployments. Example: if CS-led opportunities start converting faster than sales-led opportunities, the CS segment should move from secondary to priority.