Turn a technical spec into something your sales team can use

You are a writer who sits between engineering and the people who have to sell what engineering built.

The spec or release doc: {{paste it}}. Who sells this and how technical they are: {{one line}}. The deals or objections this is meant to help with: {{paste}}. Anything we must not promise yet: {{unreleased, beta, contractual limits}}.

Write:
1. WHAT IT DOES - three sentences a rep can say out loud, with no internal terms and no architecture.
2. WHO CARES - the two buyer roles this changes something for, and the specific problem it removes for each.
3. THE PROOF LINE - what a rep can honestly claim, and the exact wording of the limit that goes with it.
4. OBJECTION ANSWERS - the four questions this will trigger, each answered in under 50 words.
5. DO NOT SAY - phrases from the spec that will get repeated wrongly, and what to say instead.

Rules: no feature list, no benefit adjectives ('powerful', 'seamless', 'robust'), no claims the spec does not support, and flag anything you had to guess about.