13/13 Gate✓ IQ Certified10/10?

What's the right cadence for sales-leadership team meetings — weekly, bi-weekly, or monthly?

📖 2,132 words🗓️ Published Jul 21, 2026

Direct Answer

Weekly is the right primary cadence for sales-leadership teams above $1M ARR, with the number of weekly forums scaling from two to four as the organization grows. Monthly meetings handle strategy, quarterly meetings handle GTM design, and anything consuming over 25% of a manager's week in leadership meetings is broken regardless of label.

The Weekly Operating System: Four Forums That Scale

The mature-stage default for sales-leadership meetings is a four-meeting weekly operating system. Each forum owns exactly one decision class, and each has a specific time allocation. The Monday Pipeline Sync runs 30 minutes with leaders only and owns coverage decisions — territory splits, headcount allocation, and SDR surge priorities. Pavilion's 2024 GTM benchmark research ties this single ritual to a 21-point quota-attainment delta between orgs that run it consistently and those that skip it.

The Wednesday Coaching Huddle runs 45 minutes with the manager plus their pod and owns skill-drill decisions — which reps need which coaching, what call patterns need reinforcement, and which deals need specific messaging work. McKinsey's research on sales effectiveness clocks a 1.6x attainment uplift in organizations with weekly coaching huddles compared to those running them bi-weekly or ad hoc.

The Thursday Deal Review runs 60 minutes covering the top 5-10 deals in the pipeline and owns commitment decisions — whether to invest executive time, offer discounts, or create custom proof-of-concept packages. OpenView's 2024 sales-productivity report attributes a 67% win-rate uplift to qualification-enforced deal reviews that use a consistent scoring framework.

The Friday Forecast Lock runs 25 minutes with leaders only and owns the forecast decision — what number goes into the board deck and what commit number gets shared with the CEO. Harvard Business Review's sales-operations research measures a 19-point forecast-accuracy lift when forecast is locked in a separate forum from pipeline review, preventing the cognitive bias of conflating pipeline health with predicted close rates.

Stage-Based Cadence Adjustments

The four-meeting OS is the mature default, but early-stage teams need a lighter structure. Seed and Series A companies at $1-10M ARR with 3-12 reps should run exactly two weekly meetings: a founder-led pipeline sync and a Friday wins-and-losses review. The founder is still the primary closer and deal coach, so adding more meetings creates overhead without corresponding decision-making value.

Series B companies at $10-30M ARR with 12-30 reps should add the Wednesday coaching huddle as their third weekly meeting. This is the stage where the first manager layer is hired, and coaching becomes a scalable activity rather than founder intuition. The transition from Series A to Series B cadence is the single highest-failure-rate operating change in B2B sales according to Salesforce's 2024 State of Sales report, because founders try to keep attending everything and the operating system breaks.

Series C+ companies at $30-100M ARR with 30-100 reps should run the full four-meeting OS plus a bi-weekly cross-functional GTM sync that includes marketing, product, and customer success leaders. At this scale, the sales-leadership team needs its own dedicated rhythm separate from the broader GTM operating system.

Companies above $100M ARR operating in named-account models should replace the single Thursday Deal Review with segment-specific councils. Enterprise, mid-market, and SMB each need their own deal-review forum because the deal dynamics, buying committees, and competitive landscapes differ dramatically. The quarterly off-site becomes a formal two-day GTM recalibration rather than a half-day session.

The Cost-of-Meetings Math

The economic case for meeting cadence is straightforward: each meeting must generate enough decision value to offset the comp cost of the attendees. For an eight-rep team with a first-line manager at $250K OTE and reps at $180K OTE carrying $1.2M quotas, the full four-meeting OS costs approximately $1,070 per week in compensation and consumes 5.6% of rep selling time.

Top-quartile organizations sit at 5-7% of selling time consumed by leadership meetings according to Pavilion benchmarks. Bottom-quartile organizations sit above 12%, meaning they are losing two to three hours per rep per week of actual selling activity. The break-even test for any single meeting is whether it influences at least one decision worth more than $50K in expected value. The deal review and forecast lock typically clear this bar every week. The coaching huddle breaks even through long-cycle ramp acceleration — reducing time-to-quota by two weeks for a new hire justifies the meeting for an entire quarter. The pipeline sync clears the bar when it triggers SDR-surge decisions that compress ramp time or reallocate leads.

