Tools · UX & Product Design
The UX / Product Consultant's Stack
A lean, three-tool workflow for solo UX and product consultants: research and prototype in Figma and FigJam, report async with Loom.
Affiliate disclosure: SoloClientStack may earn a commission on links on this page. Full disclosure →
For most solo UX and product consultants, the stack is smaller than the industry makes it look: Figma and FigJam for research, synthesis, and prototyping, Loom for async client updates, and one lightweight notes layer such as Notion for decisions and client ops. That is usually three subscriptions, not eight. Add AI features inside Figma or Loom only where they genuinely save time, and always review the output before a client sees it — treat AI drafts as a starting point, not a deliverable.
Everything past that core is optional. This article walks through the workflow decision, the pricing math, and the setup steps so you can standardize your practice in a week instead of stitching together a new tool every time a client asks for something you have not built yet.
Choose the Figma + FigJam + Loom core if…
You run workshops or interviews, need a working prototype (not just slides), review designs live with stakeholders, or send weekly async updates instead of status calls. This covers most hands-on UX and product consulting engagements.
Choose a lighter stack if…
You mostly deliver strategy memos, slide-based audits, or one-off advisory sessions with no working prototype. A free-tier design tool plus a basic video or doc tool may be enough — skip the paid seats until a project actually needs them.
Who this stack is for
This is written for the independent UX consultant, product strategy advisor, or fractional design lead who works with 1 to 10 clients a year on an irregular project cadence. You are not running a studio with a project manager and a dedicated ops person — you are the researcher, the designer, and the account manager. The friction usually shows up at the boundary between research and delivery: interviews and workshop notes pile up in one place, prototypes live in another, and client updates get improvised in whatever tool happens to be open. The goal here is one connected system, not a bigger toolbox.
The three jobs this stack actually has to do
Strip away the feature lists and a UX or product consulting engagement only needs a stack to do three things well: capture and synthesize research, turn decisions into a handoff-ready design artifact, and report progress without adding meetings. Everything else is optional infrastructure.
| Job to be done | Best tool | Why it fits | Tradeoff |
|---|---|---|---|
| Workshop facilitation and synthesis | FigJam | Included with Figma seats; built for brainstorming, affinity mapping, retros, and journey maps | AI board tools need a paid seat and outputs still need your judgment |
| Prototype and design handoff | Figma (Professional or above) | Live file, inspect mode, and dev-ready handoff in one place | Seat types and pricing tiers add complexity as you scale |
| Async client reporting | Loom | Recorded walkthroughs plus AI summaries, chapters, and recap emails on paid plans | AI tier costs more per seat; still proofread before sending |
| Durable decision log | Notion or a similar notes tool | Keeps client decisions, action items, and research findings out of chat threads | One more login if your client work does not need long-term documentation |
Figma: the core workspace for prototyping and handoff
Primary workspace
Best for: consultants who deliver a working prototype, annotated flows, or a design file a client's dev team will actually build from.
Not best for: consultants who only deliver slide decks, written audits, or strategy memos with no interactive artifact.
Key strengths: a single source-of-truth file, comment threads tied to specific frames, an inspect and dev-handoff view, and FigJam bundled in on every seat for the messier upstream work.
Limitations: seat types (viewer, collaborator, full, dev) and plan tiers add real complexity once you are billing more than one or two client seats, and AI credits are metered by plan.
Pricing note: Figma's public pricing page lists a free Starter tier and a Professional full seat around $16 per editor per month, with higher tiers for larger teams and governance needs — verify current terms and seat definitions before you commit a client budget. See Figma's current pricing page.
If you are deciding between Figma and a lighter tool for a specific engagement, our comparison hub is the place to check before you sign up.
FigJam: synthesis, mapping, and workshop facilitation
Research layer
Best for: affinity mapping, journey maps, retros, and any workshop where the input is messy interview notes or sticky-note chaos.
Not best for: final design delivery on its own — it is the thinking space before the design file, not a replacement for it.
Key strengths: included with every Figma seat, templates for common consulting workshops, and AI-assisted board tools for summarizing sticky notes or drafting a first-pass journey map.
Limitations: AI tools inside FigJam require a paid Full, Dev, or Collab seat, and Figma's own help documentation is explicit that AI outputs can be inaccurate and should not replace your own research or expert judgment.
Pricing note: FigJam itself does not carry a separate price tag — it rides on your Figma plan, so the cost decision is really about which Figma seat you need. Verify current seat requirements on Figma's pricing page before promising a client an AI-assisted workshop.
Loom: client reporting without another status call
Reporting layer
Best for: async walkthroughs of a prototype, weekly progress updates, and explaining a design decision once instead of on three separate calls.
Not best for: deep research or live collaborative editing — it is a communication layer, not a workspace.
Key strengths: unlimited recordings on paid plans, AI-generated titles, summaries, chapters, and recap emails, plus integrations with tools like Slack and Notion that make updates easy to file and find later.
Limitations: the AI-inclusive tier costs more per seat than the base plan, and purchasing paths have shifted since Loom's acquisition — confirm what is currently bundled before you rely on a specific AI feature.
Pricing note: Loom's pricing page has listed a Business + AI tier around $24 per user per month, with a free starter tier and a 14-day trial on paid plans. Verify current terms before billing a client for it. See Loom's current pricing page.
Use Loom to reduce status meetings and make your updates skimmable — a client who can watch a 3-minute recap rarely needs a 30-minute call.
Lean vs. standard vs. expanded: matching the stack to your workload
Not every engagement needs the same stack tier. This is a rough operator's read on cost and complexity, not a fixed rule — verify current pricing before you commit.
| Stack tier | Tools included | Rough monthly cost basis | Best for | Main risk |
|---|---|---|---|---|
| Lean | Figma Starter (free), FigJam (included), Loom free tier | $0/month | One-off audits, advisory-only engagements, early practice validation | Limited collaboration and no AI features when a client expects more polish |
| Standard | Figma Professional (full seat), FigJam AI on that seat, Loom paid plan | Roughly $40 to $70/month depending on seats and AI tier | An ongoing solo practice with recurring clients and regular reporting | Seat and plan choices need occasional review as pricing changes |
| Expanded | Figma Organization-tier features, Loom Business + AI, Notion team workspace | $100+/month | Multi-stakeholder engagements with enterprise governance needs | Overbuilt and expensive for most solo practices — usually not worth it below a certain client volume |
Pricing and seat-fit notes
Figma and Loom both change plans and included features periodically, so treat the numbers below as a snapshot to verify, not a locked-in quote.
| Tool | Starting price | Key included features | Caveat |
|---|---|---|---|
| Figma | Free Starter tier; Professional full seat around $16/editor/month | Design files, prototyping, FigJam included, AI credits on paid seats | Seat type (viewer, collaborator, full, dev) changes what a client can actually do — check before inviting them in |
| FigJam | Included with any Figma plan | Whiteboarding, templates, AI board tools on paid seats | AI features require a Full, Dev, or Collab seat and outputs need review |
| Loom | Free tier available; Business + AI around $24/user/month | Unlimited recordings, AI summaries, chapters, recap emails, integrations | Purchasing path has shifted post-acquisition — confirm what is bundled at signup |
Pricing and included features for both tools change frequently. Confirm current terms directly on the vendor pricing pages before you build a client quote around them.
How to implement this in week one
You do not need a big migration project. Most solo consultants can stand this stack up in a few focused hours.
- Day 1: Set up your Figma account and confirm which seat type you actually need for the current engagement — do not default to the most expensive tier.
- Day 2: Build one FigJam board template for research synthesis (affinity map, journey map, or workshop retro) that you can duplicate for every new client instead of starting from a blank canvas.
- Day 3: Record one short Loom walkthrough of your process or a past deliverable, so you have a template tone and length before the first live client update.
- Day 4: Decide where decisions and action items will live permanently — Notion or a similar notes tool — and stop letting them get buried in chat or email threads.
- Day 5: Run one real client task through the full loop — FigJam for synthesis, Figma for the resulting artifact, Loom for the update — and time it. That timing is your baseline for how long "client-ready" actually takes in your practice.
| Stage | Task | Tool | Output | Handoff artifact |
|---|---|---|---|---|
| Research | Interviews, workshops, sticky-note synthesis | FigJam | Affinity map or journey map | Summary board (not raw notes) shared selectively |
| Design | Turn decisions into flows and screens | Figma | Working prototype | Shareable link with inspect access for developers |
| Reporting | Explain decisions and progress async | Loom | Recorded walkthrough | Recap email or summary sent to the client |
| Documentation | Log decisions and action items | Notion or similar | Decision log | Durable record the client can reference after the engagement |
What to skip if you are solo
Skip enterprise seat tiers, dedicated project-management software, and heavier AI agent tools until a specific, recurring problem justifies them. Most solo UX or product consultants do not need Organization-level governance features, a separate whiteboard tool alongside FigJam, or a second video tool alongside Loom. Adding tools for hypothetical future clients is the most common way solo practices end up paying for software they barely open.
If your work moves into regulated industries, accessibility-compliance documentation, or enterprise governance review, that is a case for bringing in specialized help or a formal audit process — not for adding more general-purpose software to this stack.
Common mistakes
The most common failure is not picking the wrong tool — it is running too many sources of truth at once. A few patterns show up repeatedly in solo consulting practices:
- Overbuying enterprise seats for a one-person practice because the sales page implies you need them.
- Sending raw AI-generated FigJam summaries or Loom transcripts to a client without reviewing them first.
- Mixing internal synthesis boards with final client deliverables, so the client sees your messy thinking instead of your conclusion.
- Recreating the same FigJam board structure from scratch every engagement instead of templating it once.
- Skipping the decision log and relying on memory or scattered chat threads for what was actually agreed.
How this fits the Consultant OS Delivery layer
In the Solo Operator OS framework, this stack sits entirely in the Delivery layer: research, handoff, and reporting are meant to feel like one connected system, not three unrelated subscriptions. FigJam captures the messy input, Figma turns it into a client-ready artifact, and Loom carries the update to the client without another meeting. If you want to see how this layer connects to intake, contracts, and billing for a full solo consulting practice, the Consultant Stack and the Consultant Operating System guide walk through the rest of the system.
Start from the tools hub if you want to compare this stack against other niche setups, or check the getting-started guide if you are building your practice stack from zero.
FAQ
What is the best UX consultant stack for a solo operator?
For most solo UX or product consultants, the default is Figma plus FigJam for research, synthesis, and prototyping, and Loom for async client updates. Add a notes tool such as Notion only if you need a durable decision log beyond what lives in the design file.
Do I need both Figma and FigJam?
If your work includes workshops, interviews, or research synthesis, yes — FigJam is included with Figma seats and complements the design file rather than duplicating it.
Is FigJam good for user research?
It is good for mapping, synthesizing, and presenting research — affinity maps, journey maps, and workshop outputs — but it is not a substitute for actually doing the interviews or usability testing.
Is Figma enough for prototyping and handoff on its own?
Often yes for solo consultants delivering a working prototype or annotated design recommendation. Confirm the seat type gives you the inspect and handoff features your project needs before you promise a developer a dev-ready file.
Is Loom worth paying for as a consultant?
It tends to be worth it if you regularly explain decisions asynchronously or want to reduce live status calls. If you rarely record updates, the free tier may cover you without upgrading.
What should a consultant use for client reporting?
A short Loom recording for the walkthrough, paired with a written summary or decision log in a doc or notes tool, covers most client-reporting needs without adding meetings.
Are AI features worth it for UX consulting?
Only where they save real time without weakening client trust. Treat AI-generated summaries or boards as a first draft to review, not a finished deliverable — vendor documentation itself flags that AI outputs can be inaccurate.
What is the cheapest usable stack?
A free-tier design tool plus FigJam and a free or low-cost video tool can be enough for advisory-only or one-off work. Verify current free-tier limits before relying on them for a paying client.
Should I use Notion, Figma, or both?
Use Figma for the working design artifact and prototype, and a notes tool like Notion for durable decisions, action items, and client operations that need to outlive the design file.
How do I keep clients out of tool sprawl?
Share only the final artifacts — the finished FigJam summary board, the Figma prototype link, the Loom recap — not every working file or draft. That keeps the client-facing surface small even if your internal process uses more tools.
Get the Solo Consultant OS Blueprint
Map your acquisition, onboarding, delivery, and automation stack. Free for subscribers.
- CRM setup and pipeline configuration
- Client onboarding automation walkthrough
- Proposal system with AI prompts
- Make scenario templates
Free for subscribers
No spam. Unsubscribe any time.
Related resources