like "I got this idea for a bridge to sell you", no not yet but teach me!

Not really, I’d rather take the time to build something solid, test it, and know for sure it’s going to deliver great value.

No, I have not but I think that would be such a cool flex to have haha.

Yes... is what every Enterprise Software sales rep will say 🤫

My soul

While it might be tempting to sell something that is yet to be built, I think this approach has its perils. Especially in software engineering things can get complicated very quickly. You might find yourself spending more time than what you should and in case the deal does not get closed it's a double whammy. Long story short - not a good idea.

Yes. I do it all the time. It seems scary but it's way better than spending hundreds of hours building something no one wants.

Personally, I think I may have done it before 😂 I have been influenced by my boss to 'sell first and figure out later' 🤣 It works especially when you're starting out since you get to explore different things and discover what you're good at (and what you're not)! It also helps you improve and make sure you deliver in the end. But now, I also do the bare minimum before trying to sell so it saves me time and effort! 🤩

Oh, Casper, you're diving into the entrepreneurial waters with a splash! Selling something before it's built, huh? That's like promising a unicorn to someone and then figuring out how to catch one 😂

Hi Casper! Interesting question. Once, I pitched an idea for a mobile app to a small business owner before writing a single line of code. I just had some rough sketches and explained how it could help his sales. To my surprise, he loved it and agreed to invest upfront. That commitment really motivated me to build it quickly! Sometimes, taking that leap can lead to great opportunities, right? Have you ever found that selling first influenced how you developed the product afterward?

I used to avoid selling or promoting things before they were fully built, but recently I've been experimenting more with a 'build in public' approach. Sharing progress updates and getting feedback as I go seems to keep people engaged and excited to support the finished product. It's working well so far, but I'm always open to trying new tactics! 🚧👷♂

I did NOT even after it's BUILT 😹😹😹

I haven't tried selling something before building it yet, but I think it could work well if you have a strong reputation and track record of delivering. Building in public seems like a smart approach to get early feedback, generate interest, and show your progress. I guess it depends on your specific product and audience. Looking forward to hearing others' experiences with this!

I've done this with Beta customers. I've also sold functionality on a more mature product that is still to be delivered. I'd always say be 100% transparent, though. Obviously for ethical reasons but also, long term the reputational damage you'll do your business will do more harm than the upside of booking revenue. Depends on the product or feature too, and the level of risk in the build!

Good ideas can be sold! :P

I've done this before for a client project - took pre-orders to gauge demand and fund initial development. It worked out, but definitely some risk involved. These days I prefer building in public like you mentioned. Keeps me accountable, surfaces issues early, and gets people invested in the journey. When they see your progress and dedication, supporting you feels natural. Building an audience as you build the product is powerful. But pre-selling can work in the right situation if you're confident in your ability to deliver!