Hi all,
An acquaintance approached me with a business idea.
BUT
It would require a LOT of upfront time. She wants:
Also, it's not validated per se. We don't really have any contract where someone will pay us money. She just says that she was in need of that app when she was working in this domain and that her colleagues told her, that this app would be useful.
We all know from the mom test, that this is not a real guarantee that someone will buy.
She doesn't really have the lean startup mentality. She wants every single feature programmed out and I cannot convince her of the opposite.
Every feature for her is basically necessary.
What would you do in my position?
The easiest job 'interview' test ever is to ask the person to complete a task. In this instance, all that I can see she has provided is 'they said, I think, therefore it is correct'.
Ask her to provide you with a short presentation on the industry, opportunity etc. Act like a VC but instead of money, it is your time that will be invested. Personally, I do agree that MVP's are crappy and if you can build the whole thing out with core features and test, then do it.
If she believes the opportunity it so high she should be able to approach people outside of her circle and get their opinion. Matter of fact, she could get a simple landing page built and reach out asking for feedback. Lean startup or not, unless she has the cash and certified research to say that this is a sure-fire success (this is impossible) you either walk away or pitch the lean startup idea over and over again.
"Personally, I do agree that MVP's are crappy and if you can build the whole thing out with core features and test, then do it."
=> So you mean MVP's are not the way to go? But isn't the product with the core features called an MVP?
I have another idea of "core features" than she has. And basically IMO i could build my version of the app, but not hers, since it's too big and uses tech I would still need to learn.
That's the problem with the MVP definition. As a developer, you may assume that 1 or 2 features are core whereas it could be that there needs to be a number of core features to enable a workflow. No workflow or having to change your workflow because of a shiny new app is never going to happen.
Viability is determined by the customer not the founder/hacker as domain knowledge and experience is often missing with these projects. I worked with a software company that provided a platform for an industry that no one on the team had ever spent any time in. The gaps in the product was insane.
Doesn't sound like a business partner you'd be able to work with long-term, point blank. You have different methods, different ideas and seemingly no way to find a middle way.
Thanks for the input :)
I think @Melomal is very right in what he says. It sounds to me as if you and your business partner are far apart in your ideas. If you don't come closer to each other, then leave it alone. I say this from bitter experience, if the interaction is not right at the beginning, it will be very difficult with the cooperation. I have always hoped to convince my partner of important things, the cooperation was really fun, despite the sometimes big differences. But in the end the deal failed and I now have a wonderful app worth $300000 lying around. That's a pity for the great programming.
Hey, thanks for your insight :)
Ask for the market opportunity. How to build traction. Marketing strategy. Pricing. How to engage with the audience. Do you go full in and quit jobs. To have the actual product/SaaS/piece of software is useless when you have no one actually using it. She might not have the mindset for such undertaking yet and thinks when the tech is available, everything else will come automatically. When I started my indiehacking journey two months ago, I was completely off the charts with my expectations. I get the full reality check at the moment. I'm rock bottom. Can't even get likes for my posts on Twitter/LinkedIn :)
Hey, thanks a lot for your insights.
I guess everyone has to go through that phase, where they get slapped in the face by the truth :D
The details surrounding customer acquisition are important. Even if the product is obvious, acquisition might be hard (process and/or cost).
Having worked with various cofounders over time, beware of idea people. It's easy to dream all day and hand-wave the rest. Your business cofounder needs to be good at "executing" business, the E in CEO.
I once tried building an app with a lady who had a similar attitude. Didn't work out and I called it quits after two weeks of failing to work together. 0/10. Would not recommend.
Thanks a lot :)
Are you a cofounder with her. Or is she paying you fee to built it?
I would be a co-founder.
Has your co-founder ever successfully launched a saas product? It's possible they think understanding the real market problem is easy because they would have been a buyer of your non-existent product.
It's possible they've never heard the term pivot applied to SaaS. I would draw some examples of costs associated with needing to pivot after a 1 month mvp build vs a 9 month full build.
There's no way that in 2021 we should be launching anything that is feature complete without first doing something resembling an MVP.
Hey
No she's never been a founder and she has low tech knowledge.
"It's possible they've never heard the term pivot applied to SaaS. I would draw some examples of costs associated with needing to pivot after a 1 month mvp build vs a 9 month full build."
This statement is amazing :)
We were all at that point sometimes with a project which turned out to not be successful, right?
Honestly, I would try to avoid working with someone with this mindset, this will never work out.
Thanks for your input :)
Explain politely and nicely that you're not currently looking to invest everything you have into a 50-50 deal and that due to your circumstances you simply can't take risks, etc, etc, but that you might be open to starting out on a paid consultancy basis. If she gets funny about "why won't developers work for free" then you've escaped a bullet.
Perhaps you can explain that you feel the strategy isn't quite right and to be a cofounder you'd want a lot more say and control. Have you actually done this or are you testing it out on us first?
It was clear from the beginning that I would be a co-founder...
No I'm not testing on IH first.
yeah I think it's a lesson many of us have learned, but occasionally we make the same mistake again!
it is a cheesy comparison, but,... meeting and dating someone, deciding to move in together, combining bank accounts, buying a house together, having kids,..... sometimes as startup founders we do the business equivalent of all this in the space of a week. And guess what, it goes wrong!!
Cofounder dating, as many have said here before, and many will continue to say needs to be rejigged. It aint working the way we do it right now.
So do you want to say that indiehackers should spend more time evaluating potential partners?
Yes I do!! Would you agree with that?
Yes :)
A lot of us have fallen for this. I'm getting out of the same mistake right now. Hold out for the right opportunity.
Can you share your story?
Sit her down and have a heart-to-heart conversation with her. Be vulnerable and lead your actual feelings, don't be accusatory, so she won't get defensive. Just like with a romantic partner, communication is important.
If she can't take positive and constructive feedback and improve, don't work with her. You want to work with talented people. That's a huge warning sign.
Thanks a lot for your advice Allen!
Hey!
I am happy that you have an opportunity to work on an exciting project! I am not sure how busy you are and how important experience is for you so the answer will depend on that.
I am working in a company that is right now pivoting towards software solutions, and their main distribution channel is salespeople. As the obvious part of a successful part of any business is solving burning customer problems you need to be close to them. Whilst talking to salespeople about any new product, they initially agree but their first request is to see a working MVP. I believe that is the crucial gap we as developers need to overcome.
If I were you I would do a detailed rundown of the time it would take building such MVP, with an exact specification of all the features and so on. This will visualise for your partner the effort ( time and cost) that is needed to complete the MVP. Then as said in other comments I would create mock ups of the products and start interviews with potential target groups discovering their needs.
Hopefully this helps, if you have any questions dm me
Hey, thanks a lot for your insights :)
Get some screenshots of the app: backend and mobile (but without implementing it), have a form on your landing page to capture emails, drive traffic to it and see how much interest you get.
Do this even if she disagree, that's the right way to start.
Couldn't agree more!
I wanted to do this, but I lack the UI skills :D I need to definitely learn that.
Good UI is essential for an early-stage startup — you definitely need a co-founder or contractor who can do it well and iterate and adapt quickly. It's no matter how complicated and unique your backend is — if your app doesn't look good it will be so tough to grab early users' attention and nearly impossible to make them use it. Learning UI is time-consuming, you need a couple of products built before you can produce something that looks "ok".
Reach out to designers you know and chances are — someone will be willing to help. I have some friend who likely will be good to help you (need to understand domain) with creating a landing page in Webflow and dynamic UI prototype in Figma — ping me if you up to.
Secondly, you mentioned that the app needs to be in Flutter and you need time to learn it too. That's another big friction point and learning curve that will delay your MVP launch further.
Why do you 'have' to use Flutter? There are tools that might be easier, starting from no-code ones going to PWA/Ionic and react-native. You can launch your app with some knowledge of React, so why limit yourself to the tech you've never worked with? In addition, Flutter isn't mature enough and you'll likely struggle with the tech itself, instead of being focused on the app's functionality.
So to recap — focus on what you good at and seek help extensively on areas you're not comfortable with (or heavily optimize them). Choose the way that will allow you to deliver and iterate very quickly (meaning days or even hours, not weeks).
P.S. You asked great questions so you're on the right way, good luck with your app in any case!
Have you shared information about lean startup with her? Maybe if she read the HBS article on it she'd understand where you are coming from.
Yes I've shared this with her. Her response was:
"Well how can I sell someone an app which isn't built yet or if its buillt and doesn't have a lot of features".
That’s a red flag in my opinion. Help her learn by reading the Lean Startup, the Mom Test, and other books. It’s important to understand you can sell without needing most of what she think she needs.
This comment was deleted 4 years ago
How can I convince her that she can sell the app with not all the features?
This comment was deleted 4 years ago
You have to explain her that having an app ready does not mean you have a machine which is generating revenue) MVP is not about technical things, it is about acquisition channels and costs of the clients:)
I'd tell her that since I'm (you) building the app, I would want to test if the idea is viable and I would want to do that as soon as possible with an MVP. You should show her the benefits of this process and method.
Now, having said that, if there's already a disagreement about how to go about doing business, there's probably going to be other disagreements in the future.
Good luck
Hey
Thanks for your insights. I haven't had any success in the past with a SaaS, but I know the failures from others. I tell her that(that we should follow the lean startup approach) and I think she isn't convinced of this approach. She isn't really part of the tech world and therefore I assume she doesn't really understand the process.
I guess we have to part in 2 ways.
Few ideas
The approach is less important than the investment.
The lady could be right about the right approach for a particular industry. In some industries trust and credibility are not to be risked with promises of a working product at some point in the future.
Theres's a concept in contract law callled 'misrepresentation' that can have serious consequences if the other party assumed that they were buying a finished product.
It can be okay to play with landing pages and deliver the solution 2 years later when lives and profit margins are not at stake... Nobody is going to court over a 'to do list' app that never worked.
The real issue is the investment. The lady has to invest enough money to cover at least half of the development costs. Development is not the most important thing but it's the hardest thing, and it has to be financed properly. People become more reasonable when they have to finance the software requirements.
I'm not sure if I get your point. She doesn't have to cover the costs, since we're both founders...
I mean she doesn't have to pay me, because we'll split the profit
You need to compare your initial investment to your co-founder's initial investment and make sure the partnership is fair.
This comment was deleted 5 years ago
That's called a slave overseer mate... That's not what a co-founder is supposed to be. Making you code for years with no investment of comparable value... I'd rather be on my own.
This comment was deleted 5 years ago
Your spare time is valuable. The time you spend on a project is time you cannot spend on another project or with your family (economists call this concept opportunity cost). If the business idea is as big as sliced bread, then it could be fair that the founder only invests his business idea. It depends on what you feel as a co-founder is a fair partnership.
Not that I disagree with anything you've written or any of the other comments, but a couple questions:
Nice. I think talk more to users is the big one.
This comment has been voted down. Click to show.
Bro, chill! It's not that serious!!!
This comment was deleted a year ago
Thanks a lot!
This comment was deleted 4 years ago
Hey, thanks a lot. Will look into it. :)
front page of Gumroad from 2011: https://web.archive.org/web/20110407095836/http://www.gumroad.com/
This comment was deleted 4 years ago
Thanks for your opinion :)