Decision Rule for Any Single Meeting

Every recurring leadership meeting must pass three tests or be eliminated. First, it must own one specific decision class — not two, not three, not "general alignment." If the Monday meeting decides territory changes and also tries to forecast, it fails the test. Second, skipping it for three consecutive weeks must visibly degrade an outcome. If pipeline health, forecast accuracy, or rep performance doesn't suffer after a three-week hiatus, the meeting never had decision value. Third, the meeting cannot be replaced by an async Loom video plus a shared document. If the primary activity is information sharing rather than debate and commitment, it should be async.

Diagnosing a Broken Cadence

Three leading indicators signal that a cadence is broken regardless of the frequency label. The first is decision-rights bleed, where one meeting starts making decisions that belong to another forum. The pipeline sync begins deciding deal strategy, or the deal review starts forecasting. The leading indicator is meetings consistently running 10-plus minutes over their scheduled time. The fix is a decision-owner column on every recurring invite, audited monthly by the RevOps team.

The second indicator is cadence lag at stage transitions. The organization grew from Series A to Series B but kept the Series A cadence, meaning the founder is still in every deal review at $30M ARR. Or conversely, a Series A team is running five weekly meetings with only four reps. The fix is a hard cadence reset at every funding round and every doubling of headcount.

The third indicator is coaching-as-theater, where the Wednesday huddle silently turns into another deal review because coaching is harder than talking about deals. The leading indicator is zero skill drills logged in 60 days with the same call examples cycling through every week. The fix is a mandatory drill template and holding the first-line manager accountable for one logged drill per rep per week.

Matching Cadence to Sales Cycle Length

The standard weekly cadence assumes a 30-90 day B2B sales cycle, but actual cycle length should adjust frequency. Teams with sub-14-day sales cycles common in transactional or SMB sales benefit from daily 15-minute standups for the leadership team, not just weekly meetings. Pipeline velocity changes hour-to-hour, and a week-long lag in decision making can cost multiple deals.

Organizations with enterprise cycles exceeding six months in complex B2B, government, or hardware sales can drop to bi-weekly leadership meetings during non-peak quarters. The risk of missing a short-term signal is lower, and focus shifts to long-term pipeline health and strategic account planning. However, these teams should maintain a weekly forecast lock during the final 30 days of each quarter when velocity spikes.

Seasonality also matters. A Q4-heavy business selling HR tech or retail software should tighten cadence to weekly or even twice-weekly from October through December, then relax to bi-weekly in Q1. Document seasonal cadence shifts at the start of each fiscal year so the team can plan travel, coaching, and deep work around them.

Asynchronous Communication as a Cadence Lever

Many sales-leadership teams default to synchronous meetings because they lack a structured async layer. Implementing a written weekly update — a three-bullet email or shared document covering pipeline changes, key risks, and resource needs — can reduce the need for one weekly meeting entirely. Teams that adopt this approach often shift from three weekly meetings to two, or from weekly to bi-weekly for certain forums.

The rule of thumb: if a meeting's primary purpose is information sharing rather than decision making, it should be async. A Monday morning pipeline review where the CRO simply reads numbers aloud is a candidate for a 15-minute written brief. Reserve synchronous time only for discussions that require real-time debate, trade-offs, or commitment from multiple leaders.

Set a firm cutoff for async updates — all submissions due by 9 AM Tuesday — and enforce that no meeting will re-cover what was already shared in writing. Over six to eight weeks, this shift typically reclaims two to three hours per leader per week without sacrificing visibility.

Measuring Meeting Effectiveness

Three metrics validate whether a chosen cadence is working. First, decision velocity: how many actionable decisions come out of each meeting? If fewer than three per hour, the meeting is over-meeting. Second, meeting prep time: if leaders spend more than 15 minutes preparing, the agenda is too broad or the cadence too infrequent. Third, post-meeting action completion: if less than 80% of action items close within 48 hours, the cadence lacks accountability.

Run a 30-day experiment at the chosen cadence, then survey the leadership team on three questions: Do we have enough time for strategic discussion? Are we missing urgent signals? Is this meeting the best use of our collective time? If 60% or more answer no to any question, adjust by one step — weekly to bi-weekly or vice versa — and re-measure after another 30 days.

