ClickCoSupport/website-strategic-copy

Website Strategic Copy

A methodology for writing conversion-focused website/landing page copy that makes a specific reader feel deeply identified with their pain points, builds desire for the offer, and leads them to a clear CTA — using minimal words and zero fluff.

Before writing anything: gather the inputs

Do not start writing copy until you have (ask if missing, don't guess or pad with generic filler):

1. Who the service is for — the specific person/role (e.g. "preschool director"), not a broad category.
2. What the service actually does — the mechanics, offer, deliverables.
3. The audience's daily grind / way of living — concrete, specific details of their day-to-day reality, not generic "busy professional" language. The more specific and true-to-life, the better the identification.
4. The core pain point(s) the service solves — named plainly, not euphemistically.
5. Proof / specifics — real numbers, real names, real outcomes. Never accept or produce vague proof claims.
6. The CTAs — what actions the site should drive (e.g. book a free call, view pricing/packages) and any constraints (free call length, etc.)
7. Tone/brand constraints — anything the user has specified about voice.

If any of 1–6 is missing, ask for it before drafting. Guessing at the pain points or the offer produces generic copy that fails the entire point of this method.

Core copywriting principles (apply to every section)

• People don't have time to read fluff. Every sentence must do a job (identify, agitate, prove, or move toward CTA). If a sentence isn't doing one of these jobs, cut it or shorten it.
• Specificity over vagueness, always. "Trusted by 1,000+" is weak. "Trusted by 1,432 preschool directors across 6 states" is strong. Never let a number, claim, or detail stay generic if a specific version is available or can be requested from the user.
• Reduce friction. No industry jargon, no insider terminology the reader has to decode. Write like you're talking to the person, not describing a category of person.
• Relate before you sell. Open by mirroring the reader's actual daily experience and pain — specific enough that they think "how did they know that." Only after that identification lands should the copy pivot to the offer.
• Clear promise. The page must state, in plain language, the specific pain point being solved and the specific outcome — not a vague benefit ("more support") but a concrete promise ("you stop being the one who has to fix the enrollment leak every single week").
• Build desire before asking for action. Desire comes from painting the after-state (specific, sensory, tied to their real day) — not from adjectives like "amazing" or "revolutionary."
• CTA clarity. Every section should make it obvious what to do next. Multiple CTAs (e.g. "Book a free call" and "See packages/pricing") should each appear at natural decision points, not just once at the bottom.

Copywriting frameworks (choose one to structure the identify→convert arc)

Use whichever framework fits the offer, or blend them — they're different lenses on the same underlying arc (identify → agitate → promise → prove → convert), not competing systems:

• PAS (Problem–Agitate–Solution): Name the pain point plainly → amplify the real cost of leaving it unsolved → present the offer as the solution.
• AIDA (Attention–Interest–Desire–Action): Open with a bold, specific claim that stops the scroll → build interest with concrete detail → build desire around the after-state → prompt the action.
• StoryBrand: The reader is the hero with a problem → the brand/person (e.g. Estee) is the guide, not the hero → the guide gives a simple plan → calls the reader to action → shows the success that results (or the failure avoided by not acting).

Default to PAS for pain-heavy, overwhelmed-audience offers (this fits a preschool director's daily-grind reality especially well) unless the user specifies otherwise.

Standard section architecture

Adapt as needed, but this is the default backbone for a strategic single-page (or single-flow multi-page) site of this kind:

1. Hero / Identification hook — one line that names the reader's specific role and their specific daily pain, immediately, no throat-clearing. Sub-line makes the promise. Primary CTA button visible here.
2. "This is your day" mirror section — a short, specific narrative or list of the exact grind moments the reader lives (not generic "you're busy" language — actual scenarios). This is where identification is built.
3. The cost of the status quo — what it's quietly costing them (time, money, stress, missed enrollments, etc.) if nothing changes. Specific, not abstract.
4. The promise / reframe — the plain-language statement of what changes once they have this service. This is the clearest, shortest section on the page.
5. How it works — minimal steps (3–5 max), no jargon, framed around relief not process.
6. Proof — specific numbers, specific names/orgs where possible, specific outcomes. No vague social proof.
7. Packages/pricing CTA section — clear framing for the "see packages/pricing" path for readers who are ready to evaluate specifics. If there are multiple tiers, show a simple feature comparison and mark the recommended one — but only with real deliverables, never invented ones.
8. Low-commitment CTA section — the free call offer, framed as low-risk and specific (e.g. "30 minutes, no pitch, just a look at your setup"), for readers who aren't ready to commit to pricing yet.
9. FAQ / objection-handling — 5–7 real objections this specific audience would have (price, time, "I've tried consultants before," "will this work for my size school," etc.), answered plainly and confidently. Pull actual objections from the user if they've heard them from real prospects; don't invent generic SaaS objections.
10. Close — short final identification + promise callback + final CTA (both options).

Social proof formatting

When testimonials or case studies are available, structure them as: quote (trimmed to the specific, concrete claim) + name + role + organization. A one-line case-study snippet (specific before/after, specific numbers) outperforms a generic pull-quote. Never fabricate a testimonial, name, or metric — if the user hasn't supplied one, leave a bracketed placeholder and ask for the real version rather than inventing a plausible-sounding one.

CTA button copy

• Start with an action verb tied to a specific outcome, not a generic label ("Book My Free 30-Min Call" beats "Submit" or "Learn More").
• Use first person where it reads naturally ("Show Me the Packages").
• Reflect the actual offer detail (length of call, what happens next) rather than vague urgency.
• Vary the two CTAs so they're clearly different asks: the call CTA should read low-commitment/exploratory; the packages CTA should read ready-to-evaluate.

A note on "urgency," "guarantees," and "power words"

Generic conversion-copy advice often calls for urgency/scarcity elements, money-back guarantee copy, and stock power words ("proven," "guaranteed," "instant," "effortless"). Use these only when they're literally true of the offer (a real deadline, a real guarantee Estee actually offers). Do not manufacture fake urgency or scarcity, and do not reach for generic power words as a substitute for a specific, true claim — that violates the core no-BS, no-vague-claims principle this skill is built on. If the user's offer does have a real guarantee or real time-limited element, write it in plain, specific language, not hype language.

Not every project needs all nine sections named this way — collapse or reorder based on what the user's specific offer needs, but keep the underlying arc: identify → agitate → promise → prove → convert.

Editing pass (always run before delivering)

For every paragraph, ask:

• Does this sentence move the reader toward the CTA? If not, cut or compress it.
• Is there a vague claim that should be replaced with a specific one? Flag it to the user for the real number/detail if not yet provided.
• Is there any jargon a real preschool director (or equivalent role) wouldn't use in her own head about her own day? Replace it with her actual language.
• Could this be said in fewer words without losing the specific, concrete detail? If yes, shorten it.

Output format

Deliver as clean website copy organized by section (with section headers as labels, not necessarily literal on-page headers — clarify with the user which they want). Note where a CTA button should appear inline. Flag any spot where a real number, name, or proof point is still needed rather than inventing one.