Screen Studio Teardown — Adam Pietrasiak's $200K MRR Mac-Only One-Time-Purchase Anomaly

Verdict

I have looked at maybe 200 indie SaaS teardowns this year and Screen Studio is the cleanest one I have seen. Not the biggest, not the fastest growing, not the most technically impressive — the cleanest. One Polish guy named Adam Pietrasiak, working alone with a handful of contractors, built a Mac app that records your screen, sells it for $89 once (not per month, once), and pulls roughly $200K in monthly revenue out of it. No funding round. No subscription treadmill. No content marketing factory. No paid acquisition. The product itself is the marketing. People watch the output, the output looks ten times better than QuickTime, and they buy it.

The reason this is worth a full teardown is not "Adam is a genius" — although the product is genuinely beautifully made. The reason is that Screen Studio quietly refutes about six pieces of conventional 2024 indie wisdom at the same time. You're supposed to go cross-platform — Adam went Mac-only and made it a feature. You're supposed to charge monthly to maximize LTV — Adam charges once and his customers love him for it. You're supposed to build in public on Twitter with growth loops and viral mechanics — Adam mostly just posts demos. You're supposed to need a co-founder, a team, a designer-engineer pair — Adam is solo with five contractors. You're supposed to compete on features against Loom — Adam competes on taste and wins specifically because of it. And you're supposed to pick a giant TAM — Adam picked the narrow slice of Mac users who care about screen recording quality, and that turned out to be enough.

Here is the thing I want you to internalize before reading the rest: Screen Studio works because Adam picked a fight he could actually win. QuickTime ships free with macOS, Loom ships with a generous free tier, OBS is free and open source. Competing on price is dead. Competing on features is dead — Loom has more features. What Adam did instead was identify one specific thing — the recording looks beautiful by default, with automatic zooms and smooth styling, with zero editing skill required — and made his product ten times better than every alternative at that one thing. That is the entire moat. Default output quality. The auto-zoom that follows your cursor and the rounded-corner gradient background that just appears, without you choosing it, are not features in the engineering sense. They are a taste decision baked into the defaults. Engineers underestimate how much money is in baking taste into defaults.

The replicate question is interesting because it is not "build another Screen Studio." That spot is taken and Adam keeps shipping. The replicate question is "what other software product has a default-output-quality gap this large between the free tool and the paid tool, in a vertical the incumbent ignored?" My personal bet is on a vertical screen recorder — a Screen Studio specifically for code review walkthroughs, or for Figma design walkthroughs, or for sales demo recording — where the defaults are tuned for that one vertical and where Adam's horizontal product still requires manual tweaking. That's the playbook section at the bottom. Read the rest first.

Quick Facts

Field	Value
Product	Screen Studio
URL	screen.studio
Founder	Adam Pietrasiak (solo)
Team size	1 founder + ~5 contractors
Location	Poland
Founded	2022
MRR (reported)	~$200,000
ARR (implied)	~$2.4M
Pricing	$89 one-time per major version (v3, v4, etc.)
Funding	$0 — fully bootstrapped
Platform	macOS only
Distribution	Direct via Paddle
Primary channel	Twitter demos + word of mouth
Category	Screen recording / video creation
Headline feature	Automatic smooth cursor-following zoom
Competing against	Loom, QuickTime, OBS, CleanShot X, Tella

The Product — Why It Looks Ten Times Better Than QuickTime

Open QuickTime. Hit Cmd+Shift+5. Record yourself clicking around an app. Stop. Look at the result. It's flat. The cursor is tiny. There's no visual hierarchy. The viewer cannot tell where you are clicking. The aspect ratio is whatever your monitor is, which is usually wrong for embedding anywhere. The output is a raw screen recording, and it looks like a raw screen recording — fine for a Slack DM showing your coworker a bug, useless for anything you want to put on Twitter or in a sales deck or on a landing page.

Now open Screen Studio. Hit record. Click around the same app. Stop. The output is already a polished product video. The cursor has a soft glow around it. The recording automatically zooms in when you click something — smoothly, with easing, with the camera following your attention. The background is a gradient. The window has rounded corners and a subtle drop shadow. The aspect ratio is whatever you want — 16:9 for YouTube, 1:1 for Twitter, 9:16 for vertical, with one click. The webcam overlay is a perfect circle in the corner if you turned it on. The cuts between actions are clean.

