Know what the number means.
Plain explanations and blank worksheets for anyone who has to say exactly where a forecast number comes from and why it moved.
28.91% of a year's billings landed in the fourth quarter of 2025 at the middle company of 14 listed US software firms, against 22.72% in the first quarter. An even split would hand every quarter the same share.
Read the forecast notes See how the year splits
To split next year's quota by quarter and month and pace the current quarter, a team can use the Quota Forecast Quarter Shape Workbook: see what its sheets hold
What you get here
This site is for the person who has to explain a forecast number to someone else. It gives you:
- A quarter-shape table showing how listed US software companies split each year of billings across the four quarters, from their SEC filings.
- Selling days for 2026 and 2027 by month and quarter, from the federal holiday calendar.
- Plain-English notes on how a forecast number is built and why it moves, sorted by topic.
- One printable sheet for writing down what each forecast category meant on a call.
It is free, needs no sign-up and never asks for your deal data.
Topics
Forecast definitions
What forecast categories and weighted deal amounts mean in tools like HubSpot and Pipedrive, and how to use them consistently.
Newest: Renewal close dates: 2 windows for Closed Won and Closed Lost
Every note in this topic
- Renewal close dates: 2 windows for Closed Won and Closed Lost
- SMS length limits: 3 checks before a follow-up
- Small sales team CRM: 4 checks before you choose
- Okta admin console session timeout: 6 checks
- SUMIF totals by deal stage: 5 forecast checks
- Rollup limits: 4 checks before a deal total column
- Recognized and deferred revenue: 3 invoice figures
- SKU rules: 3 checks for annual and multi-year deals
- Gong to-do rules: 7 checks before your deal review
- Failed payment: 2 subscription changes to check
- Commission payout mistakes: 4 checks before quarter close
- Sales tool review figures: 4 checks before you trust one
- 5 lead rules to settle before a deal enters your pipeline
- Dynamics 365 Sales scoring needs 2 deal-count minimums
- Hold deals at $10,000 or more: 8 steps to set the rule
- Daily flow email caps: 3 domain rules to check
- AVERAGEIFS errors that skew average deal size: 4 checks
- Currency amount examples: 3 checks before a deal total
- Commission automation figures: 5 to test on your cycle
- CRM seat prices to check before adding a seat: 5 steps
- Stage report audit: 4 checks before weekly review
- Deal label caps: 100 on one deal, 1000 in an account
- What 100 percent means in 4 tools before the weekly call
- Forecast category rules in 4 tools before the call
- Sales calculation tools: 4 options for deal arithmetic
- CRM validation: 4 tools to govern forecast data entry
- Archive item cap: 300,000 before the weekly board
- File size limits: 8 checks before evidence uploads
- Verify 8 catalog steps for accurate forecast totals
- Product catalog: 7 rules for the weekly forecast
- Activity linking: 8 rules for deals and visibility
- Stage count warnings at 10, above 8, and below 3
- Sales data imports: 5 field checks before upload
- Log seller emails to the right deal: 4 CRM rules to check
- Forecast period rules: read 4 before the weekly number
- Where a software deal came from across 4 tools
- Line-item rounding rules in 4 sales tools
- Deal and quote line-item rules from 4 publishers
- Weekly pipeline export checks for 4 vendors
- Export a weekly pipeline snapshot in 4 systems
- Recover deleted sales records with 4 retention checks
- Choose a deal field type: 4 systems and storage rules
- Bulk-edit sales records: 4 checks before saving changes
- Weighted deal amount: 5 fields to check HubSpot, Pipedrive
- Pipeline, Best Case, Commit: Forecast Categories Explained
Forecast meetings
Run a forecast call that settles what it needs to, with each assumption written down so it can be checked later.
Newest: Deal confidence 0 to 100: 2 closed statuses set the value
Every note in this topic
- Deal confidence 0 to 100: 2 closed statuses set the value
- 3 Microsoft Forms caps to set before a weekly forecast
- 3 items to settle before a rep's old laptop is reissued
- 2 AnyDesk password lengths for a rep's forecast PC
- State leave caps: 3 states to check for rep coverage
- 3 IT security records to name before a budget review
- Sales call recording: 10 wiretap exceptions that don't fit
- Minnesota aggrieved person and contents: 2 wiretap terms
- Windows restart timers: 3 clocks for a forecast call
- Rep offboarding: 3 access controls before the last workday
- 2FA enrollment: 4 phone and app checks for reps
- Chrome update settings for rep laptops: 3 numbers to set
- 2 errors in AE capacity when a rep leaves mid-quarter
- New rep account coverage training: 2 timing windows
- 3 Microsoft Forms response caps to size a weekly update
- Microsoft 365 and Okta idle sign-out: 7 checks
- Recorded call interception: 3 Minnesota terms to check
- 6 wipe limits to check before reissuing a rep device
- Top sellers: 4 measures to compare with the team
- Teams forecast calls: 2 settings and a dial-in rule
- Comp maturity score: 2 benchmark figures to check beside it
- Rep laptop checks before corporate access: 3 tests
- Montana recording penalties: 4 cases for a forecast call
- Dataverse relationship types: 2 links for deals
- Dropbox sharing checks for a departing rep: 3 controls
- Deal review call: 4 checks on roles, calendar, deck, chat
- Quota and plan changes: 4 figures on rep timing
- Odoo lead assignment: 6 checks for deal ownership
- MEDDICC figures: 6 checks before a forecast call
- Forecast call setup: 3 settings to check first
- Phishing figures: 6 checks for a security review call
- AE capacity planning: 4 checks before a review
- Access log checks: 4 steps after a shared login changes
- Weekly pipeline review: 3 items before the call
- Deal review call comments: 4 steps to tag a teammate
- Slido poll results: 3 rules for forecast calls
- New AE ramp rates: 3 factors for quarterly capacity
- Call log timestamps: 7 checks for fractional seconds
- Deal review: 3 call and reminder settings to check
- AI call summary: 5 fields to check before a review
- Sales goal for a forecast call: 3 checkable parts
- Median and mode: 2 measures beside average deal size
- Forecast call agenda: 5 checks before the meeting
- Deal score refresh: 4 clocks before the weekly forecast
- Check 4 currency locks before the weekly deal total
- Forecast data refresh limits: 9 figures to read each week
- Sales forecast methods: 4 CRM tools and their outputs
- Pipeline trend report: 6 steps to compare successive totals
- Deal score limits: 4 checks before turning scores on
- Forecast refresh troubleshooting: 3 steps to trace totals
- Pipeline report errors: 4 mistakes to trace in totals
- Pipeline aggregation tools: 4 options for deal rows
- HubSpot offline cache: 50 records for each type, 200 total
- Forecast pull published caps: 8 figures from vendor docs
- Sales forecast notes: 4 tools for deal review context
- Pipeline report filters: 4 tools for coverage reviews
- Pipeline count inflation: 6 mistakes behind the total
- 8 AI scorecard settings for uniform call reviews
- Forecast extract validation: 5 checks for missing rows
- Forecast call co-organizer roles: 5 rules to check
- Conditional pipeline sums: 4 mistakes that alter totals
- Commit evidence: 5 checks before promising a close date
- Calendar availability: 4 tools for forecast call timing
- Sales forecast calculation tools: 5 tools compared
- Report visibility checks across 4 tools before the call
- Pipeline risk assessment: 4 evidence types compared
- Deal formula limits: 70 parentheses, 40 fields, 10 fields
- Reconcile sales dashboard totals with 4 checks
- Check 8 data rules before the weekly sales call
- Screen sharing limits: 6 checks for forecast calls
- Recurring forecast calls: 7 scheduling rules
- Check 6 caption settings before the weekly sales call
- AI call scorecard checks: 5 rules before the forecast
Deal movement
Find out why a deal's expected close date moved, using the change history your sales tool keeps and a simple log.
Newest: Recover a deleted rep's Microsoft 365 mailbox in 30 days
Every note in this topic
- Recover a deleted rep's Microsoft 365 mailbox in 30 days
- Closed deal record changes: 3 things to log later
- Close-date imports: 6 checks for date errors
- CSV deal export: 5 checks before loading a table
- 3 time zone checks before you trust a deal close date
- Seat overage after a mid-term upgrade: 3 figures
- GitLab order processing dates: 4 published rules
- Stalled deal benchmarks: 2 survey figures to compare
- Stale deals: 5 checks before your next forecast call
- ISO week dates: 3 checks before a close date load
- Zoho Mail forwarding limits: 3 caps before a handoff
- Mid-term upgrade deal amount: 4 steps to explain it
- Deal risk scores: 2 rules before the review call
- CRM logging: 4 habits to keep deal records current
- Deal change records: 3 tools and their limits
- Quote expiry checks: 5 steps before you move a close date
- Microsoft 365 audit log retention: 5 rules to check
- Dynamics 365 task sync: 5 checks for missing tasks
- Cancellation billing day: 8 steps to check credit
- Stripe subscription schedule phase limit: up to 10 phases
- STL settings for a monthly bookings trend: 4 checks
- Reopen a won or lost deal in 5 CRMs: what to re-check
- Pipedrive deleted products: check the 30-day restore window
- Compare close dates: 3 rules for date and time fields
- Stalled deal alert: 6 steps to set it up in your CRM
- Funnel chart totals: 3 metrics and why deals repeat
- Close date mismatches: 5 mistakes in forecast records
- Date and time formats: 4 tools for forecast exports
- Deal link caps: 10,000 in HubSpot, 1,000 in Close
- Stale deal signals: 5 publishers to check before the call
- Catalog price before the software deal total: 2 checks
- Activity linking cap: 2,000 activities and 5 deals
- Due date checks for sales follow-ups: 8 rules
- Check deal stage duration across 4 CRM tools
- Stage duration: 8 checks before the weekly call
- Deal field edit history: 6 Freshsales tracking rules
- Verify 8 date and score rules for forecast accuracy
- Forecast rules for verbal commitments: 7 rules
- Deal forecast months: date rules across 4 tools
- Quota line checks across 4 sales publishers
- Assign leads equally across 5 CRM platforms
- Required-field rules in 4 tools before stage change
- Quote checks before the forecast call: 4 tools
- Meeting reminder and booking rules in 4 tools
- Weekly deal review filters across 4 sales systems
- Sales follow-up checks for 4 task attributes
- Recover deleted sales records: 4 CRM restore rules
- Find deal attachments: 4 publisher rules to check
- Check the buying company on a deal: 5 record limits
- What 3 systems store on a lost deal: 6 fields
- Open, won, and lost stage rules in 4 sales tools
- Close date change log: why the date moved
Scenario records
Write down the assumptions behind best-case and worst-case versions of a forecast so anyone on the team can follow them.
Newest: 2 cloud flow options with 250,000 requests in 24 hours
Every note in this topic
- 2 cloud flow options with 250,000 requests in 24 hours
- 3 checks before a forecast file backup starts running
- 3 password figures to log before a backup
- 2 backup sources for a rep's forecast file
- 4 checks before replacing a rep's laptop
- 3 Power Automate request caps to read before a flow runs
- 2 CISA ransomware guide sections for a forecast file
- Xactly benchmarks: 3 vendor claims to test first
- Slack export cap: 90 days in GitLab's handbook before close
- Sharing deal files: 3 license checks before you send
- Lock 3 device settings on a rep's laptop before close
- 3 Microsoft 365 Backup speed figures for a small sales team
- Windows update pause: 2 windows to log before quarter-end
- Renewal overage: 3 facts to forecast before a true-up
- Microsoft 365 storage and Teams limits: 6 figures to check
- Microsoft 365 Backup restore points: 3 figures to read
- 6 group limits to read before sharing a forecast folder
- Forecast file versions: 3 retention layers to check
- EAP methods for rep VPN sign-in: 3 to compare
- 3 file size caps to check before a deal file goes out
- SMS 2FA for a rep's sign-in: 3 reasons to avoid it
- Commission accrual errors: 3 cases that overstate liability
- Veeam backup lock: 3 expiry days after a 7-day setting
- LUKS2 records to log before a laptop reimage: 3 entries
- Immutable backup costs: 2 rates to compare
- 2 defaults that set HubSpot SMS quiet hours for prospects
- Dynamics restore: 4 windows to log before quarter-end
- Dataverse batch: 3 errors in bulk task creation
- BitLocker encryption strength: 6 laptop checks
- Backup recovery: 4 figures to check before quarter-end
- Backup frequency: 4 survey shares for forecasts
- Chargebee earlier renewal: 2 boundary times to check
- Maine rep departure pay: 3 amounts to check
- Airtable autonumber deal IDs: 3 facts before close
- Teams message deletion: 2 stages before removal
- PCI DSS status: 2 processors to check before a deal
- Standalone payment against an invoice: 3 dates to track
- Mailbox compromise: 3 steps to recover a rep's account
- Quarter and date labels: 3 forecast record habits
- 3 payroll tax figures to check before a rep's pay run
- Minnesota commission pay: 2 methods and the postmark date
- 3 password policy limits compared for Microsoft 365 and Okta
- 2FA recovery: 5 steps before a rep loses a phone
- Quarter-end record: 5 mailbox and file limits to check
- Deleted mail before rep exit: 2 periods to check
- Chargebee quantity change: 3 readings before close
- Bitwarden import limits: 3 checks before a team load
- BitLocker and FileVault: 8 steps for forecast files
- Michigan pay deduction limits: 4 rules for employers
- 3 FCPA and FEPA rules to log in a deal file before close
- Dropbox 30-day recovery: 3 figures to check before close
- Breakout-room deal review: 5 numbers to log for each call
- Call transcript record: 4 fields before a deal review
- Audit log retention: 8 options and license checks
- Deleted deal emails: 6 checks before a mailbox hold
- Commission formula field: 3 checks before deal close
- Dropbox shared folder quota: 3 rules for deal files
- restic backup exit codes: 3 results to check
- Microsoft 365 email limits: 4 quarter-close checks
- Microsoft 365 backup: 3 backup and recovery checks
- Forecast handoff: 3 checks for a readable record
- Departed rep's mail: 3 steps to save deal evidence
- Deal amount rounding: 3 rules for forecast totals
- Commission payout time: 5 checks for your monthly run
- 4 Stripe renewal date rules to check before quarter close
- Commission accrual: 3 mistakes before quarter-end close
- Quarter cutoff dates: 6 checks before freezing your record
- Multi-year deal billing: 6 figures from GitLab and Stripe
- Quarter-end bookings: 9 billing and reporting limits
- Excel forecast data limits: 30% missing points, 2 cycles
- Sales report totals that disagree: 3 causes to check
- Unsigned quote review: 5 checks for quarter-end records
- Quote approval checklist: 4 checks on quoted amounts
- Quote acceptance checklist: 8 checks for quarter close
- Invoice extract reconciliation: 6 checks for bookings
- Forecast total mismatches: 4 calculation mistakes to check
- Forecast snapshot cutoff: 5 checks for quarter close
- Accepted quote review: 6 checks at quarter close
- Sales forecast dates: 4 tools for parsing and filters
- Bookings reconciliation: 5 checks for quarter close
Latest notes
Deal confidence 0 to 100: 2 closed statuses set the value
Close fixes deal confidence at 100 for won and 0 for lost opportunities, so forecast calls can focus on the deals still open.
3 Microsoft Forms caps to set before a weekly forecast
Three Microsoft Forms limits to configure before your sales team submits weekly forecasts: response export, character pool and audience size rules.
2 cloud flow options with 250,000 requests in 24 hours
Microsoft sets two cloud flow licensing paths at 250,000 Power Platform requests in a rolling 24-hour window; here is how to plan deal-stage flows around it.
How a sales year splits by quarter
Most quota plans cut the year into four equal pieces. Listed software companies do not bill that way: the last quarter is the heaviest and the first is the lightest, year after year. Use this table to weight a quarterly quota before you judge anyone against it.
| Year | Q1 share | Q2 share | Q3 share | Q4 share | Companies counted, of 16 |
|---|---|---|---|---|---|
| 2018 | 22.96 | 23.14 | 25.69 | 29.34 | 3 |
| 2019 | 22.10 | 24.31 | 25.54 | 29.14 | 11 |
| 2020 | 21.85 | 22.72 | 25.51 | 29.70 | 13 |
| 2021 | 21.84 | 23.72 | 25.35 | 29.41 | 14 |
| 2022 | 23.09 | 24.31 | 25.30 | 27.88 | 15 |
| 2023 | 23.20 | 24.12 | 25.05 | 29.04 | 14 |
| 2024 | 22.79 | 23.88 | 25.05 | 29.18 | 14 |
| 2025 | 22.72 | 24.18 | 24.96 | 28.91 | 14 |
The fourth quarter ran from 27.88% to 29.70% of the year across 2018 to 2025. Billings are revenue plus the change in deferred revenue, taken from each company's 10-Q and 10-K filings.
Which companies count. The table follows 16 listed US software companies. A company counts in a year only when its filings give revenue and deferred revenue for all four quarters of that year; any company short of that is left out of that year, never guessed. The Companies column shows how many counted: 14 of 16 in 2025 (AppFolio and Paycom are left out: neither gives deferred revenue for any of the four quarters of 2025), and only 3 in 2018. The fourth quarter is not filed on its own: its revenue is the full year from the 10-K less the first three quarters from the 10-Q filings.
Example: put your own numbers here. A yearly quota of $1,200,000 split on the 2025 shape gives a first quarter of $270,557 and a fourth quarter of $344,269, not $300,000 each. The four middle-company shares in the table add to 100.77%, not 100%, because each quarter's middle company is a different firm, so the example scales them to add to 100%: the first quarter gets 22.55% of the year, not the 22.72% shown (22.72 divided by 100.77).
Each month then takes its share of the quarter by selling days, from the table further down this page. This month split is this site's own selling-days method: the companies do not file months, so each month simply gets the part of its quarter that its selling days make up.
Work out your own: quarter quota = yearly quota × quarter share ÷ 100.77. Month quota = quarter quota × the month's selling days ÷ the quarter's selling days. For November 2026: $344,269 × 19 ÷ 62 = $105,502.
| Month | Quarter | Selling days | Month quota |
|---|---|---|---|
| January | Q1 | 20 | $88,707 |
| February | Q1 | 19 | $84,272 |
| March | Q1 | 22 | $97,578 |
| April | Q2 | 22 | $100,551 |
| May | Q2 | 20 | $91,410 |
| June | Q2 | 21 | $95,981 |
| July | Q3 | 22 | $102,173 |
| August | Q3 | 21 | $97,529 |
| September | Q3 | 21 | $97,529 |
| October | Q4 | 21 | $116,607 |
| November | Q4 | 19 | $105,502 |
| December | Q4 | 22 | $122,160 |
Selling days in each month and quarter
A quarter is not three full months of selling. This counts the weekdays in each month and quarter of 2026 and 2027 and takes away the federal holidays that land on a weekday. Your company may close on other days too, so read each result as an upper limit.
| Quarter | Weekdays | Federal holidays on a weekday | Selling days | Which holidays |
|---|---|---|---|---|
| Q1 2026 | 64 | 3 | 61 | New Year’s Day, Birthday of Martin Luther King, Jr., Washington’s Birthday |
| Q2 2026 | 65 | 2 | 63 | Memorial Day, Juneteenth National Independence Day |
| Q3 2026 | 66 | 2 | 64 | Independence Day, Labor Day |
| Q4 2026 | 66 | 4 | 62 | Columbus Day, Veterans Day, Thanksgiving Day, Christmas Day |
| Q1 2027 | 64 | 3 | 61 | New Year’s Day, Birthday of Martin Luther King, Jr., Washington’s Birthday |
| Q2 2027 | 65 | 2 | 63 | Memorial Day, Juneteenth National Independence Day |
| Q3 2027 | 66 | 2 | 64 | Independence Day, Labor Day |
| Q4 2027 | 66 | 5 | 61 | Columbus Day, Veterans Day, Thanksgiving Day, Christmas Day, New Year’s Day (observed Friday, 31 December) |
About Quota Forecast
Aimed at the people who build and defend a sales forecast: sales leaders, managers and the teams who look after the sales tools. About these forecast notes
Who reads these notes
The readers in mind are the people who build and defend a sales forecast: sales leaders, managers and the people who look after the sales tools. Each note names the sales tool it applies to and points to the vendor's own documentation.
Record what a category meant on the call
The forecast definition record is a printable sheet for one forecast call. It holds the call date and reporting period, the time the data was taken and the way amounts are counted. Then, for each category, it holds what the category includes, what it excludes and where that rule comes from. Last comes any definition that changed since the previous call, with an owner and a review date.
Open the record page, or print the blank sheet right away. Fill it in on paper; every date and figure on it is copied from your own tool.
What the record adds up
Nothing. It has no probabilities, no weighted pipeline and no forecast total, and it gives no view on whether a number is good. A value you cannot source is marked unknown instead of guessed.
What this site is not
Quota Forecast is not a forecasting tool and never asks for your deal data. Nothing on it is financial advice or a prediction about your quarter.
Method and corrections
Editorial standards. Changes after publication are listed in the correction register.
Follow the definition before the total
A forecast discussion can involve different questions even when everyone is looking at the same screen. One note may concern the definition of a category, another the date of a data extract, and another the reason an expected close date changed. The subject shelves separate those questions. They are meant for the person preparing the call as well as the person who later needs to understand the record.
Quota Forecast stays with the explanation of the number. It does not choose a target, assign a probability to a deal or tell a leader which quarter will succeed. References to sales software describe that software’s records and settings, rather than an endorsement of a product. For a question about your own pipeline, the relevant source is your organisation’s data and definitions; a general note here cannot establish what happened in an individual deal.