Paper raises $34M: a design tool that renders as HTML

On July 23, Paper announced a $34 million Series A led by Accel and ICONIQ. The pitch: a design tool that renders in HTML and CSS, so what a designer makes is already the thing an engineer — or a coding agent — ships. If you have ever paid twice for the same screen, once to design it and once to rebuild it, that sentence is the whole story.

What actually happened

Paper is a San Francisco company founded by Stephen Haney. Accel led its seed round and came back to lead the A alongside ICONIQ, with Designer Fund participating and angels including WorkOS co-founder Michael Grinich and Lovable co-founder Anton Osika, plus engineers and designers from Anthropic and OpenAI. Accel lists Paper under its "AI-native design space" thesis.

The product bet is narrow and specific. Traditional design tools produce a proprietary document that describes a UI. Paper produces the UI — real HTML, real CSS — on the theory that when a coding agent is doing the implementation, the agent should read the actual markup rather than infer intent from a picture of a rectangle.

Company-reported traction: customers including Ramp, Lovable, Vercel, PostHog, Quartr, and Y Combinator, and ARR up 25x since Paper Desktop launched earlier in 2026. Those are Paper's numbers, not audited ones — treat them as directionally interesting, not as a benchmark.

Why it matters for your business

The design-to-code handoff has always been a tax. You pay a designer to produce a file, then pay a developer to interpret it, then pay both again when the interpretation is wrong. For most small businesses that tax is invisible because it shows up as "the site took longer than we thought."

Coding agents change the math in a way that is easy to miss. An agent given a screenshot guesses. An agent given the actual CSS does not. The gap between those two outcomes is the entire argument for tools like Paper, and it is the same argument as putting your product data in a structured feed instead of a PDF: agents reward whoever hands them machine-readable truth.

The caution is the usual one. A design tool that outputs HTML is still a tool with an export path you should test before you depend on it. Before you move a team onto anything in this category, build one real screen in it, export it, and check what you get: is it clean semantic markup you would accept in a pull request, or is it a wall of absolutely-positioned divs that technically renders? That answer decides whether you have removed the handoff or just moved it downstream.

Sources: BusinessWire — Paper Raises $34 Million Series A with Accel and ICONIQ, Accel — Paper.