How to hire a freelance designer who can deliver
A founder’s guide to hiring a freelance designer: check real contributions, constraints, working fit, and delivery before committing to the work.

When I ran Drool, my design agency, we turned down an image-generation project and recommended an in-house team. The founders were scrapping features that were still being built. Our working arrangement left us about a day behind decisions that were already changing again.
More overlapping hours wouldn’t have fixed that. The designer needed to be alongside the founders, involved in those decisions and able to act on them. We explained this during discovery and stepped away.
The same founders later came back with MyDrip, a personalized shopping app. It didn’t even have a name when we started. This time, we had the freedom to define the UX and UI, and room to think through the work.
I think of this as a decision’s shelf life. Does it stay useful long enough for the designer to understand it and do something with it?
I freelance now, so this advice comes from someone who also sells these services. I’d still recommend a template, a smaller project, or an employee when that fits the work better.
Decide what needs to change
“Make us investor-ready” is a difficult brief. The website might explain the product badly. The demo might bury its most useful feature. Or the screens might look like several engineers built them independently (which is probably what happened).
Those problems need different work. If the meeting is next week, I’d agree on the few things that must work for that audience. A complete redesign can wait. And nobody can promise that better screens will get you funded.
The same applies to “modern UI and better conversion.” If people abandon onboarding, find out where and why. Check the measurement, watch someone use the product, and look for the part that trips them up. New typography won’t fix a broken integration.
The GOV.UK guidance on understanding user needs is useful here. Test your assumptions about the problem before committing to a solution. Its measurement guidance also recommends combining usage data with user research. If the product is new, start by testing whether people can use it. You don’t need to invent a conversion baseline.
A template or an AI-assisted build may cover what you need right now. If someone on your team can judge the result, fix the awkward states, and maintain it, use that. Hire when you need help your team can’t provide.
Hire for the gap in your team
“Designer” covers a lot of work. Before looking through portfolios, write down what the person needs to take responsibility for. These are the distinctions I’d use when narrowing the search.
These responsibilities overlap. Ask about the work behind the title. A product designer might hand off files to an engineer. A design engineer might build prototypes, production interfaces, or mostly marketing websites.
If your engineers already implement UI well, a designer with a good handoff may be enough. Agree on responsive behavior, loading and error states, reusable patterns, assets, and who answers questions during implementation. If the team is mostly backend specialists, someone who can design and build the frontend may be more useful.
Coding changed how I design. Before coding agents, most of my experience was jQuery for specific changes to WordPress and Webflow sites. Learning to build made me look for patterns that several screens could share before designing another one-off solution.
For a role that includes code, ask to see how the person tests it, handles accessibility, and connects it to real APIs. Someone has to take responsibility for what happens after it ships too.
Choose between a freelancer, an agency, and an employee
Compare the time you need from them with the time you can spend managing the work.
A freelancer can stay with a product for years. An agency can take a small project. Check the actual arrangement before assuming what either will provide.
Meet the people doing the work. An agency’s portfolio may include projects by people who won’t be assigned to yours. Ask whether those people are employees or contractors, who reviews their work, and what happens if someone leaves halfway through. A subscription or retainer also needs a capacity agreement. How many things can move at once? What waits in the queue?
Keep someone on your side responsible for priorities and final decisions. Hiring outside help still requires your time, especially while they learn the product. If several freelancers are involved, decide who keeps their work consistent and handles the handoffs.
Ask what the portfolio actually proves
A good-looking portfolio gets my attention. Before hiring, I want to know what the designer actually did. Pick one project. Ask what they owned, what got in the way, and what shipped.
Self-directed work can be excellent, but it may come with unlimited time, perfect content, and no existing codebase. Ask to see work with constraints similar to yours. A designer who has handled a messy permissions flow may be more useful to your product than someone whose screens happen to use your industry’s vocabulary.
Follow one decision through. What did the designer change after feedback? What did a technical limit force them to give up? Their explanation should connect the finished screen to what happened during the work. Ask the same core questions of each candidate so you have something concrete to compare.
A walkthrough of work they’re allowed to share, a public implementation, or a client reference can help check the account. Team projects are fine. Ask which parts were theirs, without demanding confidential files.
I once hired someone through a freelance platform who passed off other people’s work as their own. An image search led to a Dribbble profile that didn’t match the one they’d supplied. I reported them to Dribbble and Contra, and they were subsequently removed from both platforms. I got half the fee back. An expensive way to learn to check attribution.
Google’s image search can help you find where else an image appears. Treat a match as something to investigate. Collaborators can show the same project, and copied work can go undetected. Use public images for this, or get permission before uploading anything confidential.
Check how you’ll work together
Tell the designer how often priorities change, when you meet, and who makes the final call. Ask how that fits their availability. If decisions expire between conversations, you may need them involved as those decisions happen. The image-generation project needed that kind of involvement.
Be honest about how involved you want to be. Some founders like thinking through the work alongside the designer. Others want to set a direction and review it later. Agree on review times, where feedback goes, and how quickly each of you can respond. Finding out halfway through that you’re expecting different relationships sucks for both people.
I’d be wary of someone who agrees to everything before understanding the work. “I don’t know yet” is a useful answer when they can explain what they need to investigate and what that will cost. A promise to raise conversion or impress an investor needs more than confidence on a call.
Agree on scope and price together
I’ve done projects worth a few hundred US dollars that took a few hours, and projects over $50,000 that took months. The useful pricing conversation starts with what you’re asking someone to do.
For app work, I look at the number and complexity of screens, whether a design system or interactive prototype is needed, and whether there’s an existing system to work with. Screen counts are a starting point. An onboarding screen with loading, empty, and error states still needs those states designed, along with its behavior on smaller screens.
Websites vary just as much. Five pages using existing assets can be a very different job from five pages with original illustrations, custom icons, motion graphics, and code. List what’s included before comparing the fees.
Use rates as a starting point
YunoJuno’s 2026 rates report gives these averages for its design and UX categories. It uses platform data from 2024 and 2025.
Upwork’s UX designer cost guide lists $25 to $39 an hour, based on certain historical contracts worldwide. These sources cover different markets and groups of freelancers. Use the one relevant to your search to get a rough budget, then ask suitable designers to quote the same brief.
Compare the total work included. A higher hourly rate can cost less overall if the work takes fewer hours. A low quote that leaves implementation to your team needs to be compared with the cost of that work added back in.
Match the payment model to the work
A fixed fee works when you can agree on deliverables, feedback rounds, and what counts as finished. For work that needs investigation or frequent changes, hourly or daily billing gives you more room. Set a spending limit and agree when the designer must check with you before continuing. Upwork’s guide to hourly and fixed-price work explains the same choice.
If nobody understands the work well enough to quote it, pay for a small discovery phase first. Use that to decide what to commission next.
For ongoing work, write down the hours or deliverables a retainer buys, how priorities are set, and what happens to unused time. On a project changing as quickly as the image-generation product, I’d want regular chances to review the work before committing more money. A fixed fee for the whole product would need renegotiating every time its scope changed.
Leave room to negotiate
I like to leave some room in the fee for negotiation. I may also lower it when there’s a good chance of more work with the same client. That depends on what I know about the relationship. A mention of future projects doesn’t automatically earn a discount.
Share your budget and ask what fits. Maybe the interactive prototype can wait, or existing illustrations will do. If the designer lowers the fee, write down whether the scope changed. If the work stays the same, record the discount so it doesn’t become the expected price next time.
Before paying, get clear answers to these questions:
- What will be delivered, and what’s excluded?
- What do you need to supply, and when?
- How will feedback and scope changes be handled?
- What counts as accepted work, and when are the deposit, milestone payments, and final payment due?
- Which currency is the quote in? Are taxes, platform fees, licenses, and expenses included?
- Who owns the files and code, what happens if the work ends early, and what support remains after delivery?
“Maintenance included” needs a duration and a description of the work it covers. Fixing a bug and adding a feature are different commitments.
Start with a small paid project
If you’re still unsure about the fit, buy a small piece of real work. One flow or page, a review, and a handoff will give you a chance to see how the person works.
Pay for it even if you decide not to continue. Have the designer quote for the briefing, design, feedback, and handoff, or agree on an hourly or daily rate with a cap. A percentage of an undefined future project doesn’t tell either of you what this work is worth.
An example brief
Suppose your product lets a workspace owner invite teammates, and you need help with that flow. A first engagement could look like this.
Share the review criteria upfront. During the work, notice what the designer asks, how they explain choices, and how they respond to feedback. Ask your engineer to review the handoff too. If you’re hiring someone to implement, include working code in the trial and give them the access needed to build it.
An investor demo needs a different brief. Specify the journey it must show and whether you need a clickable prototype or working code. Keep the trial close to the work you’re actually hiring for.
This can simply be the first milestone of the project. Strong references and relevant work may already give you enough confidence to start. There’s no need to add an audition to every hire. If the trial fee will count toward a later phase, agree on that upfront.
Ask how they handle a slipping deadline
Ask about a project where the deadline became unrealistic. When did the designer tell the client? What did they propose? Ask a reference whether they had enough notice to do anything about it.
You want someone who raises the problem while there are still choices. They might propose cutting scope to keep the date, or moving the date to finish the agreed work. Ask what changed and what each option would mean for your team.
Your part matters too. Missing access, late feedback, and new priorities can delay delivery. Agree on who provides what, and expect the designer to flag it when they’re blocked.
Feedback works better when it describes the problem. “People can’t find the next step” gives the designer something to investigate. “Make it pop” gives them a guessing game. Include them in conversations with people who use the product so they can ask their own questions.
You can disagree with the designer and make the final business decision. Explain the constraint or preference you’re working from. Asking for more versions until they guess what you had in mind wastes everyone’s time.
Before extending the engagement, ask what your team will be able to do without them afterward. Agree on documentation, editable assets, code, and a handover. You should know how to keep the product going when their part of the work ends.
Work with me
I work on product UI, UX, website design, and React frontend development. For products that need a design system, I can build and maintain reusable components, design tokens, and guidelines around your brand. I offer that as design system as a service.
Frontend work can include API integration, testing, accessibility, deployment, and maintenance. We’ll agree on the scope and support terms. Your team needs to provide the backend.
I only implement my own designs. Rough sketches and wireframes are welcome. Finished designs that need implementation alone, or a frontend outside React, need someone else.
If that fits what you’re building, send me an inquiry.