---
title: "Product design subscription vs hiring a designer: how to decide"
description: "How an e-commerce SaaS team picks between a design subscription, a freelancer, an agency project and a full-time hire, with questions to ask and red flags."
topic: "Design process and tickets"
date: 2026-10-13
updated: 2026-10-13
author: "Geetansh Saini"
url: https://www.geeetansh.com/guides/product-design-subscription
tags: ["design subscription", "hiring", "product design"]
---
# Product design subscription vs hiring a designer: how to decide

**In short:** A product design subscription fits an e-commerce SaaS team that ships every week, has more design work than one person can do in a few days a month, and is not ready to pay a full-time salary plus the months it takes to hire. A freelancer fits occasional, well-defined work. An agency project fits a one-off redesign with a fixed scope. A full-time hire fits once design is a daily need and someone can manage it. Whichever you choose, the test is the same: can they hand your engineers a design with every state, edge case and acceptance criterion, inside your Linear and Figma, without a second round of questions.

## What are the four ways to get product design done?

Every Shopify app or TikTok Shop seller tool with more than a couple of engineers reaches the point where the founder stops being the designer. There are four ways out, and they differ less in quality than in what they ask of you.

| Option | What you get | When it fits | What it asks of you |
| --- | --- | --- | --- |
| Freelancer | One person, paid per project or per hour | A defined piece of work with a clear end | Writing the brief, managing the schedule, re-explaining context every project |
| Agency project | A team, fixed scope, fixed price | A one-off redesign, a new product surface, a brand refresh | A long kickoff, approval cycles, and a handoff at the end that nobody owns |
| Subscription | One designer, flat monthly fee, continuous queue | Weekly shipping with a steady stream of features and fixes | Keeping the queue prioritised, giving fast feedback |
| Full-time hire | One employee, embedded | Design is a daily need and someone is there to manage it | Recruiting time, salary and benefits, onboarding, career growth |

The right answer changes as the app grows. Most teams go freelancer, then subscription or hire, and the ones that go agency first often end up with a beautiful redesign and nobody to design the next feature.

## How do the costs compare?

