Daniel Abebe (@realDanielAbebe) of HuggyStudio recently hit $530 MRR on a new product without building a thing — not even a landing page.
I was intrigued, so I caught up with him to find out more. Here's how he did it. 👇
Daniel: In 2013, I launched my first startup without validating the idea first. I left my job and took a loan to build an expensive MVP because I assumed that customers would come if I just built the product. The project turned into a failure and I ended up with big financial problems. That was a painful lesson.
Over the years, I learned how to validate startup ideas and my personal belief became quite extreme. I promised myself I wouldn't build anything new without having paying customers first.
So we don't have a name, logo, or landing page yet, but our first customer paid us up front for a 6-month subscription at $530/mo. The $530/mo comes from 55 employees at $12 each, minus a pilot-period discount.
We have two months now to build the product before their subscription technically begins.
So he learned his lesson in a big way. And I like the idea, but how would one go about it, and is it even possible for other indie hackers? The short answer is that it probably only applies to B2B companies, but yes, most B2B ideas could get started this way.
Here's how he did it.
Daniel: We reached out to 80 companies asking for a meeting to better understand how we could help them reinforce company culture. 20 people agreed to meet, and from our calls, we identified 6 warm leads who were really interested in getting some help.
But here comes the trick: At this stage, we didn't sell them a solution. We sold them the idea of building one together. In that regard, not having an existing product or landing page actually helped us. It showed how flexible we were to focus on their specific goals
This is what we pitched: "Let's build a solution together that will work for your specific needs. We will invest as much time as necessary. In exchange, you commit to pay and give us feedback for at least 6 months once we go live."
Of the 6 warm leads, one client accepted our offer. Our belief is that if we build something that ONE company really loves, chances are high that other companies will love it too.
Here are the outreach templates he used.
It wasn't just about the initial influx of money. The feedback/direction from a real client is really where it's at for Daniel.
Daniel: We closed that customer by Week 3. They agreed on building the platform together for 2 months and using it for at least 6 months once we go live. That was the deal.
They'll be investing 8 hours in giving us feedback for the next 2 months (the equivalent of 1 hour per week). Once we go live, they committed to onboarding all their employees and giving us continuous feedback so that we can improve the platform to better match their needs. We retain the right to evaluate each feedback/suggestion before implementation.
Nothing like time and 55 onboarded employees to get a customer invested in the product. I'm guessing it would take a lot for this customer to churn.
So they made over $3k right off the bat, along with really great direction, and a highly motivated customer. What will they do with that sweet, sweet cash?
Daniel: The first 6 months were paid all at once. We'll use that money to test some marketing campaigns and see if we can get to free trials with performance marketing. We'll probably start with Linkedin to make use of their powerful job filter. It's still unclear how the distribution of our product will go once we launch. If performance marketing doesn't work, we will keep on investing in direct sales as it is working quite well already.
As for how they'll keep the lights on while they build the product, they've set up a pretty sweet engine.
Daniel: I co-founded HuggyStudio with the vision of becoming a bootstrapped company builder, and after 2 years of providing agency services, we've set up the company in a way that we can start building new startups without investors. Five people work on client projects, bringing in over $1 million per year, and the remaining four focus on building new startups.
But let's go back to that outreach. If you didn't notice, they had a 25% response rate, which is pretty stellar. Here's how they did that. Hint: Warm outreach, and heavily vetting cold prospects.
Daniel: I started with my own network and this helped get our first interviews. When we started going outside of my network, the reply rate dropped drastically.
With some creativity, we managed to get our stats for cold outreach messages to the following: 47 cold messages, 10 replies, 6 meetings arranged. What did we do? We invested a lot of time vetting each lead before reaching out and launched a podcast to offer value in meeting us.
That podcast offer made me do a double-take. Never heard that one before. They created a podcast specifically for this and a few of the potential customers actually wanted to be interviewed.
Daniel: That was a bet we took to talk to more people and build up a brand within the space over time. As we realized that our target audience is made of remote/hybrid companies, we decided to launch "The Remote-Culture Podcast". I recorded 4 interviews so far, we have 3-5 more in the pipeline. We haven't turned any podcast guest into a paying customer yet, but we benefited greatly from in-depth discussion that helped us better understand our target audience. Down the line, we also hope that listeners will be possible customers for our SaaS.
Well, I'm convinced. Sounds like he is too.
Daniel: I hope I never go back to building something before winning paying customers first. This feels like cheating the world.
Entrepreneurship becomes easier when your product already has customers before going live. Also, you are held accountable to make progress because people are expecting you to launch now.
And collaborating with customers is an exciting process for both parties. We are not pushing our product down their throat, we are truly fighting together on helping them achieve a goal. If they win, we win.
The only downside is that you need to start with sales and this can be a painful process that kills the excitement of "building a startup". Still, this could save you a lot of time building a product nobody wants.
Now all he's gotta do is build it... Within two months. 😅
Subscribe for more tips, how-tos, and case studies.
{{subscribe}}
Smart move, @realDanielAbebe!
Meaningful collaborations are actually one of the most powerful tools for us indie hackers. It can increase output, broaden our view or even gain customers.
A difficult task for you, I assume, is developing something that's specific enough to help the partner company but is general enough to be useful for others. What's your strategy? Do you try to generalize right away or figure out how to do it later after having satisfied your partner company?
Hey @alexanderdavide, thanks for your comment! I see we are aligned :)
That's a good question. As we're still figuring out the main value proposition, it's easy to stay generic for now. The strategy is to stay generic throughout the process but I guess it's going to be more challenging over time :)
Will keep you posted
Good luck!
Thanks Stefan!
@realDanielAbebe great story!
Awww thanks man, much appreciated 🙏😍
very nice article!!
Hehe thank you, James did a great job with the interview!
Really smart move. Really great move. Did you have any solution in mind before you pitched?
Thanks for your kind words! Much appreciated :)
We actually did, it was so difficult not to pitch it haha
I'm glad we didn't try to sell our solution because we're working on another approach now. The first idea got trashed.
If we only had that one solution in mind, our discussions would have ended there. Instead, the company is already investing more time to help us build the right product.
The current iteration is something we would have never come up with alone.
Great writeup!
I'm curious about how you approached this conversation:
Did you work with a legal team on designing the contracts for their commitments during this time period? This is something I've always been curious about for deals like this.
I noticed a bit later in the post there's mention of 8 hrs of total feedback over the 2 months of development - and then "continuous feedback" from 6 months onwards. How much and to what extent is this spelled out for them?
Was this the only fully committing customer you had before starting to tackle the work?
What they are committing, at least financially speaking, isn't a huge sum of money for a business. I think that I'd have concerns that I'd be building something for them that they could easily just turn their nose up at if they don't like it after 2 months - and they wouldn't commit to their side of the bargain of giving you constant feedback for improving the product.
Or the other side of the coin: you wind up building a product that delights them, but you find that it's difficult to sell the solution to others because there are processes your product solves for that first customer that are very unique to them. This is something that would probably always be on my mind.
Hey there, those are all good questions. We did not work with a legal team, we created the proposal on our own.
The 8hrs of total feedback is pretty straightforward. We already met them for 3 hours, we still have 5 to go. The continuous feedback during the first 6 months is still unclear. We thought it would make sense to design this process together with the customer so we didn't have any strict rules.
I totally agree, this is a huge risk. It could very well be that our customer ditch us after 2 months and we have a product that others can't relate to. But we're convinced that building a product that works great for ONE company is still better than an average product for many companies. I hope we're right 😅 It remains a scary process.
I'd be happy to post an update in 4-6 months. By then, we should have our first test results and new paying customers (fingers crossed).
Thanks for the response. Looking forward to the update.
Agreed that developing for at least one customer is better than building for none 😂.
If the terms of the 6 month feedback period haven't been defined - I'd suggest finding a way to incorporate the feedback gathering process within the app itself. I.e. a small survey in app, rather than trying to follow up with each user via email.
From my own testing it seems like incorporating a survey into the app itself dramatically reduces friction for them. It's fewer steps for them to get their valuable feedback to you than email generally is, and emails can be pretty easy to ignore.
Thank you so much for your valuable input! This sounds like a great idea, we will probably do that, thanks again for taking the time and giving me feedback. Really appreciate it.
This is not MRR. This is $3180 of pre-sold product which you still have to deliver.
(Big difference to me)
However, it's still great what you've accomplished - congrats :-)
Hey 👋
Thanks, yes we’re very happy about it :)
It’s definitely no traditional MRR, you’re right. To me, this is the closest form of committed MRR possible.
How did you grow your agency big enough to support this within 2 years?
Hey Lucy
That’s a great question, we created the agency with the sole purpose of funding our startup ideas so profitability has always been the focus.
We focused on a niche that didn’t have too much international competition and started pitching large companies. By charging high prices, we didn’t need many projects to get going.
By doing a good job and being unique, it became easier to generate leads over time and several projects became recurring revenue (which was highly unexpected at first)
I hope this helps? Don’t hesitate if you have any follow-up questions :)
Hah, wow that's crazy. Props to @realDanielAbebe! Only 2 months to go - will you make it?
Thanks Toni! Much appreciated :)
Haha I hope! I definitely feel the pressure, we also had some doubts about the exact product features so it doesn’t help 😅
Will definitely keep you posted!