Single listing
For one business with a selectable duration.
CHF99per listing
1 month
Excl. VAT.
- Publish 1 listing
- Anonymous or visible contact details
- Save as draft possible
Register free
No payment before publication.
Sell a SaaS company
Sell a SaaS company: prepare a clear listing on company.ch with location, guide price, revenue and handover. Choose open, discreet or anonymous visibility while private seller data stays protected.
Subscription
For regular sellers with several listings.
CHF99per month
3 active listings
Billed yearly. Excl. VAT.
- 3 active listings at the same time
- Anonymous or visible contact details
- Change package before publication
Register free
No payment before publication.
Sell a SaaS company: recurring revenue, retention and expansion, customer acquisition, gross margin, product rights, security, infrastructure and founder dependence
To sell a SaaS company, make recurring revenue, retention and expansion, customer acquisition, gross margin, product rights, security, infrastructure and founder dependence verifiable and show what a buyer can continue after completion. The offer should connect commercial performance with the contracts, people, assets and permissions that produce it.
Show the transferable value of a SaaS company
Explain recurring revenue, retention and expansion, customer acquisition, gross margin, product rights, security, infrastructure and founder dependence, the owner's current duties and the exact transaction perimeter. Historic results, current pipeline and forecasts should be separated so buyers can test what is recurring rather than relying on a headline turnover figure.
Prepare industry-specific records and evidence
Prepare MRR or ARR bridge, cohorts and churn, contracts, deferred revenue, acquisition and support metrics, code and IP ownership, architecture, cloud cost, security, roadmap and team roles. Mark ownership, term, notice, transfer restrictions and any consent required; financial data and operating records should cover comparable periods.
Qualify buyers for the operating requirements
Software companies, investors and technical operators may fit when they can maintain product, security, support and customer success. Screen for the capabilities that protect continuity as well as available capital, and explain which skills can be transferred during an agreed induction. Do not publish source code, credentials, vulnerabilities, customer data, contracts, roadmap and security architecture. Use anonymised segments, ranges and aggregate performance to support initial evaluation, then open identifying information only for a justified review step.
Transfer work, relationships and access safely
Transfer repositories, cloud and vendor accounts, secrets, domains, billing, support queues, deployments, incident response and roadmap ownership with access rotated. Build a handover list for open work, responsible people, access, deadlines and introductions before the seller's availability reduces.
Related seller guidance for a SaaS company
Compare the broader category or return to the main seller page: sell a company and IT & software.
Questions to resolve before selling a SaaS company
How do I substantiate recurring revenue, retention, expansion and gross margin in a SaaS sale?
Show several comparable periods and evidence for recurring revenue, retention and expansion, customer acquisition, gross margin, product rights, security, infrastructure and founder dependence. Reconcile financial claims with MRR or ARR bridge, cohorts and churn, contracts, deferred revenue, acquisition and support metrics, code and IP ownership, architecture, cloud cost, security, roadmap and team roles and distinguish transferable performance from work or relationships that depend on the seller.
Which contract, code, IP, security, infrastructure and cohort records should I prepare?
A focused file should include MRR or ARR bridge, cohorts and churn, contracts, deferred revenue, acquisition and support metrics, code and IP ownership, architecture, cloud cost, security, roadmap and team roles. Explain gaps and exceptions before they affect valuation, warranties or the timetable.
What should I disclose about founder dependence, churn concentration and third-party platforms?
Identify which parts of recurring revenue, retention and expansion, customer acquisition, gross margin, product rights, security, infrastructure and founder dependence depend on the seller, individual employees, major customers, suppliers, premises or permissions. Quantify concentrations and explain which safeguards or transition steps can make the operation less dependent on them.
How can repositories, billing, deployments and support transfer without customer downtime?
Transfer repositories, cloud and vendor accounts, secrets, domains, billing, support queues, deployments, incident response and roadmap ownership with access rotated. Test the transfer on real open work and record who owns every remaining exception after completion.