Transition and stabilization
We agree scope and access, recover the essential knowledge, and set up ownership, runbooks, monitoring where it is available, escalation contacts, and a baseline of known issues and risks.
Application Managed Services
Keep a business-critical application running, and change it safely.
Application Managed Services (AMS) is ongoing operation, stabilization, and small controlled changes for an existing application, run by engineers who first took the time to understand it. It always starts with Discovery.
Start with DiscoveryAMS · AFTER DISCOVERYContinuity first. Change in small steps.Onboarding fee plus a monthly fee, scoped to your application.
Who it is for
For applications the business cannot pause
The application still matters, but the documentation is thin, knowledge sits with one or two people, incidents keep returning, or nobody is sure what a change will affect. You need someone accountable to operate it, not a rebuild you did not ask for.
How the service runs
Four phases
Operate
We triage and coordinate incidents, investigate defects, handle agreed routine maintenance and releases, keep the documentation current, and report on service health and risks.
Small, controlled changes
Small, bounded fixes and improvements go through an agreed change process: peer review, tests, release evidence, rollback steps, and your explicit approval for production.
Periodic review
At an agreed cadence we review the service evidence, upcoming risks, and your priorities. If modernization makes sense, we say so; it stays a separate, optional decision.
Boundaries
Not included unless the contract says so
AMS does not automatically mean round-the-clock operation, a helpdesk, or ownership of your full infrastructure. The statement of work names the supported components, environments, support hours, response targets, and your responsibilities.
- 0124/7 coverage
- 02Guaranteed resolution times
- 03Third-party vendor management
- 04Hosting costs
- 05Major feature delivery
- 06Modernization, which is scoped separately
Who decides
You keep the important approvals
You keep priorities, production releases, rollbacks, and acceptance of remaining risk, unless the contract explicitly says otherwise. We avoid production write access while we are still learning the system, and we only promise detection or response for signals we can actually see.
Commercial basisOne-time onboarding fee plus a monthly fee, scoped per application
Starts withDiscovery
Service levelsOnly those written into the contract
Evidence
Wassermeloni: taking over support of an ERP and customer portal
Our clearest public example of this service. The case study separates what we measured from what we observed and what we do not yet know.
- Shipped
In October 2025, three days after taking over support of Wassermeloni's ERP and customer portal, we shipped a real fix to production.
- Shipped
17 tools and systems brought under one support setup, and a 272-page handbook that replaced years of scattered notes and is still maintained.
- Observed
Before accepting the work, we set the systems up from scratch and found 23 gaps between the documentation and reality.
- Hypothesis
How much time this approach saves compared with a typical hand-off. We do not have a clean before-and-after comparison on that project, so we do not claim a number.
The first step
AMS starts with Discovery.
Before we take responsibility for an application, we confirm that we can support it safely, and agree the boundary of the service from the evidence.
Start with Discovery