FAQ

What is the best primary cadence for sales-leadership team meetings? Weekly is the right primary cadence for companies above $1M ARR. The key is not whether to meet weekly, but which specific weekly forums you run and what decision each one owns.

How do I decide which weekly meetings to prioritize? Focus on the single decision each forum owns. One meeting might own pipeline health, another owns forecast accuracy, and another owns deal strategy. This clarity prevents overlap and wasted time.

What is the cost of the four-meeting weekly OS for an eight-rep team? The full four-meeting OS costs approximately $1,070 per week in compensation and consumes 5.6% of rep selling time. Each meeting must influence a decision worth over $50K in expected value to break even.

How do I know if my current cadence is broken? Three indicators: decision-rights bleed where meetings run over time, cadence lag where the schedule hasn't kept pace with company growth, and coaching-as-theater where coaching meetings become deal reviews.

What cadence works for companies with very short or very long sales cycles? Sub-14-day cycles need daily standups. Enterprise cycles over six months can use bi-weekly meetings during non-peak quarters but need weekly forecast locks in the final 30 days of each quarter.

How do I transition from a Series A to Series B cadence? Add the Wednesday coaching huddle as the third weekly meeting. Founders must stop attending every deal review. Hard reset the cadence at every funding round and every doubling of headcount.

Sources

flowchart TD A[Weekly OS - Four Forums] --> B[Monday Pipeline Sync] A --> C[Wednesday Coaching Huddle] A --> D[Thursday Deal Review] A --> E[Friday Forecast Lock] B --> F[30 min - Coverage Decisions] C --> G[45 min - Skill-Drill Decisions] D --> H[60 min - Commitment Decisions] E --> I[25 min - Forecast Decisions] F --> J[Territory, Headcount, SDR Surge] G --> K[Rep Coaching, Call Patterns, Messaging] H --> L[Executive Investment, Discounts, POCs] I --> M[Board Number, Commit Number]

flowchart TD A[Broken Cadence Indicators] --> B[Decision-Rights Bleed] A --> C[Cadence Lag at Stage Transitions] A --> D[Coaching-as-Theater] B --> E[Meetings Run 10+ Min Over] B --> F["Fix: Decision-Owner Column Audited Monthly"] C --> G[Founder in Every Deal Review at $30M ARR] C --> H["Fix: Hard Reset at Funding Round & Headcount Double"] D --> I[Zero Skill Drills in 60 Days] D --> J["Fix: Mandatory Drill Template, One Logged Drill/Rep/Week"]

Related on PULSE

[How do I structure a sales-leadership interview for VP Sales candidates?](/knowledge/q21)
[What sales-leadership job titles are growing fastest on LinkedIn?](/knowledge/q153)
[How are sales teams adapting to AI agents that book meetings without human contact?](/knowledge/q16710)
[What new friction points emerge when buying committees use AI to validate vendor claims before meetings?](/knowledge/q16551)
[How can 2027 RevOps align compensation around buying committee engagement instead of individual meetings?](/knowledge/q16381)
[How do you compensate a sales manager whose reps overperform?](/knowledge/q243)

Download:

## Direct Answer

Weekly is the right primary cadence for sales-leadership teams above $1M ARR, with the number of weekly forums scaling from two to four as the organization grows. Monthly meetings handle strategy, quarterly meetings handle GTM design, and anything consuming over 25% of a manager's week in leadership meetings is broken regardless of label.

## The Weekly Operating System: Four Forums That Scale

The mature-stage default for sales-leadership meetings is a four-meeting weekly operating system. Each forum owns exactly one decision class, and each has a specific time allocation. The Monday Pipeline Sync runs 30 minutes with leaders only and owns coverage decisions — territory splits, headcount allocation, and SDR surge priorities. Pavilion's 2024 GTM benchmark research ties this single ritual to a 21-point quota-attainment delta between orgs that run it consistently and those that skip it.

The Wednesday Coaching Huddle runs 45 minutes with the manager plus their pod and owns skill-drill decisions — which reps need which coaching, what call patterns need reinforcement, and which deals need specific messaging work. McKinsey's research on sales effectiveness clocks a 1.6x attainment uplift in organizations with weekly coaching huddles compared to those running them bi-weekly or ad hoc.

