How to Prepare and Run a Sales Demo: Talk Track, Discovery Questions, and Next Steps

Leah Clapper

Summarize this article with your favorite LLM
Table of contents

Summarize article with your LLM

A sales demo is a live or recorded walkthrough in which a seller shows how a product solves the specific problems a buyer described in discovery.

A strong demo starts from a written summary of the buyer's needs, shows only the two or three workflows that address them, follows a timed agenda, and ends with a dated next step owned by both sides.

The demo is the point in a sale where the buyer decides whether the product is real. Before it, the buyer has read a website, perhaps watched a video, and talked through a problem with a seller.

After it, the buyer knows whether the product fits their situation, whether the seller understood them, and whether the next investment of time is worth making. Few other moments in a deal carry that much weight, and few are prepared as casually.

A rep opens the product, clicks through the standard tour, and hopes something lands.

That approach fails for a predictable reason. A standard tour shows what the product can do. A buyer wants to know what the product will do for them. The two overlap only by chance, and the rest of the tour is noise.

Buyers sit through screens that do not matter to them, miss the moment that does, and leave unable to say what they saw. The seller feels the demo went well because there were no hard questions. Nothing was decided, and the follow-up call is hard to get.

The guide is written for account executives, sales engineers, solution consultants, sales leaders, and buyers who want to know how to get the most from a demo.

It gives no benchmark conversion rates, because results depend on the product, the buyer, and the stage of the deal. It shows how to measure your own.

What Is a Sales Demo?

A sales demo is a structured presentation of a product, live or recorded, designed to show a buyer how the product addresses their stated needs.

It differs from a product tour, which shows the product broadly, and from a trial, in which the buyer uses the product directly.

Types of demo

Type

Purpose

Audience

When

Discovery-led demo

Confirm fit against stated needs

Evaluators and the champion

After discovery

Product tour

Show the product broadly

Early researchers

Before discovery, or self-serve

Technical deep dive

Test integration, security, and architecture

Technical reviewers

Mid-stage

Executive demo

Show business impact and outcomes

Economic buyer and sponsors

Late stage

Proof of concept

Test on the buyer's data or process

Evaluation team

Late stage

Recorded or self-serve demo

Support research and sharing

Wider stakeholders

Any stage

A single deal often uses several of these. The discovery-led demo is the one this guide focuses on, since it is the most common and the one that sets up the rest.

Who attends and who leads?

The account executive usually leads the conversation and the next steps. A sales engineer or solution consultant often drives the product.

On the buyer side, aim to have the person who feels the problem and someone who understands the decision process and budget. For related roles and stakeholders, see buying committee mapping and multi-threading.

The Discovery Gate

Do not demo without discovery. If you must demo early, say so, and keep it to a short vision of what is possible.

Discovery gives you the material for the demo. A discovery-led demo needs six inputs.

Input

Question to ask

Why it matters

Trigger

What prompted you to look at this now?

Shows urgency

Current state

How do you handle this today, and where does it break down?

Defines what to show

Impact

What does leaving it as it is cost you?

Builds the case

Stakeholders

Who is affected, and who decides?

Shapes the audience

Success

If this works, what does success look like in six months?

Gives the finish line

Timeline and obstacles

What is your timeline, and what could get in the way?

Sets next steps

A discovery and demo call template from OrgTP makes the same point: open with a two-way agenda so the buyer knows questions come first, spend real time on current state, pain, impact, decision process, and timeline, and then show only the capabilities that map to what the buyer said.

For more on discovery, see discovery calls and solution selling.

When discovery is incomplete

Sometimes the buyer is still exploring. In that case the goal is not to prove fit. It is to show what becomes possible, using patterns and examples from similar companies, and to earn a proper discovery conversation. Say that plainly at the start so the buyer does not mistake it for a tailored demo.

Build the Demo From a Customer Summary

Write what you heard in the buyer's own words, and build the demo from that summary.

