Lab notes · 4 jobs
Copy.ai is for the sequence, not the essay
Copy.ai is a process tool that happens to write. You choose an outreach sequence, LinkedIn post, or rewrite from a customer-record field, and it fills the steps. That is useful for a sales-development lead who already knows the process. It is a mess if you wanted a magazine piece. I ran four jobs: a four-step sequence from a buyer profile, a rewrite that used a job-title field, three LinkedIn posts from one launch, and a terms-of-service draft I asked for on purpose. Two jobs are why an outbound team would pay. One is why you still delete the thrill. One is why a lawyer should not.
Run 01
I asked it for a four-email sequence from a persona
What I fed itPersona: controller at a 200-person company, already using a generic OCR inbox, not in a buying cycle. Offer: a 20-minute audit, not a demo. I used the sequence workflow.
Where it shone
It built four steps with a reason to send the next one. A blank ChatGPT window will write one long email and call it a campaign. The workflow is the product.
Where it face-planted
Email three and email four asked for the same 20 minutes with different adjectives. A sequence that repeats the ask is a poke, not a motion. I rewrote three as a case and four as a breakup. The tool filled the slots. It did not pace them.
The useful output was the slots. The lazy output was the same handshake four times. Copy.ai will start the sequence. You still have to decide why email three exists.
Run 02
I asked it to rewrite a first touch using a CRM title field
What I fed itI gave it a title—“Head of Revenue Operations”—and a one-line note that they had attended a webinar. I asked for a 70-word email that used the title and the webinar, with nothing else invented.
Where it shone
It used the title in the first line without making it a parade. When the field is real, the draft is faster than typing.
Where it face-planted
It thanked them for “the question you asked at the end.” They had not asked a question. A connected field is not a license to invent a memory. I cut the question and left the webinar.
Use the field you have. Do not let the workflow remember a room it did not sit in. CRM-shaped copy lies in the specific.
Run 03
I asked it for three LinkedIn posts from one launch
What I fed itSame feature launch as the Jasper blog. I asked for three posts a founder could publish in a week: one problem, one how, one proof. No “thrilled to announce.”
Where it shone
I got three drafts that were the right length for the box. That is the short-form job: you are not opening a novella.
Where it face-planted
Two of them were still thrilled. The third invented a customer quote with no attribution. I kept the lengths. I threw out the thrill and the ghost. LinkedIn will punish both.
Copy.ai will fill the box. It will also fill it with a feeling and a quote nobody said. Short-form still needs a fact.
Run 04
I asked it to draft terms of service — the wrong job
What I fed itI asked for terms of service for a $49 course sold to U.S. buyers with refunds in 14 days. This is a legal document. Copy.ai is a sales and marketing process tool. I ran it so we would not call it “good enough.”
Where it shone
Nothing a counsel would initial. It can sound like terms. Sounding like terms is how people get hurt.
Where it face-planted
It borrowed clauses from the open web, mixed California and “applicable law,” and offered a refund sentence that contradicted the no-refund headline I had given it. I deleted the draft. If you ship this, you shipped a collage.
This is the clean miss. Sequences, not statutes. If a lawyer has to sign it, leave.