How to Set Sales Quotas for SaaS Teams

Quota setting is one of the highest-stakes decisions in SaaS sales leadership. Set too high and the majority of the team misses, morale deteriorates, and attrition increases — costing more in recruiting and ramp than the quota aspirations were worth. Set too low and the team hits easily, compensation costs exceed plan, and the business undershoots its revenue target.

The right quota is one that is achievable for a fully ramped, competent rep working a full pipeline with good territory coverage — roughly 60–70% of the team should be able to hit it in a normal quarter. It should stretch without breaking, be based on realistic data rather than optimistic top-down targets, and be differentiated for reps in different territory conditions.

---

The Quota Setting Framework

Quota setting begins with the revenue target — the number the business needs to achieve to hit its growth objectives. This is a top-down constraint. The quota model must, in aggregate, produce that number with reasonable probability.

The aggregation formula:

`Total quota = Business revenue target ÷ (1 - expected attrition rate - expected underperformance buffer)`

If the business needs $10M ARR and expects 15% team attrition and 10% underperformance buffer:

`Total quota = $10M ÷ (1 - 0.25) = $13.3M`

This total is then distributed across the team based on territory capacity, rep seniority, and ramp status.

Not all territories are equal. A territory with 500 ICP accounts and low competitive penetration can support a higher quota than a territory with 150 ICP accounts and two entrenched competitors. Quota set without territory capacity analysis is arbitrary — and the rep in the under-resourced territory will miss regardless of skill or effort.

Territory capacity assessment:

- Total addressable accounts in the territory (matching ICP criteria)

- Average deal size for the territory segment

- Competitive win rate in the territory

- Historical conversion rate from the territory

- Pipeline coverage available at quota assignment

From this analysis, derive the realistic annual revenue potential for the territory. Quota should be set at a fraction of this potential — typically 25–40% — to leave room for pipeline development time, deal cycles, and normal conversion variability.

What did reps at this level in this segment achieve last year? What was the distribution of attainment — what percentage hit >100%, 80–100%, 60–80%, <60%? What was the median attainment?

Quota that produces 60–70% attainment at the median is well-calibrated. Quota that produces 40% attainment at the median is too high. Quota that produces 90% attainment at the median is too low.

If historical data shows that 40% of the team hit quota last year at the current quota level — that's not a talent problem. It's a quota problem. Either the territories are undersized, the product-market fit doesn't support the deal velocity assumed, or the ramp model is incorrect.

New reps don't produce at full quota for 6–9 months. A rep hired in January with a 6-month ramp should not carry a full annual quota — they carry a ramped quota that reflects their expected productive output during their first year.

Standard ramp quota schedule:

- Months 1–2: 0% of full quota (training and initial pipeline development)

- Months 3–4: 25% of full quota

- Months 5–6: 50% of full quota

- Months 7–9: 75% of full quota

- Month 10+: 100% of full quota

Set compensation expectations accordingly — OTE during ramp should reflect the ramped quota, not the full quota, to avoid the attrition that comes from a rep realising in month 4 that their full-year OTE is mathematically impossible.

SMB AEs, mid-market AEs, and enterprise AEs carry different quotas — not just because deal sizes differ, but because deal velocities, pipeline coverage requirements, and selling complexity differ.

SMB quota is driven by volume — number of deals × average deal size × expected close rate. The SMB rep needs a large enough pipeline to cycle through deals at volume.

Enterprise quota is driven by fewer, larger deals — which means single deal outcomes have a larger impact on quarterly attainment. Enterprise quotas must account for the higher variance in deal timing that comes with 9–12 month cycles.

---

The Quota Setting Mistakes to Avoid

A quota derived only from the board's revenue expectations, divided by headcount, with no reference to territory capacity or historical attainment, is a target, not a quota. It may be the number the business needs — but if the territory capacity doesn't support it, it won't be achieved regardless of how it's labelled.

Treating new hires as full quota carriers from day 90 produces compensation mismatches and attrition. The rep who is expected to achieve $800K in their first 9 months when the team's average ramp is 7 months will leave — not because they can't sell, but because the quota math makes their OTE unachievable.

Territory equity is as important as quota fairness. Reps in over-resourced territories achieve quota with less effort; reps in under-resourced territories miss with more effort. This drives attrition in the wrong places and gaming behaviour (reps seeking territory transfers) that obscures the quota model's real performance.

Mid-year quota increases — particularly those driven by senior leadership revising revenue targets upward without changing the variables that support those targets — destroy sales team trust faster than almost any other management action.

Quota and OTE are inseparable. The rep needs to know that hitting quota delivers their promised OTE — not a number 20% below it because accelerators don't kick in until 110%.

---

How Brazn Supports Quota Setting

Brazn's pipeline analytics and MEDDPICC scoring provide the territory-level data that makes evidence-based quota setting possible — actual deal velocity, average deal size by segment, close rates by territory and rep, and pipeline coverage against quota at any point in the year. For RevOps teams building the annual quota model, Brazn provides the ground-truth performance data that replaces management intuition with empirical inputs.

---

3. How to Set Up a Sales Pipeline in HubSpot

---

How to Set Up a Sales Pipeline in HubSpot

A HubSpot sales pipeline that's set up correctly gives sales managers real-time visibility into deal progress, forecast accuracy, and rep performance. A pipeline set up incorrectly — too many stages, stages that don't reflect buyer behaviour, no required field gates — produces a pipeline that looks full but tells you very little about what's actually happening in your deals.

The setup takes 2–4 hours to do properly. The return on that investment is a pipeline that the whole team trusts — and a forecast that reflects reality rather than rep optimism.

---

Step 1: Define Your Pipeline Stages

Pipeline stages should reflect the buyer's journey, not the vendor's internal process. Each stage represents a specific milestone that the buyer has reached — not a task the rep has completed.