The Sales Engineering community's guide to using discovery to build a demo recommends writing a simple customer summary before preparing anything: the buyer's role, their most important business challenge, the problems that make it hard to solve, the specific capabilities they need, what improvement would mean for them, and the timeline that drives urgency. If a capability does not connect to something in that summary, it probably does not belong in the demo.

Read their guide on how to use discovery to build a demo the buyer actually needs to see for the full approach.

A customer summary template

Field

Content

Role and team

Who the buyer is and who is affected

Top business challenge

In their words

What makes it hard today

The causes they named

Capabilities needed

The specific things they asked for

What improvement means

Their definition of success

Timeline and driver

The date and what sets it

Stakeholders and decision process

Who decides and how

Open questions

What you still need to learn

Convert the summary into demo chunks

Take each need and turn it into a self-contained scenario. If the buyer named three needs, the demo has three chunks. Each chunk should state the problem, show the workflow that solves it, and end on the result.

Buyer need (their words)

Demo chunk

Result to show

"Reports take two days each month"

Automated report from current data

The finished report and the time it took

"We miss changes in accounts"

Signal alerts on an account

An alert and the recommended next step

"New reps take months to ramp"

Prepared briefs before calls

A brief for an upcoming call

Worked example 1: how much of the product to show

Illustrative example. A product has 40 features. The buyer named three needs, and each maps to one workflow that uses a handful of features. The demo shows those three workflows.

  • Share of the product shown: 3 workflows out of 40 features is 3 / 40 = 7.5%.

  • Time per workflow: with 20 minutes of demo time and two main workflows, each gets 20 / 2 = 10 minutes. With three workflows, each gets about 6.7 minutes.

Showing 7.5% of the product is not a weakness. A focused twenty-minute demo tied to what the buyer described usually persuades more than a long walkthrough, because the buyer can see their own problem solved. Resist the urge to show breadth.

A 45-Minute Demo Agenda

Use a fixed agenda, share it at the start, and protect the time for next steps.

Minutes

Segment

What happens

0 to 5

Open

Introductions, agenda, goal, and a promise to save time for next steps

5 to 15

Recap and confirm

Read back the customer summary and confirm it, with any changes

15 to 35

Show the fit

Demo the chosen workflows, checking in after each

35 to 45

Next steps

Recap, questions, one buyer commitment, owner, and date

Arithmetic: 5 + 10 + 20 + 10 = 45 minutes. The demo block of 20 minutes divides into two workflows at 10 minutes each, or three at about 6.7 minutes.

Other published agendas follow the same logic. The OrgTP template, for example, allots 4 minutes to opening, 15 to discovery, 15 to a tailored demo, 6 to questions, and 5 to next steps for a call that combines discovery and demo. Choose the split that fits whether discovery already happened.

Open the demo

A good opening does four things: confirms the time and attendees, states the goal, previews the agenda, and tells the buyer you will save time at the end to agree on next steps. A sample opening:

"Thanks for making time. I would like to start by confirming what you told us last week, then show how we handle those three things, and then spend the last ten minutes agreeing what happens next. Does that work? Is anyone joining who I should know about?"

Read the summary back

Start with the customer summary, in their language. For example: "You said your goal is to cut the time spent assembling account reports. The main problem is that the data lives in several systems and the team copies it by hand.

What you need is one place that shows the current picture. Is that still accurate?" That moment of recognition changes the call from a vendor presentation into a conversation, and it gives the buyer a chance to correct you before you show anything.

Talk Track Structure

Use the same five-step pattern for each chunk: recap the problem, show the outcome, walk the workflow, check in, and tie back.

Step

What you do

Example

1. Recap the problem

State the need in the buyer's words

"You said approvals take three weeks."

2. Show the outcome first

Start from the finished result

"Here is an approved request, ready in minutes."

3. Walk the workflow

Show how it gets there, narrating outcomes not clicks

