Where the team wanted to go
Sales teams have plenty of moments where better context changes the quality of the conversation.
A rep might want to understand how a customer’s industry is performing, how similar businesses are growing, or what patterns might make a pitch more relevant. The answers often exist somewhere in the business, but they are not always easy to reach at the moment they are needed.
The goal was not to give the team another dashboard. It was to help reps build the confidence to use data in their own work.
What was standing in the way
The data was there. The issue was the distance between a rep’s question and a usable answer.
Getting to the answer usually meant opening the right reporting tool, knowing which metric to look for, understanding how the data was structured, or asking someone else to pull it together. That creates a habit where reps stop asking useful questions because the path to the answer feels too slow.
For leaders, the capability gap was not just technical. It was about helping the team become more curious, more confident, and more willing to challenge the first version of a pitch with better evidence.
What we worked through
We started with the questions reps were already trying to answer.
What would help before a customer conversation? What context would make a pitch sharper? Where were people waiting on reports, dashboards, or other teams? Which questions were worth asking more often?
From there, we shaped a plain-English data agent around those real questions. A rep could ask about an industry pattern, compare similar businesses, or pressure-check a customer angle without needing to know how the underlying data was structured.
The important part was not the interface on its own. It was coaching people to ask clearer questions, follow up on the answer, and turn what they learned into something useful in the sales conversation.
How the team built confidence
We tested the agent with a small group of reps and refined it around the way they actually thought and worked.
Some questions were too vague. Some answers needed better commercial framing. Some terms meant different things to different people. Working through those examples helped the team learn what a good question looked like, where AI was useful, and when they needed to challenge the output.
Once the core patterns were working, we ran sessions with the broader sales team. The point was not tool training. It was practice: asking better questions, interpreting the answer, and using the evidence to prepare for better customer conversations.
What stayed with the team
Reps had a more practical way to bring data into their day-to-day work.
They could prepare with sharper context, test a hunch, and make customer conversations more specific without waiting for someone else to turn the question into a report.
For the team, the value was not just faster answers. It was a better habit: start with the problem, ask a clearer question, use AI to explore the answer, then decide how that changes the work.