4.1 Account Executive: Deal Analysis and Follow-Up

The role. Account Executive managing a mid-market pipeline.

The task. After every discovery and follow-up call, the AE needs to assess where the deal stands against the team's sales methodology, identify gaps in qualification, prepare for the next conversation, and send a follow-up that moves the deal forward.

How it works at this era. The AE finishes a call and pulls the transcript from their meeting recording tool. They paste it into Claude along with a brief description of their sales framework. For a team running MEDDPICC, the prompt is something like "Here's the transcript from my call. Analyze this against MEDDPICC and tell me what I've confirmed, what's still missing, and what I should ask next." The AI returns a structured breakdown showing that the AE has a clear understanding of the metrics and the decision process but hasn't identified an economic buyer or confirmed the champion's influence. The AE uses that gap analysis to plan their next call. Then they ask Claude to draft a follow-up email that recaps the conversation, confirms next steps, and subtly probes on the gaps identified. The whole process takes five minutes. Before AI, the follow-up email alone took ten to fifteen minutes and the structured deal analysis against methodology rarely happened outside of formal pipeline reviews.

The outcome. Follow-ups go out the same day, every time. Deal qualification gaps get surfaced after every call instead of once a week in a pipeline review. The AE walks into every next conversation with a clear plan for what to press on. Pipeline accuracy improves because gaps are visible early. Deals that aren't going to close get identified sooner.

4.2 SDR: Prospect Research and Personalized Outreach

The role. SDR responsible for outbound prospecting.

The task. Research a prospect, understand their context and likely priorities, and write outreach that demonstrates genuine understanding of their world.

How it works at this era. The SDR pulls up a prospect's LinkedIn profile, their recent posts or comments, the company's website, and any recent news or job postings. They copy all of this into Claude with a prompt like "Here's everything I found on this prospect. Based on their role, their company's current priorities, and what they've been posting about, tell me what this person probably cares about most right now and what angle would resonate if I'm selling them a platform that does X." The AI synthesizes the raw research into a read on the prospect. It might surface that the company just posted three new SDR roles, suggesting they're scaling outbound, and the prospect recently commented on a post about pipeline quality over quantity. That's an angle. The SDR now writes outreach grounded in a real understanding of what the prospect is dealing with, not a generic value prop. For high-priority prospects they might paste the AI's analysis back in and ask it to draft an email using that angle. For others they dictate a quick version using a tool like Wispr Flow and move on.

The outcome. Response rates go up because the outreach is actually relevant to what the prospect cares about. The SDR spends less time staring at a blank compose window trying to figure out the angle and more time working through their list. Personalization stops being a buzzword and becomes a real workflow. Instead of surface-level personalization like mentioning someone's job title or company name, the SDR is engaging with what the prospect is thinking about. The quality gap between a rushed email at the end of a session and the first email of the day narrows because AI keeps the research and synthesis consistent across the entire list.

4.3 CSM: Account Health Reporting

The role. Customer Success Manager handling a book of 30 to 50 accounts.

The task. Maintain clear, current internal visibility on the health of every account. Communicate risk, opportunity, and status to leadership and cross-functional teams.

How it works at this era. The CSM finishes a quarterly business review or a check-in call and has a transcript plus their own notes. They paste the transcript into Claude and ask for a structured account health summary. The prompt might be "Here's the transcript from my QBR with this customer. Give me a health summary covering product adoption, stakeholder sentiment, renewal risk, and expansion opportunities." The AI returns a clean, organized summary that the CSM reviews, adjusts, and drops into their internal reporting. For accounts where there's risk, they ask Claude to help draft an internal brief that flags the issue and suggests a plan of action.

The outcome. The quality and consistency of internal account reporting goes up dramatically. The CSM can handle more accounts because the time to synthesize a call into an actionable summary drops from thirty minutes to five. Leadership gets better visibility into the book of business because the reports are actually structured and current instead of outdated bullet points in a spreadsheet. Risk gets flagged faster because the friction of writing up the problem just disappeared.

4.4 Marketing: Content Production at Quality

The role. Content marketer or demand gen marketer responsible for blog posts, case studies, email campaigns, and social content.

The task. Produce a steady stream of content that sounds like the brand and drives engagement without burning out on the volume.

How it works at this era. The marketer develops a style guide and tone document that they paste into Claude at the start of every session. This is the critical difference between marketing and other revenue roles in Era 1. For an AE, a generic follow-up email is fine. For marketing, generic output is visible immediately and damages the brand. So the marketer invests upfront in teaching the AI how the brand sounds. They build prompts that reference specific examples of good and bad content. Over time, their prompting gets more sophisticated because the stakes of getting tone wrong are higher. They use AI to produce first drafts, rework messaging, generate variations for A/B testing, and repurpose long-form content into shorter formats.

The outcome. Content quality stays at the brand's standard while production speed increases. The marketer can produce more assets without the quality degrading into what audiences now immediately recognize as AI slop. The organizations that get this wrong are the ones that lead with volume and let quality slide. Audiences can smell it. Performance drops. The marketers who thrive in Era 1 are the ones who treat AI as a quality tool first and a volume tool second. They become the best prompters on the team because they have to be.

4.5 RevOps: Pipeline Analysis and Reporting

The role. RevOps analyst or manager responsible for pipeline reporting, forecast preparation, and operational visibility for revenue leadership.

The task. Turn raw pipeline data into clear, actionable reporting that leadership can use to make decisions. Prepare forecast narratives, spot trends, and surface problems before they show up in the numbers.

How it works at this era. The RevOps analyst exports pipeline data from the CRM and pastes it into Claude along with context about the team's targets, stage definitions, and historical conversion rates. They ask for a read on the current pipeline. "Here's our pipeline snapshot and our stage conversion benchmarks. Tell me where we're heavy, where we're light, what deals have been stuck in the same stage for more than 30 days, and what the implied close rate is against our quarterly target." The AI returns a structured analysis in minutes that used to take the analyst half a day of spreadsheet work. For forecast prep, they paste in the raw opportunity data alongside last quarter's forecast versus actuals and ask Claude to generate a narrative summary that a CRO could read in two minutes. The analyst reviews and adjusts, but the heavy lifting of turning numbers into a story is done. For ad hoc requests from leadership, the same pattern applies. Paste the data, ask the question, get a structured answer, clean it up, send it. The cycle time on every analytical request drops dramatically.

The outcome. Reporting cycles that used to take days compress into hours. Leadership gets pipeline visibility that's current instead of a week old. The RevOps analyst spends less time building reports and more time interpreting them, which is where they actually add value. Patterns that would have been buried in a spreadsheet get surfaced because the AI can process the full dataset at once instead of the analyst scanning rows manually. The RevOps team starts to see the potential for deeper integration. If copy-pasting data into a chat window produces this much value, what happens when the AI can read the CRM directly? That question plants the seed for Era 2, and RevOps is usually the team that starts pulling the org in that direction.