Upwork proposal templates for UI UX designers
Updated
Clients hiring a UI UX designer on Upwork usually screen for fit before style. They want to see that you understand the product, user flow, platform, and business goal. Your proposal should prove you read the post, show one or two relevant design examples, and explain how you’ll move from problem to wireframe, prototype, and handoff.
Template 1: UI UX audit or redesign
Hi {{client_name}}, I read that you want to improve {{specific_screen_or_flow}} because {{goal_from_job_post}}. That sounds like a UX problem first and a visual design problem second.
I can help you review the current experience, identify the points where users may be getting stuck, and redesign the key screens in {{tool_or_platform}}. For this type of project, I’d start with a quick audit of {{current_app_or_website}}, then map the user flow before moving into wireframes and high-fidelity UI.
Relevant examples:
- {{case_study_1_link}} — {{one_sentence_result_or_context}}
- {{case_study_2_link}} — {{one_sentence_result_or_context}}
For your project, I’d focus on:
1. Clarifying the main user action on {{important_screen}}
2. Reducing friction in {{flow_name}}
3. Making the layout easier to scan on {{desktop_mobile_or_both}}
4. Preparing clean Figma files for feedback and developer handoff
A couple of questions before I estimate the final timeline:
- Do you already have analytics, user feedback, or support tickets pointing to the issue?
- Should the redesign stay close to the current brand, or are you open to a broader visual update?
If you’d like, I can start by reviewing {{specific_page_or_flow}} and send back a short plan for the first design pass.Use this when the client has an existing product, website, dashboard, app, or landing page that needs better usability, conversion, or polish.
Template 2: New app or product design
Hi {{client_name}}, I saw that you’re building {{product_type}} for {{target_users}} and need {{deliverables_from_post}}. The key part here is turning the product idea into a clear first version without over-designing features that users may not need yet.
I can design the UX flow, wireframes, and high-fidelity UI in {{design_tool}}, then prepare the files so your developer can build from them. I’ve worked on similar projects where the challenge was making {{complex_feature_or_user_action}} feel simple for the user.
Here are two relevant samples:
- {{portfolio_link_1}} — {{why_it_matches_this_job}}
- {{portfolio_link_2}} — {{why_it_matches_this_job}}
My process for your project would be:
1. Confirm the main user roles and key actions
2. Map the core flow for {{primary_flow}}
3. Create low-fidelity wireframes so we can adjust structure quickly
4. Design the UI style, components, and responsive states
5. Prepare a clickable prototype and handoff notes
To keep the first version focused, I’d suggest we define the must-have screens first: {{screen_1}}, {{screen_2}}, {{screen_3}}, and {{screen_4}}. If there are extra ideas, we can keep them in a later-phase list instead of adding complexity to the initial build.
Before I give a firm estimate, can you share whether you already have branding, user stories, or rough sketches?Use this when the client is building a new web app, mobile app, SaaS product, marketplace, dashboard, portal, or MVP.
Template 3: Landing page or conversion-focused UI
Hi {{client_name}}, I read that the page is for {{offer_or_product}} and the goal is {{conversion_goal}}, not just a nicer-looking layout. I’d approach this as a messaging and UX structure problem first, then design the final UI around that.
I can help redesign {{page_or_funnel}} so visitors understand the offer faster and have a clearer path to {{primary_action}}. For this type of work, I usually start by checking the headline, section order, CTA placement, trust elements, mobile layout, and any friction around the form or checkout step.
Relevant work:
- {{landing_page_example_link}} — {{what_it_was_for_and_why_relevant}}
- {{figma_or_case_study_link}} — {{specific_design_detail_to_notice}}
For your page, I’d look closely at:
1. Whether the first screen explains {{main_value_proposition}}
2. Whether the page answers the objections a {{target_customer}} would have
3. Whether the CTA is visible and specific enough
4. Whether the mobile version keeps the same clarity as desktop
Deliverables can include a Figma design, mobile and desktop layouts, reusable sections, and developer notes. If you already have copy, I can design around it. If not, I can mark where the page needs stronger messaging.
One question: are you optimizing for {{signup_demo_purchase_lead}}, or is there another main action you care about most?Use this when the job is about a marketing site, homepage, landing page, signup flow, or funnel screen.
What clients hiring a UI UX designer screen for first
Most UI UX clients are not only asking, “Can this person make it look good?” They’re asking, “Will this person understand the user, avoid messy files, and help us get to a buildable design?” Your proposal should answer that in the first few lines.
- Relevant product type. A SaaS dashboard, mobile app, marketplace, landing page, and ecommerce flow need different examples. Link the closest match first.
- Clear thinking. Show that you can simplify a flow, not just decorate a screen.
- Figma quality. Clients care about organized frames, components, variants, auto layout, naming, and handoff notes.
- User focus. Mention the user role, main task, and friction point from the job post.
- Visual fit. If the client wants clean B2B SaaS, don’t lead with a loud entertainment app unless you explain the connection.
- Communication style. UI UX projects involve feedback rounds. Clients want to know how you’ll structure review, not disappear with a big design reveal.
Use an opening line that proves you read the job post
For UI UX jobs, the first line should name the product, screen, user, or problem. Don’t start with “I am an experienced UI UX designer.” The client already knows what role they posted. Start with their situation.
| Weak opener | Stronger opener |
|---|---|
| I am a UI UX designer with many years of experience. | I saw you’re redesigning the onboarding flow for a B2B SaaS tool, and the main issue seems to be users not reaching the setup step. |
| I can make modern designs in Figma. | Your mobile checkout has a clear conversion goal, so I’d start by simplifying the address, payment, and review steps before changing the visual style. |
| Please check my portfolio. | The closest match in my portfolio is this dashboard redesign because it also had dense data tables, filters, and multiple user roles. |
What to customize before sending
- The product category. Say whether it’s a SaaS app, mobile app, ecommerce site, dashboard, landing page, admin portal, marketplace, or internal tool.
- The exact screen or flow. Mention onboarding, checkout, search, booking, profile setup, analytics, navigation, pricing, or whatever the client named.
- The user type. A design for founders, patients, students, drivers, recruiters, or finance teams should not sound generic.
- The deliverables. Match the post: wireframes, high-fidelity UI, prototype, design system, mobile responsive layouts, UX audit, or developer handoff.
- The design tool. If they mention Figma, Sketch, Adobe XD, Framer, Webflow, or another tool, respond to that directly.
- The stage of work. A new MVP proposal should talk about prioritizing screens. A redesign proposal should talk about diagnosing the current friction.
Proof to include, and how to link it
A UI UX proposal needs visual proof, but don’t dump a full portfolio and expect the client to search. Link two or three specific pieces and tell the client what to notice. If your best work is under NDA, describe the type of product, your role, and what you delivered without exposing private details.
- Case study link: best when the project involved research, flow changes, wireframes, and final UI. Add one sentence explaining the problem and your role.
- Figma prototype link: useful when the client wants interaction design. Make sure permissions are viewable before sending.
- Before-and-after images: strong for redesign work. Show what changed in layout, hierarchy, navigation, or form flow.
- Design system sample: useful for larger apps. Show components, states, variants, and naming discipline.
- Developer handoff sample: helpful when the client has engineers ready. Show annotations, specs, responsive states, and component notes.
- Short Loom-style walkthrough: optional, but useful if the design problem is complex. Keep it focused on the relevant flow.
What if you’re a new UI UX designer on Upwork?
New freelancer
Lead with one strong self-initiated case study if you don’t have client work yet. Make it specific: user problem, assumptions, flow, wireframes, final UI, and what you would test next. Avoid pretending it was a paid client project.
Experienced designer
Lead with the closest commercial project. If the post is for SaaS onboarding, your SaaS onboarding case study should come before your most beautiful mobile concept.
Agency
Explain who will do the UX work, who will handle UI, who will manage feedback, and how handoff works. Clients may worry that an agency will add layers without improving the design.
Mistakes that get UI UX proposals skipped
- Opening with a biography. The client wants to know if you understand their product. Put that first.
- Sending a generic portfolio link only. A broad portfolio is fine, but point to the two examples that match the job.
- Talking only about visuals. UI matters, but UX clients also care about flow, hierarchy, accessibility, responsive behavior, and handoff.
- Ignoring the platform. A mobile app, web dashboard, and marketing page have different constraints. Name the platform and design around it.
- Promising outcomes you can’t control. Don’t guarantee conversions, funding, downloads, or sales from a design alone.
- Skipping questions. Good questions show judgment. Ask about users, goals, constraints, analytics, brand assets, and development plans.
- Not checking links. Broken Figma or portfolio permissions are an easy reason to move on.
- Overloading the proposal. A client does not need your full design philosophy. Keep it tied to their flow, users, and deliverables.
A simple structure for your UI UX proposal
- 1
1. Prove you read the post
Name the product, screen, user, flow, or problem. This should happen in the first sentence.
- 2
2. Give the likely design approach
Explain whether you’d start with an audit, user flow, wireframes, prototype, design system, or high-fidelity UI.
- 3
3. Link matching proof
Include two or three relevant examples. Tell the client why each one matters.
- 4
4. Clarify deliverables
Match the post’s language: Figma file, prototype, mobile screens, desktop screens, responsive states, components, or handoff notes.
- 5
5. Ask one or two useful questions
Ask about users, goals, existing data, brand assets, technical limits, or priority screens. Don’t ask questions already answered in the post.
Screening questions for UI UX jobs
Some Upwork posts include screening questions. Treat them like part of the proposal, not an afterthought. If the client asks for your process, don’t give a vague “research, design, iterate” answer. Tie your process to their project type.
For {{project_type}}, I’d start by clarifying the main user role and the key action they need to complete: {{primary_action}}. Then I’d map the flow, create quick wireframes, and review them with you before spending time on polished UI. Once the structure is approved, I’d design the high-fidelity screens in {{design_tool}}, create responsive states for {{desktop_mobile_or_both}}, and prepare handoff notes for development. The goal is to make {{specific_flow_or_screen}} easier to understand and build, not just make it look more modern.Use this when the client asks about your UI UX process, how you work, or how you would approach the project.
How to choose which UI UX jobs to answer
Don’t spend the same effort on every post. A good UI UX job usually has a clear product, target user, deliverables, and decision maker. Be careful with posts that say only “make it modern” with no product context, no examples, and no idea of the screens needed. You can still apply, but your proposal should ask clarifying questions before promising scope.
BidGrow can help you sort UI UX posts faster by scoring jobs with readable rules like payment verification, client spend, hire rate, rating, activity, competition, Connects cost, and rate fit. It can also draft proposals from your own templates, but you review and send them yourself. It never submits proposals for you, never logs in to Upwork as you, and isn’t affiliated with or endorsed by Upwork.
Questions
What should a UI UX designer proposal on Upwork include?
Include a first line that proves you read the post, a short design approach, two or three relevant proof links, clear deliverables, and one or two smart questions about users, goals, or constraints.
How many portfolio links should I send?
Send two or three highly relevant links. A focused SaaS dashboard case study is better than ten unrelated visuals if the client is hiring for a SaaS dashboard.
Should I mention Figma in the proposal?
Yes, if the client asked for Figma or if your deliverable will be a Figma file, prototype, component set, or developer handoff. Also mention how you keep files organized.
Can I use the same UI UX proposal template for every job?
Use the same structure, not the same wording. Change the opening line, product type, flow, proof links, deliverables, and questions for each job post.