01 / The customer decision
Start with the information the visitor needs.
Adding CMS is not always a matter of attaching an editor to the current design. Repeated content, unusual layouts and existing functionality may need to be restructured for the chosen implementation.
Begin with the changes you want to make yourself. An accurate list of tasks is more useful than asking for every part of the current website to become editable without limits.
02 / A practical content plan
Move from static pages to supported editing: a useful starting structure.
This is an example content plan for discussion. It describes information to organise, rather than an automatic promise that every feature or section is included.
Current content review
Identify static pages, repeated items and information that changes often.
Editable content model
Define the fields and page areas the CMS should support.
Transfer scope
Decide which text, images and URLs are retained, revised or retired.
Editing boundaries
Agree which changes are routine content work and which remain design or development tasks.
03 / Choose by the work required
Check the fit before choosing a package.
- Consider a CMS rebuild
- The same content areas need recurring updates.
- Keep static pages
- Updates are rare and a rebuild offers little practical benefit.
- Assess beyond five pages
- Content collections, integrations or larger archives exceed the starting package scope.
04 / Promotional packages
A clear scope at each price.
| Scope | Price | Content editing | Next step |
|---|---|---|---|
| 1 landing pageLanding page | $100 | No CMS | Discuss $100 scope ↗ |
| 5 pagesBusiness website | $150 | No CMS | Discuss $150 scope ↗ |
| 5 pagesWebsite with CMS | $200 | Supported CMS editing | Discuss $200 scope ↗ |
| Up to 10 pagesCMS + programmatic SEO | $300 | Supported CMS editing | Discuss $300 scope ↗ |
| Up to 20 pagesSEO-friendly website + pSEO | $400 | Discuss editing requirements | Discuss $400 scope ↗ |
These are promotional website packages. They are separate from the standard website packages. The ten- and twenty-page limits include the shared website pages; they are not extra pages added on top.
I agree page types, source content and functionality before work starts. Payment, delivery, domain, hosting, revisions and support arrangements should be confirmed with your project scope. No recurring service, advanced integration or unlimited future work is implied by the page count.
05 / Prepare a useful brief
What to send with your enquiry.
- The current URL and page list.
- Examples of the changes you regularly request.
- The content to keep or remove.
- Any scripts or functions the new setup needs to preserve.
Public website links and a description of your needs are enough to start the discussion. Share account access through an appropriate invitation when needed; do not put passwords in an enquiry message.
06 / Before you decide
Questions about this website scope.
Will the design remain identical?
That depends on the implementation and the agreed rebuild scope. An exact recreation should not be assumed.
Can every HTML page become a CMS item?
The right model depends on the content. Some pages are better kept as distinct structures and others as repeatable entries.
Does $200 include any migration?
The promotion covers an agreed five-page CMS website. Existing content transfer and technical migration must be assessed before a quote is confirmed.