Episode Details
Back to EpisodesFailed Software Startup to $350K With Lucep
Description
Zal Dastur's first attempt was a failed software startup that ran out of money. His second startup, Lucep, found SaaS product-market fit by solving a problem he witnessed firsthand - sales teams taking 24-48 hours to respond to online leads while competitors responded in minutes. The startup failure lessons from that first attempt made all the difference.
Zal set a target of 30 beta signups and got 100 by cold calling everyone he knew. He validated willingness to pay by charging $1/user in January, $2 in February, and full price by March - avoiding the software startup mistakes of building too long without charging. Starwood Hotels, Jaguar Land Rover, and Citibank all became customers.
From a failed software startup to a bootstrapped business doing $350K revenue, Zal shares why responding to leads within 5 minutes matters (waiting drops contact rates by 21x), how he funded Lucep with revenue from a previous enterprise product, and why co-founder agreements must be sorted while things are good.
π Key Lessons
- π― A failed software startup teaches cash flow discipline: Zal's first startup ran out of money because they did not find their revenue model until too late. That painful experience made Lucep hyper-focused on cash management.
- π° Charge from day one to avoid failed software startup mistakes: Lucep started at $1/user in January, $2 in February, and full price by March. Any amount confirms willingness to pay and reveals the true value customers place on the product.
- π Respond in 5 minutes or lose the lead: Research shows waiting more than 5 minutes to contact an online lead drops chances by 21x. Lucep built its entire SaaS product-market fit around solving this one high-impact problem.
- π€ Define co-founder roles and agreements before they matter: Lucep started with three co-founders leading by committee with no shareholder agreements. When one left, the lack of documentation created serious conflict.
- π Fund your next startup with your current product's revenue: Lucep used $250K-$1M in annual revenue from a previously sold enterprise product to bootstrap development, avoiding dilution during the critical startup failure lessons period.
Chapters
- Introduction
- Meet Zal Dastur and the Gandhi quote that drives him
- The first failed software startup in Bangalore
- Running out of money and learning cash flow discipline
- Getting corporate jobs before starting again
- How the idea for Lucep emerged from internal frustrations
- Doing things differently the second time around
- Management buyout and corporate structure
- Building the MVP in one to two months
- Setting a target of 30 beta signups and getting 100
- Early days of manual onboarding and lessons learned
- How Lucep's lead distribution widget works
- Responding in under 5 minutes versus 24-48 hours
- Converting 100 beta users into paying customers
- Enterprise product funding Lucep's growth to $1M revenue
- Why they launched Lucep instead of keeping the lifestyle business
- Advice: sort out shareholder agreements early
- Lightning round
Resources
- Full show notes: https://saasclub.io/114
- Join 5,000+ SaaS founders: https://saasclub.io/email