pull down to refresh

I'm considering building an application specifically designed for use by insurance companies and banks. Before diving into development, I'd like to validate the idea to ensure it addresses real needs in the industry. What steps should I take to effectively validate the concept, assess market demand, and gather feedback from potential users? Should I conduct interviews, use surveys, or create a prototype to present to stakeholders? Additionally, what are the key metrics or indicators that would confirm this app idea has strong potential before I start coding?
Anything enterprise like that you don't build it until you've sold it, enterprise has a long (uncertian) sales cycle.
Wireframe/Clickable prototype in a tool like UXPin (maybe even v0 these days), and a presentation deck... approach clients with that and iterate, only build it once they've paid you to start building it.
Depending on the value prop you'd bill this out as a study/readiness program.
reply
bill this out as a study/readiness program
how so?
reply
Since you don't necessarily have a product to sell yet, you'll want to position as a consultant to start iterating with them. This would be a step 1 contract to study their requirements or identify things they'll need to do to be ready to take advantage of your new tool.
reply
designed for use by insurance companies and banks
You still think that banks are the future? Why would you do such thing for them? Instead fuck'em, do something for Bitcoin.
reply
the plan is to extra as much value as i can out of them and convert to bitcoin.
reply
In other words, you want to create more fiat instead of creating a bitcoin circular economy. Right... so we will never gonna make it.
reply
i'll offer crypto but that's not their preferred payment method.
reply
i'll offer crypto
yeah, is clear, you are still in that phase of shitcoinery, when not even you don't know what to do.
reply