“the kind of thing that you start using when you're like 18 and or 16 or whatever like your first job until you die and you've got an a state that you're like leaving to your kids we're like building a company that needs to be around for the lifetime of its users so yeah so that needs to be calm”

Design for the customer's lifetime, not the product's

Josh frames Maybe as the personal-finance OS someone uses from first paycheck through estate planning. 'Lifetime of the user,' not 'lifetime of the product,' rules out hypergrowth tactics and forces a calm business that survives 60 years. Pick problems where the customer's needs evolve continuously — the software is then never finished, and retention is baked into the problem itself.