Market Sophistication

Five competitor tabs are open on Mireille's screen. Every page promises to get studios paid faster, and her draft in the sixth tab says "Get paid faster without chasing clients."

Mireille and Copperfin, her invoice-follow-up service for design studios, are invented, along with the competitors, interviews, features and copy below. She needs to decide which promise to keep before polishing its wording.

How do you tell which stage a market is in?

"Think small" puts a compact car's size straight into the headline. Volkswagen of America began its campaign with Doyle Dane Bernbach in July 1959, after losing share to Renault and American manufacturers' new compact cars.

Volkswagen's chronicle names "Think small" and "Lemon" among the campaign's classics. I'd draw a drafting question from that choice for Mireille: when buyers have similar offers to compare, which reason to choose yours deserves the opening?

Eugene Schwartz's Breakthrough Advertising, first published in 1966, offers five stages for thinking through this choice. They describe how a message changes as buyers encounter repeated promises. Treat the stages as a practitioner's guide to research; a stage assignment is a judgment, including any you might make about Volkswagen.

She needs to know whether studio owners have seen those competing pages. Five search results establish that a promise is circulating. Interviews can help establish whether her intended readers have encountered it or tried the services behind it.

Start your competitor research for copywriters with the alternatives buyers actually consider. For Copperfin, a bookkeeper and manually sent reminders could belong in the comparison. An enterprise billing platform might never enter a small studio's decision.

Three places to check the proposed difference

Competitor page

Record the opening claim verbatim, with the page date.

Customer interview

Ask which alternatives the buyer considered and what they expected.

Product check

Watch one paid invoice and one disputed invoice pass through the reminder queue.

What buyers have heard is one question. What the product delivers is another.

Compare Copperfin's promises with the evidence needed to publish them.

Mireille copies "get paid faster" into her claim sheet and records the explanation beneath each version. A page promising automatic reminders goes in a different row from a bookkeeper offering to make follow-up calls. Those rows reveal which processes her interviews need to explore.

"Other software" tells Mireille less than the name of a service a studio tried, or an account of how its bookkeeper handles reminders. She adds those details to the comparison before judging which claims have become familiar.

Stage one: state the direct benefit

Schwartz's first stage describes an audience that hasn't been flooded with similar promises. A direct benefit can introduce the opportunity: "Send an invoice reminder without writing the follow-up email."

For Copperfin, the supporting explanation shows the studio approving a prepared message and choosing when to send it. A newcomer can see which writing task the service takes over and which decisions remain theirs.

Be careful not to mistake one audience's unfamiliarity for proof that a whole category is new. One group may be discovering a tool another group has used for years.

Mireille asks studio owners to describe their last invoice follow-up. Someone who still types each email may need to see a prepared reminder before an explanation of exception handling will mean much. That answer gives her a reason to keep the direct-benefit version in contention.

Stage two: enlarge a benefit you can support

In the second stage, Schwartz describes competitors enlarging an established claim. Before you promise a bigger result, check what the product can support.

Mireille considers "Never chase another invoice," then rejects it. Copperfin can't control whether a client pays. She looks instead at how much of the follow-up work a studio can arrange in advance.

A product walkthrough shows that the studio can schedule the full reminder sequence while sending the invoice. Her enlarged benefit becomes "Set the whole invoice follow-up schedule when you send the bill." That saves the studio from returning to the invoice to schedule each message separately.

That enlarges the first-stage benefit from one prepared email to the whole follow-up schedule. If returning to old invoices interrupts project work, the added scope gives studio owners a reason to care. A claim about faster payment would still need evidence about payment outcomes.

For U.S. advertising, the FTC's substantiation policy requires a reasonable basis for objective claims before they're made. Ask for the supporting evidence while choosing the claim, including evidence for any implied result.

Build a claim inventory

• Which alternatives do these buyers actually consider?
• What outcome does each page promise?
• What process supposedly produces that outcome?
• What evidence supports the promise?
• Which limits or conditions does the page disclose?
• What have customers already tried and found disappointing?

Stage three: explain a meaningful mechanism

