The Letter Company Releases Letterpress-1: A Coding Agent Built for Growth Engineering

The Letter Company has released the beta of Letterpress-1 , a coding agent, harness and IDE for growth engineering. The Letterpress-1 coding agent reads a website and its market, then decides what should exist. It builds the change in a sandbox and opens a pull request with a live preview. TL;DR Size: Letter team says it combines frontier models with fine-tuned small models; names and sizes are not disclosed. Runs on: Letter’s hosted platform against your git repository. No local GPU needed. Setup takes under 5 minutes, per Letter. Performance: No public benchmark. Letter shows 1 self-reported, side-by-side page build against Codex. Best: 760 tools exposed through 1 registry over MCP, REST and CLI. Worst: No measurable eval; entry plan is $100/month with overage at 5x the list rate. What is Letterpress-1? Letterpress-1 is a growth engineering agent from The Letter Company. It turns site and market signals into pull requests. The letter company team argues that websites, unlike apps, react to outside forces. These include agent behavior, Google rankings, human visits and competitor activity . General coding agents were built to scale codebases, not to act on those signals. The agent is aimed at teams that host their marketing site in git. It is proactive: it suggests the next thing to build. Examples include de-anonymization, landing pages, warmed emails, blog automation and agent telemetry. How does Letterpress-1 work? Letterpress-1 runs in 3 modes : Build: create a page or feature from a prompt, with brand copy and visuals kept consistent. Plan: pick a goal and get a build plan of growth actions. Fix: find site issues and dispatch pull requests to fix them. Every change follows the same loop. The agent reads the site, plans and builds in a sandbox. It reviews its own change, then opens a pull request. Each change returns a preview link of your own site . Nothing lands until you choose a preview, a pull request, or a merge after checks pass. Letter team lists 6 surfaces. These are the web platform, a Slack app, the letterpress CLI and a website portal. A standalone app and your own agent round out the list. The in-site IDE works on a live page. Press ⌘L, edit text where you see it, and a pull request follows. Showcase examples also cover A/B tests from live edits. For developers, agents.md documents an MCP server at app.letterstory.com/api/mcp with OAuth. The MCP manifest, OpenAPI spec and API reference form 1 registry of 760 tools. Claude Code, Codex or any MCP-capable agent can call the same functions the app uses. What are Proofs, Simulations, Benches and Phantoms? The launch post highlights 4 primitives aimed at winning over AI agents as buyers: Proofs: signed evidence of customer success, built from telemetry and billing data, for agent visitors. Simulations: mirror versions of your API or MCP with simulated data, so agents can try before buying. Benches: self-hosted, reproducible benchmark apps with open-source code and independent governance. Phantoms: independent, autonomous blogs used to sandbox growth strategies. The site adds more: Kernels, Letterbases, Visitors and Mailers. Then it watches competitor sitemaps and flag new pages. Letter team positions these as replacements for tools like G2, Semrush, Profound, RB2B and Instantly. Play the loop</button> <button class="btn" id="prev">← Back</button> <button class="btn" id="next">Next →</button> </div> </section> <section class="panel" id="p-modes" role="tabpanel"> <div class="modes" id="modes"></div> <div class="card mdetail"><span class="tag" id="mtag"></span><p id="mbody" style="margin:6px 0 0"></p></div> <div style="margin-top:16px"><span class="tag">Where it runs</span> <div class="chips" id="surf"></div> <p class="note">Plus ⌘L in-site editing: change text on your live page and a pull request follows. 760 tools are exposed over MCP, REST and CLI.</p> </div> </section> <section class="panel" id="p-prims" role="tabpanel"> <div class="filters" id="flt"></div> <div class="prims" id="prims"></div> <div class="card" style="margin-top:12px"><span class="tag" id="ptag">Tap a primitive</span><h3 id="ptitle">Pre-built growth infrastructure</h3><p id="pbody" style="color:var(--muted);margin:0">Each primitive is its own endpoint. The launch post spotlights Proofs, Simulations, Benches and Phantoms.</p></div> </section> <section class="panel" id="p-calc" role="tabpanel"> <div class="calc"> <div> <div class="row"><label>Pull requests per month <span class="v" id="vpr"></span></label><input type="range" id="pr" min="0" max="200" value="20"></div> <div class="row"><label>Tokens per pull request (Letter cites 150 to 900)</label> <div class="seg" id="tpr"><button class="btn" data-v="150" aria-pressed="false">150</button><button class="btn" data-v="500" aria-pressed="true">500</button><button class="btn" data-v="900" aria-pressed="false">900</button></div></div> <div class="row"><label>Articles published per month (1,030 tokens each) <span class="v" id="var"></span></label><input type="range" id="ar" min="0" max="60" value="8"></div> <div class="row"><label>Phantom sites live (300 tokens a month each) <span class="v" id="vph"></span></label><input type="range" id="ph" min="0" max="10" value="2"></div> <div class="row"><label>AI visibility answers (12 tokens each) <span class="v" id="vai"></span></label><input type="range" id="ai" min="0" max="3000" step="50" value="600"></div> <div class="row"><label>Identified visitors (25 tokens each) <span class="v" id="vvi"></span></label><input type="range" id="vi" min="0" max="2000" step="25" value="100"></div> </div> <div class="card"> <span class="tag">Your month</span> <div class="total" id="tok"></div> <div style="color:var(--muted);font-size:13px" id="list"></div> <div id="bars" style="margin-top:10px"></div> <p class="note">1 token = 1 cent at list. Overage on each plan is 5x its own per-token rate. Defaults match Letter's own pricing example. Rates from letter.dev/pricing.</p> </div> </div> </section> <div class="ft"><span>Sources: <a href="https://letter.dev/" target="_blank" rel="noopener">letter.dev</a> · <a href="https://letter.dev/pricing" target="_blank" rel="noopener">pricing</a> · <a href="https://letter.dev/agents.md" target="_b