A delivered tool isn't a finished tool. It enters its real life: usage, incident, evolution. Here's what happens at Yumea after production go-live.

Many agencies deliver, bill, disappear. For us, delivery isn't the end: it's when real work becomes visible. A tool holds in its first six months or it doesn't. During those six months we're present, not as customer support, but as the people who built the tool and remain accountable for it. This page explains how we bill that time, and why we deliberately split it into three distinct things.

The three moments after delivery

The adjustment month. Just after go-live, your team meets the tool in real conditions. They find small grains of sand that weren't visible in UAT: an unclear label, a path too long, an unforeseen case. We fix as we go, no bill, for about a month. Included in setup. Corrections, after the first month. Any fix of a bug we let through stays on us, no time limit. If it's our fault, we fix at our cost. We don't confuse correction with evolution: a distinction we hold, and write black-and-white in the quote. Evolutions. When you want to add a function, change a behaviour, integrate a new case: it's an evolution. Quoted separately or billed hourly depending on size. Visibility: you know in advance what your request will cost, and you decide.

Why we don't sell flat-rate maintenance contracts

Flat-rate maintenance (a fixed monthly price "including" fixes and evolutions) has a flaw: it bills you for a service you may not need, and it pushes the agency to minimise time spent. For us, simpler. A clear hourly rate shown in the quote, and you're billed only if you ask us something. No monthly annuity, no "hidden share" in a subscription. Less comfortable for us to forecast, more honest for you. And it forces us to build tools that don't break every fortnight.

What we give you with the tool

Three things at delivery, included: technical documentation; a hands-on training (usually a half-day for a team, re-done free if you hire within six months); a direct line for an emergency during the first three months.

What we've seen on the ground

Six months after delivering a tool, a Friday-evening call: the software stopped recording one order type. We diagnosed that evening, fixed overnight, Monday morning it ran without any team member noticing. Billed zero: it was a delivery bug. We don't bill our own mistake.

FAQ

Hourly rate for an evolution? Stated in the initial quote, no post-signature surprise. We don't practise "urgency rate" that spikes for a fast request.

What if I stop paying for evolutions? No problem. The tool keeps running, the documentation lets you move to another provider without friction, your data stays yours.

You have a tool delivered by someone else that's living its after-delivery badly? We can take over, from the existing documentation. If it exists. Let's talk →