Pilot Ready
- Lead enrichment / prospecting
Start these as the team's first AI pilots.
Sales Team: AI Readiness
5 people · 5 fully scored
AI Opportunity
Each workflow plotted by AI fit (X, risk-adjusted) and business impact (Y). Top-right is the pilot zone: high-value work that AI can do well. High-stakes work pulls left, out of pilot territory, so the chart position matches the AI Fit score in the table.
6 of 6 workflows scored · suggestions extracted from individual survey answers
| # | Workflow | AI Fit / 100 | Impact | Stakes |
|---|---|---|---|---|
| 1 | Lead enrichment / prospecting Pilot Ready | 5 / 5 | Low | |
| 2 | CRM data hygiene Possible Automation | 3 / 5 | Low | |
| 3 | Quarterly business review prep Stay Manual | 3 / 5 | High | |
| 4 | Sales call prep notes Strategic Work | 4 / 5 | Low | |
| 5 | Renewal forecasting Strategic Work | 5 / 5 | Critical | |
| 6 | Strategic deal review Strategic Work | 4 / 5 | Critical |
AI Readiness Findings
Turns the chart above into an action plan: what to do with each workflow.
Possible Automation
- CRM data hygiene
AI could handle these, but they are lower impact. Automate if you have capacity; pilot the high-impact work first.
Strategic Work
- Sales call prep notes
- Renewal forecasting
- Strategic deal review
Keep human. High-impact work that needs human judgment; invest in the people who run it.
Stay Manual
- Quarterly business review prep
Keep this manual for now. Low impact and low AI fit, so put your AI attention elsewhere.
Keep human (for now)· workflows you scored + the team's own answers
Workflows you scored as judgment-heavy or high-stakes
- Judgment + stakesRenewal forecastingJudgment + stakes both high. Automating here would erode trust.
- Judgment + stakesStrategic deal reviewJudgment + stakes both high. Automating here would erode trust.
- Judgment-heavyQuarterly business review prepCalls for taste and stakeholder read. AI can't reliably do that.
What your team said
Unattributed by design. Use as scope input when piloting nearby.
Areas to keep people-led
Anything that touches the customer relationship without me. Sending an email under my name. Negotiating. Choosing what to say in a tough renewal conversation.
Pricing decisions. Competitive positioning in a hot deal. Anything where being slightly wrong tanks credibility.
Sending without a human eye. Some of the templates AI generates are too generic — they kill our reply rate. I always rewrite key phrases.
Real-time customer-facing technical answers. If a CISO asks about our encryption-at-rest story, I am giving the answer, not pasting an LLM output.
Customer messaging. Renewal conversations. Anything strategic about the account. The relationship is the product in CS — you cannot outsource that to a chatbot.
Where extra care is needed
If AI summarizes a customer call and gets the commitment wrong — promised features that are not on the roadmap — that is a relationship-killer. The mistake I see coming is hallucinated specificity.
If it makes up a customer reference or invents a feature, I look like an idiot in front of the prospect. Worse, I lose the deal and trust internally.
Hallucinated personalization. If AI pretends I read a blog post that does not exist, the prospect notices and we lose them forever.
Inventing security claims. If AI says we are FedRAMP-certified and we are not, that is a legal and reputational nightmare.
Tone-deaf customer responses. If AI sends a renewal email that misses that the sponsor just got laid off, we lose the customer. The risk of being inappropriate is high in CS specifically.
Voices from the team· grouped by theme, narrative answers only
Quotes are unattributed by design — see individual profiles for full surveys (leader access required).
Time drains
Quarterly business reviews. Every one has the same skeleton — usage trends, value delivered, expansion thesis, exec relationships, risks. The customer changes; the structure does not.
Repetitive workEvery QBR has the same skeleton: usage data, NPS, ROI summary, expansion thesis, risks. The narrative changes but the structure does not, and I rebuild it from scratch every time.
Repetitive work
Opportunities they see
RFP answers, code-snippet generation for sample integrations, customer-environment debugging by reading their config. Also: turning a sloppy discovery transcript into a structured POC plan.
Where AI could helpDrafting first passes — outreach, follow-ups, QBR narratives. Synthesizing call recordings into action items. Cross-referencing customer mentions across our archive when I am prepping.
Where AI could help
AI Sentiment· aggregate from 5 of 5 team members
Individual answers are never shown to leaders. Each cluster averages 3–4 related Likert items.
Enthusiasm
4.3 / 5 — high
Personal optimism about AI as a tool — energy + belief in its upside.
Org Trust
4.0 / 5 — high
Trust the company will introduce AI responsibly, with voice and psychological safety.
Clarity & Guidance
3.9 / 5 — high
People understand how AI affects their role and know where to get support.
Confidence
2.4 / 5 — low
Feels at ease about AI and secure about their role, workload, and how the company will use it.
What the team hopes & worries· aggregate · no individual attribution
Drawn from 5 of 5 team members' free-text sentiment answers. Quoted verbatim, without attribution.
Hopes
- If AI could automate the mechanical parts of forecasting and account research, I would have more time for the work only I can do — read the room, build trust, navigate executive politics.
- If AI could just take all the CRM updates off my plate, I would close more deals. The mechanical stuff is what's killing me.
- If AI handles the repetitive outbound, I can focus on personalization and being a real human to prospects. That is where I add value.
- Building reusable demo scripts and internal tooling. Right now every SE rebuilds the same demos. AI could help us systematize.
Concerns
- Hallucinations in customer-facing artifacts. If AI drafts a renewal email and invents a feature, I lose the customer.
- Quality control. I worry leadership will use AI output without checking, and quotas will get raised because we're 'more productive.'
- Other SDRs sending the same robotic-sounding AI emails. Inboxes are getting saturated and prospects can tell.
- Customers using AI to make decisions without understanding the trade-offs. Demos look great until production breaks at 2am.
What would build trust
- Clear examples of what good AI use looks like in sales contexts. Permission to experiment without fear of looking incompetent.
- Honest answers about how AI use will affect quotas, comp, and headcount over the next 18 months.
- Fast feedback loops. Let us experiment, share what works, and shut down stuff that's hurting reply rates.
- Clear policies on what data we can and can't share with cloud AI services. Engineering teams care about this more than sales realizes.
What leadership should keep in mind
- Don't substitute AI for human judgment in customer-facing work. Use it to free up time for the parts of our job that build long-term relationships.
- Don't pretend AI productivity gains are free. If we work less hours because AI helps, let us. Don't just raise the bar.
- Treat us like adults. SDRs are the test bed for everything AI-sales — if it works for us first, you save the org tons of pain later.
- Start with the work, not the tool. Identify what's actually broken in the SE process before throwing AI at it.
Capability shape
Team rangeTeam mean
The blue band is the team's min–max range per axis; the white center is where every member meets or exceeds the floor. The dashed line is the team mean. Click a name to add a person; hover to highlight. Tight bands = uniform; wide bands = either complementary or fragmented.
Team Findings
- MentorCoach pair on Domain DepthAlex Rivera, Riley Morgan (Level 5) could mentor; Sam Parker (Level 2) is a development candidate.
- MentorCoach pair on Institutional Know-HowQuinn Foster (Level 5) could mentor; Sam Parker (Level 2) is a development candidate.
- MentorCoach pair on Judgment QualityAlex Rivera, Quinn Foster (Level 5) could mentor; Sam Parker (Level 2) is a development candidate.
- MentorCoach pair on Process ClarityRiley Morgan (Level 5) could mentor; Quinn Foster (Level 2) is a development candidate.
- MentorCoach pair on CommunicationAlex Rivera, Quinn Foster (Level 5) could mentor; Riley Morgan (Level 2) is a development candidate.
- MentorCoach pair on AI FluencySam Parker (Level 5) could mentor; Alex Rivera, Quinn Foster (Level 2) are development candidates.
- ProtectKnowledge-loss risk: Riley Morgan, Quinn FosterHold substantial uncaptured context. Prioritize knowledge capture, shadowing, or written specs before any role changes.
- EnableUnderused delegators: Alex RiveraStrong at framing and validating work, but haven’t adopted AI tools. High-leverage candidates for AI enablement.
- ChampionAI pilot leaders: Sam Parker, Riley MorganStrong fit to lead AI pilots, build internal prompts/agents, and coach the rest of the team.
- DocumentKnowledge capture priority: Quinn FosterDeep expertise but workflows are unspecified. Investing in process clarity here unlocks both delegation and AI augmentation.
- LeverageGreen light sentiment: enthusiasm 4.3, trust 4.0Team energy and institutional trust are both strong. Conditions are right to accelerate pilots and let early adopters set the pace. Pair this momentum with the workflows in the Pilot Ready quadrant.
Want a diagnosis like this for your team?
Tell us a bit about you and we'll get you set up.