The Demotion Audit: what I shared at the PMA Developer Marketing Summit

It was great to speak to so many of you at the PMA Developer Marketing Summit. Thank you to everyone who stayed behind with questions, and to the few who found me in the hallway holding a sentence from their own homepage. This post is the short version of the talk, for anyone who missed it and anyone who wants the steps in writing.

The sentence that cost a buyer's trust

I opened with a sentence that sounds responsible: "Our agent writes the code. A human in the loop reviews every change."

Every word is accurate. Legal can sign off on it. And a developer reading it hears something different within about a second. "In the loop" is a checkpoint, a person placed into a process they don't own, there to approve what has already been decided. The sentence tells them their job got smaller.

I call that narrative demotion: language that quietly lowers the standing of the person reading it. It is almost never deliberate, and it is almost always true, which is why nobody catches it in review.

Right and Rejected

Two questions decide whether a message survives contact with a buyer:

1. Truth. Does the product actually do what the message implies?
2. Standing. Does the message protect the buyer's competence, and the reasonableness of the decisions they have already made?

Put them on a 2x2 and you get four outcomes. A message that is untrue and demotes dies on arrival. One that is untrue but flatters collapses the moment someone evaluates the product. One that is true and protects standing gets signed.

The fourth box is the painful one: true, and demoting. I call it Right and Rejected. If you work in product marketing you have probably been there. The positioning was flawless, the opportunity was lost, and the post-mortem blamed price, timing or a champion who left. AI developer tools land in that box more than most, because the claims really are true. The product does write the code. The human does review it. And the developer declines to champion the tool that makes them the reviewer.

Why a single word matters

The fix borrows from narrative therapy, specifically Michael White and David Epston's idea of re-authoring. The person is separate from the problem. They are living inside a story that casts them in a smaller role than the facts require, and the work is to rewrite it so they are the one acting.

Your messaging already tells a story about your buyer. The question is which character they recognise themselves as. There is a second pressure too: buying anything new asks the buyer to admit that an earlier decision of theirs has gone out of date. Copy that raises that admission cost ("your current workflow is broken") tends to lose on pride, whatever the price is. Copy that lowers it gives them an alibi: the old way was reasonable then, and here is what it grows into.

The Demotion Audit

The audit is one question, run in four passes with a highlighter. The question is: in this sentence, who is the subject, and what is the developer doing?

1. Subject. Who acts? Mark every claim where the machine is the subject and the developer is the object.
2. Verb. Is their verb a checking verb (reviews, approves, validates, oversees, signs off) or a deciding verb (specifies, directs, chooses, ships, owns)?
3. Authority. Can they see what the system is doing, stop it, override it and own the outcome?
4. Proof. Can they demonstrate that authority in a terminal, on their own repo, in ten minutes?

Then a bonus test: read the sentence aloud as their job description. Would they repeat it to their manager without wincing?

Run it first on the three places a developer meets you before anyone from sales does: the launch post, the docs quickstart and the homepage headline.

In becomes on

The smallest rewrite I showed changed one word. An infrastructure AI company was up against a bigger competitor whose pitch handed control to an autonomous agent. Their buyers were operations teams with decades of muscle memory. We changed "human in the loop" to "human on the loop". A person holds final authority either way, so the meaning barely moved. But "in the loop" is a checkpoint inside a process you don't own, and "on the loop" is standing over the whole system with your hand on the switch.

The rewrite for the sentence I opened with looks like this: "You set the direction. The agent drafts, and you decide what ships."

The constraint that keeps it honest

"On the loop" is a claim, so the product has to deliver it. Can the developer see what the agent is doing? Can they interrupt it? Can they overrule it? Is the outcome theirs? If the answer is yes, the rewrite is true and you can say it loudly. If it is no, leave the copy alone and fix the product, or stay honest and quiet. A reframe that isn't accurate is a lie dressed as a repair, and developers find that out fast. So write the promotion they can survive a terminal with.

Get the guide

Everything above is in the nine-page field guide, along with a printable audit sheet and a Monday checklist. It is free, and you can have it two ways: continue with LinkedIn, which also gives you a free pmmAgent account, or leave your name, email and company.

Get the Human On the Loop field guide

Where pmmAgent fits

If you want a second pair of eyes on a rewrite, pmmAgent is the product marketing teammate I built for this kind of work. It drafts positioning, launch messaging and battle cards in your voice and flags any claim you should verify and leaves the proof to you. Two related reads: the ten positioning questions make a good companion to the audit, and what pmmAgent is and how it works covers the rest. The Positioning tool and Battle Cards pages show where to start.

The Free plan needs no card. Start free with LinkedIn, and say hello on LinkedIn if you run the audit and want to compare notes.

Jon is the founder of pmmAgent, with 27 years in product marketing.

Consistent battle cards, positioning and launch messaging, so you can spend your time on enablement and the work that moves the sales needle.