9 articles tagged business.
Sessions fell 41% the month after the relaunch and the leads went up, because the old site counted everybody and the new one only counts the people who said yes. What the consent rule actually covers, why cookieless is not automatically banner-free, the server-side denominator that makes the numbers honest again, and why the count that pays lives in the ERP.
The new site is faster and better looking, and three weeks later organic sessions are down a third. Nothing looks broken, because a 404 is a working page. Where the URL inventory actually comes from, why the sitemap isn't it, where redirects belong in a Next.js stack, and the rule that stops people blanket-redirecting a thousand URLs to the homepage.
Belgium's structured e-invoicing mandate landed on 1 January. Switching it on was an afternoon; everything it exposed was the quarter that followed. What Peppol actually addresses, why the failures live in your contact records rather than your ERP, what UBL refuses to carry, and why 'sent' stopped meaning 'delivered'.
Three good answers to "we need a website", each right for a different shape of requirements. The five questions that actually decide it — who edits, what it talks to, whether visitors change state, who owns it in three years, and what the risk surface has to look like — plus the two migrations that go wrong in both directions.
Most maintenance contracts are a monthly invoice with a promise attached. The line items that make one real — patch cadence, backups you have restored, an SLA that says what a clock is and when it runs, and hours you can actually spend — plus the questions that expose a hollow one in five minutes, applied to ours as well as everyone else's.
Bancontact in Belgium, iDEAL in the Netherlands, TWINT in Switzerland — conversion follows familiarity, and a card form is not a neutral default. How we structure Mollie or Stripe so every market pays the way it expects, why asynchronous methods are the part that actually breaks your order flow, and what the cost conversation looks like when someone finally has it.
Studio is brilliant for a field and a filter — and a trap for business logic. The boundary we draw between no-code tweaks and real modules, and what each choice costs at upgrade time.
Microservices solve an organisational problem, not a technical one. How we decide between a modular monolith and distributed services for custom builds, and the signals that justify the split.
The cheapest moment to discover a problem is before anyone writes code. What a fit-gap analysis actually is, what it produces, and why Code Agency won't scope an implementation without one.