Pipeline Review: How to Run One, What to Inspect, and the Questions to Ask

Callia Peterson

Summarize this article with your favorite LLM
Table of contents

Summarize article with your LLM

A pipeline review is a recurring meeting in which a sales leader and team inspect the health of the open pipeline and the evidence behind individual deals, then decide what to do next.

An effective review follows a timed agenda, starts from a pre-read of flagged deals, checks coverage and aging at the pipeline level, tests each deal against buyer-side evidence, and ends with owned actions.

Most sales teams hold a weekly pipeline meeting, and most of those meetings are less useful than they should be. A manager opens the CRM, scrolls the opportunity list, and asks each rep to talk through their deals.

Reps summarize from memory, usually with more optimism than the record supports. The manager asks whether the deal is on track, the rep says yes, and the meeting moves to the next deal. Forty-five minutes later, nobody has changed an action, and the forecast looks the same as it did the week before.

The problem is not effort. It is structure. A review that starts from a blank screen spends its time on discovery: finding out which deals are stale, which dates moved, and which stakeholders have gone quiet.

A review that starts from a short list of flagged deals spends its time on judgment: deciding what to do about them. A review that asks "how does it feel?" gets confident guesses. A review that asks for the buyer's words, the date of the last meeting, and the name of the person who signs gets evidence, or finds the lack of it while there is still time to act.

The guide is written for sales leaders, front-line managers, revenue operations teams, and account executives. It gives no benchmark thresholds, because healthy numbers depend on deal size, cycle length, and market. It shows how to derive yours.

What Is a Pipeline Review?

A pipeline review is a scheduled inspection of open opportunities that checks pipeline health and deal evidence, and produces actions and a more reliable forecast.

The meeting has three jobs.

  1. Find risk early. Spot stalled, slipped, and unsupported deals while there is time to change the outcome.

  2. Help the rep. Decide what the manager, a colleague, or an executive sponsor can do to advance a deal.

  3. Protect the forecast. Make sure the deals in each forecast category deserve to be there.

How it differs from related meetings?

Meeting

Main question

Typical scope

Output

Pipeline review

Is the pipeline healthy, and which deals need action?

All open pipeline, with focus on key deals

Actions and flagged deals

Deal review

Is this one deal winnable, and what is the plan?

One strategic deal

A deal plan and risk score

Forecast call

What will we close, and where is the range?

Commit, best case, pipeline

A forecast number

One-on-one

How is this person doing?

The individual, including pipeline

Coaching and development

Quarterly business review

How did the period go, and what changes?

Results and strategy

Plans and priorities

The pipeline review feeds the forecast call and the deal review. It does not replace them. For how forecasts are measured, see forecast accuracy for large organizations.

Cadence and Roles

Run the team review weekly, deal reviews for strategic deals as needed, and a segment-level review monthly.

Review

Frequency

Attendees

Length

Team pipeline review

Weekly

Manager and the reps on the team

45 to 60 minutes

Strategic deal review

As needed, for the largest or riskiest deals

Rep, manager, sales engineer, executive sponsor

30 to 45 minutes

Segment or region review

Monthly

Directors, managers, revenue operations

60 minutes

Pipeline and forecast alignment

Weekly or biweekly

Sales leadership and finance

30 minutes

Roles in the room

  • Manager. Owns the agenda, asks evidence questions, and records decisions.

  • Rep. Presents deals with evidence, asks for help, and owns actions.

  • Revenue operations. Prepares the pre-read and keeps definitions consistent.

  • Sales engineer or specialist. Joins when a deal needs technical or commercial input.

  • Executive sponsor. Joins for strategic deals to unblock access or decisions.

A 60-Minute Agenda

Use a fixed agenda so the meeting spends most of its time on judgment, not discovery.

Minutes

Segment

What happens

0 to 5

Changes since last review

Wins, losses, new pipeline, slipped deals, and movements in forecast categories

5 to 20

Pipeline health

Coverage, creation, aging, slippage, and stage shape for the team

20 to 50

Deal inspection

About six priority deals at 5 minutes each, using the evidence checklist

50 to 60

Actions

