Urgent.News

What's breaking now, across thousands of outlets.

Tech

The startup trap that kept this longevity app founder stuck

Death Clock CEO Brent Franson says the most dangerous startups can be the ones that seem "pretty good."

Brent Franson, CEO of Death Clock, warns startups about getting stuck in a phase he calls "slow failure." He explains that when a startup isn't viable, founders should fully pivot instead of trying to patch it. Franson spent four years building the mental-health app Most Days, which initially seemed promising but ultimately didn't work as a business.

Users liked the app, but the company couldn't acquire them cheaply enough to build a sustainable business. Franson saw the dangers of "slow failure" - a business that lingers because its leaders keep rationalizing why it might soon work. The solution, he suggests, is to make a clean break and fully pivot to a new idea. Franson describes Death Clock as an "AI private doctor" that estimates users' lifespans based on health data.

The app is designed to suggest changes that could help users live longer. Franson learned three lessons from Most Days: an app people like isn't necessarily a viable business; pivots should be clean breaks, not half-measures; and a good product needs a way to reach customers without heavy marketing spend.

Written by urgent.news from Business Insider's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at businessinsider.com →

More in Tech

How I built a trade analytics dashboard with Streamlit and Plotly — and turned it into a product

I'm an AI/ML student and I build Streamlit dashboards as a freelancer on the side. A few weeks ago I was working on a trade analytics project and realized I was writing the same landed cost logic…

  • Author built LandedIQ dashboard to calculate trade unit economics
  • Uses Streamlit, Plotly, Pandas, and Requests for development
  • Deployed on Railway with manual Streamlit server configuration

AWS Lambda Durable Functions and the Replay Bug in Human-in-the-Loop Agents

Ciao 👋 Here is a sentence that should not be possible: my workflow executed an action a human explicitly did not approve.

  • AWS Lambda durable functions enable long-running workflows with human input.
  • Replay bug causes unexpected behavior when agent proposal is outside a step.
  • Properly structuring code within steps prevents replay bug issues.

More from Sunday 27 September →