Skip to content

Roles: who does what

Evergrowth is a workspace where a whole go-to-market team collaborates with AI colleagues. Different people on that team use it for different things. This page maps the four roles - RevOps, Sales Reps, the CRO, and Marketing - to what each one actually does in Evergrowth and the outcome they own.

A useful way to think about it: RevOps designs the system, reps run it every day, the CRO reads the results, and Marketing feeds it. Everyone works with the same set of AI colleagues and the same shared Agent Training Center, so the work compounds instead of fragmenting across separate tools.

Roles in Evergrowth are about responsibility, not access. Pricing is credits, not seat licenses, and all features are on every tier - so there is no “RevOps edition” or “rep edition.” Any teammate can do any of the work below; these are the natural divisions of labor, not gated permissions.

RevOps owns how the go-to-market motion is set up. They are the architects: they decide who the team should be talking to, why those accounts are a fit, and what good outreach looks like - then they encode all of that so the agents and reps execute it consistently.

In practice, RevOps:

  • Defines who counts as a fit. They build out the team’s ecosystems and verticals (the company-level definition of an ideal customer) and the personas and buying committees (the people worth reaching inside those companies). These definitions are the foundation every agent reasons from.
  • Sets the value proposition. They capture the company’s positioning, proven outcomes, and differentiators in the value proposition so every research and outreach agent speaks the same story.
  • Builds and configures playbooks. They assemble the playbooks - the repeatable agent workflows for new-business, recycling, event follow-up, signal-based outreach, and more - and tune how the agents behave inside them.
  • Schedules the work. They decide which workflows run on their own and how often, so research stays fresh and signals get acted on without anyone remembering to push a button.
  • Monitors pipeline quality. They watch what the agents are producing - fit verdicts, signals, research quality - and refine the definitions when the output drifts from what the team wants.

The payoff for RevOps is leverage. Instead of being the single GTM engineer everyone queues behind, they set the strategy once and the whole team executes it through their digital colleagues. See Context vs data for why this distributed model beats centralizing every list-build in one person.

Reps are where the work meets the prospect. They don’t build the system; they run it, on demand, against the accounts and contacts in front of them.

A rep’s day in Evergrowth looks like:

  • Run agents when they need them. From running agents and the Chrome extension, a rep can qualify an account, research it, find the right contacts, and get outreach drafted - without leaving the page they’re already on.
  • Get research-backed outreach for every contact. The outreach a rep sends is written from what the agents actually found about that account and that person - a funding round, a leadership change, a recent post - not a template with a name dropped in. That’s the context vs data difference, and it’s what lets a rep send with confidence.
  • Practice before the call. Reps rehearse cold calls and discovery against a realistic AI buyer and get structured feedback afterward. See coaching: roleplay and feedback.
  • Prepare in the moment. They can talk through objections and refine positioning with a Digital Twin before a live conversation.

The point for reps is time and confidence. The hours that used to go into manual research collapse to minutes, and what lands in front of them is ready to act on.

Reps mostly work account-by-account and contact-by-contact, often triggered from the page they’re browsing. RevOps mostly works in bulk and in advance. Both are running the same agents - the difference is on-demand versus scheduled, one record versus a list.

The CRO doesn’t run agents day to day. They read the results, and they care about whether the motion is working and what it costs.

What the CRO gets from Evergrowth:

  • Pipeline visibility across every playbook. A single view of what the go-to-market machine is producing, rather than stitching together separate reports.
  • Quota and attainment. Line of sight into whether the team is on track.
  • Coaching adoption. Whether reps are actually using the coaching and practice tools - a leading indicator of ramp and consistency.
  • Cost-per-meeting economics. Because the work is priced in credits tied to specific agent tasks, the CRO can see what it costs to generate pipeline and reason about efficiency, not just volume.

The CRO’s question is “is this working, and is it worth it” - and Evergrowth gives them the operational and financial picture to answer it.

Marketing feeds the top of the funnel and makes sure the leads they generate don’t go cold.

Marketing typically:

  • Builds signal-based account lists. They assemble lists of accounts showing buying intent and hand them straight into the agentic workflows. See account signals and the signal-based outreach playbook.
  • Triggers event follow-up. Conference and webinar lists flow into a pre and post-event playbook so attendees get qualified and followed up while the event is still warm.
  • Feeds qualified leads into playbooks. Marketing-qualified leads drop into the inbound lead qualification flow, where they’re checked for fit and routed automatically the moment they arrive.

The win for Marketing is that the leads they work hard to generate get acted on consistently and personally, instead of sitting in a queue until a rep gets around to them.

RoleOwnsWorks mostly in
RevOpsStrategy and configurationAgent Training Center, playbooks
Sales RepsDay-to-day executionRunning agents, coaching
CROOutcomes and economicsPipeline visibility, credits
MarketingDemand and lead supplySignals, event and inbound playbooks

These roles aren’t silos. The definitions RevOps writes shape the outreach reps send; the leads Marketing feeds become the pipeline the CRO measures; the cost signals the CRO watches inform how RevOps tunes the playbooks. To see the underlying machine all four roles share, read How Evergrowth works and How the layers fit together.