An engineering firm closes the commissioning phase of a project: it delivers the georeferenced asset register, activates the CMMS-plus-GIS platform it prescribed, delivers the two training days contracted with the client's maintenance team and signs the acceptance minute. Six weeks later, the project manager opens the team's monthly time review and notices a pattern they had not anticipated. Their most senior operations lead has been reporting between fifteen and twenty client calls per week. Each call runs thirty to forty-five minutes. None of them is billed, because they fall inside the project's technical warranty period. The running total climbs above ninety hours of the senior lead's time, plus another forty of the systems technician the less operational questions get routed to. The client is satisfied. The project's margin is not.
The client's learning curve does not disappear because the contracted training was delivered. It changes phase and it changes cost center. During training, the client absorbed it as internal time; after handover, the engineering firm absorbs it as hours that appear on no invoice and yet show up on the quarterly margin report. It is the least visible margin-erosion line in a technical office's P&L, and precisely because of that it is rarely tracked with the discipline that billable hours receive.
What happens in the weeks after handover
The calls are not complex technical inquiries. They are reproducible scenarios that training did not fully close. The maintenance supervisor tries to launch a preventive plan against a network segment that was not part of the start-up scope and cannot find the configuration path. A field operator tries to sign a work order against an asset whose criticality was mislabeled and cannot proceed. A quality lead wants to filter the history by contractor and does not remember which combination of fields holds the filter. Each of these situations resolves in five minutes with a shared screen and a bit of extra context; the problem is not resolution, it is volume. In a project with fifty active client users, a rhythm of twenty weekly calls sustained across eight weeks equals the hours budget of a full team member for that period, with no corresponding line in the contract. And the pattern does not spike and then settle; it decays slowly, week after week, until it merges with the baseline of "regular client relationship" and stops being visible as a project cost at all — which is precisely the moment it becomes hardest to defend on the following commercial negotiation.
The underlying mechanism is no pedagogical mystery: it is Ebbinghaus's forgetting curve, described more than a century ago and confirmed in every retention study since. Without spaced repetition, most of the content taught in an intensive training day has diluted within seven days. The kick-off session the engineering firm delivers over two consecutive days does not defy that curve; it confirms it. If the platform's interface does not compensate for the retention drop through daily use — natural vocabulary, short itineraries, obvious visual cues — the gap is filled by the engineering firm in unbilled hours.
How platform selection amplifies or dampens the line
The duration and intensity of the post-handover curve depends first on the design of the prescribed platform. Tools with complex per-role configuration, interfaces loaded with unranked options, internal terminology that does not match the client sector's vocabulary and workflows that demand more than seven or eight clicks for daily tasks produce long curves. Tools with progressive disclosure — showing the user only what they need, when they need it — with terminology aligned to the vocabulary a maintenance operator actually uses, and with workflows that resolve the typical task in three or four steps, produce short curves. The license price difference between the two categories is usually irrelevant compared with the difference in hours absorbed by the engineering firm in the post-handover phase.
How to quantify the cost before the next project
The discipline that closes this gap is straightforward and rarely applied: log and classify every post-handover interaction with the client during the first quarter after formal closure. The technical office defines a specific time code — something like "post-handover non-billable support" — and requires leads to charge time to it every time they take a client's question. After three consecutive projects, the office has an objective figure: how many post-handover hours a typical project absorbs, and how that figure moves with the platform prescribed, with the client's sector and with the size of the client's operations team. That figure enters the platform comparison for the next project with more weight than the feature list. Any platform whose typical post-handover support cost exceeds five percent of project hours is commercially disqualified for tenders where the margin is defensible but not elastic.
Verification before prescription can also be run as a short, reproducible pilot. The technical office selects an average user from the client — not the most motivated nor the most resistant, just the typical profile — and asks them to complete three concrete tasks at the end of the training session. One week later, without any intermediate reinforcement, the same user attempts the three tasks again. The share of tasks resolved without help is the one-week retention metric. Any platform with retention below sixty percent in this exercise is a platform with a long post-handover curve, regardless of what its commercial sheet or its certified-training documentation may claim.
What Maptainer brings on the engineering-firm side
At Maptainer, we work with technical offices that apply this discipline and then compare. The web interface reduces the surface of "how do I do X" questions, because the asset manager's or field operator's daily task resolves in three or four steps with vocabulary aligned to industrial maintenance; the mobile app captures a signed intervention in fewer than five taps, against the fifteen-plus taps common in heavy desktop clients. In the projects we have observed, the line of non-billable post-handover hours drops between fifty and seventy percent versus reference deployments with heavier platforms, and that delta translates directly into project margin and into the office's capacity to take the next engagement without expanding headcount.
The conversation the technical office is not having
In the annual P&L review, the office examines billable lines by client, the project mix and structural hours. The line missing from the review is the one that explains much of the unexplained variance across comparable projects: how many hours the team absorbed in unbilled post-handover support. When that line enters the analysis, platform selection for the next project starts to incorporate the expected cost as a primary economic variable alongside license price, and the conversation with the client at the start of the second project can be structured around an explicit, billable support model rather than perpetuating the implicit assumption of unlimited availability. The office that starts operating with that number in view competes on delivered profitability, which is the ground on which senior clients decide who runs their next project.