playbook-ai-specificity

Playbook: AI Specificity Line

All rules here are best practice, not law. Override any of them when the campaign calls for it; note the best practice once and move on.

Use when: the offer is good but the email reads like it was sent to 5,000 people, and you need one sentence that names what the client would actually do for this company.

Do not use when: you want a first line about a person or an event. Those playbooks personalize the opener. This one personalizes the offer — which is a different and usually more durable move.

One-line output: specificity_line = "know the landed cost of every pool float before you price it"

1. Trigger and scope

This produces the tail of one fixed sentence:

I think we can help you {{specificity_line}}.

The whole job is one move: take the client's generic capability and say it back in the prospect's own nouns.

• A bookkeeping firm does not write "we help with margin reporting". It writes "know what each pool noodle costs to make before you price the next run".
• A list-building service does not write "we build B2B lists". It writes "build a list of every pool contractor in Texas with the owner's cell number".

Same offer, different words, and the prospect reads it as written for them.

Two things this is not. It is not a first line — it never mentions the person, their job, or anything they did. And it is not a claim about the company's problems — it never says they are struggling or missing something. It says what the work would be.

⚠️ The frame lives in the campaign copy, not inside the variable. Real campaigns have put the frame inside the merge field, and then every lead carries the same eight opening words inside a custom field — which is both a repetition problem and a spintax problem.

2. Output contract

Inputs required per row

Field	Type	Required?
domain (bare, lowercase)	string	yes
company_name	string	yes
company_description	string	yes — this is the whole input
primary_offerings, revenue_streams	string	no, they sharpen the anchor
client_offer_block	text block, per client, not per row	yes, locked once per client