Six months after launch, how do you know it worked?

Six months after a custom application goes live, you have a feeling but no clear answer: did it work? The short answer comes down to three signs you can check yourself, without waiting for a formal review. The rest of this article explains how to look at each one.

The first sign: the old tools have actually disappeared#

The simplest test is one question asked to each team: "Do you still go back to the old file, just in case?" If the answer is yes, even occasionally, adoption is not finished.

A shared spreadsheet still circulating by email, a WhatsApp group still receiving site photos, a paper binder still filled in "to be safe": these are duplicates that cost time without adding anything. They signal a lack of trust in the application, not a habit that simply takes time to fade.

In this example, adoption is halfway there: one tool is gone, two still run in parallel. That is not a failure, it is a waypoint, as long as the number of teams still doubling up keeps dropping every month.

The second sign: one specific task is measurably faster#

No need for a complex dashboard: a single task, timed before and after, is enough to tell whether the change is real.

At a mid-sized building materials distributor, the branch manager used to check the order status of the three other branches every morning: one call per branch, about fifteen minutes each, so forty-five minutes a day. Six months after the application went live, the same check takes under two minutes, on one screen shared by all four branches.

Over a twenty-working-day month, that gap adds up to roughly fourteen hours recovered for this one manager. At thirty euros an hour fully loaded, a cautious assumption, that is over €400 a month, for a single task, in a single branch.

The same calculation works for any repeated task: following up a quote, finding a site photo, checking a supplier invoice. What matters is not which task you pick, but that it is timed the same way, before and after.

The third sign: change requests keep coming in#

An application that has not received a single request in three months is not necessarily perfect. It is often a sign that it is no longer really used: nobody asks anything of a tool they have stopped opening.

The opposite is true too: small requests coming in, "it would help to have this column", "could we sort by delivery date", show that the application has become part of someone's daily work. It is the most reliable sign, because it comes from the teams themselves, not from a metric built to feel reassured.

An application built for the company keeps evolving after launch: these requests find a path forward, without restarting a whole new project.

What changes with an application built for the company#

After the audit that starts the project and an application your teams actually use, what is left is the review itself. For the owner, the three signs fit on one screen instead of three separate spreadsheets: who still uses what, the time saved on the tasks worth tracking, and the requests in progress.

That same screen is used all month long, not only at the six-month mark. A branch manager or a site supervisor sees their own slice of it: the figure that concerns them, not the whole company. See what a custom-built application covers.

What not to look for at six months#

A drop in revenue or margin cannot be measured at this stage: too many other factors come into play over such a short period. The three signs in this article measure adoption and time recovered, not the company's profitability.

It is also normal for one or two screens to still be missing. A first version covers the essentials, then grows with the teams' real requests, not with a list decided in advance.

Measuring the success of a custom application: the key takeaways#

Three signs are enough to tell where an application stands six months after launch: the old tools that have truly disappeared, one specific task that is measurably faster, and change requests that keep coming in. None of them needs a complex dashboard, just a question asked to the teams and a stopwatch.

If none of these three signs shows up six months after launch, the question is not whether the application should continue, but why adoption did not happen, and what needs adjusting before going further.