Unwrapped↗

Legacy SaaS dossier · loom

Loom

Loom

CategoryAsync video / screen recordingLoom Business, 120 creatorsSite ↗

Screen capture, an upload bucket and a share link with view counts, sold per creator with a transcript add-on you can run yourself.

01 · Data

Data the SaaS sits on

Video storage
Video storageAPI
Browser capture
Browser capturePublic
SSO
SSOYours

Internal Build Score

0.77

Feasibility of a useful internal substitute for the actually-used 20% of this SaaS, built with Claude and your own data layer.

IBS = 0.25·U + 0.25·C + 0.20·D + 0.15·I + 0.15·Mthis record · 77%
  • U

    User adoption gap

    weight 0.250.65

    How much licensed surface area sits idle.

  • C

    Core simplicity

    weight 0.250.80

    How small the actually-used 20% is when re-implemented honestly.

  • D

    Data portability

    weight 0.200.80

    How clean the exit is, exports, formats, audit lock.

  • I

    Integration burden (inverse)

    weight 0.150.85

    How few external systems must keep working through the SaaS.

  • M

    Moat erosion

    weight 0.150.82

    How much the original differentiator has been commoditised by LLMs + cheap infra.

Editorial heuristic. Not investment advice, not a procurement recommendation.

03 · Feature usage

Commonly used vs. rarely touched

Commonly used

05

  • Record screen and camera
  • Upload and transcode
  • Share link with permissions
  • View and engagement tracking
  • Transcript and comments

Rarely touched

06

  • Per-creator pricing
  • AI titles and summaries upsell
  • Workspace 'HQ' hierarchy
  • Custom branding and CTAs
  • SCORM and gated embeds
  • Stock backgrounds and effects
Build it yourself→

Internal build

Build it yourself

01 · Stack & flow

MediaRecorder
MediaRecorder
Mux / S3
Mux / S3
Claude API
Claude API
Next.js viewer
Next.js viewer

Internal build map

Data in

Recording
Transcript

Agent layer

Summariser

Logic

upload + transcode
permissioned link
chapter + actions
view log

Outputs

Share page
Chapters + actions
Build time
6 weeks
Run cost
$2/seat·mo
vs. SaaS
$18K / yr

Build outline

  1. Record with the browser MediaRecorder API
  2. Upload to Mux / S3 for transcode
  3. Share page with permissioned link + view log
  4. Whisper transcript on upload
  5. Claude turns transcript into chapters + actions

02 · Build it

Paste into Cursor or Claude Code in an empty repo. It scaffolds the working core, with the AI step embedded.

Build prompt · Loom

// Build: internal screen recording (Loom replacement) # Paste into Cursor or Claude Code in an empty repo. Build an internal video tool covering the part of Loom we use: record screen + cam, upload, a permissioned share link with view tracking, and an auto transcript + summary. Ship a working v1. Stack: Next.js + MediaRecorder API + Mux (or S3) + Postgres + Claude. Data model: - videos(id, owner_id, mux_id, title, transcript, created_at) - shares(id, video_id, scope: internal|link|public) - views(id, video_id, viewer, watched_pct, at) Build, in order: 1. Record screen + camera with MediaRecorder; upload to Mux. 2. A share page with a permissioned link; log views + watch %. 3. Transcript on upload (Whisper). 4. AI assist, chapters + actions from the transcript. Call Claude: """ Given a timestamped transcript + title, return JSON { summary(1 sentence), chapters:[{start_ts,title}], action_items:[{owner_or_unknown,task}] }. Only explicit action items. No filler in chapter titles. """ Skip: per-creator pricing, the AI upsell tier, workspaces, branded CTAs. Done when: record, share a link, see the watch log, and get a transcript with chapters.

03 · Result

Summarise 'Q3 onboarding walkthrough' (12m)
rec:onboarding-q3

5 chapters · 3 action items · 1-line summary set

← Legacy SaaS indexAI wrappers index →