"The system routes it to the right approver automatically."

4. Check in

Ask what they think

"How does that compare to how you do it today?"

5. Tie back

Link to the original problem

"That addresses the three-week delay you mentioned."

Narrate outcomes, not clicks

"I click here, then here, then here" describes the interface. "This shows you which accounts need attention today, ranked by what changed" describes the outcome. Buyers remember the second.

Sell the destination

Focus on the value and the future state the product enables, not the mechanics. The mechanics matter when they answer a question, and they should not carry the demo.

Questions to ask during the demo

  • How does this compare to how your team handles it today?

  • Who on your team would use this most?

  • What would you need to see to trust this?

  • Is there anything here you would change?

  • What would make this unworkable for you?

These check-ins keep the buyer talking, and they tell you what to include in the recap.

Tailor to the People in the Room

Different roles need different views. Showing the wrong level of detail to the wrong person is a preparation failure, not a delivery failure.

Role

Wants to see

Show

Avoid

Executive or economic buyer

Business impact, trends, risk

Dashboards, outcomes, summaries

Navigation detail

Manager

Monitoring, exceptions, team coordination

Team views, alerts, reporting

Individual task screens

End user

Daily workflow, speed, simplicity

Step-by-step flows

Strategic dashboards

Technical reviewer

Integration, security, data flow

Architecture, permissions, setup

Marketing language

Procurement or legal

Terms, risk, compliance

Security and governance materials

Product tour

If a mixed audience attends, structure the demo to speak to each in turn, and say who each section is for.

Prepare for the people who are not there

Ask who else needs to see this. The next step after a first demo is often a second meeting with stakeholders who were absent, so build a version that can be shared, such as a recording and a short recap.

Handle Questions and Objections in the Demo

Surface concerns during the call. Concerns that stay unspoken harden after it.

  • Park off-topic questions. Note them visibly and return to them at the end.

  • Answer directly. If you do not know, say so and commit to a date.

  • Ask what is behind a question. "What would you do with that?" often reveals the real need.

  • Acknowledge, then respond. Do not talk past an objection. See objections for sales.

  • Check the answer landed. "Does that address your concern?"

  • Avoid disparaging alternatives. Stay on the buyer's situation.

Common demo-time objections

Objection

Response approach

"We already have something for this."

Ask what it does not do well and show that gap

"This looks complicated."

Show the shortest path to the outcome

"How does it work with our systems?"

Show or describe the integration, and offer a technical session

"Is our data safe?"

Share security and governance materials and involve security

"Can it handle our scale?"

Ask for the scale and respond with specifics, or commit to follow up

Plan for things going wrong

  • Use stable data. Prepare a demo environment with realistic data that will not break.

  • Have a backup. Keep a recording or screenshots for each workflow.

  • Test the setup. Check audio, screen share, and access before the call.

  • Handle a failure calmly. Acknowledge it, switch to the backup, and move on.

Close With Next Steps

To agree next steps before a demo ends, save time at the end, recap what you heard, and ask the buyer to commit to one specific action with a named owner and a date.

Book the next meeting while everyone is still on the call.

A repeatable closing process

  1. Say it at the start. Tell the buyer you will save the last ten minutes for next steps.

  2. Recap what you heard. Play back their top problems and how each was addressed, and ask what you missed.

  3. Ask the key questions. See the list below.

  4. Agree one commitment. One action, owned by a named person on the buyer's side, with a date.

  5. Book the next meeting now. Put it on the calendar before the call ends.

  6. Send a recap the same day. Include what was heard, what was shown, the agreed next step, and open items.

Questions for the last ten minutes

Question

What it reveals

Who else needs to see this?

Stakeholders who sign off but were absent

What has to be true for you to move forward?

Criteria, risks, and blockers

What is your timeline, and what drives it?

A real date on the buyer's side

What concerns do you still have?

Objections not yet raised

Can we book the next meeting now?

A date in the calendar

