A paid audit, one measured pilot, then a care plan. For a shop that already takes orders, or a service business whose site brings the leads. WordPress and WooCommerce are the packaged audit, not the name of the whole practice. You talk to the person who does the work.
- 20 min Free teardown
- €490 Five-day audit
- 2–4 wk One process
- 30% Credited in 14 days
What you can buy
I start with the audit. A pilot and a care plan come only after it shows where the money or the hours go.
Commerce Reliability Audit
The packaged offer for a live WordPress or WooCommerce shop. Five working days, €490, paid in full before it starts. Inventory, a restore that has actually been run, update risk, speed, the form and email path, and the money path. A prioritised plan and a short recorded walkthrough. Not a pentest.
Revenue Reliability Care
After a baseline and a proven restore. Foundation €490, Commerce €990, Growth Ops €1,750 a month. Three months minimum, billed in advance, business hours, no 24/7.
Automation pilot
One process, one KPI, €2,500–7,500, two to four weeks. Then €300–1,000 a month to keep it running. A person approves anything sensitive. The model bill has a cap.
Migration and setup
€1,500–4,000, quoted after the audit. A monitored server, HTTPS, and a way back. Care does not start until a restore has been checked.
The money path I walk
An uptime check can say the shop is fine while a promo code, a shipping method or the purchase event is already losing orders. The audit follows the path a buyer takes.
- Cart The item, the price and the quantity the buyer actually sees.
- Shipping Whether the right method is offered for that address.
- Promo A code that changes the total, or quietly breaks it.
- Payment Stripe, PayPal, and a method that disappears for one product.
- Analytics The purchase event that should fire, and sometimes does not.
The line I draw
In the work
- A written scope and an acceptance test
- 30% of the audit credited toward a pilot within 14 days
- Human approval and a monthly API budget cap
- A restore that has been run before care starts
- Three ways forward: do it yourself, a pilot, or care
I will not say
- That a backup exists if I have not restored it
- That the site will appear in ChatGPT or Google answers
- That an agent may change prices, orders or refunds on its own
- That your data never leaves the server, if a cloud model is in the path
- That maintenance includes unlimited new features
Questions before you book
Is the teardown the audit?
No. Twenty minutes and one finding you can see. The audit is five paid days.
Who is this for?
The owner or the person who runs operations. A shop with live orders, or a service business whose site brings the leads. Not a regulated payments business, and not a shop that needs a 24/7 desk.
Where does the data go?
Before AI touches it you get the data flow in writing: which services see what, whose keys are used, and the monthly spend cap. Cloud AI only with your opt-in.
Do you put several clients on one automation instance?
No. Credentials are not pooled. A shared automation UI is a separate licence question, and I do not start there.
What if you are unavailable?
The system stays yours. You hold the repository, the documented deploy and a restore that has been run. I do not keep the only copy in my head.
Can one engineer hold a serious system?
I take a limited number at a time. That is senior ownership of your system. It is not a substitute for a fifty-person bench.