GTM teams: who sits on one, who owns which decision, and how the handoffs between them actually work.

Definition

GTM teams, short for go-to-market teams, are the cross-functional groups that take a product to a market and keep the revenue coming in, instead of one department owning one stage of the buyer's journey and handing the rest to someone else.

A GTM team pulls people from marketing, product marketing, sales, sales development, customer success, enablement and revenue operations. They keep their reporting lines inside their own functions. What makes them one team is a shared revenue target, one definition of the customer, one set of numbers and one library of plays they agree to run.

The go-to-market strategy decides the market, the positioning, the pricing and the motion. The GTM team is the people who carry it out every week. This page is about them: the roles, who owns which decision, where work changes hands, and what each role is measured on.

Why companies organize as a GTM team

The case for a GTM team, in B2B companies especially, is about the gaps between departments, not about any one department. In this page's view, four problems push companies toward the model, often long before anyone says GTM team.

• Targeting drifts. Marketing chases one profile, sales calls another, and customer success inherits accounts neither side would have picked. A shared customer definition fixes that.
• The message splits. The ad says one thing, the demo says another, and the onboarding call says a third. One owner for positioning keeps the story the same from first touch to renewal.
• Numbers disagree. Each function counts leads, pipeline and churn its own way, so meetings turn into arguments about whose dashboard is right.
• Nobody owns the gaps. A lead waits days for follow-up, a closed deal reaches onboarding with no notes, a renewal risk is spotted and never raised. A GTM team names an owner for each of those moments.

How GTM teams differ from the sales team

The sales team sits inside the GTM team; it is not another word for it. Sales owns the open opportunity: the conversations, the pipeline and the close. The GTM team owns the whole route, from a stranger who has never heard of you to a customer who renews and expands.

The practical test is what happens when a deal is lost. A sales team asks what the rep could have done differently. A GTM team also asks whether the account should have been targeted, whether the message was wrong, and whether onboarding would have failed anyway.

Who is on a GTM team

Many GTM teams are built from the roles below. Small companies combine several of them in one person, and that is normal. What matters is that each line in the table has a name next to it, not that each line has a separate hire.

In this page's view, product marketing and product management are the two roles easiest to confuse. Product management decides what gets built. Product marketing decides who it is for, how it is described and how sellers explain it.

In the model used here, product marketing sits in the weekly GTM meetings, and product management joins when the roadmap is on the agenda.

Enablement is the role that keeps the team's knowledge current. The sales enablement entry covers what it produces and how it is run.

GTM team roles in official job data

GTM job titles move fast, so it helps to anchor them in something that does not. The US federal occupational databases, O*NET OnLine and the Bureau of Labor Statistics Occupational Outlook Handbook, describe several GTM roles under older, stable names. The table maps them.

What the reported job titles show

O*NET lists sample job titles reported by people in each occupation. For Sales Managers, the list includes sales director, sales VP, sales operations manager and a combined sales and marketing VP. That last title is a GTM lead under an older name.

For Marketing Managers, the reported titles include product marketing manager, product manager, brand manager and business development director. The federal taxonomy groups product marketing with marketing management rather than with product development, which is also how the roles table on this page seats it.

For Sales Engineers, reported titles include sales engineer, sales applications engineer and technical marketing engineer. For the technical sales representative occupation, they include inside sales representative, which is the closest federal match to a sales development seat.

How the Handbook describes the links between roles

The Occupational Outlook Handbook says sales managers work closely with managers from other departments, naming marketing and sales, which identify and target new customers, and research and design, which studies customer preferences. That is a cross-functional team described in plain federal language.

The Handbook says marketing managers estimate demand, identify potential markets, may develop pricing and ways to acquire and retain customers, and work with product development, public relations and sales staff. Retention appears in the marketing description, not only in a customer success one.

For sales representatives, the Handbook describes inside representatives who sell mostly from an office and outside representatives who visit clients. It says representatives often pair with technical experts or sales engineers in presentations, and may make follow-up visits after a sale. That is the account executive, solutions and onboarding handoff in one occupation.

The sales engineer entry says these engineers talk with customers, the sales team and engineers to work out needs, work with sales teams to secure and renew orders, and in some cases work with research and development on new products.

Roles the federal data does not name

When this page checked on Oct 1, 2026, O*NET keyword searches for customer success manager and revenue operations manager returned no occupation with that title, only loosely related ones. The same was true for GTM engineer. Descriptions of those roles come from employers, not from federal data.