What counts as a next step

A good next step is specific, dated, and owned by a named person. "We'll connect next week" fails.

"Priya shares the recording with the security team by Friday, and we meet Thursday at 2:00 pm to review their questions" passes.

See call summaries and next-step recommendations for how next steps affect outcomes.

The recap message

Section

Content

What we heard

The customer summary, with any changes

What we showed

The workflows and results

Agreed next steps

Action, owner, and date for each side

Open items

Questions and commitments to follow up

Resources

Recording, relevant material, and documentation

Worked example 2: next-step rate

Illustrative example. A team reviews 30 demos before and 30 after adopting the discovery gate and the closing process.

  • Before: 18 of 30 demos ended with a dated next step. 18 / 30 = 60%.

  • After: 24 of 30 did. 24 / 30 = 80%.

  • Change: 80% - 60% = 20 percentage points.

Thirty demos is a small sample, and other factors may have changed. Treat the result as a signal and track it over a larger set.

Score Your Demos

A scorecard makes review consistent and shows which part of the demo needs work.

Criterion

Weight

What good looks like

Discovery fit

25

Demo maps to stated needs

Story

20

Clear problem, outcome, and tie-back

Proof

15

Realistic data and results shown

Engagement

15

Buyer spoke, asked questions, and was checked in with

Handling questions

10

Concerns addressed directly

Next step

15

Dated step with an owner

The weights total 25 + 20 + 15 + 15 + 10 + 15 = 100. Score each criterion from 1 to 5.

Worked example 3: scoring two demos

Illustrative example.

Criterion

Weight

Demo A score

Demo B score

Discovery fit

25

4

5

Story

20

3

4

Proof

15

5

4

Engagement

15

3

4

Handling questions

10

4

3

Next step

15

2

5

  • Demo A: (25 x 4) + (20 x 3) + (15 x 5) + (15 x 3) + (10 x 4) + (15 x 2) = 100 + 60 + 75 + 45 + 40 + 30 = 350. Dividing by 5 gives 70 out of 100.

  • Demo B: (25 x 5) + (20 x 4) + (15 x 4) + (15 x 4) + (10 x 3) + (15 x 5) = 125 + 80 + 60 + 60 + 30 + 75 = 430. Dividing by 5 gives 86 out of 100.

Demo A had strong proof and a weak next step, which points the coaching at the close. Review a sample of recorded demos each month, and compare scores with outcomes such as the next-step rate and progression to the next stage.

For using call data in coaching, see sales agent call prep and live-call assistance.

Enterprise Demos

Enterprise demos involve several stakeholders, technical and security review, and longer evaluation, so they often become a series.

  • Split the sequence. A first demo for evaluators, a technical session, an executive session, and sometimes a proof of concept.

  • Prepare security and integration material. Enterprise buyers ask about permissions, data handling, and systems they use.

  • Agree evaluation criteria. Define what a successful proof of concept looks like before it starts.

  • Bring the right people. A sales engineer, a security contact, and an executive sponsor where needed.

  • Plan for procurement. Surface paper process requirements early.

  • Tailor to each unit. Different business units may need different scenarios.

  • Use account context. Draw on what the account has said in emails, calls, and earlier demos. See AI proposal personalization for tailoring materials.

The context gap in demos

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. For a demo, the gap means the presenter walks in without knowing what the buyer's colleague asked last week, which concern the champion raised, or which security question is open.

Virtual Demo Checklist

  • Send the agenda and a calendar link with a join link in advance.

  • Test audio, video, screen share, and permissions.

  • Close unrelated tabs and notifications.

  • Keep a second screen for notes and the customer summary.

  • Record, with consent, so absent stakeholders can watch.

  • Ask for the camera to be on if the group is small and comfortable.

  • Use the chat for questions in larger sessions.

  • Share a link to materials in the recap.

