#Help - Should we go to market with, or without case studies?
#Help - Should we go to market with, or without case studies?
Hi we're Budibase, an open-source web app builder with a focus on speed and customisation.
We're currently building the web app builder, but we have a question for the Indie Hackers commu
Trending on Indie Hackers
We've adopted an Agile approach to product development. I would release to market ASAP and gain feedback from users along the way. Quick feedback > examples.
Option 1
Totally agree. Even without examples you will get at least feedback what is very valuable and will help you to avoid some mistakes.
If you create examples you will not only spend your time you will probably waste it if you make mistakes you could avoid.
Very fair points. One argument is we want to put the builder through its paces first. Make sure it's top notch when launched.
But your points are valid. I think people just want to get their hands on it and build for themselves.
If you create examples you will not only spend your time you will probably waste it if you make mistakes you could avoid.
This is a great point which I will feedback to the team.
Your comments are really appreciated. Thank you and have a lovely day.
Thanks for your feedback. It's a tough call. Theres advantages to both arguments but I think we might be leaning to option 1 too
Awesome site so far! Love that you are going open-source!
I think Option 1 is generally, the better call (even if it‘s difficult one to make), release and get feedback as soon as possible...
You're too kind.
Option 1 seems to be a clear winner. I think we're just eager to build with it ourselves. Building apps with the builder before launch allows us to test it. But we could always launch the builder while we use it to develop products with it.
Your comments are really appreciated Janniks. Thank you and have a lovely day.
I'm a potential customer. Give it to me asap and you'll get an example!
Haha I've sent this comment to the team. Love it! Straight up, no bs!
If we released the builder without the hosting and management platform, would you still be keen to use it? You could pull it down locally and build with it. This way we could release it quicker.
Yeah, here's my perspective.
As a non-technical individual, the "hosting" and "management" should just work. "Here's my app, run it for me in the cloud, I don't care how." It's the builder itself which will largely determine whether or not I invest my time and money on your platform. If the builder sucks, having the best hosting and management on the planet doesn't get me to be a customer.
I think you want to de-risk the builder aspect as quickly as possible, which means making it available to a handful of customers serious about building with BudiBase and asking them for raw, honest, and frequent feedback.
That's what you'll get from me lol
Also, cheers for the feedback. Appreciate it Andrew!
I would go with option 2. It's always easier to market/sell when there's examples to fall back on. It builds confidence with your audience.
Thanks for your feedback.
Have you any examples of where option 2 paid off?