Nobody in the room can end a positioning argument. A buyer can, and in a few weeks.
Somewhere in your company a positioning argument has been running for a month. One side wants to lead with the workflow the product replaces. The other wants to lead with the outcome the CFO signs off on. The deck exists in two versions. The homepage has had three. Every Monday the argument gets twenty minutes, nobody changes their mind, and the pitch that goes out that week depends on who's giving it.
That argument is common. Positioning is the third most-named GTM challenge, after pipeline and scaling repeatably, in the 2026 State of B2B GTM Report (Kyle Poyar of Growth Unhinged and Maja Voje of GTM Strategist, October 2026), and the authors sign off with this: "One more prediction: the next battleground will be positioning and messaging. These softer elements of GTM have been ignored or underappreciated. The result is that every company sounds the same, and customers are tuning out." One caveat: that's a practitioner survey of about 300 software and AI companies who answered a newsletter's poll, a read on what practitioners say is hard rather than a market census, and the battleground line is their prediction, not a finding.
What I'd add is how to end the argument, because a meeting won't.
I'm not going to tell you how to write positioning; that's a different trade. A positioning question is a go-to-market assumption, though, and those get settled one way: put them in front of the buyer group whose reaction decides them and record what happens.
An internal argument never does that. It fails the way hire-and-learn fails as a test of a sales motion, which I wrote about in July: when the result arrives, nothing in it separates the variables. If the pitch landed, was it the positioning or the person who gave it? If it didn't, was it the positioning or the list? No buyer ever weighed in on the positioning by itself, so nothing is learned, and the argument restarts next quarter with fresh anecdotes.
The common shortcut doesn't fix that. Splitting a cold email list between two versions of the pitch and counting replies settles which sentence a stranger answers, and nobody in your meeting was arguing about that. A reply is a sign of curiosity, and curiosity is cheap. The argument is about which buyers take the pitch seriously enough to act on it, and the only evidence for that comes from a buyer acting.
A few weeks, end to end: a handful of conversations with the buyer group whose reaction decides the question, then a focused outreach test by route, recorded as who took a next step with a date or a deliverable. A second meeting on the calendar is one of the measures the market has to co-sign, and nobody in your meeting can award it.
1. Pick the buyer group whose reaction decides the question. Write the argument down as a question a buyer could answer. Not "should we lead with the workflow or the outcome," but "does the head of operations at a 200-person distributor hear 'we replace the spreadsheet' as relief, or as a threat to their team?" Then name the group whose answer would end it. If the two camps turn out to be picturing different buyers, you've found the real disagreement: it's about who you sell to, not what you say to them.
2. Hold a handful of buyer conversations first. Before anyone sends outreach, talk to people in that group. Ask how they describe the problem to their own boss, what they've tried, and what they'd have to see to take a meeting on it. Write down their words, not your translation. Stop when the latest one has stopped surprising you. These don't settle the argument. They tell you what to put in front of the wider group and which way in fits it.
3. Then run a focused outreach test by route. A route is three things: which group you reach, what you say to them, and how you reach them, whether direct, through a partner, or through an existing customer's introduction. The pitch you've been arguing about is the middle one, and it's never the headline. Pick one or two routes. If the argument is really about which buyer, the routes differ by group; if it's about how you'd get in, they differ by the way in. What each route says is whatever the step-2 conversations told you that group responds to.
4. Count only next steps with a date or a deliverable. A second meeting on the calendar, a proposal request, an introduction made. "Let's stay in touch" doesn't count, and replies and opens don't settle this. Keep the record I laid out for an inherited customer base, one row per conversation, with the last column changed to who gave the pitch.
5. Keep the results separate by route. An introduction and a cold email start from different levels of trust, and one pooled number hands the argument straight back to whoever reads it their way. Kept separate, each route makes one claim you can read.
6. Write down what the evidence can't show. Do this before the results arrive, while nobody has a number to defend. A quiet route is unproven, not disproven: before you write off the pitch that rode on it, make sure the asks went out, to the right names, with time to land. A next step isn't revenue; whether those meetings turn into deals, and keep doing so, is the next question, not one this window settles. And a route that produced next steps shows that this group, reached this way, took the meeting. It doesn't show the other camp's pitch would have failed with a different group; if that's the live question, it's the next route to test.
A note for the new US leader. The same six steps run in a market where the founder has no network and no references. The conversations come first because there's no customer to introduce you, the routes are the ways in you can build from zero, and the record of who took a next step is the first evidence you'll have from a US buyer rather than from the home market.
When the window closes, this is the sentence you can put in front of the room: "Operations leaders at mid-sized distributors, reached through our implementation partners, took second meetings and asked for proposals when the pitch led with the workflow we replace. Finance leaders, reached directly, took fewer meetings, and the ones they took went to pricing before they went to the problem." That ends the Monday argument, because it isn't anyone's opinion. It also says what happens next: the homepage carries the pitch buyers took a meeting on, and the finance route gets a second look before anyone writes it off.
Testing the sentence instead of the route. If the only difference between what goes out is the wording, you've built a copy test. It settles which phrasing a stranger answers, and that was never the argument.
Reading the conversations as the verdict. A handful of conversations tell you what to test, not what's true. People describe their problem well and forecast their own purchases badly, which is why the outreach test follows the conversations.
Letting one person carry every pitch. If the founder gives every pitch, or opens every door, the result mixes the positioning with the person. That's what the last column in the record is for: read the next steps that came after someone else ran the meeting.
The positioning argument in your meeting is a go-to-market question dressed as a brand debate, and nobody in the room can answer it. Put it in front of the buyer group whose reaction decides it, a handful of conversations, then one or two routes, and count only the next steps with a date or a deliverable. Write down what the evidence can't show before you read it. A few weeks. Then put the pitch, the people and the budget behind what buyers did, not what the room decided.
That's the shape of what I do at Congruity. A specific commercial question. The work to answer it. When the question is what buyers need before you commit to the offer, the work is buyer conversations or a standalone interview study, scoped separately. For GaggleAMP that meant interviews with sales, marketing and communications professionals at technology and healthcare companies, Salesforce, Highmark Health and Blackbaud among them. When the question is which audience, message and channel earn a next step, that's the six-week GTM Validation Sprint. It puts a specific assumption in front of real buyers, records what happens, and reports the limits of what those results establish. A test doesn't guarantee demand. It ends the argument.
If the argument in your company has been running for a month and nobody in the room can end it, bring both versions of the pitch. We'll work out which buyer group's reaction would settle it, and what to put in front of them first.
Book a 20-minute fit call