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 company: IT & software
Sell a company: IT & software: create a listing on company.ch with category, location, guide price 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.
Selling an IT or software business: value, evidence and handover
When selling an IT or software business, the listing should explain recurring revenue, retention, product rights, technical quality, infrastructure, security and dependence on founders or key developers. Buyers need evidence that the operation, people and rights can continue after completion without exposing source code, vulnerabilities, customer environments, credentials, personal data and unpublished roadmap information in the public offer.
Explain what creates value when selling an IT or software business
The public profile should make recurring revenue, retention, product rights, technical quality, infrastructure, security and dependence on founders or key developers measurable and separate recurring performance from one-off results. It should also state what the owner still handles personally and which assets, contracts or premises are part of the proposed sale.
Prepare the evidence a buyer will request
Prepare revenue cohorts and contracts, churn, licence and IP records, architecture, repositories, dependencies, cloud costs, incident history, roadmap and team roles. Reconcile every financial summary to the same sale perimeter and identify consents, licences or third-party rights that require a separate check.
Reach buyers with the right operating fit
Software companies, IT service groups and technical operators can fit when they can maintain the product, support customers and manage security. The listing should make essential qualifications, capital, location and owner involvement clear enough to filter enquiries without narrowing the search to a single buyer type. Keep source code, vulnerabilities, customer environments, credentials, personal data and unpublished roadmap information out of the public listing and first document pack. Use anonymised concentration, ranges and role descriptions until a buyer has been qualified and the information is needed for review.
Plan continuity through the handover
Inventory repositories, domains, cloud, secrets, third-party licences, customer environments, support queues and deployments, then rotate credentials during transfer. Assign responsible people, dates and completion evidence rather than describing the seller's support only as an undefined transition period.
Related seller guidance for an IT or software business
Explore the relevant industries or return to the main seller page: sell a company, IT service provider, SaaS company, Software company, Web agency, Website project and Domain portfolio.
Questions to resolve before selling an IT or software business
How should I evidence recurring revenue, retention and support cost for an IT or software sale?
Use several comparable periods and show the figures that explain recurring revenue, retention, product rights, technical quality, infrastructure, security and dependence on founders or key developers. Separate recurring operations, exceptional events, owner adjustments and any assets or costs outside the proposed transaction.
Which code, licence, security, infrastructure and ownership records belong in due diligence?
Prepare revenue cohorts and contracts, churn, licence and IP records, architecture, repositories, dependencies, cloud costs, incident history, roadmap and team roles. Start with aggregated information, then release original documents in a controlled process once the buyer and transaction fit are credible.
What should I disclose about dependence on founders, key developers or third-party platforms?
Test how recurring revenue, retention, product rights, technical quality, infrastructure, security and dependence on founders or key developers would change when the current owner steps back. Identify reliance on individual customers, employees, contracts, premises or permissions and explain the practical measures available to reduce that dependence.
How can repositories, cloud access, releases and customer support transfer without downtime?
Inventory repositories, domains, cloud, secrets, third-party licences, customer environments, support queues and deployments, then rotate credentials during transfer. Turn these topics into a timetable with owners, access, introductions and a clear point at which the buyer operates independently.