WHEN AN APPLICATION CAUSES TROUBLE
Application diagnosis
Application diagnosis is a paid audit of a web, mobile or SaaS application that someone has already built. We check the code, architecture, dependencies, performance, deployments and access, then write down what to do about it. You get a written report: every finding has evidence, an impact, a severity and an effort estimate.The plan ends with a decision: fix point by point, fix in stages, or rewrite a part.The report is yours. You can give the repair to us or to another vendor. If the project goes ahead with us, the cost of the diagnosis counts towards it.
Call: 15 minutes, video or phone, no commitment · Rather call right away? +48 663 877 600
- before the start, for the scope in the contract
- Price in writing
- from access to report
- 2–6 weeks
- to use with any vendor
- Your report
- towards the project if we go ahead together
- Credited
WHEN IT PAYS OFF · 4 SITUATIONS
When an application diagnosis makes sense
A diagnosis is not a check-up “just in case”. You order one when you have a decision to make and don't know what state the application is in.
Situation 1
The vendor disappeared or never finished the project
You are left with an application nobody in the company knows. You don't know whether the code in the repository is the code running in production, or who has the server passwords.
The question for the diagnosis: can what I have be developed further — and is it even mine?
Situation 2
The application slows down and every change breaks something
Users report bugs, fixing one thing breaks another, and releasing a new version stresses the whole team.
The question for the diagnosis: where is the bottleneck, and why are changes risky?
Situation 3
You are taking over a project or buying a product
You are changing vendors, taking over an application from another team, or assessing a product before buying or investing. When the whole company is assessed before a transaction, we work as technology consultants.
The question for the diagnosis: what exactly am I taking over, and what does it cost to keep it running?
Situation 4
You need a quote for a repair or an extension
You want to add a feature or fix the application, but two quotes differ several times over, because no vendor has looked at the code.
The question for the diagnosis: what does the change really cost, and where to start?
PROCESS · 4 STAGES
How an application diagnosis works
Every stage ends with something you get in hand. What usually takes the longest is not the review itself, but gathering the access.
15 minutes · free
A call and the question for the diagnosis
You tell us what is happening with the application and what decision you face. Together we agree on one question the diagnosis is to answer. If a simpler route will do, we say so straight away.
What you get:
An assessment of whether a diagnosis makes senseA draft scope and a list of the access we need
Before the start
Scope, contract and access
We confirm the scope and the price before the start. We sign a contract with a confidentiality clause and, when the diagnosis needs access to personal data, a data processing agreement too. You gather the access: repository, server, deployment tools, logs, a copy of the database, documentation and the contract with the previous vendor.
What you get:
The scope and the price in writingAn access checklist
First findings after 1–2 weeks
Review and measurements
We read the code, run the application in a separate environment, measure performance and go through the eight areas in scope, starting with those closest to your question.
What you get:
Findings with evidence, collected area by area
In total: 2–6 weeks
Report and walkthrough
We hand over the report with the findings and the plan, then walk you through it in a meeting. You decide what comes next: with us, with another vendor or with your own team.
What you get:
A report with findings, severity and effort estimatesA plan with a verdict and the order of stepsA meeting to go through the results
PRICE AND BILLING
What an application diagnosis costs
A diagnosis usually takes 2–6 weeks from full access to the report.
We set the price before the start, for the scope written into the contract. It depends most on four things:
- Size of the application — the number of modules, user roles and screens.
- Number of platforms — a web application alone, or a mobile app and an admin panel as well.
- Integrations — payments, accounting systems, ERP, external APIs.
- Available environments — whether there is a test environment and a database copy, or they first have to be rebuilt.
The diagnosis is paid because it is work on your code, not a sales conversation. If you then give us the repair or the extension, the cost of the diagnosis counts towards the project. If you choose another vendor, the report stays with you.
WHO IT IS NOT FOR
What the diagnosis does not cover
We would rather say this before the call. In these situations we recommend a different route.
Penetration tests and compliance audits
A penetration test, a security audit under the Polish National Cybersecurity System Act and compliance audits (GDPR, ISO, SOC 2) need specialised or certified auditors. We recommend partners.
One small fix
When you know what needs fixing and it is one thing, a diagnosis won't pay for itself. Your current vendor or a freelancer will make such a change faster and cheaper.
An assessment of the company's whole IT
When the question concerns many systems, technology strategy or choosing an ERP rather than one application, the right service is technology consulting.
Licence audits and old systems
We don't check whether software licences are legal. Nor do we work with very old technology — mainframe systems, old JEE or custom ERPs from over a decade ago.
FAQ
Questions before ordering a diagnosis
What does an application diagnosis cost?
We set the price before the start, for the scope written into the contract. It depends on the size of the application, the number of platforms, the integrations and whether there is a test environment. If after the diagnosis you give us the repair or the extension, its cost counts towards the project.
How long does a diagnosis take?
Usually 2–6 weeks, and you get the first findings after 1–2 weeks.
We count the time from the moment we have full access. What most often stretches it is not the review, but missing access, no test environment, or nobody who knows the application's history.
Can I give the repair to another company?
Yes. The report is yours and you can use it whether or not you keep working with us — hand it to another vendor or attach it to a request for proposals. We write the findings so that any team taking over the work can understand them.
What do I need to prepare before the diagnosis?
Access to the code repository, the server or cloud, deployment tools, logs and external services. Plus a copy of the database, any documentation there is, and the contract with the previous vendor. You get the checklist after the call.
What to watch for in the contract and in the rights to the code, we cover in the article How to choose a software house.
What if the previous vendor won't hand over the code or the access?
Then we start the diagnosis from what you have — the domain, the accounts, the contract, the running application — and establish what is missing and whose name the services are registered in. The rights to the code follow from the contract. When a dispute needs a lawyer, we say so plainly.
Does the diagnosis cover security?
The basics, yes — login and permissions, passwords and keys in the code, dependencies with known vulnerabilities, backups. We don't do penetration tests or compliance audits (Polish cybersecurity act, GDPR, ISO). When the report shows they are needed, we recommend partners.
Do you sign a non-disclosure agreement?
Yes, before the diagnosis starts. When the work needs access to personal data, for example a database copy with customer data, we also sign a data processing agreement. The free introductory call needs no such agreement.
What if after the diagnosis I want you to fix the application?
We run the repair as a project in the stages of the plan, and the cost of the diagnosis counts towards it. We don't take small hourly fixes in someone else's code — we work by project, because only then are we accountable for the result.
RESOURCES · BEFORE WE TALK
Before we talk
ARTICLE
Software audit and application audit — what the diagnosis checks, what the report contains and how long it takes
Software audit of an app or SaaS: what it checks, what the report should contain, how long it takes and how to read the result.
ARTICLE
Taking over a software project from the previous vendor — what to hand over, what to check in two weeks, fix or rewrite
A software handover checklist for taking over a project: what the previous vendor hands over, a two-week review, then fix or rewrite.
ARTICLE
How to choose a software development company — checks, contract and rights to the code
How to choose a software development company in Poland: reading reviews and rankings, checking KRS filings, fixed price vs time and material, and code rights.
// Next step
Describe your application. We reply within 24 h.
What doesn't work, what it is built on and what you want to do with it next. A few sentences are enough.
What happens next
- We read your message and reply within one working day.
- We set up a short call about the scope, with no sales pitch.
- You get proposed stages and a price range.