The only cost I can give you a verified number for is the full-time hire. The US Bureau of Labor Statistics puts the median annual pay for [web and digital interface designers](https://www.bls.gov/ooh/computer-and-information-technology/web-developers.htm) at $104,000 as of May 2025, within a broader occupation of web developers and digital designers at $99,520. That is before benefits, equipment, recruiting fees and the weeks of ramp while the new designer learns your merchants, your Polaris setup and your codebase. Senior product designers in SaaS markets typically sit above the median, but I have not found a source I trust enough to quote.

For subscriptions, freelancers and agencies, I am not going to give ranges, because the public numbers come from vendors selling one of those options. The trade-offs are clearer than the prices anyway:

- **Freelancer:** cheapest for a single project, most expensive per hour of your own time. Each new project restarts the context. Good freelancers are booked, so turnaround stretches when you need them most.
- **Agency project:** the most money up front and the clearest scope. The cost that does not show on the invoice is what happens after delivery, when a merchant hits an empty state the agency never drew and no one is on contract to fix it.
- **Subscription:** a flat monthly fee you can stop. Cheaper than a hire, more than a freelancer over a quiet month. The cost is on you to keep the queue full and prioritised. If you pay for a month and send nothing, that month is wasted.
- **Full-time hire:** the highest fixed cost and the longest commitment. The hidden cost is the recruiting time before day one, which can run to months, and the management time after.

The number to compare across all four is not the monthly fee. It is the fee plus your hours spent briefing, chasing and re-explaining. A cheap option that costs the founder a day a week is not cheap.

## Which option fits an e-commerce SaaS team?

Match the option to how often you ship, not to how much budget you have.

**You ship a feature a month or less.** A freelancer, briefed well. Write the ticket first, using the format in [how to write a product ticket](/guides/writing-product-tickets), so the freelancer designs from a problem and not a sentence.

**You ship every week, with two to six engineers.** This is where a subscription earns its fee. The queue never empties: a plan picker that needs a new tier, an empty state for the new affiliates tab, an error state the Shopify API just revealed, a listing screenshot refresh. None of these is a project. All of them need a designer who already knows the app.

**You are rebuilding the whole app or moving from a standalone app to embedded.** An agency project, or a subscription with a longer runway. Either way, agree in writing who designs the states and edge cases after launch.

**Design is a daily need and you have a PM or founder who can manage a designer.** Hire. A subscription is a bridge to this, not a replacement for it, once the work is genuinely full time.

## What should you look for?

The same list applies to all four options. I would not sign with anyone who fails more than one of these.

**Product design, not just visuals.** A pretty dashboard is the easy part. Ask to see how they handle a flow with a sync in the middle, a payout that fails on affiliate 40 of 200, or a merchant on the free plan clicking a paid feature. If the portfolio is all hero screens, they design the happy path and your engineers will design the rest.

**States and edge cases by default.** Every screen they hand over should carry empty, loading, error, partial and success, without being asked. A designer who delivers one frame per screen is handing your engineers a list of questions. I wrote up what a complete handoff looks like in [developer-ready design handoff](/guides/development-ready-design), and I would use it as the checklist in the interview.

**Works in your Linear and Figma, not theirs.** The design should live in your Figma file and the tickets in your Linear workspace, so when the engagement ends, you keep everything. Both tools support this. Linear's [members and roles docs](https://linear.app/docs/members-roles) describe guest accounts as restricted access to specified teams for contractors, clients and cross-company collaborators, with the note that guests are available on Business and Enterprise plans. Figma's [pricing FAQ](https://www.figma.com/pricing-faq/) describes the View seat as free with view and comment access to Figma Design, and the Dev seat as the one with Dev Mode, so your engineers can inspect the handoff without a full seat each. Anyone who insists on their own tools is making leaving harder.

**Cancel any time.** For a subscription, monthly with no lock-in. For a freelancer, per project. If a subscription asks for a six-month minimum, it is an agency retainer with a different name.

**Knows the platform.** Polaris, the Shopify App Store listing rules, Built for Shopify requirements, TikTok Shop's seller tools, Klaviyo flows. A designer who has never seen the Shopify admin will spend the first month learning what your merchants already know.

**Stays through QA.** Design is not done at handoff. The designer should test the build against their own acceptance criteria, on a phone, before it reaches merchants.

## Questions to ask before you sign

1. Show me a feature you designed that included the error and partial states. What did the engineer ask you after handoff?
2. How many tickets did you ship for your last client in a month, and what did they look like in Linear?
3. If I send nothing for two weeks, what happens to my fee?
4. Who owns the Figma file when we stop?
5. Have you designed inside the Shopify admin with Polaris, or for a TikTok Shop seller tool?
6. Do you write acceptance criteria, or does my PM?
7. What is your turnaround on a small change, like new copy on an error state?
8. Will you test the build before it ships?

The answers you want are specific. "Two business days for small changes, a week for a new flow, and I file the QA issues myself" is an answer. "Unlimited requests, fast turnaround" is a slogan.

## Red flags

- A portfolio with no empty, loading or error states in it.
- "Unlimited requests" with no statement of how many are in progress at once. One at a time is honest. Unlimited is marketing.
- A refusal to work in your Linear or your Figma.
- A minimum term on something called a subscription.
- No questions about your merchants, your plans or your churn before quoting. A designer who has not asked who the product is for will design for themselves.
- Mockups delivered as images rather than editable files.
- No mention of QA, UAT or testing anywhere in the process.

For transparency: I offer a monthly subscription for e-commerce SaaS teams that need design continuously but not a full-time designer, and it can be cancelled any time. The checklist above is the one I would want applied to me. My background is on the [about page](/about).

## Where to start

1. Count the design tasks that are waiting right now, from a new plan tier to a missing empty state. Fewer than five means a freelancer. More than five, every week, means a subscription or a hire.
2. Write the next feature as a full ticket with problem, states and acceptance criteria before you talk to anyone. It is the test you will give candidates.
3. Set up a guest in Linear and a View seat in Figma so the designer works in your tools from day one.
4. Ask the eight questions above and keep the answers. Compare them against the red flags.
5. Run a one-month trial on one real feature, and judge it by how many questions your engineers asked after handoff.

## Frequently asked questions

### Is a design subscription cheaper than hiring a designer?

Per month, almost always, because you are not paying salary, benefits and recruiting costs. Over a year of genuinely full-time design work, a hire can come out ahead. The comparison only makes sense once you include the founder or PM time each option consumes.

### Can a design subscription handle product design, or is it just marketing graphics?

Some do and many do not. The distinction is whether they deliver flows with every state and written acceptance criteria, or screens. Ask to see a feature with its error and partial states, and ask what the engineer did with it.

### When should a SaaS team move from a subscription to a full-time hire?

When the queue is full every week for several months, when someone on the team can manage a designer day to day, and when the app needs a design system owned in-house. Until then a subscription keeps the flexibility to stop.

### What should a design subscription include for a Shopify app?

Designs in Polaris where the app is embedded, every screen with its states, final copy, responsive behaviour, acceptance criteria in your tickets, App Store listing assets when needed, and a designer who tests the build before merchants see it.