Pethe Bálintcustom business software
ServicesCalculatorCase studyBlogAbout
+36 30 267 9897Consultation
Pethe Bálint e.v.One engineer, no agency markup.1171 Budapest Törpegém utca 4 1 em. 5Tax number: 92408441-1-42Registry number: 62860071
Legal noticePrivacy policyLeave a reviewBlogLinkedInMagyar
Home / Services / System Audit and Software Modernization

System audit and modernization of existing software

For companies that already have a system, but it is slow, every change is a risk, and nobody dares to touch it. I assess its state first, then put it in order step by step.

Request an assessment

Who it is for: for companies that already have a system, but every change is risky and nobody dares to touch it.

Typical symptoms· Slow pages, timeouts· The original developer is no longer reachable· No documentation, no backups
What you get✓A written, understandable status report✓A list of what to fix, rewrite or leave alone✓Gradual fixes without downtime✓Reproducible operation

When do you need a system audit?

A business system rarely breaks overnight. It gets slower and more fragile gradually, while the company depends on it more and more.

  • →Slow pages, timeouts, stuttering at peak times.
  • →The original developer is no longer available and there is no documentation.
  • →Every change breaks something somewhere else.
  • →You are not sure there is a working backup, or that it can be restored.
  • →You are about to replace or extend the system and want to know what you can build on.

What do I examine during the audit?

The audit is 1–2 days of work at a fixed price. You do not get technical jargon at the end. You get a written status report you can understand.

  • →Performance: slow queries, caching, bottlenecks.
  • →Security: known vulnerabilities, access, outdated components.
  • →Resilience: backups and a tested restore.
  • →Code quality and maintainability: how risky it is to change.
  • →Operations: deployment, environments, monitoring.

Fix, rewrite or leave alone?

The status report gives one of these three answers for each area. Most systems do not need a rewrite: most problems come from a few well-defined places, and fixing those costs a fraction of a rewrite.

If a rewrite is the better decision after all, I explain why and propose how to move over gradually, without stopping operations.

How does the repair work?

Repairs follow a prioritised plan in small steps, at an hourly rate or a fixed price. The points causing the most risk or the most frustration come first. The system keeps running throughout, and at the end you have reproducible, documented operations.

First step1–2 daysassessment, fixed price
Fixeshourly or fixed price
Request an assessment

How we work together

  1. 01

    Discovery

    1–3 days

    A free 30-minute conversation, followed by a written proposal with a fixed price or hourly rate.

  2. 02

    Development

    2-week cycles

    A version you can try every two weeks, so the direction can still change along the way.

  3. 03

    Testing and handover

    1–2 weeks

    Your team tries it out, and we only go live once the agreed conditions are met.

  4. 04

    Launch and support

    ongoing

    30 days of free bug fixing, then an optional maintenance package.

Frequently asked questions

How long does the audit take?+

The audit takes 1–2 days at a fixed price. At the end you get a written status report and a prioritised repair plan.

Can you take over a system someone else built?+

Yes. One purpose of the audit is to find out what state the code is in and how much work it takes to develop it further safely.

Does the system have to be stopped during repairs?+

No. Repairs happen gradually and without downtime, and riskier changes are tried in a test environment first.

What if it turns out it needs a rewrite?+

Then I explain why in the report and propose a gradual migration. After the audit the decision is yours, and there is no obligation to continue.

Related articles

Legacy System: Rewrite or Modernize? How to Decide

Slow, buggy or risky legacy system? When to rewrite, when to modernize gradually, and how to start with a system audit.

Read article →

Technical Debt: What It Is and How It Hurts Your Business

Technical debt explained for managers: how it arises, what it costs, what the signs are, and how to pay it down while the business keeps moving.

Read article →

Software Maintenance and Support: What It Costs and Why You Need It

Why does a finished system need maintenance? What it includes (updates, backups, monitoring), what it costs, and how to choose a maintenance plan.

Read article →

Web Application Security for SMEs: 10 Essential Steps

10 practical steps to protect your company's web application and data: passwords, updates, backups, permissions, GDPR. No enterprise budget needed.

Read article →

Other services

Custom ERP and CRM Development for SMEs →Web Application and SaaS Development →

Let's spend 30 minutes on what your company needs.

Free consultation