Technology in practice
Kinsta
Operate WordPress with clear responsibilities
A fit for WordPress sites needing managed hosting and a team responsible for the application and its changes.
Let’s discuss your situation ↗01
Choose with context
What we assess before recommending it
Hosting and website maintenance are different services. We review plugins, compatibility, traffic and the subscribed plan; migration does not automatically fix code problems.
This capability supports those areas according to the project. If the solution is still unclear, we start by organising needs and priorities. Explore Strategy ↗
02
What we can address
We inventory the installation, domains and dependencies and rehearse migration before DNS changes.
We review caching, resources and application errors to prioritise measurable improvements.
We organise updates, backups and incident handling under the agreed service.
Technical detail, explained
- Staging
- A working copy for reviewing changes before applying them to the public website.
- Managed hosting
- Provider-operated infrastructure, with a scope distinct from code maintenance.
03
What you receive
We specify these deliverables in the proposal, according to what needs building or reviewing.
- A migrated installation or reviewed configuration, depending on the engagement.
- Update and restore procedures.
- Responsibilities shared clearly between client, hosting provider and maintenance team.
The proposal identifies source code and documentation to deliver, client access and third-party licences. We agree ownership and handover before starting.
04
Getting started
We review the installation, usage, available access and support needs. We define what maintenance covers and what needs a separate project.
- Share the context: what exists, who uses it and what needs to change.
- Where technical uncertainty remains, we propose a bounded review before estimating implementation.
- We agree deliverables, phases, acceptance criteria, schedule and budget before building.
Timing, investment and third-party costs
We do not publish a single figure because a review and a full build are different engagements. The estimate separates our work from hosting, licences and usage-based services, and identifies dependencies such as access, content or app store approval.
What happens after handover
We define validation, handover and any included support period. Ongoing maintenance is agreed separately, with explicit coverage, channels and response times; continuous availability is not assumed.
Let’s start with your situation.
Tell us what you want to improve and what exists today. You do not need to have chosen the technology.