I really like the “narrow on purpose” approach.
There’s a big difference between building a replacement for a product and building a replacement for the specific workflow people actually depended on.
The cron job example makes that especially clear. Technically, there may be a free way to do the same thing, but the value is making that workflow accessible to people who shouldn't need to know how to maintain a Python script.
I think that’s a useful product lesson: sometimes the thing you're replacing isn't really the technology, it's the friction around it.
The “cron can do it for free” objection is actually the interesting part.
Curious whether the value users care about most is the SQL workspace itself, or making scheduled data access usable for people who would never touch a script.
That’s useful context. The scheduled exports seem to be where the strongest usage is emerging. I’d be interested in continuing the conversation beyond the thread — what’s the best email to reach you on?
I built SaturnSQL to replace PopSQL and SeekWell when they announced their shutdown. I believe that everyone in a company should have access to the company's data, not just engineers.
5 Comments
The “cron can do it for free” objection is actually the interesting part.
Curious whether the value users care about most is the SQL workspace itself, or making scheduled data access usable for people who would never touch a script.
For my current customers (a handfull) I would say almost everyone uses the scheduled data exports and ~50% of those also uses the SQL sharing.
Pricing is seat based so it would of course be nice to have more seats than less of them.
This comment was deleted 2 days ago