How we work
We do not show case studies with client names, because we take confidentiality seriously. Instead, you can see here exactly how a project runs and what you control at every step.
From inquiry to handover
Initial conversation
It starts with your inquiry through the contact form: a few sentences on what the app was built with, where it stands, and what worries you. We usually get back to you within two business days and clarify in a short conversation whether and how we can help. The aim is not to sell but to give you an honest assessment.
Audit of fixed scope
The audit is the first paid step. Up front, we agree what is examined, how long it takes, and what it costs. We examine code, architecture, security, dependencies, data model, and operations.
Findings report and decision
You receive the results as a report and a clear recommendation. After that, you decide at your own pace how to continue, with us or without us.
Delivery in work packages
The work is cut into bounded packages, such as closing security gaps or setting up tests and deployment. We keep you informed at short, regular intervals, typically with a brief status each week. If an assumption turns out to be wrong, we raise it ourselves.
Documented handover
At the end there is a working, documented app, with a short written overview of how it is built, how it is operated, and what to watch when changing it. You or your team can keep running it without depending on an ongoing contract with us.
What the audit delivers
- A prioritized findings report
- An honest recommendation: clean up or rebuild
- A scoped proposal for the follow-up work
Your source code and confidentiality
Before we see your source code, we agree on confidentiality. We only ask for the access the audit requires, usually read access to the repository. If your platform does not allow exporting the code, tell us in the form and we will work out what is possible.
Why no case studies
Most of our experience comes from projects with confidentiality obligations, so we cannot name specific projects or clients. That is professional discretion, not a statement about lack of experience. Instead we show the process above, typical findings on the services page, and the readiness check.