Ask five studios what product design costs and you'll get five answers, and at least three of them will be "it depends." That's not evasion; it's the honest starting point. But "it depends" is useless without knowing what it depends on.
We're Things, a digital design and engineering studio founded in 2018, working from Istanbul and Elazığ with leading brands in Turkey and worldwide. We've shipped more than fifty products, picked up a Red Dot along the way, and scoped hundreds of proposals. This is the breakdown we wish every founder and product leader had before their first pricing conversation.
How much does UX design cost?
Short answer: anywhere from a few thousand dollars for a focused sprint to well into six figures for a full product built end-to-end. The honest range for a serious app design engagement with a professional studio typically lands somewhere in the low tens of thousands to low hundreds of thousands of dollars, depending on scope, research depth, and region.
Market ranges vary widely by region and scope, so treat any single number you read online (including ours) as an indicative bracket, not a quote. A freelancer in one market may charge in a week what a top-tier agency in another charges in a day. What matters far more than the headline number is what it buys: how deep the research goes, how many platforms are covered, whether a design system comes with it, and how close the design sits to the code that ships.
Why does design pricing vary so wildly?
Because "design" describes wildly different amounts of work. Two projects can both be called "app design" while one is a ten-screen visual refresh and the other is a research-driven product with forty flows, two platforms, a design system, and engineering handoff. Same label, ten-fold difference in effort.
Three structural reasons drive the spread:
- Design is scoped, not shelved. There's no price tag on a shelf. Every engagement is a custom estimate of hours, seniority, and risk.
- Seniority compounds. A senior designer doesn't just work faster; they avoid entire categories of rework. Rates reflect that, often in the buyer's favor.
- Geography and positioning. UX agency rates in San Francisco, London, Berlin, and Istanbul occupy different bands for comparable quality. Studios pairing strong craft with a favorable cost base, as many in Turkey do, often deliver the best value-per-dollar in the market.
What actually drives the cost of product design?
Five things: scope, research depth, platform count, design system needs, and how tightly design integrates with engineering. Everything else is a variation on these.
1. Scope: how much product is there?
Screen counts are a crude proxy, but flows are real: onboarding, core loops, settings, payments, edge cases, empty states, error states. A product with five core flows is a fundamentally different project from one with twenty-five. Complexity multiplies too: a dashboard with role-based permissions costs more to design well than a content app with three screens per flow.
2. Research depth: how much do we know before we draw?
You can design from assumptions, from stakeholder interviews, or from proper discovery: user interviews, competitive analysis, usability testing, analytics review. Research typically adds 10–30% to a budget and routinely saves multiples of that by killing wrong ideas before they're pixel-perfect and expensive. We're a research-driven studio for exactly this reason: the cheapest place to change a product is before it exists.
3. Platforms: one surface or three?
iOS, Android, web, tablet, responsive marketing site. Each additional platform isn't a full duplicate of the cost (good systems thinking shares a lot), but expect meaningful increments per platform, especially where native conventions genuinely differ.
4. Design system needs: a product or a foundation?
If you need forty screens, someone can draw forty screens. If you need forty screens plus the ability to build screen forty-one without us, that's a design system: tokens, components, documentation, governance. It costs more up front and is almost always the right call for products that will live longer than a year.
5. Engineering integration: does the design have to survive contact with code?
Designs that end at a Figma link are cheaper than designs that ship. Handoff specs, developer collaboration, QA of the built product, and design-engineering pairing all add cost, and they remove the single biggest source of quality loss in digital products: the gap between what was designed and what was built. As a studio that both designs and engineers, we price this in because we've seen what happens when nobody does.
What are the main pricing models for design work?
Three dominate: project-based, retainer, and embedded team. Each trades certainty against flexibility.
Project-based (fixed scope, fixed fee)
- Best for: well-defined problems, such as a new product's first version, a redesign, or a marketing site.
- The trade-off: you get budget certainty, but you pay for it. Studios price in risk, and every scope change becomes a negotiation. If your product is still finding itself, fixed scope fights discovery.
Retainer (reserved capacity per month)
- Best for: ongoing product work, such as iterating on a live product, continuous research, and design system maintenance.
- The trade-off: flexibility and momentum, but you need internal clarity about priorities or you'll burn hours on the loudest request rather than the most important one. Monthly retainers with studios commonly range from a few thousand to tens of thousands of dollars depending on team size and seniority; again, ranges vary sharply by region.
Embedded team (studio designers inside your team)
- Best for: companies with product leadership who need senior execution capacity without hiring.
- The trade-off: the highest bandwidth and the deepest context, but you're paying for dedicated senior people and you must manage them well. If your internal process is chaotic, embedding talented people into it just produces expensive chaos.
An honest studio will tell you which model fits your situation, and will sometimes tell you the cheaper model is the right one. If a vendor only ever recommends their biggest package, that tells you something.
Why does the cheapest option usually cost more?
Because you pay for design once if it's done well and twice (or three times) if it isn't. The failure modes are predictable:
- Rework. Designs built on assumptions get rebuilt after launch, at engineering prices, which are the most expensive prices there are. A skipped $10k research phase frequently resurfaces as a $60k rebuild.
- Handoff gaps. Cheap design often ends at pretty screens. No specs, no states, no edge cases. Your developers fill the gaps by guessing, and the shipped product looks like the guesses.
- No research. Without evidence, design decisions are opinions, and opinions get relitigated forever: in meetings, in revisions, in pivots. Research is how decisions stay decided.
- No system. Screen-by-screen design without underlying structure means every future feature starts from scratch and drifts from the last one. Inconsistency is a tax paid monthly, forever.
None of this means expensive automatically equals good. It means the floor for good is real, and prices dramatically below it are subsidized by something, usually your future budget.
How do AI-augmented workflows change design economics?
They make iteration faster; they do not make thinking cheaper. This distinction matters, because "AI will make design nearly free" is the most seductive wrong idea in the current market.
At Things, AI-augmented workflows are part of how we work: generating variants, accelerating research synthesis, drafting copy and states, prototyping in code earlier. The honest impact:
- More exploration per dollar. Where a budget once bought three directions, it may now buy eight. Quality goes up because more options got compared.
- Faster loops. Research-to-prototype-to-test cycles compress from weeks to days.
- Compressed production, not compressed judgment. Knowing which of the eight directions is right (for these users, this business, this technical reality) is still senior human judgment. That's what you're actually paying for, and AI raises its leverage rather than replacing it.
Practically: expect AI-augmented studios to deliver more depth and iteration at a given budget, not the same output at a fraction of the price. Be skeptical of anyone promising the latter; it usually means the thinking was never part of the offer.
What should you ask for in a design proposal?
A good proposal makes cost legible. You should be able to see what you're buying and why. Ask for:
- A scope breakdown by phase (discovery, design, systemization, handoff) with what each phase produces.
- Named deliverables, including the unglamorous ones: edge cases, empty states, specs, documentation.
- The research plan: who will be spoken to, what will be tested, and how findings change the design.
- The team: who actually does the work, and how senior they are. "Award-winning studio" means little if juniors execute unsupervised.
- How engineering handoff works, and who's accountable for the built product matching the design.
- Assumptions and exclusions, stated plainly. Vague proposals produce disputed invoices.
- What happens when scope changes, because it will.
A proposal that can't answer these isn't underpriced. It's under-thought.
How does Things scope and price design work?
Through our process: Understand → Shape → Build → Evolve. We scope against it directly:
- Understand: research, stakeholder alignment, and problem definition. Often scoped as a fixed discovery phase, so you get real findings before committing to the full build.
- Shape: UX architecture, UI design, and design systems, scoped by flows and platforms rather than vague screen counts.
- Build: because we're a studio of designers and engineers, we can carry the work into web and mobile code ourselves, or pair tightly with your team. Design that ships is the point.
- Evolve: retainer-based iteration after launch, driven by real usage.
We're a studio, not an agency: no account-manager layer between you and the people doing the work, no juniors hiding behind a famous logo. Design. Code. Mastery. That's the pitch and the pricing philosophy in three words: you pay for craft, and you can see where every part of the budget goes.
FAQ
How much does it cost to design an app?
Indicatively, professional app design ranges from the low tens of thousands of dollars for a focused MVP to six figures for a multi-platform product with research and a design system. Ranges vary significantly by region, scope, and studio seniority, so get a scoped proposal, not a rate card.
What do UX agencies charge per hour?
Hourly and day rates vary widely by market, from under $50/hour in some regions to $200+ at premium Western agencies. Hourly rates are a weak comparison metric anyway; compare scoped outcomes and team seniority instead.
Is a design retainer better than a fixed-price project?
Fixed price suits well-defined, one-time builds. Retainers suit live products that evolve continuously. If you're pre-launch with a clear brief, start project-based; switch to a retainer once the product is in users' hands.
Can AI make product design significantly cheaper?
It makes iteration faster and exploration broader at the same budget. It doesn't replace the research and judgment that make design decisions right, so expect better outcomes per dollar, not near-zero prices.
How long does a typical product design project take?
Most serious engagements run 6–16 weeks for design, longer if engineering is included. Timelines compress with tight decision-making on the client side; slow feedback is the most common schedule killer.
Ready for an honest number for your product?
Send us what you're building; a paragraph is enough to start. We'll tell you what it realistically takes, which engagement model fits, and where you can save without paying for it later.
Write to hello@things.ist. Things, a digital design & engineering studio. Istanbul & Elazığ, working worldwide since 2018.