Just launched SnapDat — a screenshot and OG card API. Day 1 report.
I kept solving the same annoying problem across different projects: apps that need screenshots or link preview images end up with a headless browser bundled into the app. It's maintenance overhead that has nothing to do with the actual product.
Built SnapDat to solve it once. POST a URL, get back a screenshot or a preformatted OG card image. Managed, hosted, no browser to maintain.
Pricing:
• Free: 100 requests/month, no card required
• Pro: $19/mo — 2,000 requests
• Scale: $49/mo — 10,000 requests
Launched today at snapdat.io.
Day 1 numbers: 0 paid customers, a few signups. Just getting distribution going.
Happy to hear from anyone who's hit this problem before or anyone who thinks the pricing is off.
This is a clean product because the pain is very specific: nobody wants to maintain headless browser infrastructure just to generate screenshots or preview cards.
I’d be careful with distribution though. Generic dev launch channels may get signups, but the buyers are probably people already building products where screenshots or OG images are part of the workflow.
The first segments I’d test are:
SaaS tools generating share images
SEO/reporting tools needing page screenshots
social scheduling tools
directories and listing platforms
no-code/automation builders who need screenshot output
Pricing may not be the main issue yet. The first question is whether SnapDat is being shown to people who already feel the browser-maintenance pain.
Happy to put a tighter version in writing if useful. I’d map the first buyer segment, pricing angle, outreach message, and a simple 7-day path to the first paid users.
Just seeing this now, a month late. Apologies, I don't get in here often enough. This is a sharp read, and you're right that pricing isn't the real question yet. The generic launch channels brought lookers, not people who already feel the browser maintenance pain. Of the segments you listed, social scheduling tools and directories stand out to me since preview images are core to their product, not a side feature. If the offer still stands, I'd gladly read the tighter version. What made you rank those segments the way you did?
I'm glad it was useful.
I do have a clear reason for that ordering, but it's based on how I think the buying process differs across those segments. I don't think I could explain it properly in a thread without oversimplifying it.
If you're interested, what's the best email to reach you on?