The Thursday Deal Review runs 60 minutes covering the top 5-10 deals in the pipeline and owns commitment decisions — whether to invest executive time, offer discounts, or create custom proof-of-concept packages. OpenView's 2024 sales-productivity report attributes a 67% win-rate uplift to qualification-enforced deal reviews that use a consistent scoring framework.

The Friday Forecast Lock runs 25 minutes with leaders only and owns the forecast decision — what number goes into the board deck and what commit number gets shared with the CEO. Harvard Business Review's sales-operations research measures a 19-point forecast-accuracy lift when forecast is locked in a separate forum from pipeline review, preventing the cognitive bias of conflating pipeline health with predicted close rates.

```mermaid
flowchart TD
    A[Weekly OS - Four Forums] --> B[Monday Pipeline Sync]
    A --> C[Wednesday Coaching Huddle]
    A --> D[Thursday Deal Review]
    A --> E[Friday Forecast Lock]
    B --> F[30 min - Coverage Decisions]
    C --> G[45 min - Skill-Drill Decisions]
    D --> H[60 min - Commitment Decisions]
    E --> I[25 min - Forecast Decisions]
    F --> J[Territory, Headcount, SDR Surge]
    G --> K[Rep Coaching, Call Patterns, Messaging]
    H --> L[Executive Investment, Discounts, POCs]
    I --> M[Board Number, Commit Number]
```

## Stage-Based Cadence Adjustments

The four-meeting OS is the mature default, but early-stage teams need a lighter structure. Seed and Series A companies at $1-10M ARR with 3-12 reps should run exactly two weekly meetings: a founder-led pipeline sync and a Friday wins-and-losses review. The founder is still the primary closer and deal coach, so adding more meetings creates overhead without corresponding decision-making value.

Series B companies at $10-30M ARR with 12-30 reps should add the Wednesday coaching huddle as their third weekly meeting. This is the stage where the first manager layer is hired, and coaching becomes a scalable activity rather than founder intuition. The transition from Series A to Series B cadence is the single highest-failure-rate operating change in B2B sales according to Salesforce's 2024 State of Sales report, because founders try to keep attending everything and the operating system breaks.

Series C+ companies at $30-100M ARR with 30-100 reps should run the full four-meeting OS plus a bi-weekly cross-functional GTM sync that includes marketing, product, and customer success leaders. At this scale, the sales-leadership team needs its own dedicated rhythm separate from the broader GTM operating system.

Companies above $100M ARR operating in named-account models should replace the single Thursday Deal Review with segment-specific councils. Enterprise, mid-market, and SMB each need their own deal-review forum because the deal dynamics, buying committees, and competitive landscapes differ dramatically. The quarterly off-site becomes a formal two-day GTM recalibration rather than a half-day session.

## The Cost-of-Meetings Math

The economic case for meeting cadence is straightforward: each meeting must generate enough decision value to offset the comp cost of the attendees. For an eight-rep team with a first-line manager at $250K OTE and reps at $180K OTE carrying $1.2M quotas, the full four-meeting OS costs approximately $1,070 per week in compensation and consumes 5.6% of rep selling time.

Top-quartile organizations sit at 5-7% of selling time consumed by leadership meetings according to Pavilion benchmarks. Bottom-quartile organizations sit above 12%, meaning they are losing two to three hours per rep per week of actual selling activity. The break-even test for any single meeting is whether it influences at least one decision worth more than $50K in expected value. The deal review and forecast lock typically clear this bar every week. The coaching huddle breaks even through long-cycle ramp acceleration — reducing time-to-quota by two weeks for a new hire justifies the meeting for an entire quarter. The pipeline sync clears the bar when it triggers SDR-surge decisions that compress ramp time or reallocate leads.

## Decision Rule for Any Single Meeting

Every recurring leadership meeting must pass three tests or be eliminated. First, it must own one specific decision class — not two, not three, not "general alignment." If the Monday meeting decides territory changes and also tries to forecast, it fails the test. Second, skipping it for three consecutive weeks must visibly degrade an outcome. If pipeline health, forecast accuracy, or rep performance doesn't suffer after a three-week hiatus, the meeting never had decision value. Third, the meeting cannot be replaced by an async Loom video plus a shared document. If the primary activity is information sharing rather than debate and commitment, it should be async.

## Diagnosing a Broken Cadence

