SaaS Positioning Sprint

Most positioning work dies in a Google Doc because it was written by three people in a room who never asked a buyer anything. This sprint is built the other way round. Two weeks, four lessons, five customer calls, and a finished positioning document you can hand to a new AE on their first day.

What the sprint actually produces

By the end of lesson four you have two files. A one page positioning document covering market category, target segment, competitive alternative, unique attributes, the value each attribute produces and the proof behind it. And a sales one pager that says the same thing in the language a rep can use out loud on a first call.

That second artifact matters more than people expect. Positioning that only lives on a homepage never gets tested. Positioning that a rep uses on twelve calls a week gets corrected fast, because buyers push back in real time. If you want the deeper theory behind the structure, the SaaS Positioning Framework guide covers it. This page is the doing version.

Who should take this and who should skip it

Take it if you’re a founder rewriting your homepage for the third time, a first marketing hire who inherited a deck nobody on the team can explain, or a product marketer who just joined a company where sales, support and the website describe the product three different ways.

Skip it if you already have a positioning doc that your AEs quote from memory and your win rate against your named primary competitor is stable. Skip it also if you have no customers yet. Pre-revenue companies should be running problem interviews, not positioning sprints, because there is nothing to position against.

The awkward middle case is an early stage company with fifteen customers who all bought for different reasons. That team should take the sprint but expect lesson three to hurt, because segmentation is where the disagreement surfaces.

Prerequisites you genuinely cannot fudge

Two things must be true before lesson one is worth starting.

• Access to five customers who bought in the last nine months and will give you thirty minutes each
• Two recent lost deals where you can reach either the buyer or the AE who ran the deal
• A list of every competitor and workaround that appeared in those deals, including spreadsheets and doing nothing
• Whoever owns the homepage copy in the room, or at least committed to the output

The lost deals are the part teams cut first and regret most. Wins tell you what your positioning already does well. Losses tell you which alternative you keep failing against, and that alternative is the anchor for the entire document.

The lesson map and what each one costs you

Lesson	Working time	Prep needed	Artifact produced
1. Interviews and competitive alternatives	4 hrs (5 calls) + 1 hr synthesis	Customer list, interview guide	Alternatives map and quote bank
2. Unique attributes	90 min working session	Feature inventory, competitor pages	Attribute list with evidence column
3. Value and segments	2 hrs working session	Lesson 2 output, revenue by segment	Value table and best fit segment
4. Positioning statement and one pager	2 hrs writing session	Everything above	Positioning doc and sales one pager

Lesson one: interviews and competitive alternatives

You run five customer calls with a fixed guide. The single most important question is not what they like about the product. It’s what they would have done if your product had not existed. The answer is usually a competitor, a spreadsheet, a contractor, or nothing, and the split across those four tells you which market you are actually in.

The worksheet is a two column alternatives map with a quote attached to every row. No quote, no row. That rule alone removes about a third of what teams assume about their market.

Lesson two: unique attributes

Here you list what your product has or does that the alternatives from lesson one do not. Not better. Different, and provable. Lesson 2: Unique Attributes includes a scoring rubric where every claimed attribute needs evidence: a competitor page that lacks it, a support ticket, a feature nobody else ships.

Most teams start with eighteen attributes and finish with four. That’s the correct direction of travel.

Lesson three: value and segments

Attributes are only interesting because of what they let a customer do. This lesson converts each surviving attribute into a value statement, then asks which customers care most about that value. That second half is segmentation, and it’s where the sprint gets political, because it usually means naming a segment you’ll stop chasing.

The worksheet forces a revenue column next to each segment. Opinions about who your best customer is tend to soften when the numbers sit beside them.

Lesson four: the positioning statement and the one pager

Two hours of writing with the three previous worksheets open. The output template is deliberately rigid: category, segment, alternative, attributes, value, proof. Then you rewrite it as spoken language for the first call deck. Once you have this, the SaaS Messaging Framework guide is the natural next step, since messaging is downstream of everything you just decided.

The worked example carried through all four lessons

Every lesson uses the same fictional company so you can see the transformation end to end. Call it Cadence, a $28K ACV product that started life as “project management for agencies” and could not explain why anyone should pick it over Asana, Monday or a well loved Airtable base.

The category shift is the point. Cadence didn’t build anything new during the sprint. It changed which shelf it asked buyers to compare it on, and the comparison set went from crowded to nearly empty.

Where teams get stuck, honestly

Two failure modes show up repeatedly, and neither is solved by a better worksheet.

The first is the founder who won’t let go of the big category. Selling into a $40B market feels better than selling into a $900M one, so teams cling to the broad label even when every lost deal says buyers can’t place them. The fix is usually a board member repeating the win rate numbers back.

The second is a team that finishes the doc and never changes anything. The positioning document is worthless until the homepage hero, the first call deck and the SaaS Sales Enablement material all change to match. Budget a fortnight after the sprint for that rollout work. If nobody owns it, the doc becomes a nice PDF.

What to do after the sprint finishes

Positioning is one input to a much wider product marketing function. Pricing, launch process, competitive enablement and analyst relations all take their cues from it, and the SaaS Product Marketing Strategy hub maps how they connect. If your team is trying to work out whether positioning belongs to you at all, Product Marketing vs Product Management settles the boundary argument reasonably well.

Teams selling AI products have an extra problem: the category itself is unstable and buyers are comparing you to a prompt. Marketing an AI Native SaaS Product covers what changes in lesson one when the competitive alternative is ChatGPT.

Once positioning holds for a quarter, the natural follow on is turning it into demand. The SaaS SEO Sprint applies the same two week format to search, and the SaaS marketing foundations course is the wider curriculum if you’re building a function from zero.

Start with lesson one this week. Book the five calls before you open any worksheet, because everything downstream depends on them, and a calendar invite is harder to skip than a document.