A considered acquisition.
An intentional future.

The business matters.
So does the handover.

A transaction is only one part of a transition. The practical work includes understanding your promises to clients, the systems behind delivery, and the knowledge that currently lives with you.

Our services span website design, digital marketing, managed web hosting, and website support. That creates a useful starting point for conversations about businesses and portfolios that need continuing digital care.

We assess opportunities individually. A conversation is not an offer or a commitment to acquire.

Explore the shape
of your next chapter.

Select a starting point. See the questions that deserve attention.

More than a list of websites.

Explore the relationships, active projects, reusable systems, and ongoing work that make up a website-design business.

• Which projects are complete, in progress, or still under warranty?
• Which assets and delivery systems belong to the business?
• What do clients expect after launch?

A credible opportunity
must also be operable.

Strategic fit is not established by a service label alone. The proposed scope needs to make sense commercially, be supportable technically, and have a workable path from current ownership to future responsibility.

There is more than one
way to think about an exit.

Understand the business.
Then discuss the possibilities.

Revenue is one part of the picture. A useful review connects the income to the obligations, costs, relationships, and operational work behind it. No calculator on this page can establish a purchase price.

Revenue quality & commercial terms

We would review recurring and project income separately, renewal schedules, collected versus invoiced revenue, discounts, overdue balances, refunds, and what each agreement includes.

Prepaid services and work still owed need to be understood alongside the revenue already received.

Client mix & relationship health

Account concentration, length of relationships, recent departures, renewal conversations, and reliance on personal relationships help explain the portfolio beyond its totals.

A small number of large accounts can create different transition considerations from a broader group of smaller clients.

Delivery costs & support workload

Hosting, software, contractor, and staffing costs should be considered together with ticket volume, response commitments, ongoing development work, and unresolved issues.

The time an owner contributes is part of understanding how the business operates.

Platforms & technical dependencies

We would identify platforms, integrations, hosting environments, backup arrangements, domain and DNS responsibilities, licenses, and any custom code that needs specialist knowledge.

Platform suitability is assessed account by account. A sale does not automatically require every website to be rebuilt or migrated.

Ownership & permissions

The review needs to establish who owns the assets, which agreements may transfer, and what third-party permissions or client steps may be necessary.

Access should follow an agreed process. Initial discussions do not require passwords, private keys, or a client database.

People & continuity

Responsibilities, documentation, contractors, employees, and the owner’s intended future involvement all influence the handover plan.

Any role after a transaction would need to be discussed and agreed separately; it is not assumed.

Bring the operating picture
into focus.

These are examples of questions a detailed review may need to resolve. The scope of information requests should reflect the opportunity and the agreed confidentiality process.

How does reported revenue translate into ongoing obligations?

• Service schedules, billing records, and renewal dates.
• Prepayments, overdue balances, discounts, and service credits.
• Infrastructure, software, and delivery costs attributable to the scope.

A reconciled view of the revenue base, remaining service commitments, and assumptions requiring further discussion.

Your clients should not
have to figure out the handover.

A considered transition makes responsibilities clear before changes happen. The details depend on the transaction and the services involved.

Agree who communicates with clients, what they need to know, and when they hear it.

A clear sequence.
Room for the details.

Introduction

Discuss the business and what you are considering.

Clear ownership.
Defined checkpoints.

Before execution, a transition plan should answer who owns each action, what must happen first, and how completion will be confirmed. The plan is an agreed working document—not a substitute for transaction documentation.

You do not need a perfect
data room to start.

A concise overview helps make the first conversation useful. Detailed records can follow through an agreed channel if the discussion progresses.

Keep the initial summary high level. Leave out client names, credentials, personal records, and commercially sensitive documents.

A useful first-conversation checklist

Personal planning aid only. Nothing is saved or sent.

Let’s make the
unknowns smaller.

Do you only consider WordPress businesses?

The conversation can include other platforms. We would need to understand the service model, technical requirements, and whether Averane can support the proposed scope. Compatibility is assessed before a commitment.

Can I discuss selling only part of my portfolio?

Yes, a defined group of accounts or services can be the starting point for a discussion. Shared infrastructure, contracts, billing, and operational dependencies would need to be reviewed before deciding whether that scope is practical.

How would the business be valued?