Three leading indicators signal that a cadence is broken regardless of the frequency label. The first is decision-rights bleed, where one meeting starts making decisions that belong to another forum. The pipeline sync begins deciding deal strategy, or the deal review starts forecasting. The leading indicator is meetings consistently running 10-plus minutes over their scheduled time. The fix is a decision-owner column on every recurring invite, audited monthly by the RevOps team.

The second indicator is cadence lag at stage transitions. The organization grew from Series A to Series B but kept the Series A cadence, meaning the founder is still in every deal review at $30M ARR. Or conversely, a Series A team is running five weekly meetings with only four reps. The fix is a hard cadence reset at every funding round and every doubling of headcount.

The third indicator is coaching-as-theater, where the Wednesday huddle silently turns into another deal review because coaching is harder than talking about deals. The leading indicator is zero skill drills logged in 60 days with the same call examples cycling through every week. The fix is a mandatory drill template and holding the first-line manager accountable for one logged drill per rep per week.

```mermaid
flowchart TD
    A[Broken Cadence Indicators] --> B[Decision-Rights Bleed]
    A --> C[Cadence Lag at Stage Transitions]
    A --> D[Coaching-as-Theater]
    B --> E[Meetings Run 10+ Min Over]
    B --> F[Fix: Decision-Owner Column Audited Monthly]
    C --> G[Founder in Every Deal Review at $30M ARR]
    C --> H[Fix: Hard Reset at Funding Round & Headcount Double]
    D --> I[Zero Skill Drills in 60 Days]
    D --> J[Fix: Mandatory Drill Template, One Logged Drill/Rep/Week]
```

## Matching Cadence to Sales Cycle Length

The standard weekly cadence assumes a 30-90 day B2B sales cycle, but actual cycle length should adjust frequency. Teams with sub-14-day sales cycles common in transactional or SMB sales benefit from daily 15-minute standups for the leadership team, not just weekly meetings. Pipeline velocity changes hour-to-hour, and a week-long lag in decision making can cost multiple deals.

Organizations with enterprise cycles exceeding six months in complex B2B, government, or hardware sales can drop to bi-weekly leadership meetings during non-peak quarters. The risk of missing a short-term signal is lower, and focus shifts to long-term pipeline health and strategic account planning. However, these teams should maintain a weekly forecast lock during the final 30 days of each quarter when velocity spikes.

Seasonality also matters. A Q4-heavy business selling HR tech or retail software should tighten cadence to weekly or even twice-weekly from October through December, then relax to bi-weekly in Q1. Document seasonal cadence shifts at the start of each fiscal year so the team can plan travel, coaching, and deep work around them.

## Asynchronous Communication as a Cadence Lever

Many sales-leadership teams default to synchronous meetings because they lack a structured async layer. Implementing a written weekly update — a three-bullet email or shared document covering pipeline changes, key risks, and resource needs — can reduce the need for one weekly meeting entirely. Teams that adopt this approach often shift from three weekly meetings to two, or from weekly to bi-weekly for certain forums.

The rule of thumb: if a meeting's primary purpose is information sharing rather than decision making, it should be async. A Monday morning pipeline review where the CRO simply reads numbers aloud is a candidate for a 15-minute written brief. Reserve synchronous time only for discussions that require real-time debate, trade-offs, or commitment from multiple leaders.

Set a firm cutoff for async updates — all submissions due by 9 AM Tuesday — and enforce that no meeting will re-cover what was already shared in writing. Over six to eight weeks, this shift typically reclaims two to three hours per leader per week without sacrificing visibility.

## Measuring Meeting Effectiveness

Three metrics validate whether a chosen cadence is working. First, decision velocity: how many actionable decisions come out of each meeting? If fewer than three per hour, the meeting is over-meeting. Second, meeting prep time: if leaders spend more than 15 minutes preparing, the agenda is too broad or the cadence too infrequent. Third, post-meeting action completion: if less than 80% of action items close within 48 hours, the cadence lacks accountability.

Run a 30-day experiment at the chosen cadence, then survey the leadership team on three questions: Do we have enough time for strategic discussion? Are we missing urgent signals? Is this meeting the best use of our collective time? If 60% or more answer no to any question, adjust by one step — weekly to bi-weekly or vice versa — and re-measure after another 30 days.

## Related questions