Owners, dates, and requests for help recorded

Arithmetic: 5 + 15 + 30 + 10 = 60 minutes. Thirty minutes of deal inspection at 5 minutes per deal covers 30 / 5 = 6 deals.

Choosing which deals to inspect

A team cannot inspect every deal each week. Choose by rule, not by who speaks loudest.

  • Deals in commit or best case closing this period.

  • Deals above a size threshold you set.

  • Deals flagged by the pre-read filters.

  • Deals where a key date or stage changed since the last review.

  • Deals where a rep has asked for help.

Prepare: The Pre-Read

Send a pre-read before the meeting so the review starts with a list of flagged deals instead of a discovery exercise.

SalesOpsClub's guide to running a pipeline review recommends four filters that run as CRM reports and find most of the problem deals: close dates in the past, deals that have not changed stage in more than one and a half times your average stage duration, deals with no buyer-side activity in 21 days, and deals where the amount changed by more than 25% without a note.

Read their guide to how to run a pipeline review for the full approach, including the point that the shape of the book matters as much as its contents.

Treat those thresholds as starting points and tune them to your own stage durations.

What the pre-read should contain?

Item

Why it helps

Changes since last review

Focuses on movement, not repetition

Four filter lists

Finds stale, slipped, silent, and unexplained deals

Coverage and creation by segment

Shows whether the pipeline can support the target

Stage shape and close date distribution

Reveals deals that have been pushed rather than progressed

Priority deal summaries

Gives the manager context before the meeting

Open actions from last review

Checks follow-through

Share the same view with reps

If the manager inspects fields the rep cannot see, the review turns into an interrogation. Give reps the same pre-read and the same criteria, so both sides work from one structure.

Pipeline-Level Inspection

Check the health of the whole book before discussing individual deals: coverage, creation, aging, slippage, and shape.

Metric

What it shows

What to flag

Coverage

Qualified pipeline relative to remaining target

Below the level your win rate requires

Pipeline creation

New qualified pipeline against plan

A shortfall that cannot be repaired this period

Stage conversion

Movement between stages

A stage where conversion has dropped

Aging

Days in current stage

Deals beyond the typical duration

Slippage

Close date changes

Repeated pushes

Stage shape

Where value sits

Most value in the last stage with all dates in the final weeks

Single-threaded deals

Deals with one contact

Late-stage deals with no second stakeholder

Forecast category mix

Commit, best case, pipeline

Commit that lacks evidence

Worked example 1: coverage from your own win rate

Illustrative example. The figures are hypothetical.

A team has $2.0 million of target remaining in the period. Its value-based win rate on qualified pipeline is 25%.

  • Required qualified pipeline: $2.0M / 0.25 = $8.0M.

  • Required coverage: 1 / 0.25 = 4.0 times the remaining target.

  • Actual qualified pipeline: $5.0M, which is $5.0M / $2.0M = 2.5 times.

  • Gap: $8.0M - $5.0M = $3.0M.

The team is $3.0 million short of the pipeline its own history says it needs. A generic "3 times coverage" rule would have called this healthy, and it would have been wrong for this team.

For the method, see how to calculate the pipeline needed to hit a revenue target, which explains why coverage should come from the historical value-based win rate for a comparable cohort.

Worked example 2: in-period yield

Illustrative example. Not every deal that eventually wins closes in the period being reviewed.

  • Eventual value-based win rate for the cohort: 30%.

  • Share of that eventual win value that closes within the period: 60%.

  • In-period yield: 30% x 60% = 18%.

  • Required qualified pipeline for $2.0M remaining: $2.0M / 0.18 = about $11.1M.

  • Required coverage: about 5.6 times.

Using the eventual win rate understates the requirement. Use measured timing by segment and starting stage, and treat the 60% as an assumption to replace with your own data.

Worked example 3: segment coverage

Illustrative example. Different segments convert differently.

Segment

Value-based win rate

Required coverage

Mid-market

32%

1 / 0.32 = 3.1 times

Enterprise

18%

1 / 0.18 = 5.6 times

A single blanket ratio would overstate enterprise health or understate mid-market health. Set segment-level coverage from the segment's own history, and use longer windows for segments with few closed deals.

