A corporate website built with a free CMS needs separate budgets for software, delivery and ongoing operation. Core software licensing may cost zero. Your domain, hosting, theme configuration, product entry, translation, notification email and maintenance labor depend on the actual services and project scope. Define the website first, then compare costs for years one, two and three, plus exit costs, across a free CMS, paid source code and SaaS.
This guide is for teams buying a corporate website, an export product showcase or multiple brand websites. It covers free-scope checks, first-year and three-year costs, maintenance hours for additional products and languages, and explicitly hypothetical calculations. Replace every sample figure with an actual project quotation.
1. Confirm what “free” includes
For example, WordPress core can be downloaded free and hosted on your own infrastructure. Its license is GPLv2 or later; see the official license and official cost explanation. Check software licensing, theme or plugin updates and support, image and font rights, and third-party services individually. For system capabilities, read the WordPress and CatchCMS selection guide.
A free hosted plan supplies services according to its package. For example, a free WordPress.com site includes hosting, editing, themes and a platform subdomain. Check plugins and custom themes against the current plan in the official hosting guide. Record custom-domain requirements, available functions, capacity, support, export terms and charges after promotions expire. These descriptions apply to those services. CatchCMS source code plans are covered separately below.
2. Fix requirements, then list delivery and running costs
Use one brief: a corporate website in Chinese and English with a product catalog, downloads and inquiries. Specify product counts, page designs and content-entry responsibilities. For multiple brands, include site counts and domains. See the corporate website CMS guide and product catalog guide.
| Cost item | Self-hosted source code approach | SaaS approach |
|---|---|---|
| Use and updates | Source code license, update plan and agreed support | Subscription, renewals and service scope |
| Hosting and domains | Hosting, domains, backups, traffic and email | Check included services and extra domain, traffic or service charges |
| Design and launch | Theme, custom development, data preparation and content entry | Template, custom pages, setup and content entry |
| Extensions and translation | Plugins, translation, email or AI usage | Package extensions, translation and third-party usage |
| Maintenance and exit | Update testing, backup restoration, security maintenance and migration work | Content maintenance, capacity upgrades, export and migration work |
Record costs included in a package as zero, keeping evidence of the inclusion. Calculate labor as hours multiplied by an hourly rate. Use the relevant quotation for outsourced work to account for all required work and prevent double counting.
Complete these checks for a free CMS quotation
- Domains and infrastructure: enter initial and renewal domain charges, hosting and databases, backup storage, traffic overages, certificates and email delivery. Record allocated costs, capacity and an owner for existing resources. A free certificate can have a zero purchase cost; enter installation and renewal-check labor according to the actual arrangement.
- Themes and launch: list template purchase or production, mobile pages, navigation, form integration, deployment and launch checks. Keep inclusion evidence where the theme supplies required pages. Obtain project quotations for extra layouts, filters or external integrations.
- Plugins and functions: identify the component for each required function, its free-tier scope, site limits, update and support period, and renewal charges. Test multilingual pages, inquiry records and notification email through a complete sample workflow.
- Content and translation: count products, news, images and files, then estimate preparation, entry, translation and business-review hours. Include internal staff time. For AI assistance, list model usage, human review and publication checks separately.
- Maintenance and handover: name the people responsible for update testing, backup restoration, security work, content edits and incident response, together with included hours. Use the internal website maintenance checklist for editor handover.
- Exit and migration: confirm domain-account control, access to content and files, delivery of form records, migration hours and continuity of old URLs. Add the one-time charge at the expected exit date.
For every item, record the amount, billing period, inclusion evidence, owner and acceptance method. Mark an unconfirmed item “quotation pending.” Enter zero after confirming that it is included or requires no purchase.
3. Calculate first-year and three-year costs
Source code cost(n years) = license + initial delivery + n × (hosting and domains + extensions and services + maintenance labor) + additional update/renewal purchases + migration
SaaS cost(n years) = initial delivery + n × (subscription + charges outside the package + maintenance labor) + migration
Initial delivery covers design, templates, development, import and launch configuration. Hosting includes backups and operations. Extensions include plugins, translation and usage-based services. Enter additional update purchases and renewals according to the actual plan. Count updates already included in the initial licence once, and enter migration costs at the expected exit point.
4. A free CMS example with zero core license cost
This is a fictional budget in Chinese yuan. Assume a corporate showcase in Chinese and English. The company supplies approved bilingual materials; initial delivery includes theme configuration, deployment, content preparation and entry, and launch checks. Additional writing and translation charges are set to zero for this calculation. Hosting includes the required backup resources. Certificate and selected plugin purchase costs are zero. Maintenance labor covers content updates, update testing and backup-restoration checks. Enter your own writing, translation, plugin and service quotations in the checklist.
| Assumed item | Amount and arrangement |
|---|---|
| Core software license | 0 |
| One-time initial delivery | 3000 |
| Annual hosting and backup resources | 500 |
| Annual domain | 100 |
| Annual maintenance labor | 1200 (12 hours × CNY 100) |
| First-year total | 4800 = 3000 + 500 + 100 + 1200 |
| Three-year total | 8400 = 3000 + 3 × 1800 |
This base example sets additional services, separate update or support purchases and exit migration costs to zero, with fixed requirements and prices for three years. If additional services cost CNY 300 per year and migration labor costs CNY 600 at the end of year three, the total including exit is CNY 9900: 8400 + 3 × 300 + 600. Other project costs still follow the actual scope when the software license costs zero.
5. Compare paid source code and SaaS in the same budget
A separate hypothetical comparison
Every amount below is an assumption in Chinese yuan with the same brief for both approaches. The CNY 600 source code license is a calculation input. Actual quotations depend on the supplier, deployment conditions and labor. Assume fixed requirements and prices for three years. Extension, translation, update renewal and migration costs are zero in this example; template and development work are included in initial delivery.
| Assumed item | Source code approach | SaaS approach |
|---|---|---|
| One-time license | 600 | 0 |
| Initial delivery | 3000 | 1500 |
| Annual hosting or subscription | 500 | 1800 |
| Annual domain | 100 | 100 |
| Annual maintenance labor | 1200 | 600 |
| First-year total | 5400 | 4000 |
| Three-year total | 9000 | 9000 |
Initial delivery and maintenance arrangements change the result. Replace every assumption with real figures, then calculate extra languages, more sites, changing traffic or a redesign.
6. Measure the cost of extra products and languages
Base ongoing maintenance estimates on actual changes. List new products, changes to existing products, target languages and publication rounds, then separate the work into four categories. Adding a language affects the existing website inventory. Adding products to an established English edition can be estimated as an incremental batch.
| Work category | Measurement basis | Expected deliverable |
|---|---|---|
| One-time language setup | Configuration or development hours for language settings, fixed theme text, navigation, form messages and public addresses | Working sample pages, language switching and enquiry flow; price existing-content translation separately |
| Base product entry | Product count multiplied by preparation and entry hours per product; list images and attachments separately | Accurate models, specifications, images, document relationships and categories |
| Translation and review for each target language | Characters or words to process, language pair, technical complexity and human review scope | Business approval of body text, SEO text, document language and terminology |
| Each release and subsequent changes | Publication rounds multiplied by checking hours; measure later changes by affected products and languages | Matching readback, accessible public pages, readable mobile layout, working internal links and enquiry entry points |
For example, translation provider Weglot discusses translated word counts and target language counts in its customer quotation guide; its plan page also lists allowance dimensions. This example prompts buyers to check service metering. Calculate CatchCMS source code licensing and third-party translation services under their respective terms.
- Billing units: specify Chinese characters or English words, source or translated text, and treatment of spaces, specification tables, repeated paragraphs, navigation and SEO fields. Retain the count evidence for each language.
- Quotation boundaries: confirm minimum charges, glossary preparation, included revision rounds, rework rates after business edits, human review and document layout. List AI service usage, content entry and translation review separately.
- Existing content and increments: inventory existing products, news, downloads and shared text when adding a language. When maintaining an existing language, identify the changed fields and retain approved translations that still apply.
- Packages and duplicate charges: check word, language, site and request allowances plus overage handling. Count entry, review or acceptance hours included in the same service once. Apply included annual-maintenance hours according to the contract.
CatchCMS already provides multilingual content, SEO text and dynamic-field management, used according to enabled, translatable field configuration. Bulk imports, automatic translation orchestration, approval workflows and automatic stale-translation alerts require project implementation and validation. Read the bilingual content synchronization checklist for editing steps and the fact and terminology guide for AI review tasks. This budget section converts that work into quantities a buyer can verify.
7. Estimate a batch of 20 additional products
This is a separate fictional incremental example in Chinese yuan. Every duration and rate is assumed. An existing Chinese and English website already has language setup and product templates. The company supplies approved Chinese copy, English drafts, specifications and cleared images and documents. Each product reuses the current fields and layout; English work covers draft review and entry. Price new writing, translation from scratch, image production, document translation, new-language setup and custom development separately.
| Batch work | Assumed hours | At CNY 100/hour |
|---|---|---|
| Base preparation and Chinese entry for 20 products | 20 × 0.3 = 6 hours | CNY 600 |
| English draft review and entry for 20 products | 20 × 0.5 = 10 hours | CNY 1000 |
| Bilingual release and checks for this round | 4 hours | CNY 400 |
| Total incremental batch labor | 20 hours | CNY 2000 |
The total payable for this batch also includes actual additional AI, translation service, capacity upgrade or outsourced-project charges. Mark these “quotation pending” for now. This example is separate from the annual budgets above. If annual maintenance already covers this batch, use the agreed hours and calculate the excess. For a third language, obtain a fresh estimate for setup, translation of existing content, specialist review and acceptance.
Monthly incremental budget = new-product entry labor + translation/review labor for each target language + existing-content change labor + release-check labor + actual additional service/overage charges
Calculate each labor item using its quantity and actual rate, applying contractual included amounts. If two releases are expected each month, enter both rounds. Missing materials and repeated copy changes can alter the hours. Complete one representative product first, measure preparation, English review and release-check time, then set a sustainable maintenance allowance.
8. How CatchCMS pricing fits into a budget
The current pricing and source code licensing page lists one year of updates at CNY 399 for your own sites and a lifetime-update option at CNY 599 for your own sites and client project delivery. Also budget for hosting, domains, themes, development, translation, launch and maintenance labor. Confirm update periods, technical support, site counts, domains, deployment and resale scope against the applicable terms.
Review multiple languages, multiple sites, dynamic fields and form management. When using AI-assisted theme development or MCP content maintenance, include model service usage, review and testing labor.
9. Complete five checks before signing
- Confirm what free versions, paid versions and service packages include. Obtain quotations for pending items and list all three years plus exit costs.
- Ask the content editor and technical maintainer to confirm responsibilities, hours and incident handling. Deliver the acceptance record to the buyer.
- Create a real product and its translation, submit a test inquiry, and check fields, notifications and editing steps. Inspect public pages in the product demo.
- Obtain first-, second- and third-year fee schedules covering capacity limits, extensions, support and client delivery conditions.
- Confirm exit deliverables: domain control, source code or data export, attachments, form records, migration labor and continuity of page addresses.
If your team wants hosting as a service and focuses mainly on content operations, compare SaaS delivery and exit terms closely. If your team wants self hosting and custom product content and has a maintainer, evaluate the source code approach. Send site counts, languages, product scale and a three-year usage plan through project consultation and confirm scope before finalizing the budget.
10. Procurement and maintenance questions
How should an annual budget show a free CMS license?
Enter zero for core licensing and verify domains, hosting, backups, themes, plugins, content labor and service usage individually. Record internal staff time, retain inclusion evidence and mark unconfirmed items “quotation pending.”
How can we obtain comparable quotations for another language?
Supply an inventory of existing pages and products, identifying body text, specifications, SEO, navigation, forms and documents to translate. Use consistent character or word counting. List language setup, translation and review, release acceptance, package allowances and later update rates, then test the same representative sample.
How should AI-assisted maintenance change the labor budget?
Use a trial record to revise preparation and drafting hours, retaining business fact review, terminology checks and public-page acceptance. Track model service charges and staff time separately. Adjust later estimates using measured time savings and rework.