TMA (Outsourced Application Maintenance)
TMA (Tierce Maintenance Applicative, third-party application maintenance) means handing responsibility for keeping an existing application running well to an external provider: bug fixes, minor improvements, monitoring, user support. It differs from building a new project, the goal being to keep the existing software alive rather than build from scratch.
The typical case is a company that had its business software built by an agency or an in-house team that no longer exists, leaving nobody to fix a bug or add a minor feature. Third-party maintenance steps in: taking over the existing codebase, understanding its architecture, then handling routine requests without needing a full rebuild of the software.
Taking over a project under a TMA contract usually requires an audit phase of the existing code before any real work starts, yet many clients expect an immediate takeover. Skipping that step risks breaking features the provider doesn't yet understand. The contract should also clarify upfront what counts as maintenance (fixes, small improvements) versus what counts as a separate project (a redesign, a major new feature).
Follow Fragments Studio on Google
Add us to your preferred sources and our articles get surfaced first in Top Stories, AI Overviews and AI Mode.
