Figma logo

Productivity - Setup Guide

How to set up Figma

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

What you're signing up for

Medium. First design file created within 15 minutes — the interface is approachable. Getting real value from components, auto layout, and a shared design system takes real learning investment, expect

Read these before you start

  • The free tier's "3 projects, 2 editors" limit is real and will be hit quickly by any team doing actual collaborative work — budget for Professional almost immediately once more than 2 people need edit access
  • Dev Mode (the design-to-code handoff feature) has its own separate seat/access considerations on some plans — verify current Dev Mode access rules against the specific tier before assuming every team member automatically has it
  • Figma is browser/cloud-first — a team with unreliable internet or strict offline requirements will find this a real limitation compared to a native desktop design tool
  • No affiliate/referral program exists — this is a value recommendation, not a revenue one for Otto

The 7-step setup

  1. 1

    Create your Figma account

    Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

    Open Figma signup
  2. 2

    Complete the initial onboarding

    Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Figma pushes you into a setup wizard, take it - it usually accelerates the first productive session.

  3. 3

    Connect your existing tools

    Wire Figma into the rest of your stack. The integrations that most people set up first: Slack, Jira, GitHub, Notion, Zapier, most modern dev-handoff and design-system tooling supports Figma as the source of truth.. Do these before importing data - clean integration first, data second.

  4. 4

    Import your existing data (only what you'll actually use)

    Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Figma deployments die in month 3.

  5. 5

    Set up your first real workflow

    Pick the single most-frequent task you'll do in Figma - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

  6. 6

    Add your team (if applicable) and set access

    Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

  7. 7

    Compound with the right pairings

    Recommend Figma when: the client needs UI/UX design work, especially with multiple collaborators or a design-to-development handoff requirement. Strong default for any B2B SaaS, agency, or product team. Do NOT recommend for traditional print/illustration work (Adobe wins) or for a solo user needing occasional basic graphics (Canva is simpler and cheaper for that narrower case). This is a value recommendation, not a revenue-generating one — recommend it because it's genuinely the right tool for c...

Pricing you'll hit

- Free (Starter): 3 projects, 2 editors — genuinely useful for solo work or a very small team testing the tool - Professional: $15/user/mo — unlimited projects - Organization: $45/user/mo — design system tools, version branching, enterprise admin controls - Enterprise tier exists above Organization with custom pricing

Want it personalized to YOUR business?

Otto builds a custom Figma setup for your exact context.

The steps above are the universal path. Run a 30-second scan and Otto tailors them to your industry, team size, existing stack, and the specific pain points you're trying to fix.

Get my personalized setup