Positioning synthesis
Positioning synthesis that a champion can forward
Positioning, in this guidebook, is a sentence a real role can repeat inside the account without adding a number the research did not earn. It is built from claude notes, from a named friction, and from a pattern that survived an attempt to break it. It is not a tagline workshop, and it is not a promise of return on investment.
Start from a situation, not from a virtue
Virtues are cheap. “Reliable,” “modern,” and “partner-led” can be said by anyone, which is why buyers stop hearing them. A usable positioning line names a situation the account already recognizes: a role, a touchpoint, and the friction in the way. The situation has to be one you can point to in the notes. If the line needs a new metaphor the buyers never used, it is not synthesis. It is copy written in another room.
Read the pattern aloud and underline the condition. That condition must survive into the public sentence, even if it makes the sentence less grand. “For security reviewers who stall when tenant isolation arrives as a product noun” is narrower than “for the enterprise.” Narrow is a sign the pattern synthesis was honest. Wide, with no condition, is a sign it was sanded down for a homepage that wanted everyone.
A writing test with teeth
Hand the draft to someone who was not in the interviews and ask them to find the supporting claude note. If they cannot, the line is floating. Then ask a second question: could a champion forward this to a skeptical peer without feeling they had over-claimed? If the line would embarrass the champion in a Friday staff meeting, it is not ready. Those meetings showed up often enough, in customer interviews, to be treated as a real room rather than a figure of speech.
The third test is negative. Does the line imply a percentage, a payback period, a win rate, or a “majority of leaders”? Cut that implication. Qualitative evidence can support a description of a stall. It cannot support a performance promise. trykux does not make an exception for lines that “everyone in the industry already says.” Common sayings are not measurements.
Before and after, as craft, not as a result
These pairs show the edit. They are writing examples. They are not outcomes from a client engagement and not proof that any company achieved them.
Leaves the evidence
“We help enterprises cut review cycles by 30 percent.”
The number was never in the claude notes. The role is “enterprises,” which is not a role. A champion cannot defend the figure in front of procurement.
Stays with the evidence
“A write-up a security reviewer can circulate when the vendor’s nouns will not survive the examiner.”
The situation matches a proof gap heard from reviewers. It claims no speed, no savings, and no share of the market. It can be checked against the note.
Who the sentence is for
Pick one forwarding path. A line for a champion to send upward is different from a line for an operator to accept during onboarding, and different again from a line procurement can file. Decision-maker research tells you which path you actually studied. If you studied only champions, write a champion line and label it. Do not let it masquerade as the economic buyer’s criterion.
Tie the path to a touchpoint. A sentence that should be forwarded into a security review has to be usable in that review, which you only know if someone did the market observation or heard the review reconstructed in detail. A beautiful line that does not fit the artifact in the room — the questionnaire, the redline, the standup — will be admired in the marketing meeting and ignored in the account.
Field list
Essays on language, not a drip of promises
trykux writes when there is a new reading of interviews, friction, or positioning. Leave an email if you want that note. You can also write [email protected].
Keep the chain intact
Notes, then pattern, then one sentence
If the chain breaks, go back a page rather than forward into a louder claim. The glossary is there when a word starts to swell.