Repair, takeover and modernization · remote

Repairing and taking over a system after a previous contractor.

The system works badly, the previous developer has disappeared, or an app built with Base44 or Lovable is no longer enough? I keep what works, fix the source of the errors and modernize the rest — without stopping the company’s work.

  • outages and bugs
  • takeover after a contractor
  • legacy code
  • Base44 / Lovable
  • server migration

Before you pay, you see how it will work.

A free demo: a working demo, a mock-up, a cost calculation or a repair plan. Then a fixed price in writing and a warranty of at least 30 days on every stage.

If I don’t pick up, I call back the same business day.

Client testimonial

“The program works perfectly, and on top of that we are saving money thanks to the server change.”
Jerzy Czupik, owner of a company with three points of sale Translated from Polish
01

When to call

It is a good moment to talk if…

  • A bug hits sales or billing

    The system loses orders, charges twice or stops a payout.

  • The previous contractor does not respond

    The system still serves the company, but nobody knows how to change it safely.

  • Fixes do not remove the cause

    The bug comes back in another form, and every change breaks something else.

  • An app built with Base44, Lovable or Bubble is no longer enough

    The first version works, but bugs, limits and costs keep growing.

02

Scope

What I repair and take over

First I stop the losses, then I look for the cause. I keep what works — I do not assume a rebuild from the outset.

  • Fixing outages

    Payments, billing, access and notifications — at the source, not patched over.

  • Takeover after a previous contractor

    I recover the code, the server and the data — even without documentation.

  • Modernizing legacy code

    I replace what blocks growth and leave what serves well.

  • WordPress repair

    Bugs, slowdowns, updates and new modules on an existing site.

  • Base44, Lovable, Bubble

    I will fix it, plug in custom code or move it to a more durable solution.

  • Server migration

    To a new, cheaper or more secure one — with a way back and a verified backup.

Urgent outage
call — I reply the same business day and limit the losses first
To start
free: the state of the system and a plan of action
Deeper diagnosis
when needed — the first fixed-price stage; you know what I will check and why
Rule
first a data backup and a way back, then the changes
After the repair
a warranty of at least 30 days, then IT care if you want it

Modernization instead of building from scratch

It is often cheaper and safer to modernize what already works — and the team does not have to learn everything anew.

What I do not do

I do not repair hardware and I do not build new WordPress sites — only repairs and modules on an existing one.

03

Case studies

Recovered and repaired

A system abandoned by the previous contractor, and a payout that used to break off halfway. The numbers come from real deployments.

Client testimonial · service studio, Switzerland

“We started with a single Telegram outage. Artur quickly understood the system and helped us put payouts, staff access, notifications and automations in order. Today the system runs more reliably and is easier for the team.”
Owner of a service studio · ongoing cooperation since February 2026 Translated from Polish

Company with three points of sale

Client deployment

15 s → < 1 s order printout in a system with 18,000 orders

The previous contractor disappeared, while the company kept working on the system he had built. I recovered it, modernized it and moved it to a cheaper server.

  • a new back end without stopping the company’s work
  • server change: 14 minutes of downtime, no data lost
  • a daily backup stored off the main server

Client: Jerzy Czupik, company owner.

Illustrative image of the order system — data changed for privacy reasons
Illustrative image of the application — for privacy reasons

Service studio, Switzerland

Repair, then ongoing care

126 s → 3.9 s a payout of CHF 18,080, now without errors

Without warning, the system broke off a payout halfway and left the data in an uncertain state. I changed the way it is calculated and added a correctness check and notifications.

  • 210 items settled in 3.9 seconds
  • an automatic check for discrepancies every night
  • one repair turned into ongoing care
Illustrative image of the billing and payout panel — data changed for privacy reasons
Illustrative image of the application — for privacy reasons
All case studies →
04

Terms in plain language

What the words you hear mean

You do not need to know these words — it is enough to describe what is not working. But if you hear them from a previous contractor, here is a one-sentence explanation.

System takeover
A new contractor takes over the code, the server and the data from the previous one — and takes responsibility for keeping it running.
Legacy code
A system written years ago in older technologies. It often works, but is hard to change and to secure.
Modernization
Bringing the system up to date piece by piece, without throwing away what works.
Refactoring
Tidying up the code without changing what the user sees — so that later changes are faster and safer.
Technical debt
Shortcuts and stopgaps from the past that slow down every change today. It can be paid off in stages.
Code audit
A check of the system: what works, what threatens an outage, what blocks growth. I do a preliminary one free with the demo; a full audit is the first fixed-price stage.
Show the remaining terms (8)
Documentation
A description of how the system works and how to run it. When it is missing, I reconstruct it from the code and the database.
Base44, Lovable, Bubble
Tools in which an app is assembled without programming or with the help of AI. Great for a start; at a larger scale they need a developer.
No-code, low-code
Building apps from ready-made blocks instead of writing code. Fast, but with limits that only show as you grow.
WordPress
The most popular system for websites. I fix bugs, run updates and add modules on existing sites.
Data migration
Moving data from the old system to the new one so that nothing is lost and everything adds up.
Test environment
A copy of the system on which I check changes without risk to the company’s day-to-day work.
Hotfix
A quick fix for an urgent bug on a running system — before there is time for a full repair of the cause.
A way back
Before I change anything, I secure the data and prepare a way to return to the previous version.

