Home / WordPress support
WordPress support and ongoing development
Updates, backups, and small website changes. I help maintain your website and handle ongoing tasks. Before starting, we define the support scope and how requests will be managed.
The initial estimate is free. Send a link or briefly describe your project.
WORK DIRECTLY WITH ME
A clear way to keep your website moving
Agreed priorities
We decide what to work on during the current period.
Careful changes
I account for dependencies and recovery options.
Visible progress
I document completed tasks and the next steps.
When your website needs ongoing support
Support suits recurring work within a scope agreed in advance. For one specific task, you can start with a one-off improvement.
01
Your website receives inquiries
Important technical workflows need checking, and issues need to be addressed when they arise.
02
Your content and offers change
You regularly need new blocks, page edits, and small feature changes.
03
You do not have an in-house developer
You want to send tasks to someone who understands your website and its development history.
Recurring tasks within an agreed scope
We define the support package after reviewing your website. These are the areas it can cover.
01
Planned updates
WordPress, theme, and component updates, taking compatibility and the website’s condition into account. We discuss higher-risk changes first.
02
Backups
We agree on what to back up, where to store it, how often to create copies, and how to check recovery.
03
Checks of important workflows
We define the checks needed for forms, pages, and other features. Actual submissions and transactions follow the agreed procedure.
04
Small changes
Work on the pages, blocks, and settings covered by the agreed scope. Larger features are estimated separately.
05
Technical questions
I investigate questions about the current implementation and suggest the next step. If other specialists are needed, I explain the limits of my part of the work.
06
Work records and reporting
I record completed tasks and the work involved, note unresolved questions, and agree on priorities for the next period.
What ongoing support includes
The package combines maintenance and small changes for your website. Before starting, we define its scope, communication arrangements, and the process for urgent requests.
01
Within the package
Planned technical tasks and small changes from an agreed list. We set priorities and the available scope at the start of each period.
02
Estimated separately
Redesigns, major features, complex integrations, recovery after a security incident, paid licenses, and external services.
The package terms define response times, work records, and how unused capacity is carried forward. Major features, emergency recovery, and external costs are estimated separately.
Kivilab: continuing the work after launch
After developing Kivilab, I continue its technical development and support. Knowing the catalog, shortlists, and spreadsheet connections helps me account for dependencies when making changes.
01
Send a task
Include a page link, description, and the result you need. I help establish the priority.
02
Follow the progress
We clarify the scope and how to check it, then I show you the completed changes.
03
Review the outcome
I record what was done, the questions still open, and the next tasks.
Cost and terms agreed before work starts
Support estimate
The scope, communication arrangements, and process for additional work are agreed after I review your website. Request an estimate for your ongoing tasks.
What determines the package
The website’s condition, components, important workflows, and the volume of recurring changes.
Estimated separately
Major changes, emergency work, third-party services, and licenses. We agree on any additional scope first.
Agreed before starting
Support tasks, scope, response times, request handling, work records, and how support ends.
How support starts and continues
01
Review the website
I review the implementation, access requirements, dependencies, and examples of recurring tasks.
02
Agree on the process
We define the package, priorities, communication, backups, and additional work.
03
Work through the list
I complete the agreed tasks and report questions that need a decision.
04
Review the period
We record completed work, open tasks, and priorities for the next period.
What I need to get started
01
Your website and current tasks
A link, the features you use, known issues, and examples of changes you need regularly.
02
Access and dependencies
After we agree on the work, provide the necessary access and information about hosting, licenses, and backups. You retain ownership of the accounts and key access credentials.
A link and a short description are enough for the first message. We clarify the other materials after reviewing the task.
Questions before you start
Do you support websites built by other developers?
Yes, after reviewing the implementation. If technical issues prevent routine support, I will first suggest a separate preparation stage.
Is support available 24/7?
No. We agree in advance on communication hours, response times, and urgent requests. Round-the-clock availability requires a separate agreement.
Are revisions unlimited?
No. The package has an agreed scope and priorities. If tasks exceed it, we discuss additional work or moving some tasks to a later period first.
Who pays for licenses and hosting?
External services, hosting, and paid licenses are not added silently to the support fee. We agree on the necessary costs and payment arrangements separately.
Can I request a one-off task?
Yes. For a specific list of changes, you can request website improvements. This suits projects that do not yet need ongoing maintenance.
What happens when support ends?
We agree on the handover process in advance: provide details of completed work and open tasks and check access. You retain your website and accounts.
Tell me about your project
Describe the website you need or what you would like to change. I will provide a free initial estimate of the work and cost. A detailed brief is not required.