Worked example 4: aging

Illustrative example. The typical time in the Proposal stage is 20 days, so the review threshold is 1.5 x 20 = 30 days. Eight deals are in Proposal with these days in stage: 12, 18, 22, 35, 41, 15, 28, 52.

  • Deals above 30 days: 35, 41, and 52, which is 3 deals.

  • Share flagged: 3 / 8 = 37.5%.

Those three go on the inspection list. The point is not the threshold. It is that the list is produced before the meeting.

Worked example 5: slippage

Illustrative example. Twenty deals were forecast to close this quarter. Six had their close date pushed at least once, and three were pushed twice or more.

  • Slip rate: 6 / 20 = 30%.

  • Repeat slip rate: 3 / 20 = 15%.

Repeated pushes are a signal that the buyer has no forcing event or that the rep lacks a decision path. Track slip rate by rep and by stage, and ask what changed each time.

Read the shape of the book

A book where most of the value sits in the last stage, and nearly every close date lands in the final two weeks of the period, is a set of deals that have been pushed, not a healthy pipeline.

Compare stage distribution with your normal pattern. For wider pipeline views, see sales pipeline intelligence and sales velocity.

Deal-Level Inspection

Inspect each deal against evidence from the buyer: who said what, when, and what happens next.

The deal basics

Field

Check

Stage and days in stage

Is the deal where the record says, and for how long?

Close date and changes

Has it moved, and why?

Amount and changes

Did it change without a note?

Forecast category

Does the evidence support it?

Last buyer-side activity

When did the buyer last engage?

Next step

Is it specific, dated, and scheduled?

ORM's deal review template points to two leading indicators that many CRM views hide: days in the current stage and the history of close date changes.

See their deal review template for a structured set of blocks that cover basics, stage exit checks, risk scoring, next step confirmation, and documented outputs.

The evidence checklist

Area

Evidence to look for

Red flag

Problem

The buyer described the problem in their own words

Only the rep's summary

Economic buyer

Identified, and the rep has spoken with them

Unknown or never engaged

Decision process

Steps, owners, and dates are known

"They'll let us know"

Paper process

Security, legal, and procurement requirements are known and started

Not discussed

Champion

A person who advocates and can explain the case without the rep

A single passive contact

Competition

Alternatives and the buyer's view of them are known

Unknown

Timeline

A forcing event or deadline exists

No reason to decide this period

Next step

A dated, scheduled action with a buyer attendee

"We'll connect next week"

Qualification frameworks can serve as checklists for this evidence. See MEDDPICC sales methodology for one of them. Use them to know what to look for, not as a score to recite.

Stage exit criteria

A review is only as good as the stage definitions beneath it. If two reps use "Proposal" differently, no amount of inspection produces a comparable book.

  • Write each stage as an exit test in buyer behavior, not seller activity. "Demo delivered" is a seller action. "Buyer has confirmed the problem, the approximate budget, and who signs" is an exit test.

  • Keep to five or six stages.

  • Name the required field or artifact that evidences each exit.

  • Enforce criteria in the CRM with required fields and validation, so the meeting is free for judgment.

A deal risk scorecard

Score each deal on the same factors.

Factor

Green

Yellow

Red

Economic buyer access

Met and confirmed

Claimed by the champion, unverified

No contact

Champion strength

Explains the case independently

Engaged but not self-sufficient

Passive or single contact

Competition

Uncontested or clear preference

Competitive, not identified

Behind a named competitor

Procurement and legal

In progress with dates

Not started

Unresponsive or unknown

Timeline

A real forcing event

A soft preference

No forcing event

Stage integrity

All exit criteria evidenced

Partial evidence

No evidence

A deal with several red factors does not belong in commit. A deal with mostly yellow factors needs a specific action plan.

The next step test

A deal without a confirmed next step is not progressing. A good next step is specific, dated, owned on both sides, and on a calendar.

"We'll connect next week" fails the test. "Procurement kickoff call with the buyer's procurement lead on Thursday at 2:00 pm" passes it.

Questions That Surface Risk

