Draft product positioning from internal conversations
Turn a presentation draft and team discussions into a positioning proposal that the product team can challenge.
How this works
Positioning from internal discussions is a proposal about who the product serves, what problem it addresses and why its approach matters. Internal enthusiasm is useful context but not customer validation. Build a claim ledger that distinguishes demonstrated capabilities, customer evidence, future intentions and team assumptions.
Use the draft presentation and transcripts to expose inconsistent descriptions before writing polished copy. The objective is a reviewable strategic statement with unresolved decisions attached, not a consensus narrative manufactured by blending incompatible claims.
Before you start
Current product boundary
Identify the product version and capabilities actually available today; separate roadmap material.
Review roles
Identify who confirms product facts and who decides audience and commercial positioning.
Evidence access
Use approved presentation versions and transcripts with sensitive material excluded from the shareable draft.
Prepare the inputs
- presentation
- Required
Versioned deck or extracted slide text
Retain slide IDs and distinguish speaker notes from approved claims.
- discussions
- Required
Transcripts with meeting dates and speaker role aliases
Uncertain transcription and unsupported statements need explicit flags.
- product_facts
- Required
Approved capability and limitation records
Roadmap intentions must not become present-tense claims.
- audience_evidence
- Optional / conditional
Customer observations or research excerpts
Keep interview sample and context visible; optional evidence absence means hypotheses remain unvalidated.
Implementation, step by step
Extract positioning elements
- Find stated audience, job, pain, alternative, benefit and differentiator. Attach a slide or transcript passage to each candidate.
- Classify the evidence as product fact, customer observation, opinion or future intention. Avoid filling an absent audience with a stereotype.
Checkpoint: A traceable matrix contains the ingredients and evidence types.
Identify substantive disagreements
- Compare statements across dates and roles. Separate terminology differences from incompatible target segments or capabilities.
- Group conflicts into decisions the team must make, and retain each position with its basis instead of voting by mention count.
Checkpoint: The review agenda names the unresolved decisions.
Construct candidate positions
- Draft a small set of distinct statements using audience, problem, product category, benefit and support. Use only confirmed facts as assertions.
- Label positioning choices as proposals. Include the plausible alternative each position competes against and the tradeoff it makes.
Checkpoint: Each candidate can be traced to a specific audience and evidence set.
Stress-test the claims
- Check every benefit against supplied capability evidence and customer observations. Remove invented guarantees and unsupported superlatives.
- Ask whether the audience can recognize its own problem and whether the claimed distinction is meaningfully different from alternatives.
Checkpoint: A reviewer can see which claims are supported and which need research.
Deliver a decision-ready draft
- Prepare the concise positioning statement, supporting points and slide edits for the selected candidate or the still-open alternatives.
- List questions, evidence gaps and deciding owner roles. Preserve draft status until the owner confirms the chosen direction.
Checkpoint: The handoff makes the decision and the next evidence request explicit.
Decisions along the way
A transcript says a feature is planned
Keep it in roadmap context and exclude it from claims of current capability.
Two audiences need incompatible messages
Show two positioning options and their tradeoffs; do not combine them into a vague universal audience.
No customer evidence exists
Label the position an internal hypothesis and suggest focused validation before external claims.
What you will produce
positioning-proposal.md
MarkdownA concise proposal with evidence-linked supporting points.
Include: audience · problem · category · benefit · differentiation · support · status
claim-and-decision-ledger.csv
CSVReview record behind the polished language.
Include: claim_id · statement · evidence_type · source_ref · conflict · owner_question
Check the result
- Trace factual claims to the current product or dated source passages.
- Verify that roadmap statements retain future or proposed status.
- Ensure contradictory audience choices remain visible rather than silently merged.
- Read the short statement without the deck to check that audience and benefit remain understandable.
When something goes wrong
The latest deck version is unclear
Compare versions and ask the owner which is authoritative; preserve a provisional evidence map.
Transcript wording is ambiguous
Quote a minimal local passage in the private review ledger and mark the interpretation uncertain.
Stakeholders request an unsupported promise
Offer accurate alternatives and retain the missing evidence requirement instead of polishing the promise.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Draft positioning from our presentation and product discussion.
Inputs
Synthetic slide S2 says the tool summarizes approved documents. A call proposes adding automatic approval next quarter. The buyer role is operations manager; no customer interviews are supplied.
Expected result
Draft a document-summary positioning hypothesis for operations managers. Do not claim automatic approval exists. Put audience validation and roadmap wording in the decision ledger.
Run a small pilot
Start small
Apply the method to one product and one review meeting.
Record the baseline
Record current conflicting claims and repeated clarification questions.
Agree success criteria
Evaluate whether owners can choose a direction and identify required evidence with fewer corrections.
Stop or revise
Revise if the draft hides disagreement or turns internal speculation into a product fact.
Keep the scope clear
- Do not publish positioning or change public sales material without authorization.
- Keep sensitive internal quotations out of externally shareable copy; use generalized evidence summaries.
Check before using
Verify every product claim and separate customer evidence from the team’s assumptions.
Business activities
- Create and publish content
- Plan products and business changes
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Draft presentation · Internal call transcripts
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow