Website Maintenance Cost: What I Charge For, and What I Don't
I don't sell monthly update retainers for brochure websites. I charge for maintenance where downtime costs money: stores, integrations, custom logic.
Posts on system design, boundaries, and how pieces fit together.
I don't sell monthly update retainers for brochure websites. I charge for maintenance where downtime costs money: stores, integrations, custom logic.
A business website is worth building when it reduces repeated sales friction, owns discovery, and gives clients a reliable next step before they call.
Stack-switching is cheaper than ever, yet WordPress is still set against the rest of the CMS world. This isn't really about code - it's about who owns the publishing workflow.
Why I chose Laravel over WordPress for a small internal tracker: the shape of the data, integrity requirements, and operational workflows mattered more than framework preference.
Anthropic pulled its newest models worldwide after a US government directive targeted foreign nationals. The stack lesson: model access is a revocable dependency.
A headless WooCommerce coupon sale spans two stores and an unreliable network. The design choices that make fulfilment recoverable after payment.
Why auditable git-tracked context beats agent memory you cannot version, review, or scope when many client repos run in parallel for paid work.
WooCommerce B2B starts with plugins, but role pricing, VAT display, account approval, and caching still demand an integration layer you own.
WooCommerce product import succeeds when the tool matches the data shape. Choose native CSV, WP All Import, or manual entry without corrupting custom meta.
A closed B2B WooCommerce store needs explicit decisions about access, product pages, ERP availability, and account approval. Plugins cannot make them for you.
Why long-running WordPress jobs need an atomic start lock, durable run state with a run ID, and recovery that survives worker crashes without duplicate imports.
When a Python sidecar improves a WordPress workflow, what it adds to operations and security, and how to keep the integration recoverable in production.
AI skills turn repeated decisions into reviewable workflow infrastructure by packaging context, procedures, tools, and acceptance criteria for technical work.
Why blocking scripts outperform manual review in AI content workflows: deterministic gates catch what tired humans skip under deadline pressure.
Symbolic regression finds formulas, not predictions. What the EML operator teaches developers about stack redundancy and interpretable ML alternatives.
CMS trends 2026: composability fatigue is real, AI earns its place only in narrow workflows, and GEO is changing how you should model content.
AI doesn't replace developers - it multiplies them. But ignoring it means everyone else scales while you stay linear.
Europe's first conference dedicated to CMS architecture and content decisions is coming to Gdynia, Poland this November. Here's what it's about.