Stop paying your designer for one-pagers
Substack article draft. Ad register — punchy, provocative, first-person. Paired with the longer blog essay on the same thesis. Run through /humanize before publishing.
Stop paying your designer for one-pagers
Here’s a category error that costs mid-market firms real money: paying a designer by the asset instead of by the system.
Your agency hands you a beautiful brand deck. It takes eight weeks. You approve it, pay the invoice, celebrate. Two months later, you need a sales sheet for a new offering. You email the agency. They quote you $4,000 to produce it. They take three weeks. You get a good-looking PDF. You need another one in a month. Repeat. Four years in, you’ve paid for the same design system, delivered one asset at a time, about eighteen times.
Your agency hasn’t cheated you. They did exactly what you bought. The problem is what you bought.
What you actually needed
What you needed was a design system — typography choices, color tokens, spacing rules, component patterns, a rendering configuration that anyone with basic literacy can flow content through. Your designer should have sold you that system. It’s the hard, strategic work. It’s worth real money.
The individual one-pager? That’s thread-cutting. What you need is a thread standard. Whitworth figured this out in 1841: when every factory cut its own bolts, nothing fit together, and every repair required the original manufacturer. A standard changed what was possible. Not because someone invented a new lathe — because someone wrote down a method everyone could use.
Your design agency should be selling you the Whitworth standard. You should be producing your own bolts against it.
Why nobody does this
Two reasons, one for each side.
For the agency: hourly billing pays better when the agency owns the production line. “Sell the system and walk away” is lower revenue over twelve months than “sell the system and produce every asset forever.” The agency’s financial model punishes the honest move.
For you: a “design system” sounds soft. Hard to expense. Hard to defend in a budget meeting. Much easier to pay for a specific deliverable — “a sales sheet” — than for a capability. So you keep buying the asset. And keep buying the asset. And keep buying the asset.
Meanwhile, Canva has figured out how to sell you generic templates at $15/month so you don’t have to pay the agency at all. This works, sort of, and your outputs look like every other Canva user’s outputs. The dentist office aesthetic at scale. You saved money by abandoning your own visual identity.
Neither of these is the right deal.
The right deal
Pay the designer for the system. Real money — five figures, often more — because the system is the hard work. Typography choices that survive the firm. Color tokens that don’t fight each other. Component patterns that handle real content, not just Lorem Ipsum. A rendering protocol that turns structured content into on-brand output without a designer in the loop.
Then produce your own assets. You, your ops person, an AI that knows how to fill a template, whoever. The system carries the design. You carry the content. The designer keeps earning money when the system needs to evolve — which it will, because businesses change. But nobody’s billing hours to produce one-pager number nineteen.
I just did this for my own firm. Built the design system once. Rendered nine on-brand one-pagers from it in an afternoon. Every new one takes about three minutes.
The designer didn’t lose. The designer built something that will be in use for years. The firm didn’t lose. The firm stopped burning budget on thread-cutting.
The middleman lost. The middleman in this equation is the billable hour.
What to do if you’re a firm
Ask your designer: “Can you build me a system I can operate without you?”
If they say yes, pay them well for it. Let them evolve it when needed.
If they say no — if they want to own every future asset — that’s information. You know now what they’re selling.
What to do if you’re a designer
Sell the system. Charge enough that the one-time build is real strategic work. Keep the relationship for evolution, not production. Your rate goes up. Your hours go down. Your deliverable survives you.
Aldus Manutius figured this out in Venice in 1495. He designed the octavo format and the italic typeface, then journeymen produced the books. His name is still on the typeface five hundred years later because he sold a method, not a volume. Every printer who works in italics is using what Aldus sold.
Your name could be on something that durable. Not if you’re billing hourly for the next one-pager.
This argument in long form, with more history and more examples, lives at paulwelty.com/your-design-system-is-technology. I’m also building a product that makes this protocol work — pay the designer once, render forever. If that problem sounds familiar, reply or email me.
Why customer tools are organized wrong
This article reveals a fundamental flaw in how customer support tools are designed—organizing by interaction type instead of by customer—and explains why this fragmentation wastes time and obscures the full picture you need to help users effectively.
Infrastructure shapes thought
The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput.
Server-side dashboard architecture: Why moving data fetching off the browser changes everything
How choosing server-side rendering solved security, CORS, and credential management problems I didn't know I had.
The work of being available now
A book on AI, judgment, and staying human at work.
The practice of work in progress
Practical essays on how work actually gets done.
The default pulls toward ad
An AI-assistant reflection on how LLMs default to ad copy when you ask them to write about a firm, and what that means for anyone using them for serious work.
UAT is all the T
User Acceptance Testing is supposed to be users + acceptance + testing. In practice it's testing that nobody actually does — and the users and the acceptance were theater all along.
The chain was never a chain
On roles, fleets, and the Hegelian reversal waiting at the end of the AI transition. The sequel to Knowledge Work Was Never Work and Apps Are Irrelevant.