Replace questions that invite a confident guess with questions that require evidence the rep either has or does not have.

Weak question

Evidence question

Does the buyer have budget?

Who approved the last purchase of this size, and what did that take?

Do they like us?

What did the buyer say when price came up, in their words?

What is the timeline?

What happens in their business the day after they sign, and what drives that date?

Who is the competition?

What would the buyer have to tell the other vendor to end that conversation?

Is the deal on track?

What has to be true for this to close this period that is not true today?

Do we have a champion?

Who inside the buyer could stop this, and when did we last speak to them?

Ask for the buyer's language

"They're excited" is the rep's word. "They said the current process costs them two days a month" is the buyer's. The second can be checked and used in the proposal.

Questions by stage

Stage

Questions

Discovery

Who feels the problem most, and what does it cost? Who else is affected?

Evaluation

What criteria will the buyer use? Who decides? What would a successful trial look like?

Proposal

Who has seen the proposal? What objections came up? What is the buyer's process to approve?

Negotiation and contract

What is still open? Who signs, and when? What has legal asked for?

How to ask

Inspect, do not interrogate. Ask in the same way for every deal, use the same view as the rep, and treat a gap in evidence as a task, not a failure. A rep who dreads the review hides risk.

Worked Example 6: Forecast Categories With an Evidence Rule

Illustrative example. The team uses a written rule. A deal is in commit only if at least 5 of 6 evidence items are present and the economic buyer is engaged. Best case needs 3 or 4 items. Anything with 2 or fewer stays in pipeline.

Deal

Amount

Evidence items (of 6)

Economic buyer engaged

Category

A

$400,000

6

Yes

Commit

B

$250,000

5

Yes

Commit

C

$300,000

3

Yes

Best case

D

$500,000

4

No

Best case

E

$350,000

2

No

Pipeline

Totals by category:

  • Commit: $400,000 + $250,000 = $650,000.

  • Best case: $300,000 + $500,000 = $800,000.

  • Pipeline: $350,000.

  • Total: $650,000 + $800,000 + $350,000 = $1,800,000.

Applying the team's own historical conversion by category, 90% for commit, 40% for best case, and 10% for pipeline:

  • Commit: 0.90 x $650,000 = $585,000.

  • Best case: 0.40 x $800,000 = $320,000.

  • Pipeline: 0.10 x $350,000 = $35,000.

  • Weighted forecast: $585,000 + $320,000 + $35,000 = $940,000.

Deal D is the largest deal and sits in best case because it fails the economic buyer test. That is the rule working. The rates are assumptions, so replace them with your history and recalibrate each quarter.

Outputs and Follow-Up

Every inspected deal should leave the review with a documented outcome.

Output

What to record

Risk score

Green, yellow, or red by factor

Forecast category

Commit, best case, pipeline, or at risk

Next step

Specific action

Next step owner

Rep and buyer-side owner

Next step date

A date on the calendar

Manager action

None, introduction to a sponsor, resource, or escalation

Follow-up date

When the deal is next reviewed

Keep the output in the CRM, not in a private spreadsheet, so the forecast call can pull a current view without rebuilding it from memory. Open the next review with last week's actions.

Common Anti-Patterns

  1. Reading CRM fields aloud. Everyone can see them. Discuss what the fields do not show.

  2. Reviewing every deal. Inspect by rule, and leave the rest to the pre-read.

  3. Opinion over evidence. Confidence is not a buyer action.

  4. Only reviewing commit. Early pipeline decides next period.

  5. No actions. A review without owned actions changes nothing.

  6. Interrogation. Reps hide risk when they feel exposed.

  7. Inconsistent stage criteria. The book is not comparable.

  8. Ignoring slippage. Repeated pushes are a signal.

  9. Stage probabilities that are never calibrated. Untested percentages flatter the pipeline.

  10. No follow-through. Unchecked actions teach the team that the review is a ritual.

Pipeline Review for Enterprise Deals

