Write a positioning statement and messaging framework for a B2B product

You are a product marketing lead who has positioned many B2B software products.
I work in IT & Software: a software company that ships a SaaS product. This work matters to engineering leads, developers and IT buyers.

## Goal
Define how our product is positioned against alternatives and turn it into a messaging framework the whole company can use.

## What matters in IT & Software
- How customers decide: technical evaluators and budget owners decide together; they judge security, integrations, total cost and support quality; free trials and proofs of concept are common; contracts are usually annual and renew.
- Rules and standards that usually apply: data-protection law (GDPR in the EU, the DPDP Act 2023 in India, CCPA in California); SOC 2 or ISO 27001 security audits; OWASP secure-coding practice; open-source licence terms; the uptime and support promises in customer SLAs.
- Timing and seasons: quarterly planning; release trains; annual renewal dates; end-of-quarter and fiscal-year-end deals.
- Words people in this field use: SaaS; multi-tenant; SLA; incident; sprint; release; tech debt; API; ARR.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Product and what it does: [PRODUCT]
- Target customers and buyers: [SEGMENTS, ROLES]
- Main competitors and alternatives (including doing nothing): [COMPETITORS]
- Proof we have: [CUSTOMERS, RESULTS, AWARDS]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Summarise the audience, the offer and the single action we want people to take. Note what you would need to know about past results to do this better.
2. Identify the competitive alternatives customers actually consider.
3. List our unique attributes and the value each one creates.
4. Choose the best-fit customer segment and why.
5. Choose the market category frame.
6. Write the positioning statement.
7. Build the messaging hierarchy: headline, value pillars, proof points per pillar.
8. Write messaging variants for each buyer role.
9. Explain how to measure success: the metrics, targets and how to track them.
10. Suggest two variations worth A/B testing and what each test would teach us.

## What to deliver
- Positioning canvas
- Positioning statement
- Messaging framework table
- Messages per buyer role
- Words to use and avoid

## Expert rules
- Write for one specific reader and their problem, not for everyone.
- Lead with benefits and proof; avoid hype words such as "revolutionary", "game-changing" or "unlock".
- Keep every claim honest and checkable; flag any claim that needs proof or legal review.
- Respect uptime, security and data-protection requirements. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Use headings for each deliverable so I can copy them straight into my tools.
- Mark character or word limits where a channel has them.
- Put final copy in quote blocks, separate from your notes.

## Before you answer
Check your draft against this list and fix anything that fails:
- Every claim can be backed up, and the copy speaks to engineering leads, developers and IT buyers in words they use.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on deployment frequency and uptime.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.