Freelance UI/UX kickoffs fail in predictable ways: no decision owner, brand files in someone’s downloads folder, success defined as “make it nicer,” and engineering constraints discovered at handoff. You can prevent most of that in one structured call plus a short written questionnaire.
This is a practical agenda for a 45–60 minute kickoff — not a workshop theater production.
Before the call (30 minutes of setup)
- SOW signed, deposit in — or you are still selling.
- Send the onboarding questionnaire 24–48 hours ahead. You will not get perfect answers; you need enough to interrogate live.
- Create Notion rows: Client (Active), Project (Phase = Kickoff), link the Deal.
- Prepare a Figma file (or confirm their library) with cover page: goals, non-goals, links.
- Confirm attendees: decision owner required. Extra stakeholders optional for listening.
If the decision owner cannot attend, reschedule. Critique hell starts at kickoff, not at round two.
Kickoff agenda (45 minutes)
| Time | Block | Outcome |
|---|---|---|
| 0–5 | Framing | Restate SOW scope and non-goals; confirm decide-by for Phase 1 |
| 5–15 | Users & success | Agree primary user, JTBD, success signal for this engagement |
| 15–25 | Constraints | Brand, a11y target, breakpoints, stack, expensive patterns to avoid |
| 25–35 | Process | Critique format, rounds remaining, feedback SLA, tools |
| 35–40 | Access & assets | Figma/Drive/staging; owner for missing items + due date |
| 40–45 | Immediate next steps | Your actions, their actions, next meeting date |
Keep a visible timer. Kickoffs expand to fill any vacuum.
Block detail: framing
Read the in-scope list aloud. Ask: “What wants to sneak in that we should park?” Capture a parking lot in the meeting note. Parking lot items are not promises.
Block detail: users & success
Force one primary user for Phase 1. Secondary users can inform edge cases later. For success, prefer something observable: “User can complete X without support,” or “Eng can implement Y without Slack archaeology.” Avoid owning revenue targets you cannot control.
Block detail: constraints
Ask engineering one blunt question: “Which UI patterns are disproportionately expensive?” If nobody from eng is present, assign the client to return answers by a dated action.
Confirm accessibility expectations. “Should be accessible” is not a target. WCAG 2.2 AA (or “best effort polish pass”) is.
Block detail: process
Agree:
- Feedback lives in Figma comments or a single doc — not five WhatsApp threads
- One consolidator
- Round definition matches the SOW
- Response SLA (e.g. 3 business days)
Block detail: access
Do not leave with “we’ll send logos later” as a vibe. Leave with names and dates. Missing assets = timeline slip language already in your SOW; remind them calmly.
The questionnaire: what must be written
Live talk invents consensus that evaporates. Written answers you can paste into Notion:
- In-scope flows/screens
- Out-of-scope list
- Decision owner
- Brand/design system links
- Stack and eng contact
- Billing quirks (PO numbers)
- Portfolio confidentiality
Your designer-only section (not sent to client): Fit score, scope sniff, which AI prompts to run on the notes.
Meeting notes template (fill live)
## Decisions
-
## Actions — me
- [ ]
## Actions — client
- [ ] Owner · due date
## Artifacts
- Figma:
- Staging:
- Brand:
## Risks
-
Create the Meeting Notes database row before you hang up. Link Client + Project. Set Next Touch.
What “onboarded” means (exit criteria)
You may call kickoff successful only when:
- [ ] Scope and non-goals restated without disagreement
- [ ] Decision owner named
- [ ] Success signal for Phase 1 agreed
- [ ] Breakpoints + a11y expectation set
- [ ] Critique process + SLA agreed
- [ ] Access list assigned with dates
- [ ] Next working session booked
- [ ] Project Phase can move to Research or Flows
If half the boxes fail, you did not onboard — you socialized.
Handling awkward moments on the call
“We’ll all comment in Figma.”
Reply: “Everyone can comment; one person decides. Otherwise rounds never close.”
“We need it to feel premium.”
Translate: density, typography, imagery, motion — pick two levers for Phase 1.
“Can you also look at the brand?”
Park it. Brand identity is a different product. Offer a separate proposal if you sell that.
“Engineering will figure it out.”
Schedule a 20-minute constraints call this week. Handoff is too late for platform surprises.
First 72 hours after kickoff
- Send a short summary email: decisions, actions, dates.
- Chase assets with a single checklist — not drip pings.
- Run discovery synthesis prompts on your notes (JTBD, risks, opportunity brief).
- Update Project: Open Blockers, Risk color if assets are late.
- Start the smallest flow that validates direction — do not boil the design system ocean on day one.
Why one call is enough (and when it isn’t)
One call is enough for a contained freelance Phase 1: defined flows, existing product or clear marketing scope, adult decision owner.
Book a second call when: regulated domains need compliance guests, multi-brand politics, or research interviews must be planned live. Still keep call one about operating agreements; do not merge kickoff with a three-hour ideation workshop.
Tie it to your client OS
Onboarding is where CRM becomes delivery:
- Client Status → Active
- Pipeline → Won (if not already)
- Project → Kickoff → next phase
- Assets rows for contracts and brand files
- Invoice checklist for deposit (should already be Paid)
Designers who skip this scaffolding redo kickoff tribal knowledge every engagement. Designers who run the rail spend the call on product truth — which is the actual job.
For a reusable questionnaire, SOW, and Notion structure aimed at UI/UX freelancers, use your own docs or a kit like Clientrail. The method matters more than the brand name: one call, written boundaries, dated actions, linked records.
Want the full Client OS?
Clientrail packs Notion structure, 50 prompts, and deal templates for freelance UI/UX — no fake testimonials, no income claims.