Common Mistakes

  1. Demoing before discovery. The buyer sees features that solve no problem of theirs.

  2. Showing everything. Breadth dilutes the moments that matter.

  3. Narrating clicks. Describe outcomes.

  4. No agenda. The call drifts and the end gets squeezed.

  5. Skipping the read-back. You lose the chance to check your understanding.

  6. One demo for every audience. Executives and users need different views.

  7. Talking past objections. Concerns harden after the call.

  8. Ending without a dated next step. "We'll follow up" is not a plan.

  9. Using unstable demo data. A broken demo damages trust.

  10. Contradicting the website. Inconsistency undermines credibility. Gartner's survey of 632 B2B buyers found that 69% reported inconsistencies between a vendor's website and what sellers told them; see the Gartner survey on rep-free buying preferences.

  11. No recap. The buyer forgets, and absent stakeholders have nothing to read.

Using AI to Prepare and Follow Up

AI can prepare the brief, tailor materials, and draft the recap. People review everything before a buyer sees it.

Task

What AI contributes

Control to keep

Account brief

Gathers account research, history, and attendees

Check key facts

Discovery summary

Drafts the customer summary from call notes and transcripts

Confirm with the buyer

Tailored assets

Prepares decks, one-pagers, or scenarios

Review for accuracy and tone

Talk track

Drafts a structure around the buyer's needs

Edit to your voice

Recap

Drafts the follow-up message

Approve before sending

Review

Summarizes the demo against the scorecard

Spot-check against the recording

AI-generated outputs 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.

Preparing for a Rox Platform Demo

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.

If you are preparing to see Rox in action, use the same method this guide describes, from the buyer's side.

What to bring to a Rox demo

Item

Why it helps

The workflow you want to improve

Keeps the demo on your problem, such as prospecting, deal reviews, or expansion

Who will attend and their roles

Lets the team tailor the views

Your systems

CRM, email and calendar, and data warehouse, since Rox's site lists Salesforce, HubSpot, Gmail, Microsoft Outlook, and Slack among its integrations

Success criteria

Defines what you need to see to continue

Data and security questions

Brings the right reviewers in early

Timeline and decision process

Shapes next steps

Questions to ask in the demo

  • Which signals does the agent use for my accounts, and where do they come from?

  • How do I review and correct what the agent does?

  • What does setup involve, and who maintains it?

  • How are permissions and governance handled?

  • What would a pilot on my own accounts look like?

Resources before the call

Rox Academy lists product demo videos organized by category, including a platform tour titled "One Agent Per Account." Watching one before the conversation can help you decide which workflows to ask about. Ask the Rox team about the format and length of a live demo for your use case.

How Rox supports demo preparation on the seller side?

Rox's Deal Execution capability can generate personalized artifacts on demand, and workflows can prepare assets ahead of meetings and key deal milestones, in a team's own messaging and style.

Rox assigns one dedicated revenue agent to each account, which retains account context and monitors signals, so a brief can draw on what the account has discussed across email, meetings, and calls.

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 meeting summaries and prepared assets, 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. Review any brief or asset before it goes to a buyer.

Watch Rox product demos in the Rox Academy demo library: Explore the Rox Academy.

A 30-Day Plan to Improve Your Demos

  1. Week 1: Set the gate. Define the discovery inputs required before a tailored demo, and write the customer summary template.

  2. Week 1: Build the agenda. Adopt the 45-minute structure, and prepare an opening script.

  3. Week 2: Build demo chunks. Turn your most common buyer needs into reusable scenarios with stable data.

  4. Week 2: Prepare backups. Record each scenario and keep screenshots.

  5. Week 3: Score a sample. Review 10 recorded demos with the scorecard, and note patterns.

  6. Week 3: Coach. Focus on the lowest-scoring criterion.

  7. Week 4: Measure. Track the share of demos that end with a dated next step and progress to the next stage.

  8. Week 4: Refine. Update the template, scenarios, and closing questions.

Conclusion

