msmello

I’m building a new web-scraping API (similar to Firecrawl, Apify, or ScrapingBee) and am on the fence about launching the MVP now vs. waiting until I complete two related services (Verðandi and Skuld) that will handle data differently—hopefully giving me an “unfair advantage” in the future.

My questions: 1. Timing: Should I release the MVP now to gather feedback and iterate, or keep developing behind closed doors until I have a more robust offering? 2. Open Sourcing: I’d like to open-source the core scraping functionality while offering a paid “cloud version” on top. Do most projects split the code into a separate open-source repo, or is there a more streamlined approach?

Any advice or experiences with launching MVPs prematurely vs. waiting, and how to handle an “open core” model effectively, would be much appreciated!

Certainly! Here's a more concise version of your message:

Subject: Your Insights Needed for Promptify Pro!

Hi Community,

In the past year, Promptify Pro has grown to serve thousands of users, but I'm looking for ways to improve. I'm at a crucial point and need your expertise and fresh ideas, especially on enhancing functionality and conversion rates.

Please try out Promptify Pro at https://promptify.pro/ and share your honest feedback. All suggestions, big or small, are incredibly valuable to me.

Thank you for helping shape the future of Promptify Pro!