Five months ago I deleted two months of work and started over.
This is the honest version of what happened next building Beonmap, an AI-powered job discovery platform, as a bootstrapped team. The good parts, the expensive mistakes, and the problem we still haven't solved.
Quick summary if you're skimming:
Before Beonmap, I was building a CRM SaaS.
After about two months, I realized the problem wasn't the code it was the market. CRM is a crowded space with well-funded incumbents, and I couldn't articulate a reason for anyone to switch to mine. Building it was never the hard part. Finding a place where we could create real value was.
So I stopped.
Walking away from two months of work is not fun. But continuing down a path you already know is wrong is more expensive than restarting.
Takeaway: Sunk cost is not a strategy. If you can't explain why someone would choose you over what already exists, keep looking.
In February, I started working on Beonmap with a simple idea:
Help people discover better career opportunities using AI.
Job search today mostly means scrolling through thousands of listings and hoping something relevant appears. We wanted something different AI matching based on skills and goals, plus a map-based interface so you can actually see opportunities around you, by location and company.
I built a web app first. Then I built the mobile app and deleted the web version entirely.
Our users are job seekers. They check opportunities on the commute, during breaks, before bed. They're on their phones. Keeping two platforms alive as a small team meant doing both badly, so we picked the one that mattered.
It cost me weeks of work. It was still the right call.
Takeaway: Building a product means following users, not your original plan.
Google Play approved v0.1.0 without much friction.
Apple was a different experience. Our first accepted iOS build was v0.1.7 roughly a month of review cycles, rejection feedback, and resubmissions.
It was frustrating, but honestly, several of those rejections made the app better. Apple's reviewers caught things our own testing didn't.
Takeaway: If you're shipping mobile, budget real calendar time for iOS review. Don't plan a launch date around it. Plan the launch date after you're approved.
Beonmap is now on v0.2.2 22 releases since we started.
Almost every one of them was about the same thing: user experience. We tested flows, removed features nobody used, simplified onboarding, and fixed things users told us were confusing.
None of this is glamorous. All of it is the job.
Takeaway: Version one is a starting point, not a product. The product is what version twenty looks like.
At one point I set up a company for Beonmap, because it felt like the professional thing to do.
We weren't making revenue. The company came with costs, paperwork, and accounting obligations that gave us nothing in return at that stage. Looking back, I should have waited until there was actual money to protect.
This one genuinely stings, so I'll say it plainly: I regret it. If you're pre-revenue and pre-product-market-fit, that money is better spent on the product.
Takeaway: Not every startup step needs to happen immediately. Timing matters more than looking legitimate.
After months focused almost entirely on development, I hit an uncomfortable realization: nobody discovers a good app on its own.
I've since partnered with two marketing professionals, and growth is now where most of our energy goes. The app works. Getting people to know it exists is a completely separate problem, and I underestimated how different a skill set it requires.
Takeaway: Build time and distribution time are not the same budget. Plan for both.
We're bootstrapped. Most of what we have has gone into development, infrastructure, and growth.
That's a real constraint, and I won't pretend otherwise, we need sustainable revenue, and we need it sooner rather than later. The hard part was never the technology. It's building a business around it.
Here's the challenge I'd most like to hear from other founders about.
A recruitment platform needs two sides:
Job seekers won't pay to find a job and I don't think they should have to. So revenue has to come from the company side. But companies only pay when there's enough talent on the platform to make it worth it. And talent only shows up when there are enough jobs.
Right now we're investing everything into growing both sides at once and monetizing neither. It's the classic chicken and egg problem, and knowing its name doesn't make it easier to solve.
If you've built a two-sided marketplace and found a way through this, I would really like to hear how.
There are days I wonder whether a different idea would have been easier. That's an honest thing to admit and I suspect most founders feel it.
But Beonmap is free, people are using it, and the feedback we get from users who found something through it is the reason we keep going. We have real problems ahead, growth and monetization above all but we're learning and shipping.
Our goal hasn't changed: make career opportunities easier to discover, and help people find where they truly belong.
If you're building a SaaS right now, I hope some of these lessons save you from a few mistakes I made. And if you've built a two-sided marketplace or found a way to solve the monetization challenge, I would genuinely love to hear your experience. The comments are open.
Thank you for reading.
Beonmap is free on iOS and Android.
https://beonmap.com We're still early in this journey, but we are excited to keep building, learning, and improving every day.
See you in the next update.