The GTM Strategy Workshop: What to Bring, What to Expect, What You Walk Away With

‍TL;DR: A genuinely useful GTM strategy workshop requires the client to bring three specific things beforehand: recent closed-won and closed-lost deal data, current CRM access or an export, and a list of the two or three biggest internal disagreements about direction. During the session, expect structured, sometimes uncomfortable questioning that tests existing assumptions against real data rather than a passive presentation of frameworks. A workshop done well leaves the room with a documented, validated point of view on ICP and channel priority, not just a list of general ideas everyone found interesting.

‍

A GTM strategy workshop gets scheduled, attended, and often forgotten within a week, because most companies walk in unprepared and most facilitators default to a passive, framework-heavy presentation rather than a genuinely structured, evidence-based working session. Knowing what to bring and what a good session should actually produce changes both of those outcomes.

Why an unprepared workshop produces generic output regardless of the facilitator's skill

A skilled facilitator working with a room that hasn't brought any real data can still run an engaging, thoughtful session, and the output will necessarily be built on assumption and general market knowledge rather than the client's own specific evidence. The workshop's value ceiling is set largely by what the room brings into it, which is exactly why preparation matters as much as, or more than, who's running the session.

What to bring, and why each item matters

Why closed-won and closed-lost data matters more than closed-won alone

A workshop that only reviews closed-won deals sees half the picture; closed-lost deals, particularly ones lost after reaching a late stage, often reveal exactly where a company's positioning or ICP assumptions break down under real scrutiny. purple path's method for validating an ICP against real sales calls depends on exactly this kind of complete data set; bringing only the flattering half of the picture into a workshop produces a strategy that looks confident and hasn't actually been tested against the deals that didn't work.

Why live CRM access changes what happens during the session itself

A workshop working from static slides or pre-prepared summaries can discuss the data only in the form it was originally packaged. A workshop with live CRM access can test a claim in real time, someone asserting "our best customers are mid-market fintech companies" can be checked immediately against an actual filtered query, rather than accepted on faith or investigated only after the session ends. This live-checking capability is what separates a workshop that genuinely interrogates assumptions from one that simply discusses them.

Why the list of internal disagreements is the single most valuable thing to bring

Every company has at least one or two genuine, unresolved internal disagreements about direction, usually left unspoken in normal day-to-day operations because raising them feels disruptive. A workshop is specifically the right forum to surface these directly, since it's structured, time-boxed, and facilitated by someone with no personal stake in which side of the disagreement wins. purple path's analysis of the gap between board expectations and marketing org reality covers a related dynamic; a workshop that never surfaces the real underlying disagreement produces a strategy document that looks resolved on paper while the actual tension continues unaddressed underneath it.

What to expect during a well-run session, structurally

A genuinely useful workshop follows a specific rhythm: an opening review of the brought-in data, a structured questioning phase where the facilitator directly challenges existing assumptions against that data, a working session building consensus on the two or three biggest open questions, and a closing summary confirming what was actually agreed. This is meaningfully different from a passive session where a facilitator presents general frameworks and the room nods along without the friction that genuine, evidence-based challenge requires.

Why some discomfort during the session is actually a good sign

A workshop that surfaces genuine disagreement and requires the room to work through it directly will feel less comfortable than one where everyone simply agrees with whatever's presented. This discomfort isn't a sign the session is going poorly; it's often the clearest evidence that the workshop is doing its actual job, forcing a resolution to tension that's been left unaddressed rather than avoiding it for the sake of a smoother, more pleasant meeting.

What a good workshop should leave you with, specifically

The session should conclude with a documented, validated point of view on two things specifically: which ICP the data actually supports, and which one or two channels deserve priority given that ICP. This is meaningfully different from a list of general ideas or possibilities that felt interesting during discussion; a genuinely useful output is a narrowed, evidence-backed position the team can actually act on, not an expanded menu of options requiring further deliberation after the session ends.

Why this workshop typically sits within a broader strategy engagement, not as a standalone event

purple path's breakdown of a real GTM strategy engagement week by week covers where this workshop typically fits: usually during the ICP and positioning validation phase, building directly on the discovery work completed in the preceding weeks. A workshop run in isolation, without that prior discovery groundwork, tends to produce a weaker result, since the room is working from whatever data participants happen to bring rather than a properly prepared, comprehensive review already completed beforehand.

How to tell if a scheduled workshop is likely to be genuinely useful before it happens

Ask the facilitator directly, before the session, what specific data they expect the client to prepare and what specific output the session is designed to produce. A facilitator who can answer both questions with genuine specificity is signaling a structured, evidence-based session; one who describes the workshop only in general terms, "we'll explore your positioning together," is more likely running a passive, framework-presentation format that produces interesting discussion without the concrete, actionable output a real workshop should deliver.

Why the room's seniority mix affects how honestly the disagreement discussion actually goes

Beyond simply having the right people present, the relative seniority balance in the room shapes how openly junior participants are willing to voice disagreement with a founder's stated view during the session. A skilled facilitator will actively create space for this, directly inviting quieter participants to weigh in rather than letting the most senior voice in the room dominate the discussion by default, since some of the most useful tension a workshop surfaces comes precisely from a less senior team member's on-the-ground perspective diverging from leadership's stated assumption.

Why following up within a week of the workshop matters as much as the session itself

A workshop's documented output loses momentum quickly if it isn't acted on soon after the session ends. Scheduling a specific follow-up meeting within a week, focused on translating the workshop's validated ICP and channel priorities into concrete next actions, prevents the common pattern where a genuinely productive session produces a strong document that then sits unused while everyone returns to pre-workshop routines and priorities.

Frequently Asked Questions

How many people from the client side should attend the workshop?

Enough to represent the key internal perspectives and disagreements, typically the founder or CEO along with whoever leads sales and whoever leads marketing, but not so many that the room becomes too large to have a genuinely direct, working conversation rather than a passive presentation to a large audience.

How long does a well-run GTM strategy workshop typically take?

A focused session usually runs three to four hours, long enough to work through the data review, questioning, and consensus-building phases properly, without stretching into a full day that risks losing the room's energy and focus partway through.

What happens if the workshop surfaces a disagreement that can't be resolved in the session itself?

A good facilitator documents the specific disagreement clearly, along with what additional information or decision would be needed to resolve it, rather than forcing an artificial resolution the room doesn't genuinely agree with just to complete the session on schedule.

Should the workshop happen before or after the CRM and closed-deal data has been reviewed by the facilitator independently?

Ideally after; a facilitator who has already reviewed the data independently beforehand can run a considerably more efficient and pointed session than one seeing the data for the first time live in the room, which wastes valuable session time on basic data familiarization rather than genuine strategic discussion.

Is a single workshop sufficient, or do most strategy engagements require more than one?

Most engagements benefit from at least two: one focused specifically on ICP and positioning validation, and a separate one later focused on channel and pillar-specific strategy, once the ICP work from the first session has had time to be documented and built upon.

‍

Preparing these three specific items before your next GTM strategy workshop is what actually determines whether the session produces something real or just a pleasant afternoon of discussion. Talk to purple path about what to prepare for your own strategy workshop.