Prevailing wisdom says build a landing page and do pre-sales before writing a single line of code.

But is this always the right advice?

What happens if your SaaS has a simple value proposition but a deep technical moat behind-the-scenes to deliver it reliably, robustly and simply? To get something in the hands of users that actually delivers, is it ever OK to build out an initial prototype and then market? Especially if the core idea is coming from a deep place of need/gap.

--

i'm asking for myself! I'm building Tract Stack: no-code analytics website builder to grow your business, https:/tractstack.com

* It's not just another website builder with analytics included! People need effective ways to woo their audiences and make a significant impression on each prospective buyer while they are yet in the funnel (before they leave the web page). The core mechanics of Tract Stack are basically a more atomic reconstruction of a 'website'. It breaks out of traditional web 2.0 and opens a quantum of surface-level effects. Under the hood a knowledge graph is being generated based on user interactions. This is fed back in real-time **while the users are yet on-page and in the funnel** allowing for a personalized experience

A live prototype is up and running. I've got another month of work to finish the 'visual editor / wrapper' around this tech so anyone can build their own dynamic websites. Thus far my focus has been on product development and not doing validation or building a waitlist.

Any advice for making this transition to user conversations and product validation?