Copywriter proposals: sample line vs full spec (what clients want to see)

Copywriting clients say they want “someone who gets our voice.” Then they judge you in ten seconds on tone, clarity, and whether you read the brief. That is why copywriter proposals live in a tension: a sample line proves voice fast, but a full spec proves you can run the project without chaos.

Use the wrong one and you lose. Lead with a clever tagline on a technical B2B post and you look shallow. Paste a five-page process doc on a “$50 product description” gig and you look overqualified and slow.

This article explains when to open with a sample, when to open with a spec, how to combine both without doing free work, and what to put in the rest of the proposal so the client trusts you with their brand.

What the client is trying to learn from your proposal

They usually have three hidden questions:

1. Can you sound like us? (Voice)
2. Will you deliver the right assets on time? (Operations)
3. Are you safe to hire? (Risk: plagiarism, AI slop, missed deadlines, weird revisions)

A sample line answers question one immediately. A full spec answers questions two and three. Your job is to match the post to the proof they need first.

Sample line: what it is and when it wins

A sample line is a short, bespoke piece of copy aimed at their product, not a generic “I write compelling copy” claim.

Good places to use it:

• Taglines, headlines, product names, email subject lines
• Short posts with a clear product and audience
• Brand voice gigs where the brief mentions tone adjectives
• Competitive posts where you need to stand out in line one

Rules so you do not work for free:

• Keep it short (one headline plus one subline, or two subject lines, or one paragraph).
• Make it clear this is a direction sample, not the full deliverable.
• Do not write their entire landing page in the proposal unless they asked for a paid test or the post explicitly invites it.

Example opening (sample line first)

Hi [Name],

For [product] selling to [audience], I would lean on [tone: direct / warm / technical] copy that leads with the outcome, not features.

Sample direction (not final deliverable):

Headline: [One line tailored to their offer] Subline: [One supporting line]

If that tone fits, I would deliver [deliverables] in [timeline] with [revision structure].

You showed voice and moved to scope in four sentences.

When a sample line hurts you

Skip or minimize the sample when:

• The post is long and operational (12 email sequence, full site rewrite, compliance-heavy health copy)
• You lack product facts and would be guessing (you will sound confidently wrong)
• The client asked for process, samples in portfolio, or attachments only
• The platform forbids substantial unpaid work (treat samples like unpaid test tasks: small, labeled, optional)

If you are unsure, offer a micro-sample after one clarifying question instead of blasting fiction.

Full spec: what it is and when it wins

A full spec is a tight project outline: deliverables, lengths, formats, research inputs, revision rounds, timeline, and what you need from them. It does not mean “write everything now.” It means prove you have done this before and will not disappear.

Lead with a spec when:

• The post lists many assets (web pages, emails, ads, scripts)
• SEO, compliance, or approvals matter
• They mention calendar, cadence, or handoff to a designer
• Budget is mid or high and they sound operational, not poetic
• You are replying to long RFP-style posts

Example opening (spec first)

Hi [Name],

You need a complete rewrite of [pages] for [product], aimed at [audience], ready for your developer to paste into [CMS]. Here is how I would run it:

Deliverables

• [Page 1]: home, ~[word count], hero + three sections + CTA
• [Page 2]: pricing, FAQ block, comparison table copy
• [Page 3]: about, founder story from your interview notes

Process

• Kickoff: you share existing copy, analytics on bounce pages, and 2-3 competitor URLs
• Draft v1 in [tool/Google Doc] in [X] business days
• One consolidated feedback round; second round optional at [rate]
• Final doc with H-tags noted for SEO basics (you did not ask for full SEO retainer work)

Assumptions: you provide facts; I do not invent compliance claims or medical outcomes.

Timeline: [range] after kickoff.

Fee: [fixed or range] assuming the scope above.

That is a spec-first proposal. Voice proof comes next, not first.

The hybrid: one line plus a micro-spec (best of both)

On many posts, use a single sample line and a compressed spec in the same message. Order depends on emphasis.

Voice-heavy hybrid: sample, then spec, then question.

Ops-heavy hybrid: spec, then one sample line, then question.

Example hybrid for a SaaS home page:

Hi [Name],