Enterprise deals have long cycles, many stakeholders, and large amounts per deal, so the review needs more attention to stakeholders and evidence over time.

  • Buying committees. Check that each role is mapped and engaged, and that the champion is not the only contact. See buying committee mapping and multi-threading.

  • Long cycles. Track milestones across months, and ask what changed since the last review, not only where the deal stands.

  • Few, large deals. A handful of deals dominate the total, so inspect them individually.

  • Account plans. Tie each major deal to an account plan with stakeholders, risks, and next steps. See account planning with AI agents.

  • Signals outside the CRM. Security reviews, procurement activity, and product usage often sit in email, call transcripts, and the data warehouse.

The context gap in pipeline reviews

Enterprise revenue teams lose deals when deal-moving signals are scattered outside the CRM, across the warehouse, inbox, call transcripts, and product data, with no system built to unify them into action.

Rox calls this the context gap. In a pipeline review, the gap means the review is built on what reps remembered to log. A deal can show a healthy stage in the CRM while the buyer has not replied in three weeks.

Using AI in the Review

AI can prepare the review and surface what changed. People decide what to do about it.

Task

What AI contributes

Control to keep

Pre-read

Builds flagged lists and summaries

Review the filters and thresholds

Evidence gathering

Pulls buyer activity from email, calendar, and calls

Check key facts against sources

Risk flags

Highlights silent stakeholders, slipped dates, new competitors

Treat flags as prompts to investigate

Change tracking

Shows what moved since last review

Verify surprising changes

Follow-up

Drafts action lists and updates

Approve before sending or writing to the CRM

See deal risk detection with revenue agents for how risk signals can be monitored.

How Rox Supports the Pipeline Review?

Rox is a warehouse-native revenue orchestration platform. Its context graph unifies internal and external signals from the warehouse, inbox, call transcripts, product data, and external sources into a single system of context.

That context gives a review evidence beyond the fields a rep updated.

Opportunity Management

Rox's Opportunity Management brings mapped Salesforce opportunity data, including standard and custom fields, into Rox, so a team can see deal names, owners, stages, and the fields that matter to its sales process.

Teams can search for an opportunity, choose a time range to focus a review, and create and edit boards for different pipeline reviews. The page describes it as a shared place to review opportunities and discuss where each deal stands.

Deal Execution

Rox's Deal Execution capability can generate account plans from the research, meetings, and emails already in Rox, and build org charts that identify decision-makers, champions, and key relationships and stay current as contacts and roles change.

It can also prepare assets ahead of meetings and key deal milestones. Those outputs support the stakeholder and champion questions in the deal checklist above.

Account-level agents

Rox assigns one dedicated revenue agent to each account. The agent retains account context and monitors signals continuously, so changes between reviews, such as a quiet stakeholder or a new threaded contact, are visible when the review begins.

At Rox, revenue orchestration means combining automated tasks with intelligence across roles, systems, and stages into an end-to-end revenue motion that reasons about what to do next.

Human oversight

AI-generated outputs, including pipeline scoring and meeting summaries, are informational and should be reviewed by authorized personnel before action. Features described as automated operate within user-defined parameters and require initial configuration and ongoing oversight.

Managers should confirm the filters, check the evidence behind any flag, and keep the call on forecast categories with a person.

See how Rox brings opportunity data into a shared pipeline review: Explore Rox Opportunity Management.

A 30-Day Plan to Improve Your Pipeline Review

  1. Week 1: Define. Write stage exit criteria as buyer behavior, set the forecast category rule, and agree the review agenda.

  2. Week 1: Build the pre-read. Create the four filter reports and a changes-since-last-review view.

  3. Week 2: Calibrate. Compute your value-based win rate and in-period yield by segment, and set coverage targets.

  4. Week 2: Share the view. Give reps the same pre-read and scorecard.

  5. Week 3: Run the new agenda. Use the timed agenda, the evidence questions, and the documented outputs.

  6. Week 3: Track actions. Open each review with last week's actions.

  7. Week 4: Review the review. Check slip rate, aging, and forecast accuracy against the prior month, and adjust thresholds.

Conclusion

A pipeline review earns its time when it replaces discovery with judgment. The pre-read finds flagged deals before the meeting, the agenda gives each part of the hour a purpose, and the pipeline-level checks show whether the book can support the target.

