The actual process of writing copy that converts
Most people skip straight to writing sentences, which is why their copy reads like a product brochure nobody asked for. The workflow I use has nothing to do with inspiration. It's a sequence of decisions, each one narrowing the gap between what the product does and what the buyer actually cares about. When you follow the order, you stop guessing and start producing work that doesn't need to be rewritten three times. Here's the sequence I actually follow. It takes about 20 to 45 minutes for a standard landing page, longer for complex offers. The time varies because step two is where most people stall. Step one: Define the single outcome. One sentence. Not five benefits, one result the buyer gets. "Lose 12 pounds in 90 days without giving up carbs." That's a result. "Improve your health" is not. If you can't state the outcome in one sentence, you don't understand the offer well enough to write about it yet.
Step two: Map the buyer's current state to that outcome. This is the part everyone rushes. You need to answer three questions in writing before you draft a single headline. What is the buyer currently experiencing? What have they tried already and why did it fail? What specific moment made them decide to look for a solution? I once spent four hours on a SaaS pricing page because I assumed I understood the customer's problem. I'd never actually read a support ticket or spoken to a sales rep. The page performed below baseline until I pulled three months of customer call transcripts and rewrote the entire hero section around the actual complaint they voiced, which was nothing like what I'd written. The workaround was brutal but fast: I made a rule that I cannot begin copy for any product category until I've reviewed at least ten direct customer interactions, even if it means waiting on access. Step three: Write the headline and subhead together. The headline grabs attention. The subhead justifies the click. They are two parts of one statement, not two separate pieces of writing. A headline that works without a subhead is usually vague. A subhead that works without a headline is usually a description. Test them as a pair. Read them out loud in sequence. If you stumble, rewrite. Step four: Lay out the objection stack. Before you write a single benefit, list every reason someone would say no. Price, trust, timing, relevance, complexity, competition. Then address each one in order. Not in the order that feels nice to write, in the order of how likely someone is to actually raise it. The first objection should be the most common one you hear from sales teams, not the one you assume exists based on the price point.
Step five: Draft the body in plain language. Short sentences. Active voice. No jargon unless your audience uses it themselves. If you wouldn't say it out loud in a conversation with a colleague, don't write it. This step usually takes longer than the headline because you're translating features into consequences. A feature says "256-bit encryption." The consequence is "your data stays yours even if someone intercepts it." One is a spec. The other is a reason to care. Step six: Add proof at the exact points where skepticism peaks. Testimonials belong after the claim they support. Case study snippets go after the section that makes the boldest statement. Numbers and metrics anchor vague promises. I put a stat next to every percentage claim and a name next to every result claim. If you can't support a statement with something verifiable, either remove the statement or go find the evidence before you keep writing. Step seven: Write the CTA as a continuation of the preceding sentence. The button text should not repeat the headline. It should complete the thought the reader is already having. "Get started" works when the reader is ready. "See how it works" works when they need more information. Match the CTA to the reader's actual position in the decision funnel, not to what sounds punchy.
Get the Full Details
Step eight: Read it backward. Start at the bottom and work up to the top. This prevents your brain from auto-correcting weak logic because you're caught up in the narrative flow. You'll spot gaps, repetition, and claims that don't connect to anything that came before them. Fix those before you do a forward read. Step nine: Get it outside your head within 24 hours. Send the draft to someone who has never worked on the product. Watch where they pause. Watch what they misinterpret. This single step catches more problems than any amount of internal review. Most copy issues aren't grammar. They're assumptions the writer made and the reader doesn't share.
What the checklist doesn't cover
The sequence above assumes you already know who you're writing for and what the product actually does. It doesn't help if your offer is unclear, your audience is too broad, or the product has no real differentiator. A perfect checklist on a confused product produces polished confusion. That's not a copywriting problem. It's a positioning problem. Another limitation: this method favors rational buyers. If your market is driven mostly by impulse, identity signaling, or emotional urgency, some of these steps feel slow or irrelevant. You might spend less time on the objection stack and more time on tone and visual framing. The framework still applies, but the weighting changes. There's no rule that says you have to treat every piece of copy the same way. For high-volume work like ad variations or email sequences, the full checklist is overkill. I strip it down to steps one, three, four, and seven for those assets. The rest adds time without adding signal. Knowing which steps to drop is as important as knowing which ones to follow.
