Why Design Subscriptions Sound Great but Don't Actually Work
Design subscriptions sound great until you actually run one.
I tried it for a year. Clients loved the idea of "unlimited" design. I loved the idea of predictable income. Everyone wins, right? Not quite.
What the subscription model promises
The pitch is compelling. Pay a flat monthly fee, submit as many design requests as you want, get them turned around in 24-48 hours. No contracts, no scope creep, no surprise invoices. Companies like Design Joy popularised the model and it spread fast.
For clients, it feels like hiring a designer without the commitment. For designers, it feels like stable recurring revenue without the sales cycle. On paper, it solves everyone's biggest problem.
What actually happens
It quickly turned into a race. Fast briefs. Faster turnarounds. No time to think deeply or solve the real problem. Just constant requests and notifications.
The subscription model incentivises volume over quality. When a client is paying a flat fee, they naturally want to maximise the number of requests. When a designer is handling unlimited requests, they naturally optimise for speed. The result is a lot of output that solves surface-level problems without ever getting to the root cause.
I found myself producing work I wasn't proud of. Not because I didn't care, but because the model didn't leave room for the thinking that good design requires. It was project work taken to its extreme: no context, no continuity, just a queue.
The context problem
Design isn't a drive-through service. It's problem solving. It needs context, patience, and conversation.
The best design work I've ever done came from understanding a client's business deeply: their users, their constraints, their competitive landscape, their growth goals. That understanding takes time to build and compounds over months.
Subscriptions work against this. The model treats design as a commodity, interchangeable tasks that can be queued and processed. But a designer who understands your product deeply will produce fundamentally different work than one who's seeing your brief for the first time. The best design work comes from that deep understanding, not from processing a queue faster.
What works better
What has worked far better is something far less exciting: a simple retainer. One day a week with a client's product team. Ongoing. Predictable revenue for me, consistent design capacity for them.
The difference is subtle but significant. A retainer gives me deep context. I attend the team's key meetings. I understand why decisions were made three months ago. I know which parts of the product are fragile and which are solid. That context shows up in every design decision.
Projects work well too, especially for founders shipping something new or teams with a specific challenge to solve. The key difference from subscriptions is scope. A project has a defined problem to solve, not an unlimited queue to process.
The real question
Before choosing an engagement model, ask yourself: do you need a lot of design tasks done quickly, or do you need the right design decisions made thoughtfully?
If it's the first, a subscription or junior designer might work. If it's the second, understanding what to hire a designer for helps clarify which model fits. You need someone with enough context to make strategic calls, and that takes either a well-scoped project or an ongoing relationship.
It's not trendy, but it works. And that's what actually matters.
---