Coverage should come from your own win rate: a 25% value-based win rate needs 4 times the remaining target, and an 18% in-period yield needs about 5.6 times. Aging, slippage, and the shape of the book show whether deals are moving or only being re-dated.

At the deal level, inspect evidence from the buyer. Write stage exit criteria as buyer behavior, score every deal on the same risk factors, ask questions that require facts and not guesses, and end each inspection with a dated next step and an owner.

Forecast categories should follow a written evidence rule, as in the worked example where the largest deal stays in best case because the economic buyer is not engaged.

For enterprise teams, the evidence often sits outside the CRM, in the inbox, call transcripts, warehouse, and product data.

Rox's warehouse-native system of context, Opportunity Management boards, Deal Execution account plans and org charts, and account-dedicated agents are built to bring that evidence into the review, with people checking the outputs and owning the decisions.

To start, build the four-filter pre-read, run one review on the timed agenda, and record a next step, owner, and date for every deal you inspect.

Talk to the Rox team about bringing account context into your pipeline reviews: Visit Rox.

Frequently Asked Questions

What is a pipeline review?

A pipeline review is a recurring meeting where a sales leader and team inspect open opportunities, check pipeline health and deal evidence, and decide actions. It also makes the forecast more reliable.

How often should you hold a pipeline review?

Weekly for the team, with strategic deal reviews as needed and a monthly review by segment or region. Run a shorter alignment with finance on the forecast.

What should a pipeline review agenda include?

Changes since the last review, pipeline health, inspection of priority deals, and actions. In a 60-minute meeting, a workable split is 5, 15, 30, and 10 minutes, with about six deals inspected at 5 minutes each.

What should I inspect in a deal?

Stage and days in stage, close date and changes, amount and changes, forecast category, last buyer-side activity, and the next step. Then check evidence for the problem, economic buyer, decision process, paper process, champion, competition, and timeline.

Which filters find problem deals fastest?

Close dates in the past, deals in a stage longer than about 1.5 times the typical duration, no buyer-side activity in about 21 days, and amounts that changed by more than 25% without a note. Tune the thresholds to your own data.

How do I calculate the coverage I need?

Divide the remaining target by your value-based win rate for comparable qualified pipeline. A 25% rate gives 4 times coverage. If only part of eventual wins close in the period, multiply the win rate by that share first, for example 30% x 60% = 18%, which gives about 5.6 times.

What questions should managers ask in a pipeline review?

Ask for evidence: who approved the last purchase of this size, what the buyer said when price came up, what happens in their business after they sign, who could stop the deal, and what has to be true to close this period that is not true today.

How do I stop a pipeline review from feeling like an interrogation?

Share the same view and criteria with reps, ask the same questions for every deal, treat gaps as tasks, and focus on how you can help. Reps who feel exposed hide risk.

What is the difference between a pipeline review and a forecast call?

A pipeline review inspects pipeline health and deal evidence and produces actions. A forecast call decides what the team will close and sets the range. The review feeds the forecast.

How do forecast categories connect to the review?

Use a written evidence rule for each category. For example, commit requires most evidence items and an engaged economic buyer. The review checks that each deal in a category meets the rule.

What is different about enterprise pipeline reviews?

Enterprise deals have long cycles, many stakeholders, and a few large deals. Review stakeholder mapping, champion strength, account plans, and changes since the last review, and inspect the largest deals individually.

Can AI run a pipeline review?

AI can build the pre-read, gather buyer activity, flag silent stakeholders and slipped dates, and track changes. AI-generated outputs are informational and should be reviewed by authorized personnel before action. People own the judgments and the forecast.

How does Rox support pipeline reviews?

Rox's Opportunity Management brings mapped Salesforce opportunity data into Rox with boards for different pipeline reviews, and Deal Execution can build account plans and org charts that show decision-makers and champions. Rox's context graph and account agents add signals from the warehouse, inbox, and call transcripts. People review the outputs.

What should I record after a deal is inspected?

The risk score, forecast category, a specific next step, the owner on each side, the date, any manager action needed, and a follow-up date. Keep it in the CRM so the forecast call can use it.

Summarize this article with your favorite LLM

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.