A store is alive - plugins update, traffic grows, now and then something breaks. Support is the guarantee that you are not left alone with it: backups, safe updates, monitoring and priority when something happens. I run maintenance for WordPress sites and Laravel applications the same way - the B2B panels and integrations that have to work every day. One thing never changes: the code is looked after by the same person who wrote it.
Prices net, per month. I run every plan personally - nothing gets handed to a support desk. Online stores, WordPress sites, Laravel applications.
Most clients stay on support after the first project. Here is where I usually start: the Złota Faza case - performance 38 → 100.
Unused hours roll over to the next month. Bigger work is quoted separately - with a discount for support clients. The contract runs for a minimum of 3 months, then 30 days notice. 10% off when you pay for the year up front. I keep clients with quality, not with small print.
This is my work from the inside - two pieces that show how I approach maintenance:
WordPress and plugin updates always with a backup taken first, daily backups, uptime monitoring, a security scan and a budget of hours for fixes or development. The higher plans add checkout and payment monitoring, performance reviews and a guaranteed response time. The scope of every plan is written out above - no asterisks.
Basic from 1,000 PLN net per month, Pro from 2,000 PLN, Premium from 3,500 PLN - quoted individually, depending on the budget of hours and the SLA. You pay for a concrete scope and a concrete response time, all written out in the plans above, with no asterisks and no hidden extras.
I begin with a technical review: access, backups, the state of updates and security. From that moment the store is monitored and the response times from your plan apply. The contract runs for a minimum of 3 months, then continues indefinitely with 30 days notice.
No. Every project ends with 30 days of support included anyway. Most clients stay longer though, because ongoing support is cheaper and calmer than repairing things after an outage.
Yes. The condition is a technical review at the start - I need to know the state of the code before I take responsibility for it. The same goes for WordPress sites and Laravel applications built by someone else.
Bigger work is quoted separately - with a discount for support clients, so nothing stalls. It works the other way round too: unused hours roll over to the next month, so you keep them as a buffer for later.
The store is down, an order cannot be placed or the site will not load. In applications: the process you earn from stops working. Those reports jump the queue, within the response time from your plan.
Describe the project in a few sentences - I come back personally with the scope, a fixed amount and a date.
Loading…