How I work.
Six phases, ~6–8 weeks end-to-end for a full project. Async-first with weekly live syncs and milestone Looms. I work from Karachi (UTC+5), so I overlap with EU mornings and US-East evenings.
- 01Week 0
Discovery
Free 30-min call to align on scope, audience, and constraints. I ask the questions that filter projects I'm wrong for and clarify what success looks like at the end. Within 48 hours you get a fixed-scope proposal with timeline and price.
What you'll see- Discovery call (recorded for your reference)
- Fixed-scope proposal within 48h
- Clear timeline + price (no hourly surprises)
- Mutual NDA if needed
What I'll need from you- Product brief or pitch deck
- Existing analytics / research (if any)
- Names of the 2–3 stakeholders I'll work with
- 02Week 1
Research
Discovery interviews (4–8 users), heuristic eval of any existing product, competitive teardown, and synthesis. The goal isn't a 40-page deck — it's the shortest possible doc that captures what we now know that we didn't know before.
What you'll see- 4–8 user interview recordings
- Heuristic eval of existing product (if applicable)
- Competitive teardown of 3–5 competitors
- Themed synthesis doc + recommended next steps
What I'll need from you- Access to your customer list (or budget for UserInterviews.com)
- Read-only Figma / Notion / Linear access
- A quick async intro to your engineering lead
- 03Weeks 2–3
Wireframes
Mid-fidelity wireframes for every flow. Walked through in a live session with you + engineering. Tight iteration loop — we'll do 2–3 rounds of revisions before locking flows. This is where I want pushback.
What you'll see- Wireframes for every screen + state
- Click-through prototype (Figma)
- Live walkthrough call (recorded)
- Async Figma comments throughout the week
What I'll need from you- Founder + PM availability for 1 live session
- Engineering input on technical constraints
- Decisions on content / data model where required
- 04Weeks 3–5
Visual design
Hi-fi screens in lockstep with a growing design system. Components built with variants + states. Edge cases — empty, loading, error, offline — designed alongside the happy path, not after. Weekly Loom milestone.
What you'll see- Hi-fi screens for every flow + state
- Living design system (tokens, components)
- Weekly milestone Loom walkthrough
- Variant explorations on critical screens
What I'll need from you- Brand guidelines / logo assets (if existing brand)
- Async review within 48h of each milestone
- Final copy decisions before week 4
- 05Weeks 5–6
Prototype & test
Interactive Figma prototype + 5-person moderated usability test. I recruit, moderate, and synthesize — you watch a 20-min highlight reel. Fixes get integrated before handoff so engineering doesn't inherit known-broken flows.
What you'll see- Stakeholder-ready interactive prototype
- Recruitment + scheduling for 5 testers
- Recorded test sessions (full + 20-min highlight)
- Themed findings + design fixes integrated
What I'll need from you- Approval to share prototype with testers (anon NDA available)
- Decisions on which findings to act on vs. defer
- 06Weeks 6–8
Handoff
Dev specs, animation specs, asset exports, and a 2-week Q&A office hours window so your engineering team isn't translating Figma alone. I'm in your team's Slack for the first 2 sprints of build to answer questions in real time.
What you'll see- Spec doc (tokens, type, spacing, motion)
- Animation specs with named easing curves
- Asset exports (SVG / PNG, plus motion specs as needed)
- 2-week Q&A office hours window
What I'll need from you- Add me to your engineering Slack for 2 weeks
- 15-min sync at handoff to walk through specs
- Reasonable response time on edge-case questions
How we'll talk.
Weekly sync
30-min live call every week. Always on calendar — never gets cancelled.
Milestone Loom
5-min recorded walkthrough at every milestone. Async, watch when you can.
Figma comments
All design conversation happens in Figma where the context lives.
Slack < 24h
I'm in your Slack during active engagements. Reply within 24h, faster on weekdays.
Tools I live in.
Figma + FigJam
Design, components, library, prototypes, comments, async review.
Loom
Weekly milestone walkthroughs + decision-rationale recordings.
Slack
Daily-availability throughout active engagements.
WhatsApp
Quick check-ins, voice-notes, urgent decisions across timezones.
Google Drive
Brief docs, research files, asset handoff, async stakeholder review.
Trello
Project board for milestones, decisions, and active threads.
Notion
My own decision log + reference library across projects.
What makes the difference.
I document every design decision in writing
Most designers ship a Figma file and trust everyone will remember why. I write a short rationale per major decision — in Figma comments and a project decision-log — so when a new PM joins in month 6, they can read why onboarding has 3 steps instead of 7 instead of relitigating it.
I sit in on user-test sessions live
Most designers send a research firm and get a report. I moderate the 5-person test myself — you get my real-time interpretations alongside the raw findings.
Loom for every milestone
You get a 5-min recorded walkthrough at every milestone explaining what changed, why, and what trade-offs I made. No more "is this what you meant?" calls.
I push back on scope creep
Revisions are tier-scoped — 1 round on Design Sprints, 3 rounds on Full Projects, unlimited on monthly Retainers within reserved hours. Anything bigger goes through a short change-order doc. I'd rather pause and reprice than ship resentment — every founder I've worked with has appreciated this.