ARR, bookings and cash: three startup numbers that should never share a label
A recurring-revenue business needs to distinguish its commercial run rate, signed commitments and actual collections.
TOPIC
Every Foundra story on SaaS, newest first.
13 stories to explore
A recurring-revenue business needs to distinguish its commercial run rate, signed commitments and actual collections.
Read gross and net retention together to see whether expansion is masking losses in the existing customer base.
The right trial length follows the customer’s path to value. More days do not fix an experience that never reaches the important task.
A long introductory tour can compete with the work a new customer came to do. Contextual help can make the first task more manageable.
A pipeline forecast is useful only when its stages correspond to things the customer has actually done.
A marketplace can put a product near an existing customer workflow. Discovery, activation and ongoing support still need deliberate design.
A growing collection of customer information can create costs and responsibilities that outlast the feature it was gathered for.
A startup can make procurement easier by answering specific questions about access, data, recovery and responsibility before a buyer asks.
Being able to view code does not by itself explain what a company may do with it. Product planning needs the actual licence and its conditions.
A successful backup job does not prove a startup can recover its service. Restoration needs its own plan, test and owner.
Clear publication dates, accessible article text and accurate metadata give a news page a sound technical foundation. They do not replace useful reporting.
A relevant image can help a reader understand a story. Filenames and metadata should support that purpose rather than attempt to disguise a weak visual choice.
Fast pages are about more than a loading indicator. Readers need stable content and controls that respond when they use them.