What it costs
Projects typically start from around 5,000 PLN net. The exact quote always follows a conversation, within 48 hours.
You will not find a table of prices for "a website" or "an app" here, because those words mean nothing until I know what sits underneath. Instead, this page describes what actually moves the price up and down — so that by the end you can estimate for yourself which side your project falls on.
What raises the price
No tests, no documentation
Every change has to be verified by hand to confirm nothing else broke. That is not a luxury — it is the only way to avoid shipping a fix that breaks three other things.
Production that cannot be stopped
Working on a live system means maintenance windows, a rollback plan and double-checking before every deployment. A database migration can be done with zero downtime — it simply costs more than one with an hour of planned outage.
Integrations with systems you do not control
An external vendor, payments, a partner API. When something on their side does not behave as documented, time goes into workarounds and waiting for their support — not into code.
Nobody knows how it works
The original author is gone; what remains is a database and a working frontend. Reconstructing the logic from what is left is a stage of its own, before any writing begins.
What lowers it
A working test environment
A copy of the system where I can verify changes without risk. It shortens every stage and removes the most expensive part — the fear of deploying.
A tightly closed scope
"Fix the payouts" is quicker and cheaper to quote than "improve the system". The narrower the task, the less I have to assume just in case.
One decision-maker on your side
Someone who can say "yes, we do it this way" without calling three meetings. Waiting for decisions can cost more than the work itself.
Agreement to work in stages
Diagnosis and the most urgent problem first, the rest after. You pay for the next stage only once the previous one works — and you can stop whenever you want.
How we get to a number
A conversation
A phone call or the chat on this site. You describe the problem in your own words — no technical specification needed.
A quote within 48h
You get scope, price and timeline by email. If I think the problem can be solved cheaper, or without me, I say so directly.
Work in stages
The first stage is usually diagnosis or the most urgent failure. You see a result before committing to the rest.
What fits into which bracket
Instead of ranges — real projects with their scope written out. Each one has a case study describing exactly what had to be done.
Common questions about pricing
How much does it cost to fix a system?
Projects typically start from around 5,000 PLN net. The exact price depends on whether the problem is already diagnosed or still has to be found, and on whether the system has tests and a test environment. You receive the quote by email within 48 hours of our conversation.
Why is there no price list with fixed figures?
Because the same task name means different things. "Fixing payments" is sometimes a single faulty condition and sometimes a rebuild of the entire payout flow with a state machine and an audit. Quoting ranges without knowing the system would be guesswork, and you would remember a number I cannot honour.
Is the diagnosis paid?
The initial conversation and diagnosis are free. You pay only for work you approve after receiving the quote.
What if my project is smaller than 5,000 PLN?
You will hear that directly, instead of an inflated offer. Sometimes an hour of consulting is enough, or pointing out what you can fix yourself — I will say so if that is your case.
Do you bill hourly or per project?
By default per project or per stage, with an agreed scope and price. I use hourly billing for work that cannot be closed upfront — for example standby during a migration, or extended supervision after a rollout.
How long does it take?
An urgent production failure — from a few hours to a few days. An infrastructure migration or legacy modernisation — from two weeks to several months, depending on scale. The timeline comes together with the quote.
Describe the problem, get a quote in 48h
A short conversation gathers the context. If your case is smaller than it looks — you will hear that directly.