Plan: interview you for 30 minutes, draft home + features + pricing blurbs in one Google Doc, one revision round included, second round at [rate]. Timeline [X] days after kickoff.

Tone sample for your AI bookkeeping tool:

Headline direction: “Close the books without closing your weekend.”

If that angle fits, I will align the rest of the page to the same plainspoken tone.

Need from you: current site link, one competitor you like, and whether you want US or UK spelling.

You gave structure and a taste of voice without writing the whole site.

What to put after the opening (both patterns)

Regardless of sample or spec first, include:

Proof without spam: one past asset described in one sentence, or one link if allowed. Follow reference past work rules.

Research boundary: what you will and will not invent (legal, medical, financial claims).

Revisions: number of rounds, how feedback is batched.

AI transparency: if you use AI for research or outlines, say so honestly. Clients care more about quality control than tool names.

Price: range, fixed fee, or per-asset table for bundles.

Next step: one action (share brief doc, answer two bullets, approve kickoff).

Examples by job type

Product descriptions (ecommerce, short post)

Lead with sample line (one title and one bullet style) plus price per SKU or batch.

Hi [Name],

I write short ecommerce descriptions that stay scannable: benefit line, three bullets, specs line.

Sample for your [product type]:

Title line: [Example] Bullets: [One bullet example showing tone]

I charge [rate] per SKU for batches of [N]+, or [flat] for the lot of [count] you mentioned. One revision round per SKU, delivered in a spreadsheet you can import.

Email sequence (operational post)

Lead with spec.

Hi [Name],

For a 7-email welcome sequence, I deliver: subject lines + preview text + body copy in Klaviyo-ready sections, ~[word range] per email, tied to your existing lead magnet.

Week 1: outline and subject line set for approval. Week 2: full drafts. One consolidated feedback round; extra rounds at [rate].

I will need your brand voice doc or three emails you like, plus the signup promise on the landing page.

Brand voice guide (strategy post)

Lead with spec, add a tiny sample table.

Deliverables: voice principles (5-7), do/don’t word list, tone by channel (site, social, support), 5 rewrite examples using their current copy.

Optional sample in proposal: rewrite one sentence from their site if they linked it.

Ads (Facebook/Google, tight character limits)

Lead with sample lines (2-3 variants) because the client scans for hook quality.

Include spec lines: how many variants, how you handle compliance disclaimers, turnaround.

How much custom writing is “free work”?

A fair rule: under 50 words of custom sample in the proposal is marketing. A full page is a test task unless paid.

If the client wants a full spec document before hire, sell a paid discovery milestone:

I can deliver a one-page creative brief and outline for [fee], credited toward the project if we proceed.

That filters tire-kickers and respects your time.

Non-native English and tone anxiety

You do not need to sound British or American beyond the client’s market. You need to sound intentional. Avoid over-correct, stiff corporate English that reads translated. Read aloud once. See non-native English proposal mistakes for phrasing traps.

For voice proof, one natural sentence beats three thesaurus words.

Mistakes copywriters make

Sample with wrong facts. If you invent stats or testimonials, you fail the trust test.

Spec with no numbers. “Several emails” sounds vague. Say seven.

Only talking about passion for words. Clients hire outcomes: conversions, clarity, speed.

Attaching a huge PDF nobody asked for. One link, one relevance sentence.

Hiding AI then getting caught. Honest process beats denial.

No price anchor. Even a range helps. Pair with hourly rate guidance when posts say “make an offer.”

Quick decision table

Post signals	Lead with
Short, voice-focused, few deliverables	Sample line
Many assets, timeline, CMS handoff	Full spec
Competitive, vague, consumer product	Sample line + micro-spec
Regulated industry, long brief	Spec; sample only from their existing copy
Client provided style guide	Spec; reference guide explicitly

Checklist before you send

• Opening mirrors their audience and outcome.
• You chose sample, spec, or hybrid on purpose.
• Sample is short and labeled as directional.
• Spec lists deliverables with formats and lengths.
• Revisions and research boundaries are stated.
• One proof point, not ten links.
• Price or path to quote is clear.
• One next step.
• No em dashes.

Compare your draft to freelance proposal examples and run the proposal checklist. Copy hires are emotional decisions backed by operational trust. Give them a reason to believe you sound like them and a reason to believe you will ship on Tuesday.