UX/Product Designer

• Figma
• Framer
• Sketch

• Bonsai
• Notion
• HoneyBook

• Maze
• Loom
• Dovetail

You are a freelance UX/product designer reaching out to a SaaS startup founder. Write a cold outreach email that:
- Opens with a specific observation about their product (I'll fill in [PRODUCT_NAME] and [SPECIFIC_OBSERVATION])
- Identifies one concrete UX problem visible from their public-facing product or app store reviews
- Proposes a specific, low-risk first engagement (e.g., a free 30-minute UX audit call or a paid 3-day sprint)
- Keeps the entire email under 150 words
- Ends with a single, frictionless CTA (a Calendly link or a yes/no question)
- Sounds like a real human, not a marketing template

Product name: [PRODUCT_NAME]
Specific observation: [SPECIFIC_OBSERVATION]
My specialty: [YOUR_SPECIALTY, e.g., onboarding flows, dashboard design, mobile UX]
My portfolio link: [PORTFOLIO_URL]

Do not use phrases like 'I hope this email finds you well' or 'I wanted to reach out.' Be direct and specific.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

Act as a senior UX designer conducting a professional audit. I will describe a SaaS product's onboarding flow, and you will produce a structured UX audit report.

Product type: [e.g., project management SaaS, B2B invoicing tool]
Onboarding steps I observed: [paste the steps the user goes through, e.g., signup → email verify → profile setup → dashboard]
Key friction points I noticed: [list what felt slow, confusing, or unnecessary]
Target user: [e.g., non-technical small business owners]

Produce a report with these sections:
1. Executive Summary (3 sentences, business impact framing — not design jargon)
2. Friction Point Analysis (each issue: what it is, why it hurts conversion, severity rating Low/Medium/High)
3. Quick Wins (fixes achievable in under 1 week)
4. Strategic Recommendations (bigger redesign opportunities)
5. Suggested Success Metrics (what to measure after fixes)

Use plain English. Avoid jargon like 'affordance' or 'gestalt.' The founder reading this is not a designer.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

I am building a design system for a [COMPANY_TYPE, e.g., B2B SaaS startup] in Figma. Help me create a professional, scalable naming convention and token structure.

Brand colors provided: [list hex codes or describe the palette, e.g., primary blue #2563EB, neutral grays, one accent color]
Product type: [web app / mobile app / both]
Team size: [just me as the designer / me + 1 developer / larger team]

Deliver:
1. Color token naming structure (primitive tokens → semantic tokens → component tokens)
2. Typography scale with names (not just sizes — actual token names like 'text-body-md')
3. Spacing scale naming
4. Component naming convention rules (e.g., how to name variants, states, sizes)
5. A short style guide (one paragraph) I can paste into Figma's team library description so developers understand the system

Follow the approach used by Radix UI and Tailwind CSS for token naming. Keep it simple enough for a 2-person startup to actually maintain.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

Write a professional freelance project proposal for a UX/product design engagement. Use the details below to produce a complete scope of work document.

Client type: [e.g., early-stage SaaS startup, 8-person team]
Project goal: [e.g., redesign the user onboarding flow to reduce drop-off]
Timeline requested by client: [e.g., 6 weeks]
My hourly rate: [$X] OR My preferred project rate: [$X]
Deliverables I plan to provide: [e.g., user research summary, wireframes, high-fidelity Figma mockups, prototype, design handoff doc]

Produce:
1. Project Overview (2–3 sentences summarizing the problem and goal)
2. Scope of Work (bulleted list of exactly what is included)
3. What is NOT included (out-of-scope items to prevent scope creep)
4. Timeline with phases and milestone dates
5. Investment (pricing, payment schedule — suggest 50% upfront, 50% on delivery)
6. Revision Policy (suggest 2 rounds of revisions per phase)
7. A short 'Why This Approach' paragraph that builds confidence without overselling

Tone: professional but warm. Not corporate. Not salesy.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

Always send a written proposal with an explicit 'Out of Scope' section before starting any work. Use a simple contract (Hello Sign or Bonsai) with a change order clause. Charge for revisions beyond two rounds per phase.

Frame every portfolio case study around a business problem and a measurable outcome. Structure each case study as: Problem → Research → Decision → Design → Result. Even if you can't share metrics, describe the qualitative outcome. If you have no client work yet, do a paid or free audit for a real product and document the process.

Set a floor rate before you talk to any client. Quote project rates rather than hourly when possible — it decouples your income from your hours.

Build a lightweight research phase into every engagement, even if it's just 3 user interviews and a competitive analysis. Make it a non-negotiable line item in your proposal. Frame it to clients as 'this phase saves us 3 weeks of wrong-direction design work.'

Include a handoff document with every project: annotated screens explaining interactions, a component inventory, spacing and color specs, and a short Loom video walkthrough. Use Figma's Dev Mode or a tool like Zeplin to make specs developer-friendly. Budget 4–6 hours for handoff in every project estimate.