By stage three, buyers have heard the outcome repeatedly. Schwartz turns to the mechanism: the process that makes the promised result plausible.

What happens when a client pays between the studio scheduling a reminder and Copperfin sending it? Mireille follows that invoice through the queue.

Her first draft says "Follow up on unpaid invoices without reminding clients who already paid." She runs a paid invoice through the walkthrough and watches it leave the queue after the connected payment record updates.

The update matters. A delayed bank-transfer record could leave a paid invoice in the queue, so her first draft promises too much. She narrows the explanation to the event she can demonstrate: the connected record updating.

Mireille also strikes "Intelligent Revenue Accelerator" from the draft. The revised copy below explains what happens to a paid invoice and a disputed one. Readers can ask whether their accounting system connects and decide how that process would fit their records.

Make the mechanism inspectable

A label without an explanation

Our Intelligent Revenue Accelerator gets you paid.

An operational explanation

A paid invoice leaves the reminder queue after its connected record updates. A dispute waits for manual review.

Name the event that changes the queue, then demonstrate each state you describe.

Stage four: distinguish the mechanism itself

In stage four, similar mechanisms have become familiar too. "Automated reminders" offers Mireille little distinction if every relevant alternative already includes them.

Mireille checks a disputed invoice in the walkthrough. The studio can pause its reminders and assign the dispute to a named teammate.

She drafts "Pause the reminder. Give the dispute an owner," with the assignment screen directly beneath it.

In these invented interviews, studio teams recognize "get paid faster" from services they've tried. They already use scheduled reminders and payment-status checks.

Their remaining difficulty is handing a disputed invoice from the project lead to the person handling payment; a solo designer has no such handover.

Mireille checks the reminder services those teams tried. They can pause messages, but leave the handover in an email thread; Copperfin keeps the named owner beside the paused invoice. That gives her a mechanism difference for this comparison, with a demonstration she can put beneath the claim.

Use evidence from customer objections to check whether that difference matters. Here, the teams describe reopening email threads to find who took responsibility. Mireille selects the assignment opening for those teams, keeping her comparison scoped to the alternatives they named.

Stage five: make identification specific and earned

Schwartz's fifth stage describes an audience tired of repeated claims and mechanisms. Identifying a recognizable situation gives you another possible opening.

Copperfin could address "Studios where the same person finishes the project and follows up on the invoice." The next paragraph would explain how that person sets a reminder schedule when sending the bill and handles exceptions later.

Compare that with "Built for people who think differently." A studio owner can't locate their working day in that sentence. Mireille's version names the uncomfortable overlap between finishing creative work and asking to be paid for it.

Copperfin's identity line needs a firm connection to the offer: the person finishing the project must also own the follow-up work. Mireille checks for that overlap in customer accounts before considering it as an opening for solo studios.

Keep customer awareness separate from sophistication. Someone familiar with competing promises may still need an explanation of your particular service.

Evidence to collect before choosing an opening

Benefit

• A demonstration that the product performs the promised action.

Larger benefit

• A demonstration supporting the added scope or scale of the benefit.

Mechanism

• A walkthrough showing each step and its exceptions.

Mechanism difference

• A comparison against the alternatives buyers actually consider.

Identification

• Customer accounts of the specific working situation you describe.

This editorial adaptation of Schwartz's stages can be used out of order.

Choose an opening from your claim ladder

Keep your value proposition and the Psychology lessons beside your draft. Collect opening claims from alternatives buyers have mentioned, including their current way of doing the job. Record the size of your sample so you can see where more research is needed.

Draft five openings, one for each stage. Beside each, record the evidence needed to publish it and what your audience has already heard that might make it familiar.

Choose the version whose reason to care survives both checks. Mireille chooses the stage-four opening for the teams she interviewed: they already use reminder automation, and their alternatives leave dispute ownership in email. She saves the stage-two version for a separate audience whose main difficulty is scheduling follow-ups.

Beside "Pause the reminder. Give the dispute an owner," Mireille records the intended audience, the services those teams tried and the handover they described. Her sixth tab now has an opening chosen for readers whose experience she can trace through the claim sheet.