Website management in a shared account
Explore web hosting options for brand websites managed by the same team. Consider shared resource usage and account access across the websites.
Web hosting options →Keep client websites, access permissions, email and renewals visible in one list. Let's assess the right hosting setup for your agency using a project inventory, a pilot website plan and a written scope.
Consider the access each client needs and the management required by their applications, alongside the number of websites.
Explore web hosting options for brand websites managed by the same team. Consider shared resource usage and account access across the websites.
Web hosting options →Consider a reseller setup if your clients need separate control panel access. Assess the account count, resource allocation and licence coverage together.
Reseller hosting options →Explore server options if you need custom services or operating system access. The team responsible for system and application maintenance is part of the scope.
Virtual server options →At each stage, make clear what information is needed and what will be documented. All work, including any pilot project, and any fees are defined in the proposal before implementation.
| Stage | Information needed | What we clarify together | Deliverable |
|---|---|---|---|
| 01 · Inventory | Websites, applications, storage, mailboxes and renewal dates. | Which clients need separate accounts, different resources or priority migration. | A single project list to guide service selection and proposal preparation. |
| 02 · Pilot website plan | A website representative of your portfolio, plus critical form, login and email workflows. | The pilot's scope, owner, tests and rollback conditions. | A pilot checklist and a migration sequence for the remaining websites. |
| 03 · Written scope | Account structure, management expectations, licences and billing period. | Included services, additional work, support boundaries, initial-term and renewal prices. | A comparable proposal and a list of each party's responsibilities. |
Example client handover record: Domain owner: client company · Technical access: project-specific user · Licence owner and scope: as recorded in the agreement · Renewal: date, billing contact and notification address · Handover: latest backup and access review.
Review temporary agency permissions at the end of the handover. Do not enter passwords in this record; grant access to the new authorised person through a secure channel, account by account.
Enter the amounts from your own proposals to calculate your monthly total, per-client share and first-year budget together. The amounts you enter are not sent or saved.
Enter all recurring expenses as monthly amounts in TRY, excluding VAT. Divide an annually paid licence by 12 before adding it. Do not enter a service a second time if it is already included in the hosting price.
The calculation distributes costs equally among clients. If a busy store and a company website use different amounts of resources, calculate the groups separately. Tax, payment collection, overheads and sales profit are excluded from this calculation.
This tool does not generate Ajans Hosting sales prices. Compare reseller resources and calculate your own initial-term and renewal proposals separately.
Recurring monthly amounts are assumed to remain the same for 12 months; the one-off charge is added only to the first year. If renewal prices change, calculate that period using the new amounts.
The division of responsibilities below is a starting point you can adapt to your own client agreement. Define the boundaries between application maintenance and hosting support from the outset.
| Business | Agency / client responsibilities | Details to include in the service scope | Handover record |
|---|---|---|---|
| Domain ownership | Keep the client's registrant details and recovery address accurate. | Who manages DNS and holds transfer authority. | Registrant, renewal date and authorised contact. |
| Content and application | Identify who approves content, holds theme/plugin licences and handles maintenance. | Work included in application support and development outside the scope. | Version/licence list, latest update and test result. |
| Backup and recovery | Define an acceptable data loss window based on how often the data changes. | Coverage of files, databases and email; retention and restoration procedure. | Last tested backup, recovery steps and authorised person. |
| Incidents and support | One responsible person gathers the client's observations. | Support channel, scope of work and escalation route. | Record of the affected website, time, error, action and outcome. |
| Renewal and handover | Identify who tracks payment and client approval. | Initial-term/renewal price, cancellation and account handover steps. | Approval, final backup, access handover and removal of previous permissions. |
Report technical incidents using the support request template; use the interactive migration checklist during a transition. Do not add passwords to an inventory, email or handover record.
No. A multi-site plan can host several domains within one account; the reseller model uses separate accounts for clients. Specify the account separation, permissions and control panel licence you need when requesting a proposal.
You define the scope of the service you offer your own clients. Requirements for private nameservers, branding, a client panel and billing are assessed separately, together with their technical and commercial scope.
No. Once the pilot's scope and owner are defined, the checklist can be assessed using a representative website. Other projects are grouped according to renewal dates and operational schedules.
We consider the number of websites and separate client accounts, resource needs, licences, billing period and requested operational support together. Initial-term prices, renewal prices and any additional work should each be clear in the written proposal.
Share the number of websites and client accounts, your email requirements and your top priority. Start with the information you already have.