@AKaarten Ga ik doen. Had in de google sheet gekeken maar zag daar niet zijn naam, de naam van het rekeningnummer of het rekeningnummer. Andere manier om iemand te checken voor de volgende keer?
Just watched @asmartbear teardown @dmytrokrasun's $32k/mo screenshot API (9% churn)
Jason laid out Options A-D:
- Option A: Optimize baseline
- Option B: Build a marketing tool
- Option C: Sell the business
- Option D: Go all-in on MCP / AI
I think Jason missed the best strategy
Thereโs an "Option E" that is even better ๐
Why not Option D (MCP / AI):
Dmytro noted at 1h:31m that desktop agents already have browser access. Jason brushed it off as a sales objection, but Dmytro is right:
1. Local browsers are free & instant
Cursor, Claude Code, and Windsurf spin up isolated Playwright instances (0ms latency, $0 cost). No 3rd-party API needed for prompts.
2. Static PNGs vs. interactive DOM
Agents don't just need a picture, they click buttons, fill forms, and wait for DOM states. If you need cloud execution, you buy browser infra (@browser_use), not a screenshot API.
3. The "security" argument is backwards
Jason argued local agents get access to "your email and bank". But Playwright launches fresh ephemeral profiles with zero cookies or saved sessions.
Plus, 3rd-party APIs can't reach internal or staging URLs behind a corporate VPN anyway. Local IS the enterprise-safe option.
4. ScreenshotOneโs real moat
Itโs not LLM chat prompts, itโs background execution and automation at scale (anti-bot bypass, Cloudflare evasion, 500 parallel renders). Thatโs how I use it at https://t.co/fiqqEJPjZ6 for web scraping and https://t.co/X5gQf8nHsk for brand identity.
Why Option B (Jasonโs version) falls short:
Jason suggested reusing screenshot code for a marketing regression tool, but Dmytro is burned out on screenshots.
The real asset isn't screenshot code. It's DISTRIBUTION.
Dmytro has:
- 1,000 paying B2B customers
- Domain Rating of 62 (DR 62)
- #1 ranking high-intent search traffic
๐ Option E: Launch SaaS #2 to the same audience
1. Analyze the full workflow
What do users do right before or after screenshots?
- Cold email teams need contact email enrichment
- AI devs need HTML โ Clean Markdown for LLMs
- QA teams need visual regression diffs
2. Sell a 2nd full-priced subscription
Don't add cheap $5 add-ons. Launch a 2nd standalone API at a full $30โ$50/mo.
3. $0 CAC expansion MRR
Starting from zero means 12 months grinding backlinks. SaaS #2 gets instant cross-sells from 1k paid users + DR 62 search leads on Day 1.
Write listicles & "how-to" guides on ScreenshotOne that rank immediately for adjacent API keywords.
4. Cures founder burnout safely
Fresh product momentum backed by a $30k/mo cash-flow safety net.
Option E is the ONLY play that fits Dmytroโs psychological state on the call:
- Option A makes him feel "tired" & "not super excited"
- 5 more years of it feels like "there's so much more to do"
- Option C (selling) would be a "painful experience... from zero"
SaaS #2 gives him new-build energy without from-zero pain: new problem, new market, new landing page, backed by 1,000 customers and a ranked domain.
TL;DR: Keep App #1 on maintenance โ Analyze workflows โ Launch SaaS #2 to your current audience.
Crazy this isn't in @laravel Nightwatch. Such a weird product, you never hear about it, all just Cloud. Hardly any product updates either though there is still so much room for adding to an already very solid base.
Do you build agents with the @laravelphp AI SDK? Do we maybe ship support in the @sentry Laravel SDK next week? ๐คซ See exactly what your agents are doing, with full conversation context, token spend, tool calls and much more!