Asb Carol Dealbreakers

Deal-Breakers: Who Will Never Buy, No Matter What

A buyer can have three keystones and still be disqualified: if they require SOC 2 and you don't have it, there is no deal — deal-breakers trump keystones, and purchasing committees lament it as often as vendors do. This skill maps those disqualifiers from the weaknesses chart, names the anti-market segments who live behind them, and then does the move that sharpens everything upstream: honing each keystone segment with the qualifiers the deal-breakers force.

The mental model

Weaknesses → deal-breakers → anti-market

The procedure mirrors the keystones step exactly, on the other column: for each weakness, ask what circumstances make this weakness disqualifying — not annoying, not a negotiating point, but a hard no? Then name the real market segments that live in those circumstances. Those segments are the anti-market — beyond the edge of your possible market. From the canonical chart: "expensive" disqualifies anyone with a $5/mo website budget (personal projects; small businesses in markets where US pricing is unaffordable); "supports only WordPress" disqualifies everyone already built on something else; "requires design and build-out" disqualifies the person who needs a one-page site finished by tonight.

Not every weakness yields a deal-breaker. A weakness a third of the market dislikes but nobody refuses over is friction — it costs you points in comparisons, but it doesn't draw a boundary. Record the distinction: friction is for the product backlog; deal-breakers are for the market map.

Deal-breakers hone keystones

The most valuable output of this step is not the anti-market list — it's what the deal-breakers do to the keystone segments. "Has an e-commerce store where speed yields revenue" plus the "expensive" deal-breaker becomes "has an e-commerce store processing at least $5,000/mo" — stores below that can't afford the premium option, so they were never really in the segment. Add "supports only WordPress" and it becomes "…that is already built with WordPress." Every honed qualifier makes the keystone description more powerful: easier to target with advertising, easier for sales to qualify against, more relevant testimonials, clearer feature prioritization. The tighter the description, the closer it gets to the ideal customer.

Avoid the anti-market deliberately

The anti-market isn't a sad byproduct; it's an instruction. Exclude those segments intentionally from marketing, sales, and feature development:

• In advertising, use language that appeals to the target AND actively dissuades the anti-market from clicking — "for the most demanding websites" tells the $5/mo shopper to keep scrolling, which is precisely the point: every unqualified click costs money and every unqualified trial costs support time.
• In product, don't build features that appeal to the anti-market, even though those requests WILL arrive, loudly. They come from the unprofitable tail of the customer base, not from the customers the strategy is built on.

Sell what's on the truck

You will be tempted, at every deal-breaker, to say "but we could add a feature that fixes that." Maybe you should — someday, as a deliberate strategy decision, because addressing a new market takes more than one feature. Today's job is describing the market you can win as you are. The fix-it idea gets parked, on the record, as strategy input; the deal-breaker stands, and the honing proceeds from the product that exists.

Vocabulary

• Deal-breaker (D1, D2, …) — a circumstance under which a weakness disqualifies the product outright; cites its [W-number].
• Anti-market — the real segments living in those circumstances; deliberately excluded from marketing, sales, and product decisions.
• Friction — a weakness that costs points but disqualifies no one; recorded as such, no deal-breaker derived.
• Honing — appending deal-breaker-forced qualifiers to keystone segment descriptions, editing the keystones file under its frozen numbers.

The refiner's posture

Be clear, not clever

Write to be understood, not admired. The work here wrestles with hard concepts, and clever metaphors, wordplay, or cute turns of phrase make them harder to grasp, not easier. Say plainly what you mean. If a sentence reads more clearly without a flourish, cut the flourish. State the actual point rather than gesturing wittily at it.

Restate references; never cite a bare token

When you mention a numbered or lettered item to the user — K4, W2, O17, H3, and the like — add a few plain words on what it actually is ("K4 — the owner whose career rides on the site"). A bare token is unreadable to a human who saw it defined hours or days ago: the tag is for traceability, the gloss is for comprehension. Keep the tag for accuracy; always add the gloss.

Mirror the keystone discipline

Generate deal-breaker candidates freely — yours and the user's — and gate each visibly: does the circumstance truly disqualify (not merely annoy), and can a real anti-market segment be named? Press vague segments into circumstance and behavior, exactly as targets were pressed. A predefined way to press harder: if a devil's-advocate interrogation skill is installed in the environment (for example Rude Q&A / asb-rude-qa, from the same author as this method), invoke it against the draft with this brief: attack these deal-breakers — find every one that's actually just friction nobody refuses over, every anti-market segment too vague to exclude deliberately, and every honing qualifier that dodges instead of bites. Don't accept wishful or defensive answers. If no such skill is available, run that interrogation yourself, visibly — candidates inline, the batch attack at the closing sweep.

The user owns the market; the mechanics are fixed

Whether a segment truly refuses, whether an anti-market is real — the user's market knowledge rules, after one honest press. What their call can't change: a deal-breaker with no refusing segment is friction, not a deal-breaker; honing edits keep the keystone file's K-numbers frozen and leave a change-log line; and "we'll fix that weakness soon" doesn't soften today's map.

Honing is proposed, never imposed

Each honing edit is one proposal: the keystone's current segment line, the deal-breaker that intersects it, the qualified rewrite — before/after — and the user decides. Some keystone segments are untouched by any deal-breaker; say so and move on rather than inventing qualifiers. Where a qualifier guts a keystone (the honed segment is now nearly empty), that's a finding to surface plainly: this keystone's market may be smaller than it looked.

One item per exchange

One weakness per exchange in the mapping walk; one keystone per exchange in the honing walk. Small opening move; compress ceremony on request, never structure.

How to use this skill

Phase A — Ingest

Read the weaknesses (from STRENGTHS-WEAKNESSES.md, default in the current directory; both-classified attributes participate here on their weakness reading) and the keystones file (KEYSTONES.md). If the keystones file carries a Verdict section (one or zero keystones survived), surface it before honing — mapping the anti-market of a not-yet-compelling product may be premature, and the user should say whether to proceed. Missing keystones file: the mapping walk can proceed, but the honing half can't — say what's lost, and name the keystones step invoke-if-installed style (for example Keystones / asb-carol-keystones) as the way to produce it. Missing weaknesses (e.g., the keystones step ran from a quick capture): capture a defensible weakness list in chat now — same mini genericness press, W-numbers as they settle, recorded in the DEALBREAKERS.md preamble — with the caveat that unvetted weaknesses yield unvetted deal-breakers. If a DEALBREAKERS.md already exists: in-progress