A sales demo works when it answers the buyer's question, which is whether the product will solve their problem, with evidence from their own situation. That starts before the call.

Discovery supplies the needs, a customer summary in the buyer's words turns them into a plan, and the demo shows only what maps to that plan.

In the worked example, three workflows covered 7.5% of a 40-feature product, and that was enough because each one addressed something the buyer said.

The call itself follows a structure: a short open that previews the agenda and promises time for next steps, a read-back of the summary, workflows shown outcome first with check-ins, and a close in which one buyer commitment, an owner, and a date are agreed before the call ends.

A same-day recap carries the conversation to stakeholders who were absent. Scoring demos with a rubric shows where to coach, and tracking the next-step rate shows whether the changes work.

For enterprise teams, demos run as a series and depend on account context that sits across the inbox, call transcripts, warehouse, and product data.

Rox's warehouse-native system of context and account-dedicated agents are built to bring that context into preparation, with people reviewing everything a buyer sees.

To start, write the customer summary template, adopt the 45-minute agenda for your next five demos, and record a dated next step at the end of each one.

Talk to the Rox team about a demo built around your own workflow: Contact Rox.

Frequently Asked Questions

What is a sales demo?

A sales demo is a live or recorded walkthrough in which a seller shows how a product addresses a buyer's stated needs. A discovery-led demo is built from what the buyer said in discovery.

How do you prepare for a sales demo?

Complete discovery, write a customer summary in the buyer's words, choose the two or three workflows that map to their needs, prepare stable demo data and a backup, confirm attendees, and set an agenda that saves time for next steps.

How long should a sales demo be?

Many demos run 30 to 60 minutes. A workable 45-minute structure is 5 minutes to open, 10 to recap and confirm needs, 20 to show the fit, and 10 to agree next steps.

What discovery questions should I ask before a demo?

Ask what prompted the evaluation, how they handle the problem today and where it breaks down, what it costs to leave it as it is, who is affected and who decides, what success looks like in six months, and what the timeline and obstacles are.

How much of the product should I show?

Only what maps to what the buyer said. If a product has 40 features and the buyer named three needs, showing the three workflows that address them is about 7.5% of the features, and that is usually enough.

What should a demo talk track include?

For each need: recap the problem in the buyer's words, show the outcome first, walk the workflow while narrating outcomes, check in with the buyer, and tie it back to the original problem.

How do I handle objections during a demo?

Surface them, acknowledge them, and answer directly. Park off-topic questions, ask what is behind a question, check that the answer landed, and avoid disparaging alternatives.

How do I end a demo?

Recap what you heard, ask who else needs to see it and what has to be true to move forward, agree one buyer commitment with an owner and a date, and book the next meeting before the call ends. Send a recap the same day.

What should a demo follow-up include?

What you heard, what you showed, agreed next steps with owners and dates, open items, and resources such as the recording and documentation.

How do I tailor a demo to different roles?

Show executives impact and trends, managers monitoring and exceptions, users the daily workflow, technical reviewers architecture and security, and procurement the terms and governance materials. Say who each section is for.

How do I measure demo quality?

Use a scorecard with weighted criteria such as discovery fit, story, proof, engagement, handling questions, and next step. Track the share of demos that end with a dated next step and progress to the next stage.

Can AI help prepare a demo?

AI can build an account brief, draft the customer summary, tailor assets, suggest a talk track, and draft the recap. AI-generated outputs are informational and should be reviewed by authorized personnel before they reach a buyer.

How should I prepare for a Rox demo?

Bring the workflow you want to improve, the attendees and their roles, your CRM, email, calendar, and data warehouse details, your success criteria, and your security and data questions. Ask the Rox team about the format and length of a demo for your use case.

What is different about enterprise demos?

They involve several stakeholders, technical and security review, and sometimes a proof of concept, so they often run as a series. Prepare security and integration material, agree evaluation criteria in advance, and bring the right people.

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.