01
Decide what you are, who buys it, and why they should care, before anyone writes a word.
You get the decisions everything downstream depends on. What the product is, who it's for, what it replaces, and the words your whole company will use to say so. Positioning, ICP, message architecture, brand voice, and the research that shows any of it is true.
Most teams need this before a launch, after a pivot, or when the same demo convinces one buyer and confuses the next. If three people at your company answer "why you" three different ways, start here.
Positioning, ICP, message architecture, brand voice, and the GTM plan that follows from them.
The decisions, and the documents that carry them.
Who else your buyers are considering, what those companies claim, and where the market is moving.
Primary and secondary research, aimed at a decision you already have on the table.
Structured interviews with the people who bought, the people who didn't, and the ones who left.
Run as an ongoing program with a fixed cadence, not a one-off study that gets read once.
A written positioning statement, an ICP tight enough that sales can disqualify with it, a message architecture with the proof sitting under each claim, and the research behind the decisions. It's all documented, so a new hire or an agency can pick it up without a briefing call.
Research is periodic and outside-in. You commission it, read it, and decide. Market feedback runs continuously out of your own pipeline and your own customers, so the decisions keep getting corrected instead of aging.
Six to eight weeks gives you room to write the story, build the assets, and get sales ready before anything ships. Two weeks means you're choosing what to cut. If the date is already close, start with the narrative and the sales material, because those two carry the most weight.
It helps, and it's usually faster. If you don't have one, the first step is a short framework pass so the writing has something underneath it. Writing without a framework produces pages you rewrite in six months.
They overlap, and a lot of the technical work underneath is shared. The difference is what you optimize for: a search engine ranks pages, while an answer engine extracts and repeats claims, so clear definitions and consistent naming across the web carry more weight.
Sales enablement equips the people who sell, with decks, talk tracks, and objection handling. Internal systems serve everyone else, so support, product, and the hire in week two are all working from the same source.
Tell me what you are launching and who has to believe it. I will tell you which of these you actually need, and which you can skip.
Great tech doesn't sell itself.
Let's meet. It's free.
