Capacity Based Pricing

Capacity based pricing is the discipline of anchoring your productized design service monthly fee to the real number of clients you can serve before your personal bandwidth or system reliability cracks. Start by picking your annual revenue target and divide by twelve for the monthly number. Then run time studies on your last thirty projects to determine average hours per request type. Adjust for 2026 efficiencies where tools like Adobe Firefly handle asset exports and Figma AI generates initial concepts cutting your hands on time in half. If your target is eighteen thousand per month and your process supports six clients at two day turnarounds with one active request each your price becomes three thousand per client. This forces you to say no to extra clients even when demand is high. Instead you raise the price as your capacity expands through better systems or AI. The article on productized design services calls this pricing to capacity first and it remains the difference between a sustainable solo business and one that scales into unwanted overhead.

This approach is not the lazy habit of checking what other productized services charge and matching them. Design Pickle sits at one thousand nine hundred dollars for their entry tier but that price reflects their large team and different scope. Copying it without your own capacity data is suicide for a solo operator. It is also not value based pricing that requires deep client interviews to uncover their budget and then anchoring to a percentage of their projected gains. Capacity pricing does not give a damn about the clients willingness to pay or their ROI calculations. You set the number from your constraints. A traditional retainer that bills monthly for a bank of hours fails the test too because the client controls the volume and your capacity becomes their variable. Project pricing for a single website design at fifteen thousand dollars also lives in a different universe. Those models tie your income to individual transactions instead of predictable monthly output within fixed limits.

The strongest concrete example remains Designjoy by Brett Williams. By 2024 he had refined his capacity to support fifteen clients at the top tier of seven thousand nine hundred ninety five dollars per month. The secret was not working harder but enforcing one request at a time per client using a shared Linear board for transparency and requiring briefs through a structured Notion form. AI tools available in 2026 further expanded what he could deliver in one to two business days without adding staff. He hit over one million in annual recurring revenue as a true solo act. Another example is a freelance motion designer named Sarah who transitioned in 2023. She limited her offer to short form video content for social media. After two months of tracking she calculated capacity at seven clients. Each could have one active video request with forty eight hour delivery. Her math targeted twenty one thousand monthly so she set the subscription at three thousand dollars. Excluded work like long form YouTube edits or 3D animation triggered clear upsells. Clients respected the boundaries because the value was obvious and delivery was reliable. On the flip side consider the case of a deck designer in Austin. Seduced by stories of easy subscriptions he launched at two thousand nine hundred ninety nine dollars aiming for twelve clients to hit thirty six thousand monthly. Without capacity testing he quickly drowned in revision loops that the article warns against. He had not defined what done meant or limited revision rounds to the original brief. The queue backed up clients churned and he returned to hourly billing within six months wiser about the need for capacity first pricing.

Deploy capacity based pricing when you operate in execution heavy repeatable categories like social media assets presentation decks or website components where briefs can be standardized and output measured. It works best for designers who have implemented the full system stack from request intake to delivery using tools like Typeform for briefs Trello or Linear for queues Stripe for billing and Loom for async critiques. The model exploded in popularity between 2022 and 2026 precisely because AI reduced the time sink on production work allowing one person to serve more clients at higher price points. Use it if your goal is predictable revenue and you are disciplined enough to turn away work that falls outside your defined scope. The approach does not suit every situation. Avoid it for high variability work such as original brand identity creation in depth UX research or intricate custom illustrations that cannot fit into a queue without constant back and forth. New designers still building their portfolio and process should not start here either. They lack the historical data to calculate true capacity and will set the number too high leading to broken promises. If you panic when a client pauses their subscription or you crave fresh creative challenges every week this model will feel like a cage. Test your readiness with the self assessment table in the productized services guide. Only those who can define scope without hedging and enforce it daily should flip the switch.

Calculate capacity first set the price second and protect that number like it is your most important design decision.