Productivity - Setup Guide

How to set up Loom

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.

Read these before you start

• The free tier was cut from a more generous historical limit down to 25 total videos capped at 5 minutes each after Loom's acquisition by Atlassian — a team evaluating Loom based on older reviews describing a better free tier will be disappointed by the current, more restrictive version (Source: Supademo, https://supademo.com/blog/loom-pricing/)
• Roughly 40% of negative Trustpilot reviews for Loom specifically cite billing issues — verify the account's actual plan and renewal terms carefully, this is a documented pattern worth watching for, not an isolated complaint (Source: Screenify Studio "Why Teams Are Leaving Loom" analysis, https://www.screenify.studio/blog/2026-04-29-why-people-leave-loom-2026)
• Lag, audio sync issues, and failed uploads appear consistently across review platforms through 2025 into 2026 — test recording and upload reliability on the client's actual network/hardware before rolling it out team-wide, don't assume flawless performance
• No affiliate/referral program is currently active — this is a value recommendation for Otto, not a revenue-generating one
• Loom Creator Lite (an older lower-cost tier some users were on) has been discontinued for affected teams — anyone previously on that plan needs to migrate to a current tier

The 7-step setup

1. 1

   Create your Loom account

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

   Open Loom 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 Loom pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Loom into the rest of your stack. The integrations that most people set up first: Slack, Notion, Gmail, GitHub, Jira.. 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 Loom deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Loom - 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 Loom when: the client needs async video communication — client updates, tutorials, feedback recordings, or replacing unnecessary status-update meetings — especially for remote teams, consultants, and agencies. Do NOT position it as a live video-call replacement, that's Zoom or Google Meet's job. Test actual recording/upload reliability on the client's setup before a team-wide rollout given the documented reliability complaints. This is a value recommendation, not a revenue one for Otto...