That matters when you write job descriptions or compare pay. For the roles with a federal match, the O*NET and Handbook pages give a neutral description to start from. For the newer roles, write the description from the decisions and metrics the role will own on your team, which the next sections lay out.

What each part of the team owns, by stage

The cards read left to right, but the work does not. Customer success hears why customers stay, which should change the message product marketing writes. Sales development hears objections first, which should change who demand generation targets. A GTM team is built so that those signals travel backward as easily as leads travel forward.

Who leads a GTM team

Ownership varies, and there is no single correct answer. What a GTM team cannot survive is having no answer, because every disagreement between functions then goes to whoever argues loudest. The common patterns below are described as options, not as a ranking.

• A chief revenue officer or revenue leader. One person owns the number across marketing, sales and customer success, decides where the next hire goes and settles disputes between segments.
• A GTM manager or GTM lead. A coordinator, often close to product marketing, who runs launches and the GTM sync without owning the revenue target.
• The founder or CEO. In early companies the founder is the GTM lead by default, because nobody else sees both the product and the customer every day.
• A leadership group. Function heads share the target and meet weekly. This works when the definitions are settled and fails when they are not.

Whichever model you choose, separate two jobs. One person owns the revenue number. Another, often revenue operations, owns the definitions and the data. When the same person owns both, the definitions tend to bend toward the number, which is a reporting problem worth designing out from the start.

Go to market team ownership: who decides what

Alignment is mostly a list of decisions with a name next to each one. The matrix below was written for this page as a starting point. Change the names to fit your team, but keep the rule that each decision has exactly one owner.

Notice how many decisions depend on a written rule. Most friction on GTM teams, in this page's view, comes from decisions that were never written down, so each side remembers a different agreement.

Metrics each GTM role owns

A GTM team shares one target, but each role still needs a number it can move by itself. If a role only owns shared numbers, nobody can tell whether it is doing its part. The pairing below is this page's suggestion: one number the role owns, one it shares.

The numbers the whole team shares

GTM teams fail quietly when each function reports a different number for the same thing. Agreeing on the definitions is revenue operations work, and it is worth more than any new dashboard.

• Pipeline created, split by source and by play, so a play can be credited or retired on evidence rather than on opinion.
• Stage conversion, measured between the same stages by everyone, using the same sales process definitions.
• Cycle length, from first meeting to closed, which can differ sharply by motion and by segment.
• Win rate against a named alternative, including the option of the buyer doing nothing, which a loss review should always consider.
• Retention and expansion, because a GTM team that wins accounts it cannot keep is running the wrong plays or targeting the wrong market.

Where GTM teams break: the handoffs

In this page's view, many failures blamed on alignment are really handoffs with no written rule. Four of them matter most, and each needs a definition both sides have signed rather than a slide both sides have seen.

• Marketing to sales. What counts as a qualified lead, how it is routed, and how quickly it must be worked. MQL vs SQL covers the two qualification stages.
• Sales development to account executives. What makes a meeting accepted, and what happens to the credit when it is rejected.
• Sales to customer success. What was promised, what is in scope, and who introduces whom, covered in sales handoff.
• Customer success back to sales. When an expansion signal becomes an opportunity, and who owns the conversation with the budget holder.

How CRM software records a handoff

CRM vendors build the handoff into the record itself. HubSpot's knowledge base says its lifecycle stage property shows where a contact or company is in the marketing and sales process and how leads are handed off between marketing and sales.

HubSpot's default stages run subscriber, lead, marketing qualified lead, sales qualified lead, opportunity, customer and evangelist, plus other. Its documentation defines a marketing qualified lead as one marketing has qualified as ready for sales, and a sales qualified lead as one sales has qualified as a potential customer.

Microsoft's Dynamics 365 Sales documentation describes the same moment from the sales side. Qualifying a lead validates it as a real opportunity, associates an account and contact, and creates the opportunity record; a lead that does not meet the criteria can be disqualified with an audit trail kept.

The lesson for a GTM team is that the software will record whatever rule you give it. If marketing and sales have not agreed what qualified means, the stage changes still happen, but they mean different things to each side. Lead routing covers how a qualified record reaches the right person.

How to align a GTM team

Alignment is not a feeling. It is a short list of things the team has agreed in writing and checks on a schedule. The older word for sales and marketing alignment is smarketing; a GTM team extends the same idea to customer success, product and operations.