- Each stage represents a specific buyer commitment or milestone

- Stage names should be meaningful to both rep and manager

- There should be a clear, specific exit criterion for each stage

- Typical SaaS pipeline has 5–7 stages — more than 8 creates confusion and inconsistent usage

| Stage | Name | Exit Criterion | Default Probability |

| --- | --- | --- | --- |

| 1 | Qualified | ICP confirmed, pain hypothesis validated, next step agreed | 10% |

| 2 | Discovery Complete | Pain quantified, business case hypothesised, key stakeholders identified | 20% |

| 3 | Evaluation | Demo complete, success criteria agreed, technical evaluation in progress | 40% |

| 4 | Proposal | Commercial proposal delivered, EB engaged, decision timeline confirmed | 60% |

| 5 | Commit | Verbal agreement, legal/procurement in progress | 80% |

| 6 | Closed Won | Contract signed | 100% |

| 7 | Closed Lost | Deal lost or withdrawn | 0% |

Adjust stage names and criteria to match your specific product, sales cycle, and team's language. The specific names matter less than the consistency with which they're applied.

---

Step 2: Configure Required Properties at Each Stage

HubSpot's required properties feature (Professional and Enterprise tiers) prevents a deal from advancing to the next stage unless specific fields are completed. This is the most important configuration step for pipeline data quality.

Stage 1 → Stage 2:

- Primary Contact (association)

- Company (association)

- Deal Value (estimate)

- Primary Pain (custom text field)

- Lead Source

Stage 2 → Stage 3:

- Quantified Business Impact (custom text field)

- Key Stakeholders Identified (custom text field)

- Next Follow-up Date

Stage 3 → Stage 4:

- Decision Maker Identified (custom text field)

- Decision Timeline (custom date field)

- Competitors (custom text field)

- Success Criteria (custom text field)

Stage 4 → Stage 5:

- Economic Buyer Name (custom text field)

- Economic Buyer Engaged (checkbox)

- Expected Close Date (confirmed)

- Contract Value (confirmed)

Stage 5 → Closed Won:

- Close Date (actual)

- Win Reason (custom picklist)

- Contract Value (final)

Stage 5 → Closed Lost:

- Loss Reason (custom picklist)

- Competitor Won (custom text, if applicable)

- Close Date (actual)

---

Step 3: Create Custom Deal Properties

Beyond HubSpot's default deal properties, create the custom fields that make the pipeline genuinely useful for your team. For MEDDPICC-based selling:

- Metrics (Rich text)

- Economic Buyer (Single line text)

- Decision Criteria (Rich text)

- Decision Process (Rich text)

- Identify Pain (Rich text)

- Champion (Single line text)

- Competition (Single line text)

- MEDDPICC Score (Number, 0–16)

- Deal Health Score (Number, 0–100)

- Primary Pain (Single line text)

- Compelling Event (Single line text + date)

- Next Step (Single line text)

- Next Step Date (Date)

- Win/Loss Reason (Dropdown)

- Product Line (Dropdown)

- Deal Source (Dropdown)

---

Step 4: Set Up Automation

HubSpot's workflow automation reduces admin and ensures pipeline hygiene without manual enforcement:

- No activity reminder: If a deal has had no activity in 14 days and is in Stage 2–5, create a follow-up task for the rep owner

- Close date approaching: If close date is within 7 days and deal is not in Stage 5+, create an "At-risk close date" task for the rep and their manager

- Stage stuck: If a deal has been in the same stage for more than [stage-specific SLA], notify the rep's manager

- Lead assignment: Auto-assign new deals to reps based on territory, company size, or round-robin

- Deal creation from form: Automatically create a deal when a qualified form is submitted

- Task creation on stage change: When a deal moves to a new stage, automatically create the appropriate next task for the rep

---

Step 5: Configure Views and Reports

- Customise deal cards to show: Deal Name, Close Date, Deal Value, Next Step Date, and MEDDPICC Score

- Group deals by owner for pipeline review meetings

- Add colour-coding: red for deals past close date, yellow for deals with no activity in 7+ days

- Pipeline by stage (current): Deal count and value by stage, updated in real time

- Forecast report: Deals closing this month/quarter by rep, with weighted forecast

- Stage duration analysis: Average days in each stage, by rep and overall

- Win/loss reason breakdown: Closed deals segmented by win/loss reason

- Activity by rep: Calls, emails, and meetings per rep per week

- Deal created vs closed: New pipeline added vs deals closed, tracked weekly

---

Step 6: Connect Brazn for AI Enrichment

With the pipeline structure in place, connect Brazn to enrich deal records automatically:

- Map Brazn's MEDDPICC extraction output to the custom MEDDPICC properties created in Step 3

- Configure Brazn's call summary output to create a Note on the deal record after each call

- Map Brazn's deal health score to the Deal Health Score custom property

- Set up workflow triggers based on the Deal Health Score — flagging deals below threshold for manager review

The HubSpot pipeline configuration provides the structure; Brazn provides the intelligence that keeps the fields populated, current, and trustworthy.

---

How Brazn Completes the HubSpot Pipeline

A HubSpot pipeline configured according to this guide provides the structure for accurate, manageable pipeline tracking. Brazn provides the AI layer that keeps it populated — automatically updating MEDDPICC fields from call analysis, writing deal summaries from every customer interaction, and flagging pipeline health issues before they become forecast misses. Together, they produce a HubSpot pipeline that functions as a genuine source of truth rather than an aspirational data model that the team has agreed to maintain but doesn't.

---

####

Book a demo to see how Brazn AI fits into your sales stack.

About the Author

Alex Margarit, Sales AI Expert, SaaS Sales Leader, BMC, ServiceNow, Docusign — 25+ years in SaaS sales.