Also searched for

  • software repair
  • app takeover
  • developer for fixes
  • WordPress site repair
  • Lovable app not working
  • Base44 help
  • system modernization
  • source code recovery
05

You know what you are buying

How we start

Before you pay, you see how it will work.

  1. 01

    A description or a call

    The more precise the description, the more I can show at the very first meeting.

  2. 02 free

    A demo before you buy

    A working demo, a mock-up, a cost calculation or a repair plan.

  3. 03

    Delivery in stages

    Scope, price and deadline in writing. Every stage delivers something and lowers the risk.

  4. 04

    Warranty and care

    At least 30 days on every stage. Then I look after it, extend it and connect it.

Projects usually from PLN 3,000

The price agreed in writing before we start does not change. A non-disclosure agreement on request. Pricing →

  • Warranty

    At least 30 days per stage, longer for bigger projects — set in the contract.

  • A difficult case

    I look into the data, the code and the logs. If I need to go deeper, you know up front what I will check and why.

  • Urgent matters

    I reply the same business day and tell you when I can step in.

Demo before you buy · free
screen mock-up · sample dataNew orderstep 2 of 3 · detailsClientABC Ltd.ServiceAssemblyDate12 Nov 10:00AmountPLN 1,240send the quote to clientSave and sendPDFcost calculationby hand today20 hafter go-live2 hsaving≈ 18 h / month
This is what a demo can look like: a screen mock-up and a cost calculation, on sample data
06

Who I work with

For companies that want it done properly

I am most useful where the system matters for how the company runs. You talk and work directly with me.

  • Urgent repair

    in fast, with a cool head

  • Systems in production

    the ones that cannot stop

  • Payments and billing

    amounts, statuses, exceptions

  • A project with a deadline

    time and flexibility matter

Working together makes sense when:

  • Technology matters for how the company runs
  • I talk to the person who decides
  • The result counts, not the lowest price — projects usually from PLN 3,000
  • You show me how you really work

What I do not take on

  • hardware repair
  • office helpdesk
  • cheap brochure sites
  • online stores from scratch
  • ideas without a budget

If price is all that counts, you will do better elsewhere.

These are the jobs closest to this service. All types of jobs →

07

Technically

How I work and what I build on

You do not need to know any of this. But if you are comparing contractors or showing this to your IT person — this is what my work looks like from the inside.

  1. 01

    Backups that can be restored

    Daily, in a second location, with a verified restore.

  2. 02

    Every change in Git

    Described and reversible. You know what changed and why.

  3. 03

    Tests where the money is

    Billing, payments, permissions. Changes go to a copy first.

  4. 04

    Documentation and ownership

    The code, the data and the access belong to the company.

Architecture · in layers

What I build on

I pick the tools to fit the problem, not the other way round. I connect ready-made services to the rest of the system where they make sense.

Logic and API rules, permissions, background jobs
  • Node.js
  • Python
  • Deno
  • REST API
  • webhooks
  • cron and queues
  • Edge Functions
Data one version of the truth
  • PostgreSQL
  • MySQL
  • Supabase
  • SQL
  • RLS
  • data migrations
  • Excel / Google Sheets
Servers and maintenance infrastructure that does not need daily watching
  • Linux
  • VPS
  • Docker
  • Nginx
  • PM2
  • Vercel
  • Cloudflare
  • GitHub Actions
  • SSL / DNS

The layers closest to this service. Full list of technologies →

08

Questions

Frequently asked questions

Your question is not here? Call — I will answer right away.

Artur Mrowicki

Artur Mrowicki

you talk directly to me

+48 881 441 426

How much does a system repair cost?

It depends on whether the cause is known or still has to be found. To start, I check free of charge what is there and show a plan of action. When an honest diagnosis needs several days in the code and on the server, you know before the start what I will check, why, and what the result will look like — that is the first fixed-price stage. Projects usually start at PLN 3,000.

Will you take over a system without documentation?

Yes. I reconstruct how it works from the code, the database and the way people work. That is how I recovered an eight-year-old system for which the company no longer had the source code.

Will the company’s work have to stop?

Usually not. I check changes on a copy and do the switchover outside working hours. For a client with three points of sale, the move to a new server took 14 minutes.

Will you fix an app built with Base44, Lovable or Bubble?

Yes. I check what can be fixed in place and what needs custom code. Sometimes a fix is enough, sometimes it is better to move the app to a more durable solution — we make the decision together once you have seen the plan.

Do you repair WordPress sites?

Yes: bugs, updates, slowdowns and new modules on an existing site. I do not build new WordPress sites.

Do you give a warranty on the repair?

Yes. Every stage has a warranty of at least 30 days for defects within the agreed scope; longer for bigger projects — we set it in the contract.

09

Contact

The fastest way — a phone call.

+48 881 441 426

If I don’t pick up, I call back the same business day.

// Poznań · 52.4064° N, 16.9252° E CATHEDRAL TOWN HALL OKRĄGLAK BAŁTYK ANDERSIA COLLEGIUM ALTUM WARTA
Poznań — also on site Remote for clients in Poland and abroad