• One customer definition. A single ideal customer profile that marketing targets, sales qualifies against and customer success can confirm from real accounts.
• One message. Product marketing owns the positioning, and every function uses the same words for the problem, the alternatives and the proof.
• One set of definitions. Lead, qualified lead, opportunity, stage, churn and expansion each mean one thing, written down where everyone can read it.
• Shared data. One customer record that every function writes to, so the notes from a sales call reach onboarding without a separate document.
• Incentives that point the same way. If marketing is paid on lead volume and sales on closed revenue, expect a fight about lead quality. Tie part of each plan to the shared number.
• A fixed review. The GTM sync checks these agreements and changes them deliberately, instead of letting each team drift on its own.

Incentives deserve a warning. In this page's view, compensation plans are slow to change and quick to shape behavior, so a written agreement that conflicts with the pay plan will lose. Check the plans before you announce the alignment.

GTM team rituals and operating cadence

A GTM team is held together by a small number of recurring meetings, each with a decision attached. In this page's view, a meeting with no decision drifts into a status update, and people start skipping it.

The cadence in the table is a suggestion written for this page, not a standard. Two rules matter more than the timing: every ritual has one owner who writes the decision down, and every play named in a ritual has a person attached to it rather than a department.

Go to market team structures: functional, pod and segment

The same roles can be arranged in different ways, and the arrangement changes how fast the team learns. A go to market team structure is really a choice about where information travels quickly and where it stalls.

Whichever structure you pick, the plays and definitions stay shared. A pod that invents its own message rebuilds the silo the structure was meant to remove, which is why the play library and the definitions belong to the whole team.

How the GTM motion shapes the team

A motion is how a buyer is moved forward. The strategy entry covers how to choose one. This section covers only what each motion does to the team you need, because the choice changes headcount more than any other decision.

What changes in hiring and incentives

• Sales led needs deal sizes that can carry the cost of sellers. The team grows by adding quota carriers, so enablement and management ratios matter early.
• Product led moves budget from sellers to engineers and analysts. The scarce skill is reading usage data well enough to know when a human should step in.
• Partner led trades control for reach. Compensation has to reward a partner sourced deal as much as a direct one, or nobody will route it.
• Community led is slow to start and hard to attribute. It needs someone whose job is the community, not a marketer running it as a side project.

Many companies run more than one motion. Each extra motion means another set of plays, another definition of a good lead, and one more rule about who owns an account that moves from one motion to the other.

First GTM hires, by stage

Hiring order should follow what the company is trying to prove, not a template. The table below is this page's suggestion, and every company will bend it.

Two rules survive every stage. Do not hire a specialist to prove something the founders have not proven yet. And do not hire sales development before an account executive can close the meetings they book, or the team will scale activity that converts into nothing.

The account executive role entry covers what that first closing hire does day to day and how the role is usually measured.

Revenue operations and the GTM engineer

Revenue operations, often shortened to RevOps, owns the plumbing: the customer record, routing rules, stage definitions, reporting and tooling. It is the role that makes a cross-functional team workable, because it removes the argument about whose number is right.

GTM engineering is a title some teams now use. It sits next to revenue operations and builds the mechanics of plays: enrichment, signal capture, list building, and the automation that fires a play when a trigger appears.

The distinction used on this page is that revenue operations keeps the system of record correct, while GTM engineering builds the pipes that feed it. On smaller teams one person does both, and that is fine as long as the definitions still have an owner.

Why data quality is a GTM team problem

Every role on the team reads from the same records, so bad data spreads. A wrong job title sends the play to the wrong person, a duplicate account splits the history, and a missing close reason empties the loss review. Treat data quality as a shared metric, owned by revenue operations and fed by everyone.

What the team needs from its tools

• Signals. Job changes, hiring, funding, technology in use and engagement, which supply the triggers most plays are built on.
• Data and enrichment. Company and contact records matched to your ICP, so a list is built from the market rather than from guesswork.
• Engagement and sequencing. The tool that runs the email, LinkedIn and call steps in order, a category known as sales engagement.
• CRM. The system of record where stages, handoffs and plays are stamped on the account, so results can be read later.
• Reporting. One place where pipeline, plays and retention are counted the same way for every function.

What a GTM play is

A GTM play is one repeatable motion written down. It names a situation, the people it applies to, what you offer them, where you reach them, who runs each step, and the number that says whether it worked. Plays are how a GTM team turns the strategy and its shared definitions into specific, shared work.

The analyst firm IDC describes plays as repeatable, proven motions that turn insight into action. That phrasing is useful because it puts the insight first: a play starts from something you noticed about buyers, not from a channel you want to use.

The six parts of a GTM play

