What's an MVP?

Building a startup is never a straight line—it’s a rollercoaster. While I'm excited about the early interest in SplitSense, THANKS TO ALL WHO SUBSCRIBED TO THE WAITLIST ALREADY!!, I want to share some behind-the-scenes struggles in getting the product ready and defining what the MVP should actually look like.

The Struggle Is Real

When I first started writing the code for SplitSense, I underestimated just how complex A/B testing could get. Sure, the concept seems simple—show two versions of a page and pick the one that performs better. But when you start diving into the nitty-gritty, there are a million questions:

• How do we define "significance" in the test results?

• How do we handle edge cases, like when there isn’t enough traffic to reach meaningful insights?

• What’s the best way to present actionable data without overwhelming users?

As a solo founder (at least for now), balancing coding, testing, dreaming and planning is tough. Some days, it feels like you’re stuck in a loop of “What if this doesn’t work?” But here’s the thing: every struggle feels worth it when you see progress.

Less Is More?

One of the hardest decisions in this process was deciding what features to focus on for the MVP. It’s tempting to include everything and try to deliver a fully polished product from day one, but that’s not realistic. Instead, I had to ask myself:

• What’s the core problem we’re solving?

• What’s the simplest version of the solution that provides real value?

For SplitSense, that meant focusing on these key features:

1. AI-Driven Variant Creation: Automatically generate A/B test variants for landing pages.

2. Automated Testing: Run tests with minimal user input.

3. Actionable Insights Dashboard: Provide clear recommendations based on test results.

Anything beyond that—like integrations with major CMS platforms, custom analytics, or advanced segmentation—can come later. Right?

Lessons Learned So Far

1. Perfection Is the Enemy of Progress: I’ve learned that it’s better to launch with a smaller feature set and improve over time than to wait for everything to be perfect.

2. User Feedback Is Gold: The subscribers who’ve already signed up for early access are shaping the direction of the platform. Listening to them will help us build something that truly solves their problems.

3. Keep It Simple: A/B testing can be overwhelming. My goal is to make it so intuitive that anyone can use it without a manual.

What’s Next?

The next step is to finalize the beta-demo and share it with the early subscribers. I’m thrilled (and a bit nervous) to see how SplitSense performs in the real world.

To everyone who has signed up already: thank you! Your support means everything. If you haven’t joined the waiting list yet, now’s the time: https://subscribepage.io/splitsense.

Final Thoughts

Building SplitSense is a journey, and every challenge is an opportunity to make the product better. I’ll keep sharing updates as we get closer to launch—both the wins and the lessons learned along the way.

Let me know: What’s one feature you’d love to see in an A/B testing tool?