First pilot SaaS: recommandations?
Hi all,
This is my very first post on the IndieHackers forum!
I spent some time on the forum, and was amazed by the level of goodwill and collaboration this community shows every day. I see people building stuff like I do, and it already feels like home!
I have been working for 2 month on a SaaS product, and I am now doing a free pilot with a 4-people team. I would love to hear what are your thoughts/recommandations on driving a successful pilot, and some tips/tricks around keeping the excitement/interest for the projet high. What would be in your opinion the most important things to "check" when doing a pilot?
Thanks so much in advance for your input! Enjoy the rest of the week-end
Congratulations on your first pilot and first post!
I would suggest picking 3 assumptions that you are looking to validate. I'm sure you have a long list of assumptions about your project in your head. Assumptions like, "I think my product meets their needs", "they will pay for this", "I can acquire more people like them". Just pick 3 for this round and keep an eye out for queues that will validate or invalidate your assumptions. I would try to ask them "why" questions that aim to invalidate your assumptions (so that you are pleasantly surprised when your assumptions are validated!).
You will likely have more chances if they like the product. If they don't like it set up an exit interview to try to better understand why they didn't like your product and record the audio so you can refer back to the meeting.
Regardless of the outcome, you should feel like you have accomplished something because you have. Keep up the good work!
Hi Phil, thanks for your recommendation – I like how you suggested to try invalidate some of the assumptions, will definitely prepare this for my next discussions. And thanks for the encouragement, it's very nice!
welcome! first post! whoot!!
Thanks John ;)
As a user, for me the interest would be kept high by:
Hey Jaymie, thanks for your feedback! Super interesting, I think a roadmap could show them the product is getting better and better – I encourage them to give me feedback and I do have regular meetings, I would love to be able to show them improvements based on their inputs. Have a nice day!
It's a very good question!
From what I gathered there is a "correct" way to do it, and it's iterate, iterate, iterate.
I know that doesn't say much but here it goes in more detail:
1- What's the most important thing you need to test with the pilot? ( For example, what part of the lean canvas is more risky? What assumption are you making that you have no data to prove it's correct?)
2- Focus on having testing point number one.
3- Talk to your users. Interview them and squeeze them for the most amount of information possible.
That's the basic, I guess. Reading "Lean Startup" is really important too, as well as "Lean Costumer Development". Also another indie hacker shared a great sum up of his experience: https://twitter.com/KarthikS2206/status/1379657618130493441
I'm always up to talk a bit more about it/give a outsiders perspective if you need :) if so, just send me an email, with the subject indie hackers to jigui.17 [at] hotmail [dot] com
Hi Joao, thanks for your input! Funny how reading/learning about entrepreneurship can be different from actually practicing it! I did read the Lean Startup a few years ago, but completely put the methodology aside for that project – will definitely look into this, it should help me mitigate risk indeed. Cheers