The same ticket comes back every month
The problem is worked around, the ticket is closed and the cause stays. In the report it looks like productivity. In the budget it is a cost that never ends.
Why a different kind of support
A contract that counts closed tickets has no reason to make tickets stop. Ours measures whether the system gets better.
We work with an SLA, like everyone else. The difference is what we deliver alongside it: the cause of what keeps repeating, a documented system and technical health measured every month, so you can decide its future with data.
The system depends on who remembers
Business rules nobody wrote down, known by only two or three people. When one of them leaves, operations are exposed and switching vendors becomes a risk.
Debt grows without showing up in any report
Every quick fix leaves the system a little more fragile. Nobody shows the trend until the day modernizing becomes an emergency, not a choice.
What you get
Stable operations today, and a system that costs less to maintain tomorrow.
Every month of support leaves something behind: a cause solved, a rule documented, a part of the system in better health. That is what separates supporting a system from just keeping it switched on.
01
Support prepares the modernization
The team that supports the system learns it from the inside. When you decide to modernize, it runs the work with Core Up, in parts, without switching vendors and without stopping operations.
3xlower maintenance cost with Core Up
02
Fixes that do not come back
A recurring incident becomes a root cause analysis, with an owner and a deadline. Every change goes through human review before it reaches production.
97%right the first time
03
Change without scares
Rule changes, integrations or regulatory updates go into production with tests and a rollback plan. The system changes and the business keeps running.
0operational downtime with Core Up
04
The knowledge becomes yours
AI agents read the code and help write down how the system works. Our engineers review every page. The documentation follows every change and belongs to you.
05
Decisions with data, every month
A technical health report in plain language for leadership: what improved, what got worse, how much effort went to causes and how much to patches.
How we work
One way in, a cycle every month and the way out you choose.
Support is not a project with a beginning, middle and end. Once we have taken over the system carefully, the work becomes a cycle that repeats every month, and each round makes the system easier to maintain.
At the start, once
Assessment
A quality and security X-ray, a map of what is critical to the business and an SLA proposal by criticality. Proposed format: 2 to 3 weeks.
Gate · SLA and priorities approvedTransition
First we shadow whoever supports it today. Then we run it while they watch and correct us. What existed only in someone's head becomes a document.
Gate · Formal transition sign-off
Every month, for as long as the contract runs
- A ticket comes in and gets a deadline based on its criticality.
- AI agents help locate the problem in the code.
- An engineer reviews and approves the fix, which is tested before production.
- The ticket log groups whatever repeated during the month.
- Each recurring problem gets a root cause analysis, with an owner and a deadline.
- Agents write down how each part of the system touched that month works.
- An engineer reviews each page before it goes into the documentation.
- Technical debt, security, dependencies and recurring tickets are measured and turned into a report your leadership can read.
- At the monthly committee, with the report on the table, you decide the focus for the next month.
- what the committee decides guides the next month
When you decide
Modernize with Core Up
When the data shows it is worth it, the same team modernizes piece by piece, without stopping operations.
Keep supporting it
Many systems should simply be maintained. The monthly report shows when that is the case.
Bring it in-house
Documentation, reports and the system map are yours. Handing over to your team or another vendor is simple.
How the market does support
Everyone offers an SLA. Almost nobody measures whether the system gets better.
We compared what the two most common support models sell with what we deliver. The SLA is the same. The difference is in what comes with it.
How to engage
Three formats, based on where your system stands.
All of them start with the assessment and have an SLA by criticality. What changes is how much capacity goes to evolving the system and how much to preparing its modernization.
Corrective work under SLA
Essential Support
Who it is for: A stable system that changes little but cannot stop.
Fixed monthly fee, after a proposed 4 to 6 week transition
- Corrective service with response times by criticality
- Root cause analysis of recurring incidents
- Living documentation of everything we touch
- Monthly report on tickets and SLA compliance
Corrective, evolutionary and technical health
Evolving Support
Who it is for: A system the business still changes every month: rules, integrations, regulatory updates.
Monthly capacity allowance, reviewed every quarter
- Everything in Essential
- Evolutionary work within the allowance, prioritized with the system owner
- Living documentation of the whole system
- Monthly technical health report for leadership
- Tech Talent reinforcement at demand peaks
Prepares for Core Up
Support with Continuous Modernization
Who it is for: For those who already know the system needs to be modernized and cannot stop operations to do it.
Monthly allowance, with a modernization plan reviewed every quarter
- Everything in Evolving
- Part of the allowance set aside to reduce technical debt
- Modernization map: what, in which order and with what risk
- First parts modernized with Core Up by the same team
Format, SLA by criticality and price come out of the assessment, not a price list. You can change formats when your system moves to a new stage.
BRK · Sanitation
BRK & DB1 case: from the Minha BRK app to agentic engineering.
A partnership that started with the Minha BRK app and reached agentic engineering: the migration of a real portal, 4x faster.
26 years supporting software that cannot stop, with a process audited by outsiders.
The natural path
Support it today, modernize it when it makes sense.
Frequently asked questions
Before handing over support.
How is this different from a regular AMS contract?
Traditional AMS (Application Management Services) measures closed tickets and hours used. We also work under an SLA, but we measure whether recurring tickets go down, document the system and deliver its technical health every month. Support prepares the modernization instead of just postponing it.
How does the transition from the current team work?
In two phases. In shadow, our engineers follow the current team and document the system with help from agents. In reverse shadow, we run it and the current team watches and corrects. The handover only happens after a formal sign-off, with criteria agreed beforehand.
Our system is old and barely documented. Will you take it on?
Yes, that is the most common case. AI agents help read the code and write down rules, flows and weak spots. Our engineers review everything with the people who know the system. The documentation lives in your repository and is updated with every delivery.
What is measured in technical health?
Technical debt, security vulnerabilities, outdated dependencies, test coverage, recurring incidents and how effort is split between corrective work, evolutionary work and debt reduction. The report shows the month by month trend, in business language.
How is it priced?
It depends on the format. Essential is usually a fixed monthly fee. Evolving and Continuous Modernization use a monthly capacity allowance, reviewed every quarter. Format and price come out of the assessment, not a price list.
Do we have to modernize afterwards? Are we locked in to DB1?
No and no. Many systems should only be maintained, and the data shows that. The documentation, reports and system map are yours. If you want to bring support in-house or switch vendors, the handover is much simpler than it was for us.