There is no automatic valuation or stated multiple on this page. Any proposal would follow a review of the business and a discussion of the specific assets, obligations, risks, and transition arrangements involved.

Is there a minimum business size?

No public minimum is specified here. A high-level overview helps establish whether a further conversation makes sense; sending one does not establish eligibility or guarantee an offer.

Do I have to stop working immediately?

Your preferred level of involvement is part of the discussion. The scope and duration of any transition work or future role would need to be expressly agreed.

Will clients have to move platforms?

Not automatically. Existing systems, service obligations, and practical support requirements should be reviewed before deciding whether to retain, change, or migrate any part of the setup.

What about my team or contractors?

Their roles, agreements, and contribution to delivery need to be understood. This page does not promise continued employment or engagement; any proposed arrangements require separate discussion.

Can we discuss confidentiality first?

Yes. Raise confidentiality requirements before sharing sensitive information so the parties can agree an appropriate process. Do not treat this public page or a general booking form as a secure data room.

How long does an acquisition take?

Timing depends on the scope, available records, review findings, documentation, and practical handover requirements. Milestones can be discussed once the opportunity is better understood.

What if it is not a fit?

An introductory conversation may conclude without a transaction. Clarifying the fit early can help both sides decide whether to continue, refine the scope, or stop.

Should I involve advisers?

The parties should have access to the professional advice appropriate to their situation when evaluating and documenting any proposed transaction. This page describes a conversation process, not legal, tax, or valuation advice.

What should I send first?

Start with a short description of the business, services, approximate portfolio size, and what you are considering. Detailed financial records and account access are not needed to request an initial conversation.

What could your
next chapter look like?

Tell us what you have built, what you are considering, and what matters most in a transition.

Use the booking notes to mention an acquisition discussion. Do not include sensitive client or financial records.

Additional interactive perspectives

Start with the business you have built: its clients, commitments, systems, and ambitions.

Explore the proposed scope, information needs, and responsibilities before deciding how to proceed.

Sequence communication, access, open work, and operational ownership around an agreed handover.

Agree who communicates with clients, what they need to know, and when they hear it.

Map open requests, ongoing work, billing, and escalation routes to named responsibilities.

Plan the sequence, test changes, and confirm service ownership before the handover is complete.

More than a list of websites.

Explore the relationships, active projects, reusable systems, and ongoing work that make up a website-design business.

Which projects are complete, in progress, or still under warranty?

Which assets and delivery systems belong to the business?

What do clients expect after launch?

Relationships

Commitments

Delivery

Recurring services. Real responsibilities.

Look at the operating picture behind each hosting account before discussing a potential transition.

Which environments and licenses support the portfolio?

What has been prepaid, and which services remain owed?

Who owns domains, backups, and administrative access?

Renewals

Infrastructure

Ownership

Understand the promise behind the plan.

A website-care portfolio includes expectations, workload, and accumulated knowledge—not just a monthly invoice.

What is included, excluded, and handled as additional work?

Which requests are open and who is responsible?

What knowledge must move with the relationship?

Scope

Workload

Knowledge

How does reported revenue translate into ongoing obligations?

Service schedules, billing records, and renewal dates.

Prepayments, overdue balances, discounts, and service credits.

Infrastructure, software, and delivery costs attributable to the scope.

A reconciled view of the revenue base, remaining service commitments, and assumptions requiring further discussion.

What needs to remain reliable throughout a change in ownership?

Platforms, environments, integrations, and supported versions.

Backup and recovery arrangements, administrative ownership, and dependencies.

License restrictions, custom code, and specialist support requirements.

An environment inventory and a clear list of constraints to address before considering technical changes.

How is the work delivered, and where does knowledge sit?

Support queues, service scopes, unresolved requests, and active projects.

Responsibilities across the owner, team, and external providers.

Documented procedures and activities that rely on undocumented knowledge.

A practical view of workload, coverage, and the knowledge-transfer work needed to support continuity.

What must be agreed before responsibility changes?

Communication ownership, access sequencing, and billing arrangements.

Required permissions, third-party dependencies, and readiness conditions.

Open exceptions, escalation routes, and completion evidence.

A proposed handover sequence with accountable owners, dependencies, and checkpoints for mutual agreement.