Awareness-Based Headline Creative
Use for text-led static concepts, especially B2B feed ads. These are compact treatments within the existing angle and template workflow; they do not replace audience research, the hook system, or platform specs.
Concept lineage: the maintainer's #404 follow-up to the ivangfalco/ads-skills remix. Re-expressed independently and reconciled with this repo's grounding and AI-tells rules; no source copy or creative assets imported.
Choose the Reader's Next Step
| Awareness | What the reader needs | Useful treatments | CTA direction |
|---|---|---|---|
| Unaware / unfamiliar with the category | Recognize a specific lived situation | Feeling, conversation | Learn about the situation or mechanism |
| Problem-aware | See a credible path out of a named friction | Pain + outcome, time-anchored friction | See the workflow or explanation |
| Solution-aware | Understand a concrete way this approach differs | State change, documented statistic | Compare the mechanism or watch a demo |
| Product-aware | Resolve an objection with specific proof | Statistic, pain + outcome | Inspect proof, try, or book the relevant next step |
Stage is a working hypothesis about this audience, not a diagnosis based on the platform alone. If unknown, state the assumption and propose two distinct stage hypotheses. A formula alone cannot prove an ad will convert.
Six Treatments
The examples below are invented illustrations of structure, not approved product claims, real customer quotes, or ready-to-run ads. Replace their facts with the user's verified corpus. Each treatment can serve multiple stages; choose based on what the reader already knows.
| Treatment | Construction and guardrail | Illustrative SaaS example | Illustrative DTC example |
|---|---|---|---|
| Feeling | Name a recognizable feeling tied to a specific work/life moment. Avoid vague empowerment or a forced positive/negative reveal. | “Leave Friday with the forecast finished.” | “Dinner sorted before the commute home.” |
| Conversation | Two short lines from a recognizable situation. Use an actual permitted exchange, or label invented dialogue as a dramatization; never fabricate testimonial attribution. | “Is this the final sheet?” / “There are three final sheets.” | “What's for dinner?” / “I'm still on the train.” |
| State change | Show the current and proposed workflow with concrete artifacts. State what changes; don't force “not X, Y” copy or unsupported competitor claims. | “Bring the three approval threads into one queue.” | “Pack tomorrow's lunch while tonight's dinner cooks.” |
| Time-anchored friction | Name an obsolete or repetitive process and its actual moment. Critique the process without shaming the buyer or inventing a trend. | “Month-end still starts with copying CSVs.” | “The Sunday grocery list starts over again.” |
| Documented statistic | One supported number plus the population, period, or meaningful qualifier. Keep its real precision; rounded numbers are not evidence of fakery. | “Pilot teams cut weekly reconciliation from 6 hours to 2.” | “Three dinners packed in one delivery.” |
| Pain + outcome | One named friction and a concrete next action/outcome, usually under ten words. Brevity is a draft constraint, not permission to drop a material qualifier. | “Find the missing invoice before close.” | “Get dinner ready between calls.” |
Read each draft against the existing AI-tells guidance. Do not produce six near-identical sentences just to fill a formula menu. Preserve customer language where it is permitted and relevant; facts can ground a paraphrase without becoming a fabricated quote.
Gather Proof Before Copy
Build a small evidence sheet: source ID, verbatim phrase or product fact, audience, date, allowed usage, and limitations. Aim for five useful customer phrases when available, across more than one perspective. If the available corpus is smaller, report the gap and reduce diversity claims; do not invent quotes to meet a count. Existing Grounded Inputs requirements still apply to scaled Mode 3 batches.
Separate language evidence (“the export takes forever”) from claim evidence (a measured reduction across a defined pilot). A complaint supports the pain angle; it does not substantiate a numerical performance promise. Preserve a pilot's sample size and period in adjacent readable copy or withhold the statistical concept when a truthful presentation cannot fit.
Make the Headline the Visual
Apply this treatment to Headline Statement or Stat Callout from the static library when the words carry the concept. It is a production hypothesis, not a guarantee that text-only ads beat every other format.
- Start with one dominant sentence and a bold, legible sans-serif face. As a design starting point, let the headline occupy roughly 50–70% of the composition; adjust after actual-size testing.
- Use intentional line breaks that keep phrases together. Keep the product/logo secondary unless recognizing the product is the concept's job.
- Test a dark background with light text, or a strong brand-colored background with contrasting text. Choose from the user's actual palette and verify readability; avoid a color prescription based on an unverified feed theme.
- Include the audience's specific moment, one defensible idea, and enough qualification to read truthfully. Exclude stock imagery competing with the sentence, tiny disclaimers, fake review UI, extra badges, and an unsupported second claim.
- Make a preview at the actual mobile feed display size, not only on a desktop canvas. Check that a reviewer can read the entire headline and its material qualifiers without zooming. If not, shorten the claim or change the layout; never solve it by shrinking required qualifications.
- Get current export dimensions, cropping, safe areas, and text-field limits from the platform-spec reference and the selected placement. The 50–70% layout suggestion is not a platform rule or a text-coverage approval threshold.
Deliver and Learn
For each concept, provide: audience/stage assumption, distinct angle, treatment + static template, headline, supporting qualification, CTA, source IDs, and visual specification with mobile-readability check. Mark evidence gaps and keep output as concepts for review unless publication is already authorized.
Test stage/angle hypotheses before fine font changes. Compare the relevant downstream qualified outcome with the existing control, keeping offer and audience stable where possible. Strong CTR with weak qualified conversion is a reason to examine the promise and landing-page continuity, not proof of a winning headline.