- Notes on Solopreneurship Engineering
- Posts
- Issue #3: MRR here I come! š Or maybe not? š¤
Issue #3: MRR here I come! š Or maybe not? š¤
The Stripe chart is not flat anymore
Wooooooo! š„³
Yeah the title and subtitle are not click-bait, it really happened! š¤£
But itās bittersweet as Iāll explain later.
Does this mean I got promoted from an indie hacker to a solopreneur? š š
Long journey yet, but in the meantime it was a nice injection of dopamine. It feels a bit as if I broke a barrier. š
However, as I mentioned in the past newsletter issues, I thought a lot about what to⦠x.com/i/web/status/1ā¦
ā Lou Marvin Caraig (@LMCaraig)
7:16 AM ⢠May 10, 2024
Starting from todayās issue, Iām moving the overview of the current status to the end. Those interested in looking at the current stats can still do it, but at least we start talking about the most interesting stuff early on. š
The first paying customer
As anticipated the gross volume chart is not flat anymore! š„³
BUT
The MRR chart still is. š
The reason is that the first paying customer already canceled the subscription. It would be more than fine as I donāt expect users to subscribe for a long period, but what hurts is the reason behind it.

User subscription cancellation
The best would probably be to reach out and ask what was the expectation and also if it was related to the job board or the CV analysis.
The plans for NextCommit
In the āTo push or not to pushā section of the last week's issue I already shared my concerns about making NextCommit profitable. The TL;DR of my concerns could be summarized with:
people are less inclined to spend their own money (B2C),
subscriptions imply commitment, and commitment is scary, even more so if weāre talking about committing with your own money
landing a job is not a consistent issue people are facing, and this makes committing to a subscription even scarier.
From the data I have right now, I cannot really extract any meaningful statistics, but letās play this game anyway. š¤£
I have 140 signed-up users, and 1 paying user. This results in an astonishing conversion rate of 0.7%. This is damn low, especially considering that tons of users do not even signup. š
However, my organic search is also ridiculously bad. According to Google Search Console:
31 clicks,
186 impressions.
I donāt know whatās the acquisition channel of my first customer, but for sure organic search can be improved. Letās just assume for a second that Iāll be able to get to 10k signed-up users with the same conversion rate, and everyone buying the monthly subscription at 11.90 EUR.
This makes an 800 EUR MRR. š
Ofc, theyāre not peanuts to throw away, but still way below my target goal.
I know that the math is off, but as I mentioned, with these low numbers thereās really not much that can be done, itās more to have some VERY rough idea. Moreover, this doesnāt take into account churn which I expect will be a big component. For example, it could be that I convert 7 users every 1000, but also lose 5 every 1000.
However, the interesting thing is that reaching that amount of traffic could unlock the potential for sponsored job posts. āØ
This would move the business model from B2C to B2B and hopefully, conversion would improve, alongside the pricepoint.
For all these reasons, I will focus mostly on SEO instead of building other features.
But I still need to better understand why the first paying customer canceled due to āQuality less than expectedā. I could have huge amount of traffic, but if the product is useless, well also the traffic is. š
Programmatic SEO
Iām not at all an SEO expert š .
But Iām learning and experimenting and seeing what works or seems to work, and what does not.
This week I added a page for each company with the corresponding job posts.

Company page of a random company
As you see from the screenshot, thereās not much content associated other than the website and the base URL the job posts have been extracted from.
I then generated the sitemap and submitted it to Google Search Console.
8k+ pages! š
Whatās in the sitemap for now? You can check it out yourself here, but basically:
one page for each category,
one page for each country,
one page for each company.
Are those pages going to be indexed and ranked by Google? Who knows. š
Maybe they wonāt because thereās not much content associated with each page, or maybe they wonāt because the internal linking structure is not optimal, etc.
On the page content, this could be improved by adding an āaboutā section for each company, itās not a piece of information that I currently scrape, but it should not be hard to implement. Maybe a few days?
On the internal linking structure, if you open the app you quickly realize thereās no link to go to the companiesā root page with the list of all companies. If you go to the URL https://app.nextcommit.careers/companies you see nothing. š¤£
When I implemented those pages, I added a section in the menu as well. But when I deployed it to production the API crashed. This is the reason:

API server instance type
I was lazy and didnāt implement pagination so all the 8k+ companies in a single call were being returned and the API just crashed. š
This is another easy thing to do as Iām already paginating the job posts, I just didnāt have the time to do it.
Another thing that I could do is generate one page for each job post. For those who experienced the very first version of NextCommit (you can see a snapshot here), you might remember that each entry was expandable and showed different sections āCompensationā, āRole and Responsibilitiesā, etc. I do have that information already, so I can do it again but on a separate page. The only caveat is that it might not be fully accurate, or the text is just the output of an LLM that hallucinated. But maybe itās not that bad, the worst thing that could happen is probably a user complaining about wrong information while the best thing is that the app starts getting ranked higher. Iād say that itās worth the risk. šŖ
This is also another thing that Iād like to experiment with:
I see so many job boards not adding jobPosting schemašš»
To get your job listings featured on Google Jobs you need them šš»
Google Jobs is one of the most significant potential traffic sources for job boards š”
Millions of job searches occurring on the search engine each day š„
ā Rodrigo Rocco šØāš»šš from JobBoardSearch š (@rrmdp)
5:06 PM ⢠Apr 29, 2024
Ranking higher takes time, it doesnāt automagically happen in one night. šŖ
Thatās why this week I thought a lot about other paths that Iād like to give a shot.
What should I bake next?
Lots of people in the indie hackersā community often say:
Ship fast!
I agree with that, but I also think that itās important to allocate the proper time for thinking and planning rather than just build and ship whatever comes to our minds. š
I have a Trello board that I use to store ideas, and I already have more registered domains that live projects, so better be careful. š¤£
Considering the learnings from NextCommit, this time Iād like to work on something B2B.
No-code user journey testing
This is one of the ideas that I came up with.
The idea is to empower non-tech persons to test user journeys without engineering help.
In my career I saw this problem often where thereās a need for end-to-end testing, but never the time to implement them because of higher priority tasks on the engineering team.
But what if the engineering team is not needed anymore? š¤
Imagine a very simple form with just 2 fields:
an input field asking for a URL,
a text area where the user would describe what has to be tested.
Letās take NextCommit as an example. This could look like as:
URL:
https://nextcommit.careers
Text area: āMake sure that the filters are working and showing results according to the selection, and ensure that all the sections except for āSearchā require a loginā
I also spent some time exploring it in a Jupyter Notebook to evaluate technical feasibility.

Experimenting e2e QA
I think itās a very interesting project and the offering is very specific, which makes it a good candidate for a bootstrapped product. But at the same time, the range of cases that this could bump into is huge and unpredictable, and this puts on the table a lot of hidden complexities. š¤Æ
I decided not to pursue this path as it seems like an idea that would fit a bigger team, maybe VC-backed, as it could lead to quite some effort dedicated to proper researching and handling of different scenarios.
Moreover, the currently existing solutions based on recording the actions from the browser and replicating them, such as the one offered by Datadog, are cheap and good enough.
Customer experience industry
Among all the different industries, customer experience interests me. Others like healthcare, and fintech would also be good candidates, but Iād avoid anything that might require some strict regulations. ā
At the same time, customer experience is HUGE:
customers onboarding,
customers support,
customers retention,
etc.
and each requires a lot of effort.
There are quite some companies in the space like Intercom, Customerly, Crisp, Zendesk, Vitally, etc. and theyāre either trying to focus on a specific area, or theyāre big enough to try everything.
I had a look at those to have an understanding of what this space looks like, but Iām still wrapping up my thoughts. I also donāt want to focus too much on what exists already.
What did I do then? š¤
The best way to better know the problems to solve is to ask the people facing them. š
I started preparing some questions and Iāll try reaching out to people who dealt to different extents with customer experience/success, ask those questions, and take notes. āļø
Iāll start from my network and then move to sending cold emails or DMs on LinkedIn I guess.
Ideally, I should be able to understand the most painful problem and focus on that as a starting point. The trickiest part is probably that companies already relying on some solution would not be willing to migrate/try even a beta for free unless theyāre unsatisfied with the current solution. But letās see, one step at a time. š£
In the meantime, I also registered a domain. But if youāre reading this within the few days after the publication, the button does nothing as Iām still preparing the form. š
So, what will I be building?
Thatās the point! I donāt know yet. š But I want to figure it out by talking to people. It might even happen that everyone is just happy and it just doesnāt make sense to jump in the mix.
Conclusion
Not many features or marketing updates this week, but mostly about what could come next. So the next weeks Iāll explore the customer experience space and continue working on SEO-ing NextCommit.
Iām eager to see what Iāll write in next week's issue.
I hope you enjoyed it! š
If youāre interested in following my journey, make sure to subscribe or follow me on Twitter and LinkedIn!
Appendix
Overview of current status
Here are some snapshots of different stats.
NextCommit
Users
In the last 7 days, I got:
+43 signups, now at 139 (+45%)
77 active users (sum of daily active users, not weekly unique active users) (it was 74, +4%)

Summary stats (from Clerk)

New sign-ups (from Clerk)

Active users (from Clerk)
Stripe

Gross volume (from Stripe)
Plausible Analytics

Analytics of the application usage and landing
Google Search Console

Google Search Console
Personal branding
X

X Premium analytics

Active subscribers
Reply