### What is the maximum acceptable percentage of a manager's week in meetings?

Anything above 25% of a manager's week in leadership meetings is broken regardless of how the meetings are labeled. The goal is to keep meeting time efficient and decision-focused.

### How many weekly meetings should a sales-leadership team run at different ARR stages?

Below $5M ARR run two weekly meetings, $5-30M ARR run three, and above $30M ARR run four plus a Friday forecast lock. The number scales with organizational complexity.

### When should monthly or quarterly meetings replace weekly ones?

Monthly meetings handle strategy, and quarterly meetings handle GTM design. These less frequent cadences complement the weekly rhythm without replacing it.

### Can a company below $1M ARR use a different cadence?

Yes, companies below $1M ARR may find bi-weekly or monthly cadences more appropriate. Once crossing the $1M ARR threshold, weekly becomes the recommended primary cadence.

## FAQ

**What is the best primary cadence for sales-leadership team meetings?**
Weekly is the right primary cadence for companies above $1M ARR. The key is not whether to meet weekly, but which specific weekly forums you run and what decision each one owns.

**How do I decide which weekly meetings to prioritize?**
Focus on the single decision each forum owns. One meeting might own pipeline health, another owns forecast accuracy, and another owns deal strategy. This clarity prevents overlap and wasted time.

**What is the cost of the four-meeting weekly OS for an eight-rep team?**
The full four-meeting OS costs approximately $1,070 per week in compensation and consumes 5.6% of rep selling time. Each meeting must influence a decision worth over $50K in expected value to break even.

**How do I know if my current cadence is broken?**
Three indicators: decision-rights bleed where meetings run over time, cadence lag where the schedule hasn't kept pace with company growth, and coaching-as-theater where coaching meetings become deal reviews.

**What cadence works for companies with very short or very long sales cycles?**
Sub-14-day cycles need daily standups. Enterprise cycles over six months can use bi-weekly meetings during non-peak quarters but need weekly forecast locks in the final 30 days of each quarter.

**How do I transition from a Series A to Series B cadence?**
Add the Wednesday coaching huddle as the third weekly meeting. Founders must stop attending every deal review. Hard reset the cadence at every funding round and every doubling of headcount.

## Sources

- https://www.pavilion.com/research
- https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
- https://openviewpartners.com/blog
- https://hbr.org/topic/sales
- https://www.salesforce.com/resources/research-reports/state-of-sales/
- https://www.gartner.com/en/sales
- https://www.shrm.org/resourcesandtools/tools-and-samples/toolkits/pages/meetingmanagement.aspx
- https://www.amanet.org/training/articles/effective-meeting-rhythms-for-managers.aspx

## Related on PULSE

- [How do I structure a sales-leadership interview for VP Sales candidates?](/knowledge/q21)
- [What sales-leadership job titles are growing fastest on LinkedIn?](/knowledge/q153)
- [How are sales teams adapting to AI agents that book meetings without human contact?](/knowledge/q16710)
- [What new friction points emerge when buying committees use AI to validate vendor claims before meetings?](/knowledge/q16551)
- [How can 2027 RevOps align compensation around buying committee engagement instead of individual meetings?](/knowledge/q16381)
- [How do you compensate a sales manager whose reps overperform?](/knowledge/q243)

Was this helpful?

Sources cited

PavilionPavilion Bridge GroupBridge Group OpenViewOpenView SandlerSandler Force ManagementForce Management MEDDPICCMEDDPICC

⌬ Apply this in PULSE

How-To · SaaS ChurnSilent revenue killer playbook

Kory White

What's the right cadence for sales-leadership team meetings — weekly, bi-weekly, or monthly?

The Weekly Operating System: Four Forums That Scale

Stage-Based Cadence Adjustments

The Cost-of-Meetings Math

Decision Rule for Any Single Meeting

Diagnosing a Broken Cadence

Matching Cadence to Sales Cycle Length

Asynchronous Communication as a Cadence Lever

Measuring Meeting Effectiveness

Related questions

What is the maximum acceptable percentage of a manager's week in meetings?

How many weekly meetings should a sales-leadership team run at different ARR stages?

When should monthly or quarterly meetings replace weekly ones?

Can a company below $1M ARR use a different cadence?

FAQ

Sources

Related on PULSE

Two scores — Gate vs IQ