Sell a web agency

Sell a web agency: 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.

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.

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 web agency: retainers and projects, margin and utilisation, client concentration, code and design rights, hosting responsibility and team skills

To sell a web agency, make retainers and projects, margin and utilisation, client concentration, code and design rights, hosting responsibility and team skills 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 web agency

Explain retainers and projects, margin and utilisation, client concentration, code and design rights, hosting responsibility and team skills, 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 an anonymised mandate schedule, revenue and margin by service, contracts, work in progress, repositories and IP, hosting and vendor accounts, staff and freelancer terms, pipeline and support obligations. 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

Digital agencies and technical successors may fit when they can maintain development, design, hosting and account support. 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 client sites before launch, code, credentials, analytics, commercial terms, personal data and security information. 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 each client with scope, repository, deployment, domain and hosting, licences, open work, support, access and a new account lead. Build a handover list for open work, responsible people, access, deadlines and introductions before the seller's availability reduces.

Related seller guidance for a web agency

Compare the broader category or return to the main seller page: sell a company and Consulting & agencies.

Questions to resolve before selling a web agency

How should I demonstrate retainer and project margin after all delivery hours are counted?

Show several comparable periods and evidence for retainers and projects, margin and utilisation, client concentration, code and design rights, hosting responsibility and team skills. Reconcile financial claims with an anonymised mandate schedule, revenue and margin by service, contracts, work in progress, repositories and IP, hosting and vendor accounts, staff and freelancer terms, pipeline and support obligations and distinguish transferable performance from work or relationships that depend on the seller.

Which client, code, design, hosting, licence and access records should I compile?

A focused file should include an anonymised mandate schedule, revenue and margin by service, contracts, work in progress, repositories and IP, hosting and vendor accounts, staff and freelancer terms, pipeline and support obligations. Explain gaps and exceptions before they affect valuation, warranties or the timetable.

What should I disclose about founder-led accounts, freelancers and recurring hosting duties?

Identify which parts of retainers and projects, margin and utilisation, client concentration, code and design rights, hosting responsibility and team skills 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 projects, renewals, credentials and administrator access move without interruption?

Transfer each client with scope, repository, deployment, domain and hosting, licences, open work, support, access and a new account lead. Test the transfer on real open work and record who owns every remaining exception after completion.