Key takeaways
- Every workflow an agent runs needs one named person who answers for it.
- The builder role sits in RevOps or with a GTM engineer, not with each seller.
- Sellers spend less time on research and drafting and more on conversations.
- Someone must own the company knowledge the agents work from.
- The structure shrinks to two or three people in a small company without changing shape.
Which roles does an agentic GTM team need
An agentic GTM team needs five roles, though one person can hold several: a leader who sets goals and guardrails, a builder who designs the workflows, workflow owners who answer for results, reviewers who check output before it reaches customers, and a knowledge owner who keeps the company context accurate.
The roles matter more than the titles. In a twelve-person company the founder may lead and own knowledge while one seller builds and reviews. In a larger company each role becomes a job.
Who should own the agents
The person accountable for the workflow's outcome should own the agent that runs it, not the person who configured it. If an agent drafts first-touch emails for a segment, the sales manager for that segment owns the result, and the builder supports them.
This avoids the common failure where an agent belongs to whoever set it up, nobody checks its output after the first week, and problems surface only when a prospect complains.
What happens to SDRs and AEs
In most teams, SDRs and AEs keep their roles but change how they spend the day. Agents take on the repeatable preparation, such as account research, contact finding and first drafts, and the seller reviews, edits and decides what goes out.
That shifts hiring and coaching towards judgement: spotting a weak draft, choosing the right account, and running a good conversation. Many teams also give one experienced SDR part of the builder role, because they know what good preparation looks like.
How does the structure change with company size
The shape stays the same as you grow; what changes is how many hats each person wears. A founder-led team combines leader, owner and knowledge owner in one person. A mid-market team usually adds a dedicated RevOps or GTM engineering role. A large team splits building from governance and gives each region or segment its own workflow owners.
- Founder-led: the founder leads and owns knowledge, one seller builds and reviews.
- Growing team: a RevOps or GTM engineer builds; each sales manager owns their workflows.
- Mid-market and above: a small GTM engineering group, plus marketing owning brand voice.
Roles in an agentic GTM team
One person can hold more than one role in a small company.
| What they own | Typical title | |
|---|---|---|
| Leader | Goals, guardrails and which workflows to automate | Head of sales, CRO or founder |
| Builder | Designing, testing and changing workflows | GTM engineer or RevOps lead |
| Workflow owner | Results of one workflow and its review rules | Sales or marketing manager |
| Reviewer | Checking output before it reaches a customer | SDR, AE or marketer |
| Knowledge owner | Company facts, offer and brand voice | Product marketing or founder |
Where Pebbles Ai fits
- FoundationCompany IntelAdmins keep Company Intel current, with Business knowledge and Brand voice that every assistant works from, so the knowledge owner updates one place.
- FoundationAgent memoryCompany memory reaches colleagues' assistants, while Your memory and Project memory stay with the person or project, so shared facts and personal ones stay apart.
- CapabilityAI workspaceThe Marketing and Strategy assistants work in Assistant chat, with projects that keep related chats together for each workflow.
Common questions
Do we need to hire a GTM engineer to run agents?
Not at first. A RevOps lead or a technical seller can build the first workflows. Hire for the role once several workflows are live and keeping them working takes real time each week.
Should marketing or sales own the agents?
Each side owns the workflows whose results it answers for. Marketing usually owns brand voice and content workflows, sales owns prospecting and outreach, and RevOps keeps the shared rules consistent.
How often should the team review agent output?
Review every piece at the start, then move to sampling once the owner trusts the workflow. Keep a weekly check even when things go well, because company facts and markets change.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
