Do design subscriptions do real product and UX design? How to check, before you pay

The short answer: some do, many do not, and the provider's own scope page usually tells you which. Most "unlimited design" services grew out of graphic design: logos, social posts, ad creative, print. Many list "UI design" beside those and leave out the work that makes software usable. A subscription does real product design when five things are true: the scope names flows, states and prototypes; a senior designer reviews each delivery; the handoff is a file an engineer can build from; testing with users is available; and the team can build it, or hand it cleanly to the people who will.

This guide is those five checks. The examples are quoted from providers' own pages as we read them on 12 October 2026. Pages change, so open the link before you rely on any of them.

What is the difference between graphic design and product design?

Graphic design is the design of a single artefact that communicates: a logo, an advert, a slide, a landing page hero. It is finished when it looks right.

Product design is the design of how software behaves: the flows a person moves through, every state of every screen, and the components and rules that keep a hundred screens consistent. It is finished when a person can complete the task and an engineer can build it.

UX design is the wider discipline that product design sits in. Don Norman and Jakob Nielsen's definition is that user experience "encompasses all aspects of the end-user's interaction with the company, its services, and its products". They add that it is important "to distinguish the total user experience from the user interface (UI)".

That distinction is the whole question. A service can draw a good dashboard and still not do product design, because one frame of a dashboard is a picture of a product, not a product.

Does the scope list flows, states, prototypes and UX?

A scope page has three parts worth reading: what is included, what is excluded, and which plan each item sits on. Read the exclusions first.

ManyPixels' scope page is a clear example. Under web design it lists "UI design" and "SaaS dashboards". Under "We don't do" it lists "Prototypes" and "UX Design". Both statements are true at once, and a buyer who reads only the first list will assume more than is on offer.

The words that signal product design are flows, states (empty, loading, error, success), prototypes, components, tokens, design system and usability testing. The words that signal graphic design are social posts, ad creative, print, packaging and presentations. A scope page made mostly of the second list, with "UI" as one line among thirty, describes a graphic design service that also draws screens.

Then check the plan. Duck.Design's pricing puts "UI/UX & Mobile App Design" on its $1,899 plan, not on its $1,199 graphic design plan. A homepage tends to describe the top plan. The pricing table says which plan you would be on.

Who reviews the work before you see it?

A review layer is a senior designer who checks each delivery against the brief and the design system before it reaches you. In graphic design, review catches a wrong logo. In product design it catches what you will not notice until the build: a missing error state, a component that almost matches the one on the previous screen, a flow with no way back.

Ask for a name and a role. Ask whether that person sees every delivery or only the ones that are escalated.

Providers answer this differently, and the answer is usually on the site. Designjoy says it is "a one-man agency" run by its founder, who does not employ other designers or outsource, so the person you brief is the person who designs. Penji's plans list a "Project Manager" on the $995 plan and an "Art Director" on the $1,995 plan. Eleken's plans include "The guidance of our Head of Design". At Recast, one lead designer reviews each delivery and is on every call.

None of these is the right answer for everyone. Not knowing is the wrong one.

What does the handoff file contain?

A developer-ready handoff is a design file an engineer can build from without asking the designer what was meant. For a product screen in Figma, that means:

• every state of the screen, not only the filled-in one;
• components with named variants, used as instances and not as detached copies;
• design tokens, which are named values for colour, type, spacing and radius that the file and the code share;
• a spec frame that states spacing, behaviour and edge cases in words;
• layers that read properly in Figma's Dev Mode, which Figma describes as "a developer-focused workspace for inspecting designs, viewing properties and generated code".

Tokens are no longer only a house convention. The Design Tokens Community Group has published the first stable version of its format, 2025.10, so you can ask a provider whether its variables export to it.

Ask to see one finished file from a past product project, with the client's name removed if need be. Open it and click a colour. If it shows a variable name, the file was made to be built. If it shows a hex code typed by hand, it was made to be looked at.

Can they test the design with users?

UX design without evidence is opinion. The cheapest evidence is a usability test: a few people from your audience attempt a task on a prototype while someone watches where they stop.

It does not take many people. In Why You Only Need to Test with 5 Users, Jakob Nielsen reports that a first study with five participants finds 85% of the usability problems in a design. He recommends several small tests over one large one.

So ask three things. Is usability testing in scope? How many participants? What comes back: recordings, a list of findings, a written recommendation?

A provider whose scope excludes prototypes cannot run this kind of test, because there is nothing for a participant to click. That is why the prototype line on a scope page matters more than it looks.

At Recast, usability testing is available on request: five users and a written recommendation.

Can they build what they design?

Build matters for two reasons. A team that also builds knows what is expensive to build, and designs accordingly. And if the provider does not build, the handoff file has to carry everything, so the handoff check above gets stricter.

The table shows what five providers' own pages say about product scope and build.

Provider	Product and UX scope, as stated	Build, as stated
ManyPixels	Lists "UI design" and "SaaS dashboards". "We don't do" includes "Prototypes" and "UX Design".	"We don't do" includes "Coding (HTML/CSS/JS)" and "WordPress, Framer, Wix, Webflow".
Designjoy	Lists "UI/UX design" and "Mobile apps". "Most requests are designed using Figma."	"Webflow development" is on the plan.
Penji	"Web & landing page design" on all three plans.	"Front-end development" on the $4,500 plan only.
Duck.Design	"UI/UX & Mobile App Design" from the $1,899 plan.	A "No-code development" plan at $1,999: Webflow, WordPress, Wix, Framer.
Recast	Developer-ready Figma: components, tokens, spec frames. Design system built and maintained. Usability testing on request.	Front-end build hours included: React, Next.js, Webflow, Framer.

What should you ask before you pay?

Seven questions, in the order that saves the most time:

1. What is on your exclusions list? Every provider has one. If it is not published, ask for it in writing.
2. Which plan includes product and UX work? Get the plan name, not "yes".
3. What does a finished screen include? States, components, tokens, a spec frame.
4. Are prototypes in scope, and usability testing?
5. Who reviews the work, by name, and do they see every delivery?
6. Can I see one finished Figma file from a past product project? A file, not a portfolio image.
7. Do you build, and in what? If not, what do my engineers receive?

A provider that does product design can answer all seven in one email. Then test the answers on a real task: how to test a design partner covers trials, pilots and guarantees, and what "unlimited" gets you in a month covers how much work a plan gets through.

Where Recast fits

Recast is a product design studio in Amman, Jordan, led by Daniel Makhamreh, lead designer, with 300+ projects designed. It is one example of a subscription built for product work, not the only one. It is the wrong choice if what you need is social graphics and ad creative at volume. A graphic design subscription does that for less.

The plan is $3,900 a month, billed monthly: unlimited tasks with five worked in parallel, first concepts in 48 hours, one lead designer reviewing each delivery, developer-ready Figma, a design system built and maintained, and front-end build hours included. There is a 14-day full refund.

To run the checks in this guide on us, book the free 20-minute pilot call, put a week of real work through the $490 pilot, or read the plan.