CMS websites
CMS website development services
CMS development services range from specialists in one platform to agencies that work across several. Specialists bring depth; generalists may give more neutral advice on which platform fits. Either way, a sound engagement starts from your requirements rather than the provider's preferred tool, models your content, lets editors test before launch, defines what finished means, keeps accounts in your name and plans for maintenance. Asking how a provider would choose the platform, and why, tells you a lot about how it will run the project.
This page covers engagement types, stages, responsibilities, what you should receive, questions to ask and warning signs. LetGetGrow builds, redesigns and maintains WordPress and Webflow websites, with the scope, cost and timeline of each project set out in a custom quotation.
Illustrative diagram
- Requirements
- Platform
- Build
- Editor test
- Handover
Types of provider
| Provider | Strength | Check |
|---|---|---|
| Single-platform specialist | Depth on one system | Whether that system fits you |
| Multi-platform agency | Broader comparison | Depth on the chosen platform |
| Freelance developer | Direct contact, flexibility | Capacity and cover |
| In-house with support | Your team owns it | Training and escalation |
Platform advice from requirements
Ask how the provider would decide which CMS to use. A good answer starts with your content, editors, integrations, budget and plans, then compares a shortlist. A provider that recommends its usual platform without asking about these may still be right, but you have less reason to be confident.
Stages to expect
Requirements
Content, people, integrations.
Output: Requirements document
Platform and model
Platform chosen, content modelled.
Output: Decision and model
Design and build
Templates on staging.
Output: Staging site
Editor testing
Real editors try real tasks.
Output: Feedback fixed
Launch and handover
Training and maintenance plan.
Output: Live site and guides
Warning signs
Platform chosen before questions
It may not fit your needs.
Accounts in the provider's name
Changing provider becomes hard.
No editor testing
Problems surface after launch.
No maintenance plan
The site may be left unpatched.
Example: a brief that kept the choice open
Illustrative example — not a client case study
Situation: A professional body asks providers to recommend a CMS rather than naming one.
- The brief lists content types, editor roles, approval steps and integrations.
- Providers are asked to compare two platforms and explain their recommendation.
- The chosen provider arranges a test session for editors before the build is signed off.
What this shows: The body chose a platform that matched its approval process. This example is illustrative.
What you should receive
Decisions
- Requirements and platform rationale
- Content model
Ownership
- Accounts in your name
- Code and design files
Running the site
- Editor guide and training
- Maintenance responsibilities in writing
Acceptance criteria
Agree what finished means: templates match designs, content types work as modelled, roles and permissions behave correctly, forms and integrations work, pages meet agreed accessibility checks and editors can complete listed tasks.
Questions worth asking
Why this platform for us? How will editors be trained? Who applies updates? How do we export content if we leave? What happens if you are unavailable? Specific answers suggest a provider planning for the site's whole life. Ask too how they handle disagreements about scope during the project.
What the contract should cover
Scope, stages and review rounds; acceptance criteria; payment milestones; ownership of code, designs and content; accounts; confidentiality; and support after launch. Take advice on terms for significant projects.
Support after launch
Ask about a warranty period for defects and the cost and scope of ongoing support. Separate fixes from new work so expectations are clear. Ask how quickly the provider responds to urgent problems, such as the site going down.
Checking references
Ask to speak to past clients on similar projects, and ask them how easy their site is to update and how the provider handled problems. Look at the live sites yourself on a phone as well.
Content modelling
Expect the provider to work through your content types, fields and relationships before designing templates. A written content model, approved by you, is the blueprint for the build. It should be readable by non-developers and kept as part of the handover, so later changes start from an accurate picture.
Editor testing before launch
Ask for a session where the people who will run the site try real tasks on staging: adding a page, publishing an article, updating a listing. Their feedback often reveals confusing field names, missing help text or permission problems that are easy to fix before launch and frustrating after.
Who does what
Providers usually handle requirements, platform setup, design, build and testing. Clients usually provide content, decisions, editor availability and approvals. Write down who owns hosting and domain accounts and who will maintain the site after launch.
Questions about CMS website development services
Should we choose a platform specialist?
If you know the platform fits; otherwise a broader comparison may help.
How should a provider choose the CMS?
From your content, editors, integrations and budget.
Why test with editors?
They reveal problems that feature lists hide.
What should we receive?
Rationale, content model, accounts, files, guides and a maintenance plan.
What should sign-off criteria cover for a CMS build?
A written list of what must work for the site to be finished.
How do we check a provider?
Speak to past clients about updates and problem handling.
Request a Custom Quote
Ask about CMS website development services
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.