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.
Report
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!
No, I have not but I think that would be such a cool flex to have haha.
Report
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?
Report
like "I got this idea for a bridge to sell you", no not yet but teach me!
Report
Yes... is what every Enterprise Software sales rep will say π€«
Replies
Owwly
Owwly
PerceptInsight
Flow State Training