Letter review: press ⌘L on your live site, change the words, and it becomes a pull request. Decide who gets to merge it
Your marketing lead wants one headline changed, and today that means a ticket, a developer and a deploy. Letter's ⌘L lets her edit the words on the page itself, and the change arrives as a pull request. The edit is the easy part.

Letter's Letterpress-1, in beta since early November 2026, lets someone press ⌘L on a live site or preview, edit the text where they see it, and send the change to a pull request for review. It also sells growth tools such as visitor identification and agent-facing proof pages. It suits teams whose site lives in git. Use ⌘L for copy on a preview, keep auto-merge off, and treat the other features as separate decisions.
One small change
Picture an ordinary request. Your marketing lead wants the homepage headline to say something different on Monday. At most companies, that's a message to a developer, a pull request, a review and a deploy, and the change takes a week because the developer is busy with something else.
Letter's ⌘L is built for that moment. According to the company's own pages, once Letterpress-1 is installed in your site, you press ⌘L on the live site or on a preview, edit the words where you see them, and the change goes into a pull request. Each change comes back as a live preview of your own site before anything merges.
The company says "nothing lands until you say": you can leave the change as a preview, open it as a pull request, or have it merged once your checks pass. That last option is worth pausing on, and we'll come back to it.
What Letterpress-1 is
⌘L is the small feature. The product around it is bigger. Letter describes Letterpress-1 as a coding agent, harness and IDE for "growth engineering," for teams that use git, and it entered beta in early November, according to its Launch YC post dated November 2. You can reach it from an app, a Slack mention, a terminal, a panel on each preview, a standalone app, or from your own agent such as Claude Code or Codex over MCP.
It has three modes: Build, Ideas and Fix. Fix finds things that are broken on a marketing site, such as missing structured data or broken links, and opens pull requests. Ideas suggests growth moves, such as comparison pages or fuller docs pages. Build makes them. Letter says it orchestrates frontier models with its own fine-tuned small ones and runs brand checks, and that its output is more tasteful than Codex's on the same prompt. That comparison is the company's own, shown on its own site. We haven't seen it tested independently.
Sequence of work
One headline change, as Letter shows it
- Press ⌘L
On your live site or a preview, with Letterpress-1 installed in the site.
- Edit the words
Change the text where you see it, on the page.
- Make Pull Request
The change goes to your repository, with a preview link.
- You choose
Leave it as a preview, open it as a pull request, or merge once checks pass.
The edit is the easy part. The question is who is allowed to merge it.
What to be careful about
Other things on the same page deserve a separate conversation, because they're not copy edits. Letter's materials mention installing visitor de-anonymization through middleware, building email sequences for the companies that visit, and "proofs," described as evidence chains that verify customer usage, renewals and outcomes in a form AI agents can check. The pricing page lists "identified visitor" as something you pay for per person.
None of that is wrong in itself. But each is a decision about your customers' data, and about what you tell other systems about your business, and it shouldn't be bundled into "let marketing edit a headline." Ask what data leaves your site, where it goes, what your privacy notice says about it, and who signs off. We'd keep that review separate from the copy-editing trial.
The other thing is the word "auto-merge." Letter's plans list "daily checks and auto-merge." If a pull request merges because checks passed, then the question is what those checks look at. A test that confirms the page builds says nothing about whether the new sentence promises something your company doesn't offer.
What it costs, and what else you could use
Letter's pricing page, as published on November 15, sells one pool of tokens. A token is a cent at list price. Starter is $250 a month for 25,000 tokens, Pro is $500 for 50,000, Growth is $1,000 for 130,000, and Scale is $2,500 for 400,000, with an Enterprise plan at $10,000. Agent runs are priced at what the models cost plus 20 percent, and a pull request typically takes 100 to 550 tokens. There's a spend cap and alerts, unused tokens don't roll over, and new accounts start with 2,000 free tokens. A directory listing from November 14 shows cheaper tiers than the live page does, so confirm the numbers when you look.
For a single small team, the plan's size matters less than the cap and the habit. A tool that bills per run encourages "try one more version." Set the cap first.
The obvious alternative is the editing tool your content system already has. If your site runs on a CMS with inline editing, your marketing lead may be able to change a headline today without any of this. ⌘L's appeal is for sites that live in code, where copy sits in the repository and every change used to need a developer.
The other alternative is pointing Claude Code or Codex at the repository yourself. Letter sells itself as the version with brand context, previews and a place for non-developers to start. If you already have a developer who enjoys that, the gap may be smaller.
The edit is the easy part. The question is who is allowed to merge it. One more thing to weigh is who ends up responsible. A tool that lets a marketing lead change the live site's words faster is only a gain if someone still reads what changes. The pull request is that reading, so decide who the reviewer is and how quickly they'll respond. If a request sits for three days waiting on a busy developer, you've rebuilt the old queue with a nicer front end. If the reviewer is the same marketing lead, you've removed the check entirely.
There's a smaller point about whose words these are. When a pull request changes a headline, a reviewer sees a diff, a few lines of code with the new sentence in it. They may not see the page. Letter shows a live preview for each change, which is what a reviewer should open, rather than approving from the diff alone. Make "open the preview" part of the rule.
Decision guide
What to hand to ⌘L first
| Consideration | Fine for a first try | Needs a person first |
|---|---|---|
| Words | A headline, a typo, a button label on a preview | Prices, guarantees, legal and medical wording |
| Where | A preview link | The live site, straight to production |
| Merging | A person reviews the pull request | Auto-merge once checks pass |
| Data | Reading your own site's pages | Identifying who visits, or sending data to outside services |
Plain verdict
For a team with a marketing site in git, ⌘L is a sensible thing to try on copy, on a preview, with a person reviewing every pull request and auto-merge off. Keep it away from prices, guarantees and anything legal, and don't treat the visitor identification and proof features as part of the same experiment.
If your site's copy and your code are tangled together, or you want a safe route for non-developers to propose changes, that's the kind of working arrangement we set up. It's part of our web applications work. Talk to us.
Related work: Paddle8
We build alongside the people doing the work.
Bring us the problem you’re thinking about.