- WordPress and plugin updates, always with a backup taken first
- Daily backups
- Uptime monitoring 24/7
- A pool of 3 h of small fixes per month
- Response within 48 working hours, critical outage within 8 h
- Peace of Mind Guarantee: store down because of my work and not back within 8 h, you don't pay for that month
- Contact: email
Support for your store and website. I stay.
For a store that should earn, not stand still: the Store plan is for WooCommerce with a turnover from about 50,000 PLN a month, Start for a company website or a small store, Plus for a critical store. I take over the store within 48 h of access, with an entry audit. You get updates always with a backup, monitoring, a pool of hours for fixes and a person who walks the checkout to the last step after every change. Peace of Mind Guarantee: the store went down because of my work and was not back within the outage time of your plan, you don't pay for that month. I run WordPress sites and Laravel applications the same way.
The same outage, two different evenings.
The site is up, but the basket does not work.
That is the most common loss in a store: monitoring shows a green 200 and a customer cannot pay. So after every update I walk the checkout to the last step, not just the response code of the home page.
I take over the store in 48 h, with an entry audit.
The clock starts when I have access: WordPress admin, FTP or SSH and hosting. I take over stores built by others too - the entry audit tells me the state of the code before I take responsibility for it. You get a list of what I found.
Three levels of calm.
Prices net, per month, no minimum term. I run every plan personally - nothing gets handed to a support desk. Online stores, WordPress sites, Laravel applications.
- Entry audit when I take over the store, within 48 h of access
- Checkout test after every change
- A pool of 6 h of work per month (fixes, configuration, small development)
- Response within 24 working hours, critical outage within 4 h
- Peace of Mind Guarantee: store down because of my work and not back within 4 h, you don't pay for that month
- Monthly report
- Contact: email plus priority
- A pool of 12 h of development and optimisation per month (performance, conversion, new features)
- Quarterly technical review (Core Web Vitals plus security) with a report
- Response within 8 working hours, critical outage within 2 h
- Peace of Mind Guarantee: store down because of my work and not back within 2 h, you don't pay for that month
- The role of your IT department - Laravel applications and B2B systems included
- Contact: phone or Slack, straight to me
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. No minimum term: cancel by the end of any month. I keep clients with quality, not with small print.
Would you rather read first?
This is my work from the inside - two pieces that show how I approach maintenance:
Before you ask.
WordPress and plugin updates always with a backup taken first, daily backups, uptime monitoring and a pool of hours for fixes or development. The Store plan adds an entry audit, a checkout test after every change and a monthly report; the Plus plan adds a quarterly technical review and shorter response times. The scope of every plan is written out above - no asterisks.
Start 1,200 PLN, Store 2,000 PLN, Plus 3,500 PLN net per month. The prices are fixed, no "from". No minimum term: you pay month by month and cancel by the end of any month. Scope and response time of every plan are written out above, with no asterisks and no hidden extras.
Monitoring reports the outage to me before your customer does. Every plan carries the Peace of Mind Guarantee: if the store went down because of my work and is not back within the critical outage time of your plan (Start 8 h, Store 4 h, Plus 2 h), you don't pay for that month of support. An outage with another cause jumps the queue, within the same time.
Hosting keeps the server up and clicks "update" overnight. Nobody there checks whether an order can still be placed afterwards. Support is a person who takes a backup before the change, walks the checkout to the last step after it and picks up the phone when something happens.
I begin with the takeover within 48 h: a backup, an entry audit (access, the state of updates and security) and a clean-up. From that moment the store is monitored and the response times from your plan apply. No minimum term: you cancel with one email by the end of any month.
No. After launch I propose the Store plan at 2,000 PLN net a month, but the decision is yours and there is no minimum term. Most clients stay longer, because ongoing support is cheaper and calmer than repairing things after an outage.
Yes, that is the usual case. The condition is the entry audit in the first 48 hours - 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.
Want your store under ongoing support?
Describe the project in a few sentences - I come back personally with the scope, hours, price and a date. For a 20-minute call I keep two fixed slots: Tuesday and Thursday, 18:00-19:00 CET.