If any of the six parts below is missing, the play gets run inconsistently and its result cannot be read. The third column is the answer that signals the part has not really been decided.

The trigger is the part that decides quality. A play built on a real event, such as a new leader arriving in the buying role, gives the message a reason to exist. Trigger marketing covers how those events are detected and acted on.

A GTM play written for this page

The situation: a company sells a reporting tool to revenue operations teams. Its team believes accounts respond better when the buyer is new in the role. That belief becomes a play, labeled as a hypothesis until the team's own results confirm or reject it.

Notice that three roles own parts of one play. That is the GTM team in miniature: sales development runs the touches, product marketing owns the material, revenue operations owns the data, and the play review decides its fate.

Notice also what the play does not contain. No claim about how well it performs, no promised conversion rate, and no company name. Those belong to your own results once you have run it, which is the only place the numbers can honestly come from.

How to write a GTM play

The hard part of writing a play is agreeing on the trigger and the kill rule, because both make the team commit to something that can be proved wrong. The steps below were written for this page.

1. Start from an observation, not a channel

   Write one sentence about buyer behavior you have actually seen. If you cannot point to where you saw it, the play is a guess and should be labeled as one.

2. Turn the observation into a trigger

   Define the event precisely enough that software or a person can spot it, including how recent it has to be to count.

3. Name the accounts and the roles

   Filter your customer profile down to accounts where the trigger applies, then list the roles inside them who feel the problem.

4. Write the offer before the message

   Decide what the buyer actually receives. If the only offer is a meeting, what you have is a cadence, not a play.

5. Lay out the channels and the timing

   Sequence the touches across email, LinkedIn, phone and ads, with days between them, so every owner knows when their step is due.

6. Assign one owner per step

   Every step gets a person, not a function. In this page's view, a step owned by two people tends to be run by neither.

7. Set the measure and the kill rule

   Pick one number and the point at which you stop. Write both down before launch, while nobody is attached to the play.

8. Review it on a fixed date

   Put the review in the monthly play review, and record keep, fix or kill in the playbook next to the play itself.

A starting library of GTM plays

Keep the live library small enough that everyone on the team can name what is running. The categories below are starting points, and each one needs its own trigger, owner and measure. For plays aimed at a named account list, see ABM plays.

• Job change plays. A buyer moves into a relevant role, or a past customer joins a new company where your product is not in use.
• Usage plays. A free or trial account crosses a threshold your own data links to team purchases, and an assist conversation opens.
• Intent plays. Accounts show research behavior on topics you solve, and are routed to outreach with that intent context attached.
• Website visit plays. People from a target account visit specific pages, such as pricing, and the SDR or a chat prompt follows up with that page as context rather than a generic opener.
• Closed-lost revival plays. A deal lost for a reason that no longer applies, such as a missing capability that has since shipped.
• Champion plays. A known advocate is identified inside an account and asked for an introduction rather than for a meeting.
• Partner plays. A partner opens an account, and both sides agree in advance who runs discovery, who demos and who signs.
• Expansion plays. An existing customer adds headcount or a second team, and customer success brings the account executive in.
• Launch plays. A new capability ships, and product marketing, enablement and sales agree which existing accounts hear about it first and from whom.

Common mistakes GTM teams make

• Renaming the sales and marketing meeting a GTM sync without changing what gets decided in it.
• Leaving the revenue number and the definitions with the same owner, so the definitions bend whenever the quarter looks short.
• Letting each function keep its own definition of a qualified lead, then arguing about lead quality forever.
• Paying marketing on volume and sales on revenue, then asking both to agree on quality.
• Writing a playbook full of personas and positioning, with no play anyone could run this week.
• Launching plays and never killing them, so the library grows until nobody knows what is live.
• Running several motions badly instead of one well, usually because a new channel feels easier than fixing the current one.
• Copying a competitor's team shape without their deal size, buying committee or motion.
• Writing job descriptions for new roles from vendor blogs instead of from the decisions and metrics the role will own.

In a sequence

The email below is the first touch in the play above. It names the trigger, connects it to one problem the new leader may inherit, and offers a document instead of a meeting.

Subject: new in the {{roleTitle}} seat at {{companyName}}

Hi {{firstName}},

Congratulations on the {{roleTitle}} role. When someone takes over {{functionName}} at a company the size of {{companyName}}, {{problem}} is often waiting on the desk in the first month.

We help {{teamType}} teams with {{outcome}}. I can send the one-page version instead of asking for a call.

Want it, or is this someone else's project now?

{{senderName}}

Frequently asked questions