4.1 Account Executive: Connected Deal Prep and Execution

The role. Account Executive managing a mid-market pipeline of thirty to forty active opportunities.

The task. Prepare for upcoming customer calls, execute a consistent qualification process across every deal, and follow up from every interaction with structured, personalized communication.

How it works at this era. The AE starts their day by opening Claude, which is connected to their CRM, Gmail, Google Calendar, and meeting transcription tool through MCP. They say "prep me for my calls today." Claude pulls their calendar, identifies three customer calls, and for each one assembles a brief that includes the opportunity record from the CRM, the last two call transcripts, the most recent email thread, and any open action items from previous conversations. The AE reviews the briefs over coffee. For a deal that's been stuck in the same stage for three weeks, Claude flags the gap against their MEDDPICC framework. The AE walks into every call knowing exactly where they stand and what they need to press on. After each call, the AE says "help me follow up from that conversation." Claude pulls the transcript, cross-references it against the deal brief, drafts a follow-up email that references specific things the prospect said, confirms next steps, and sends it through Gmail. The AE reviews the draft, makes one adjustment, and approves the send. The whole post-call process takes two minutes. Before Era 2, the context assembly alone took longer than that.

“The entire post-call process takes two minutes. Before Era 2, the context assembly alone took longer than that.”

The outcome. Every deal gets the same analytical rigor regardless of how busy the AE is. Follow-ups go out within minutes of every call, not hours or days. Deal qualification gaps surface in real time instead of at weekly pipeline reviews. The AE manages forty opportunities with the same engagement quality they used to bring to twenty-five. Time spent on administrative work drops and time spent on actual selling goes up.

4.2 Customer Success Manager: Portfolio-Level Health Monitoring

The role. CSM managing a book of forty mid-market accounts.

The task. Maintain current visibility on the health of every account, identify risk early, surface expansion opportunities, and prepare for quarterly business reviews with a clear picture of where each account stands.

How it works at this era. The CSM runs a weekly workflow through Claude connected to their CRM, support ticketing system, meeting transcripts, and email. They say "scan my book for risk and opportunity signals." Claude pulls recent activity across every account. For an account that hasn't had a meaningful interaction in six weeks and has three open support tickets, Claude flags it as a risk with the evidence attached. For an account where the champion recently mentioned headcount growth and asked about a feature on the roadmap, Claude flags it as an expansion opportunity. The CSM gets a prioritized view of their entire book with specific, evidence-based flags instead of relying on memory and gut feel. For QBR prep, the CSM says "build my QBR deck for this account" and Claude assembles the key metrics, relationship timeline, open issues, and recommended next steps from data already in the connected systems. The CSM reviews, adjusts the narrative, and walks into the QBR prepared in fifteen minutes instead of two hours.

The outcome. Risk gets caught weeks earlier. Expansion opportunities get surfaced that the CSM would have missed reviewing accounts one at a time. QBR prep time drops from hours to minutes. The quality of internal reporting improves because every account summary is built on actual data from multiple systems instead of the CSM's recollection. The CSM's capacity goes up without their engagement quality going down.

4.3 RevOps: Live Pipeline Intelligence

The role. RevOps analyst responsible for pipeline reporting, forecast preparation, and operational visibility.

The task. Provide revenue leadership with current, accurate pipeline intelligence. Surface trends, flag risks, and prepare forecast narratives that leadership can use to make decisions.

How it works at this era. The RevOps analyst connects Claude to the CRM directly. There is no export step. When the VP of Sales asks "where do we stand against target for the quarter," the analyst opens Claude and asks the same question. Claude queries the CRM in real time, pulls pipeline data, applies the team's stage conversion benchmarks, and produces a pipeline summary with specific callouts. Deals stuck in the same stage for more than thirty days. Deals with close dates this quarter but no recent activity. Deals where the commit amount doesn't match the historical conversion rate for that stage. The analyst reviews the output, adds their own interpretation, and sends it to leadership. For forecast prep, Claude generates the narrative summary by pulling pipeline data alongside last quarter's forecast versus actuals. The analyst focuses their time on interpreting the story the data tells rather than assembling the data in the first place.

The outcome. Reporting cycles compress from days to hours. The gap between reality and the pipeline view leadership sees gets smaller because the data is current instead of a week old. The RevOps analyst shifts from data assembly to data interpretation, which is where they actually add value. Ad hoc questions from leadership get answered the same day they're asked. The RevOps function becomes faster and more responsive without adding headcount.

4.4 SDR: Scaled Prospect Research and Outreach

The role. SDR responsible for outbound prospecting across a target account list of two hundred accounts.

The task. Research prospects in target accounts, understand their priorities and pain points, and write outreach that demonstrates genuine understanding of their world. Do this at a volume that moves the pipeline needle.

How it works at this era. The SDR opens Claude connected to their enrichment tools, CRM, and email. They say "research the next twenty accounts on my list and build a brief for the primary contact at each one." Claude pulls company information, recent news, job postings, the prospect's LinkedIn activity, and any prior CRM history with the account. For each prospect, Claude produces a research brief that identifies likely priorities, relevant pain points, and a recommended outreach angle. The SDR reviews the briefs in batch, makes adjustments based on their own knowledge, and then asks Claude to draft personalized first touches for each one. The drafts are grounded in the research, not in generic templates. The SDR reviews, adjusts tone, and sends through the connected email integration. Twenty personalized, research-backed outreach emails go out in the time it used to take to research and write three.

The outcome. Response rates improve because the outreach is genuinely personalized, not template-personalized. The SDR covers more of their target account list per week. Pipeline generated from outbound increases because the volume of high-quality touches goes up. The SDR spends their time on strategy and relationship building instead of manual research and writing.