CMS websites
WordPress website development services
WordPress development services range from freelancers who set up a theme to teams that design and build custom sites with ongoing support. Comparing them is easier once you know what a sound engagement looks like: a discovery stage that produces a content model, clear review points, a staging site you can test, written acceptance criteria, a plugin list, agreed ownership of code and accounts, and a plan for who looks after the site once it is live.
This page sets out the engagement types, responsibilities on each side, the stages to expect, what to check in a proposal and the 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
- Discovery
- Design
- Staging build
- Testing
- Handover
Types of WordPress engagement
| Engagement | What it usually covers | Check |
|---|---|---|
| Theme setup | Ready-made theme configured with your content | Limits of the theme |
| Custom design and build | Designed templates built into a theme | Who maintains the theme |
| Build plus care plan | Build followed by ongoing updates and support | What the plan includes |
| Development support | Work on an existing site | Access and code quality |
Who does what
Projects stall when responsibilities are vague. A provider is usually responsible for design, build, testing and launch. The client is usually responsible for content, images, approvals and decisions, delivered on time. Write down who supplies copy, who sources photography, who sets up hosting and who registers or controls the domain, and agree how long each side has to respond at review points.
Stages to expect
Discovery
Goals, content types, integrations.
Output: Scope and content model
Design
Key templates designed and reviewed.
Output: Approved designs
Build on staging
Theme, editor and plugins configured.
Output: Staging site for review
Content and testing
Content entered; devices and forms tested.
Output: Test results
Launch and handover
Go live, redirects, training.
Output: Handover notes and access
Acceptance criteria
Acceptance criteria say what must be true for the work to count as finished: templates match approved designs, forms deliver to the right inboxes, pages work on agreed devices and browsers, redirects are in place, editors can perform listed tasks. Agreeing them at the start avoids arguments at the end, and gives both sides a clear checklist for sign-off.
Warning signs in a proposal
No discovery stage
The build may not match how your content works.
Hosting in the provider's name only
Leaving them later can be difficult.
Long plugin list with no reasons
Maintenance and conflicts grow.
No mention of updates after launch
The site may be left unpatched.
Example: comparing three proposals for a law firm site
Illustrative example — not a client case study
Situation: A small law firm receives three proposals that look similar on price.
- Only one includes a discovery stage and a content model for practice areas and people.
- Only two put the hosting and domain in the firm's name.
- The firm asks all three for acceptance criteria and a plugin list before deciding.
What this shows: The comparison became clearer once each proposal answered the same questions. This example is illustrative.
What the handover should include
Access
- Administrator login for the business
- Hosting and domain in your name
Documentation
- Plugin list with purposes
- Editor guide
Assets
- Theme code and design files
- Premium licence keys
Questions worth asking
How will customisations survive theme and plugin updates? Who applies updates after launch, and how are backups tested? What happens if a plugin is abandoned by its author? How is the site handed over if we part ways? Clear answers to these show whether a provider plans for the life of the site, not just the launch.
Reading a portfolio
Look at live sites rather than screenshots, check them on a phone, and if possible ask the owners how easy they are to update. A portfolio shows design taste; conversations with past clients show how projects run.
What the contract should cover
The scope, stages and review rounds; acceptance criteria; payment milestones; ownership of code, designs and content; confidentiality; what happens if the project is paused or ended; and support after launch. Take advice on contract terms if the project is significant.
Support after launch
Ask whether a warranty period covers defects found soon after launch, and what ongoing care costs and includes. Separate fixing defects in the delivered work from new requests, so both sides understand what is covered.
Testing on a staging site
A staging site is a private copy where you can review the build before it goes live. Use it to click through every template on a phone and a laptop, submit each form, and try the editing tasks your team will do. Note problems against the acceptance criteria rather than as general impressions, so fixes can be tracked.
Questions about WordPress website development services
What types of WordPress service are there?
Theme setup, custom design and build, build with a care plan, and development support.
What should the client provide?
Content, images, approvals and timely decisions.
What are acceptance criteria?
A written list of what must be true for the work to be finished.
Who should own the hosting?
The business, with access for the provider.
What should the handover include?
Access, plugin list, editor guide, code and licence keys.
How do we judge a portfolio?
Check live sites on a phone and talk to past clients.
Request a Custom Quote
Ask about WordPress 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.