How much software revenue recurs after support and hosting cost?
Analyse recurring licences, maintenance, project revenue, churn, gross margin, hosting and development cost. Distinguish capitalised work and founder coding from maintainable earnings.
Does the company own all code needed to build and operate the product?
Audit source-code ownership, contributor agreements, third-party licences, architecture, security, backups, roadmap, customer contracts, support backlog and cloud accounts.
What breaks if a key developer or the founder leaves?
Technical debt, key-developer dependence, weak security and customer control-change clauses can undermine recurring revenue and require immediate investment.
How will releases, infrastructure and customer support continue?
Transfer repositories, infrastructure, credentials, release process, support, product roadmap and undocumented system knowledge with tested buyer access.