Work continues after a website goes live: updating service terms, fixing a form, adding a new section, or checking that everything works after a change. To plan costs, a business owner needs to understand the scope of work and how it will be billed.
Hourly pricing suits small, occasional tasks. Ongoing maintenance makes sense when a website needs regular checks, reserved team time, and an agreed process for responding to problems.
Choose based on the project's actual needs: what work arises, how often, and how quickly it needs to be completed.
What website support can include
The scope of support is agreed for each website. It may include technical maintenance, bug fixes, content updates, and interface improvements. New functionality needs a separate estimate, even if the same team develops it.
For example, restoring data delivery from an existing form is a repair task. Adding lead routing between departments, notifications, and new processing rules expands the functionality.
This distinction helps you agree on the result and budget. A substantial improvement is easier to manage as a separate project with stages, even if it is still billed by the hour.
What to consider on Tilda, WordPress, and Webflow
We work with Tilda, WordPress, and Webflow. For each platform, we define the tasks and estimate the time based on the website's structure, custom code, and connected services.
On WordPress, maintenance may include updating the core system, themes, and plugins, creating backups, and checking compatibility. Clarify which tasks the hosting provider handles and which belong to the website specialist. WordPress recommends backing up the website before an update. WordPress update documentation.
A complete WordPress recovery requires both files and the database. Agree on the backup frequency, storage location, and recovery process. WordPress backup guidance.
On Tilda and Webflow, tasks may include changes to published pages, checks of forms and external connections, improvements to mobile layouts, and custom code changes. Also clarify the available options for saving and restoring the project.
For any platform, assign responsibility for the domain, subscriptions, licenses, and external services. For example, an expired subscription to a connected tool can affect the website even if nobody has changed the page itself.
How to choose a payment model
There are several ways to organize website support. Compare them by scope, team availability, and the rules for approving costs.
Hourly pricing is particularly useful when you may need one or two changes in one month and none in the next. With a steady flow of work, compare the cost and terms of ongoing support.
Response time and completion time are different commitments. Responding to a request or starting the diagnosis does not mean the problem will be resolved within the same period. If speed is critical, agree on working hours, urgent task priority, and communication arrangements in advance.
A recurring payment alone does not confirm monitoring around the clock or a guaranteed recovery deadline. These terms should be explicitly described in the offer.
How to budget for hourly support
At iuntsevich.cz, our hourly website support and design service is available at €30 per hour. Before starting, we discuss the task and agree on a time estimate and budget.
Use this formula for planning:
Work cost = agreed billable time × hourly rate.
The estimate accounts for the necessary stages: understanding the task, carrying out the work, checking it, and handing over the result. Licenses, subscriptions, paid assets, and other external costs are agreed separately.
Illustrative example: a company groups several small tasks into one order. The times below only demonstrate the calculation; they are not estimates for equivalent work on any website.
- Update finished text and service terms — 0.5 hours.
- Fix the mobile display of an existing section — 1 hour.
- Find and resolve a form submission problem — 1.5 hours.
- Check the changes and hand over the result — 1 hour.
Total: 0.5 + 1 + 1.5 + 1 = 4 hours.
Budget at €30 per hour: 4 × €30 = €120.
Suppose a comparable monthly package costs a hypothetical €180 and covers the tasks listed. Under these assumptions, the hourly option costs €60 less. The package price in this comparison is fictional and is not a rate offered by our agency.
At €30 per hour, €180 pays for 6 hours. This is a useful budget comparison, but the final choice also depends on the included checks, specialist availability, and urgent support terms.
If the monthly package includes other necessary work, include it in the comparison. Otherwise, the amounts will cover different scopes of support.
How to estimate a task when the cause of an error is unknown
A description such as “the form sometimes does not work” is not enough to give an exact repair time immediately. The cause may lie in page settings, custom code, a connected service, or data processing after submission.
In this situation, it helps to divide the work into stages:
- Diagnosis with an agreed cap. The specialist reproduces the problem, reviews the settings, and identifies the cause or describes what further checks are needed.
- A repair estimate. After diagnosis, agree on the changes required, the time, and how the result will be checked.
- Implementation and acceptance. The team makes the changes and confirms that the original user journey works.
Agree in advance on how diagnosis time will be billed and what happens when the cap is reached. A practical process is to report the findings and obtain approval to continue before incurring additional costs.
This lets you pay for clearly defined stages and control the budget even when the initial information is incomplete.
How to brief a specialist and reduce unnecessary questions
Provide a short description:
- URL: a link to the page or section.
- Current behavior: what happens now, which actions trigger it, and on which device.
- Expected result: what should change and how you will accept the work.
- Materials: finished text, images, mockups, or examples.
- Deadline: your preferred date and the reason for urgency, if any.
- Budget: the spending cap and how additional work will be approved.
For example: “The mobile menu on the service page covers the inquiry button. After opening the menu on a phone, the button cannot be tapped. Please fix the behavior and check it on the agreed devices. Before starting, provide a time estimate; any budget increase must be approved separately.”
A screen recording or a sequence of steps can help explain the issue. Grant the access needed for the agreed task, and keep control of the domain and primary accounts within your company.
What to agree before work starts and receive afterward
Before starting, record the expected result, time estimate, cost, deadlines, and how hours will be tracked. Clarify how new requests are handled and what terms apply to correcting defects in the completed work.
After completion, request a short report: what changed, on which pages, how much time was recorded, and how the result was checked. For forms, confirm inquiry delivery; for interface changes, check the agreed user journey on the relevant devices.
If some issues involve an external service or require separate development, this should be clear from the report and the subsequent estimate.
To choose a support model, list the upcoming tasks and essential recurring checks. Assess their frequency, the response time you need, and the budget. This will help you decide when hourly assistance is sufficient and when the project needs ongoing support.