A website agency needs a CMS that supports client content maintenance, team access and a clear handover. CatchCMS manages enterprise websites by site within one instance and provides source code for the admin, public runtime and official theme. It suits developers and agencies building company websites, brand sites and multilingual product catalogues. Define how the client will maintain and take over the website before planning implementation.
Choose the management and delivery arrangement
- Agency-managed operation: maintain projects in one instance, organise content, languages and domain themes by site, and assign site and feature permissions.
- Client content management: provide an account for the relevant site and document editable pages, file updates and submission handling.
- Client deployment handover: prepare the environment, data, source code and operational documents for the agreed deployment. Confirm deployment and delivery rights in advance.
Multisite management defines business data and access scopes. Separate databases, independent deployments, central publishing and cross-client synchronisation require project-specific arrangements.
Collect inputs before quoting
- Client and website: contracting party, purpose, brands, domains, site count, languages, launch date and existing website.
- Pages and data: sections, product or case types, maintained fields, translations, images, files and publication permissions.
- Implementation and handover: design references, assets, theme scope, deployment owner, client administrators, training and maintenance responsibilities.
- Commercial scope: source-code recipient, delivery arrangement, update plan, deployment scope, support and separately charged work.
Turn each item into a deliverable and acceptance method. Include advanced filtering, approvals and third-party integrations in the agreed development and maintenance scope.
Six delivery steps
- Confirm inputs and licensing. Prepare page and asset lists, account responsibilities and acceptance records.
- Configure sites and languages. Bind domains and themes, arrange hosting and HTTPS, and use the multilingual workflow to plan translations.
- Define the content structure. Use content models and custom fields for products, cases and documents, with appropriate validation.
- Implement the theme. AI theme development can assist with templates and styles. Check CMS data, mobile pages, navigation and forms before packaging and installation.
- Enter and check content. Validate one complete record first. Redesigns also need old-to-new URL and file checks from the migration guide.
- Run client acceptance. Use the handover account to edit content, check language pages and files, test submissions and notifications, and deliver source and operational documentation.
Example: acceptance for two client projects
This is a fictional example. Client A maintains a Chinese and English equipment website; Client B maintains services and case studies. The agency creates two sites in its managed instance and assigns editors to the relevant site and actions. Deployment and commercial rights are confirmed in the contract.
- Use A's account to update a test product. Check permitted sites and actions, read back the record and verify both language pages.
- Open B's case-study page and confirm it still displays B's data. Sign in as B's editor and check the available scope.
- Submit an enquiry labelled as a test on each site. Check corresponding records and notification results.
- Give the client operation instructions. Have them change a title, replace a file and view a submission, recording each result.
Maintenance after handover
Assign content and technical owners and agree on review, publishing, backups and updates. MCP tokens belong to admin accounts. AI content maintenance follows feature permissions and site authorisation. Tasks specify the site, record, language and allowed fields, followed by read-back and public checks.
The handover checklist includes source code, database, files, theme version and environment documentation. For independent deployments, prepare agreed data and verify domains, links, attachments and notifications. Backup and recovery checks belong in the operations plan.
Questions agencies ask
Does the source-code plan include custom design and development?
Published plans describe system and official-theme source code, updates and documentation. Client-specific design, extensions, data preparation, deployment and training need an agreed scope in the agency contract.
Which plan covers client work?
The current plans list one year of updates at CNY 399 for self-operated projects and lifetime updates at CNY 599 for self-operated projects and client delivery. Agencies should review the latter against their contract. Confirm site count, domains, independent deployments, resale scope, support duration and source-code recipients before purchase.
Confirm one real project first
Prepare the website type, site and language list, deployment and handover arrangement, and required custom features. Use agency project enquiry to confirm licensing and implementation scope before finalising your quote and acceptance checklist.