The single most important feature, and the one I want you to understand if you understand nothing else about this product, is automatic cursor-following zoom. When you click a button in the recording, Screen Studio's editor automatically inserts a smooth zoom-in to that button at that moment, then zooms back out. You did not tell it to do this. You did not select the button. You did not set keyframes. The app detected your click event, decided "this is the interesting part," and animated the camera there. This is what people pay for. This is the single feature that separates a Screen Studio video from a QuickTime video, and once you have seen one, you cannot unsee how flat a QuickTime recording looks.

The technical implementation matters here because it is what an indie copycat needs to understand. Screen Studio is recording the screen at high resolution using ScreenCaptureKit (Apple's modern screen-capture framework, which replaced the older quartz-based APIs in macOS 12.3+). It is also recording every mouse event, every click, every keystroke, every window-focus change as a separate event track. When you stop recording, the editor has a timeline of events layered on top of the raw video. The auto-zoom is then applied as a Metal-rendered effect at export time — not baked into the original recording. This means you can adjust the zoom afterward, change the easing curve, change the background, change the aspect ratio, all without re-recording.

Two consequences fall out of that architecture. First, the export is rendered fresh each time at whatever resolution you pick, which is why Screen Studio exports look razor-sharp at 4K even if your screen was 1080p. Second, the editing surface is post-hoc and forgiving — you can tweak the auto-zooms after the fact, you can add manual zooms, you can trim — without ever losing the original raw recording.

The other set of decisions that matter: the defaults are good. Most "professional" video tools assume the user is a video editor. They open with a blank timeline, twelve panels, fourteen menus, and a request to set up your project preferences. Screen Studio opens with a recording button. You record. It auto-edits. You hit export. You ship. The opinionated defaults — the gradient background, the cursor glow, the smooth zoom easing curve, the corner radius on the recorded window — are not configurable on the first export. They just appear. That is the product. You can dig into preferences later if you want to change them. Most people never do, because the defaults already look good. This is the same trick Apple's iMovie and Apple's GarageBand pulled in 2003 — make the default output look good enough that 80% of users never touch the advanced settings.

The Pietrasiak Solo Bootstrap Story

Adam Pietrasiak is a Polish software engineer who started building Screen Studio in late 2021 / early 2022, launched the first public version around mid-2022, and the product caught on through Twitter. He posts demos of new features as short looping videos on Twitter (@PietrasiakAdam), and these demos go viral because — recursively — the demos are made with Screen Studio and they look ten times better than other product demos, which makes you want to know what tool made them, which leads you to Screen Studio.

I want to flag this loop because it is the entire distribution engine and most people miss it. Screen Studio's demos look like Screen Studio's output looks. The marketing is the product. There is no marketing budget separate from the engineering budget. Every time Adam ships a feature, he records a demo of that feature using the feature, posts it on Twitter, and the inherent visual quality of the post is itself an ad for buying the product. This is the highest-leverage marketing structure I have ever seen in indie SaaS, and it works only because the product happens to be a tool for making content. You cannot do this with a database admin panel. You can do it with a screen recorder, an animation tool, a slide deck builder, a logo maker, a code-screenshot tool (which is exactly what Ray.so / Carbon are). Pick a product category where the output is itself the demo.

Adam has been open about his revenue numbers — he has posted MRR screenshots on Twitter showing the ~$200K/mo figure — and about his solo founder structure. He has roughly five contractors he works with for things outside his core skillset: design, video, support, marketing. He does the engineering himself. He does not have a co-founder. He has not raised. He is in Poland, which means his cost of living is meaningfully lower than a San Francisco founder's, which means the same $200K MRR translates to a fundamentally different lifestyle and runway. This is part of the math and a copycat in San Francisco should not ignore it.

Business Model — One-Time vs Subscription Math

Here is the question every SaaS person asks when they first hear about Screen Studio: why is he charging $89 once instead of $15 a month?

The naive subscription model on the same product would look like: $15/month × 12 = $180/year per customer. With a 12-month average customer lifespan that's $180 LTV per customer. With $89 one-time, Adam is leaving $91 of LTV per customer on the table per year, if and only if every customer would have stayed subscribed for 12 months.

That conditional is doing all the work. Let me run the actual math.

Scenario A — Subscription at $15/mo: Adam charges $15/mo. Assume 5% monthly churn. Average customer lifespan is 1/churn = 20 months. LTV = $300. Sounds great. But to maintain MRR at $200K with 5% monthly churn, Adam would need to acquire 10,000 new paying customers every single month. Forever. Just to stay flat. With his current organic distribution (one solo founder posting demos on Twitter), this is plainly impossible. Subscription would have killed Screen Studio.

Scenario B — One-time at $89: Adam charges $89 once per major version. He ships a major version every 12-18 months (v1 → v2 → v3 → v4). Existing customers can keep using their bought version forever. To upgrade to the new major version they pay $89 again. In practice this turns into roughly an 18-month subscription with no churn anxiety — customers feel like they own the product (because they do), and Adam gets a re-purchase cycle when he ships a meaningful upgrade.

The numbers behind ~$200K MRR at $89/license imply roughly 2,250 sales per month, or ~27,000 sales per year. Acquiring 2,250 customers a month organically through Twitter demos is plausible — the demos go viral, each viral post sells a few hundred copies, a steady stream of word-of-mouth recommendations does the rest.

The one-time price is not a quirk. It is a structural design choice that matches the distribution channel. Organic Twitter virality has spiky, batch-like demand. One-time purchases convert spiky demand to revenue cleanly. Subscriptions convert spiky demand to revenue badly because most of the spike never renews. Match your price model to your distribution.

The other thing one-time pricing buys Adam: trust. Indie tool buyers, especially designers and developers, are exhausted by subscriptions. Every tool wants $15/mo. The mental tax of tracking 40 subscriptions is itself a buying friction. When Screen Studio says "$89 once, yours forever, optional upgrade later," the buyer's defensive posture relaxes.

Screen Studio vs Loom vs QuickTime vs OBS vs Tella

Tool	Price	Auto-zoom	Output quality (default)	Platform	Sweet spot
Screen Studio	$89 one-time	Yes, automatic	Beautiful by default	macOS only	Polished demo videos, indie devs, designers
Loom	$0 free / $15/mo Business	No	Plain	Web + Mac + Win	Async work communication, internal screen-shares
QuickTime	Free	No	Flat	macOS only	Quick raw recording, no sharing infra
OBS Studio	Free	No (manual)	Whatever you configure	Mac + Win + Linux	Live streaming, advanced multi-source production
Tella	$19/mo	Some templates	Good, template-based	Web	Async talking-head videos with branded backgrounds
CleanShot X	$29 one-time / $10/mo cloud	No	Clean screenshots + basic video	macOS only	Screenshot annotation primary, recording secondary

Loom is the only one of these that is structurally competitive with Screen Studio, and it isn't really competitive — they serve different jobs. Loom is for async communication. Screen Studio is for polished video production. The output formats are incompatible.

QuickTime and OBS are the free baseline — they are what you use when you do not know Screen Studio exists. The conversion event for a Screen Studio customer is almost always: "I saw a beautiful product demo on Twitter, I asked what tool made it, someone replied 'Screen Studio,' I tried QuickTime first because it's free, I realized my recording looked terrible, I bought Screen Studio." The free tools are not competitors — they are the qualifying step that makes the buyer ready to pay $89.

Distribution Engine

Adam's distribution is:

1. Build a feature.
2. Record a demo of the feature using the product itself.
3. Post the demo on Twitter (@PietrasiakAdam).
4. The demo goes viral because it looks beautiful — beautiful in a way that visually advertises the product without saying anything.
5. People in the replies ask "what tool is this?" and other commenters answer "Screen Studio."
6. Some fraction click through, try QuickTime, decide it looks worse, and buy.

That's it. No paid ads. No content marketing team. No SEO play. Twitter demos and word of mouth.

For a copycat the load-bearing question is: can your product also produce a demo that is itself an ad? If yes, the Screen Studio distribution model is available to you. If no — if your product is a database tool, a billing API, a backend monitoring service — you need a completely different distribution strategy and the Screen Studio playbook does not apply.

Why Now

The macOS screen-recording API got radically better. Apple shipped ScreenCaptureKit in macOS 12.3 (March 2022). Screen Studio launched right after this API became available. Twitter became the demo distribution channel for indie SaaS. The AI content-creator boom drove demand for good-looking screen demos.

If you are reading this in 2025-2026 and wondering whether the window has closed: the exact Screen Studio wedge (general-purpose horizontal product demo recorder for Mac) is closed. The adjacent wedges — vertical-specific screen recorders, Windows screen recorders with the same taste, mobile screen recorders, terminal-specific recorders, design-tool-specific recorders — are mostly still open.