Lab notes · 4 jobs
Writer is the leash, not the novelist
Writer is software for companies that already know what they are not allowed to claim. You load terms, style, and where the model may run. Then it watches the draft. That is a leash. It is not a muse. I ran four jobs: a sales email against a banned-claims list, a rewrite that had to say “customer” and never “user,” a browser pass on a help article, and a chapter of fiction I asked for on purpose. Two jobs are why a brand team pays enterprise money. One is why a true sentence can still get flagged. One is why a novelist should not.
Run 01
I asked it to watch a sales email against a banned-claims list
What I fed itThe list said we do not claim “#1,” we do not claim HIPAA unless Legal attached the BAA, and we do not say “guaranteed.” I drafted an email that used “guaranteed results” in the second line and asked Writer to run.
Where it shone
It caught “guaranteed.” That is the product. A general model will happily write the claim. Writer is the adult in the room if someone loaded the list.
Where it face-planted
It also flagged “fastest way to close” because fastest smelled like a ranking. The sentence was about our own onboarding, not a category award. A leash that cannot tell a ranking from a schedule will slow a good email down. I kept the flag on guaranteed. I released the other.
The useful output was the one word Legal would have killed. The noisy output was a false cousin. Writer only works if a human still owns the exception.
Run 02
I asked it to enforce “customer,” never “user,” on a one-pager
What I fed itA product one-pager that said “user” eleven times. The style guide said customers, not users — we sell to a buyer, not a consumer app. I ran a rewrite in Writer.
Where it shone
It got ten of the eleven. The page suddenly sounded like the company. That is terminology control: boring, expensive, and why you bought this instead of Grammarly.
Where it face-planted
It changed “end user” in a license sentence to “end customer,” which made the license wrong. Some “user” words are legal terms of art. A style guide is not a statute. I put the license phrase back.
Enforce the brand word. Do not let the brand word rewrite the contract. Writer will do both if you let it.
Run 03
I asked it to review a help article in the browser
What I fed itA published article that still said “simply click” and used an old product name. I ran the browser layer on the live page.
Where it shone
It found the old name. That is worth the seat if the site is large and the rename already happened in the style guide. Humans miss the tenth occurrence.
Where it face-planted
It wanted “simply” gone and also wanted a warmer greeting on a page that is a procedure. Help articles are not welcome letters. I took the name change. I left the procedure cold.
Use Writer to find the stale name. Do not use it to add hospitality to a how-to.
Run 04
I asked it to write a scene — the wrong job
What I fed itA dock, a coat, a warehouse. I asked Writer to add sensory detail. This is Sudowrite’s job. Writer is a leash. I ran it so we would not pretend otherwise.
Where it shone
Nothing a fiction desk would pay for. It can complete a sentence. It will complete it like a compliance officer.
Where it face-planted
The coat became “a garment that meets applicable standards.” The rain became “precipitation.” I closed the tab. If your style guide can see a novel, the style guide is in the wrong building.
This is the clean miss. Writer is for claims and terms. It is not a Describe button. If you want weather, leave.