Choosing Between Shipping an MVP and Going Production Ready
I still cannot get myself to write on a regular basis, even short progress notes.
The MVP with a minimal feature set, fully working, is already done. I am surprised by how easily the core features came together, and how good they turned out.
A couple of days ago this created a dilemma for me: should I release the project as an MVP and then keep adding extra features, or should I turn it into a production-ready product first?
I chose the second option. Even though the market is not yet overcrowded with similar products, there is still competition, and I need to offer users some unique advantage right from the start. Making everything free is a very bad idea. I learned this from Fullyst, which launched as a free project and attracted a lot of users, but as soon as limits appeared, which you could raise for a small fee, there was a significant user churn.
So I keep working on something good, but I will probably launch not in July, but in August.
More to explore
The Failure of AI Skepticism: Why Manual Coding Is Already the Wrong Layer
In recent months I keep seeing the same pattern: someone posts another example where some "vibe coders" used AI to generate a project, left API keys on the fron…
You Don’t Need a Perfect Modern Stack to Agentize Your SDLC
Continuing the idea from the previous post. Many companies believe that to add agents to their SDLC they first need to completely get rid of legacy, move to mic…
AI in Software Development: What Comes Next?
AI. What’s next? Up until around December, using AI in development basically meant: prompt -> copy some code -> paste -> tweak -> repeat. Now this a…
Startup Taxes Between Estonia and Portugal: A Quick Reality Check
As a tax resident of an EU country who files my own returns, today is my quarterly 'Tax Day'. On this day I set aside a few hours to file social security report…