Consulting, audit & code review
Before you pour money into it, I want to see what you already have. I go through the site or app you run, read the code and write up findings: what is fine, what will hurt in six months, and what it costs to fix. If the answer is that it should be rebuilt, I will say so. And if the answer is to leave it alone, I will say that even louder.
Who this is for
- An agency quote is on your desk and you cannot tell what the price is actually for
- The app runs, but every change takes longer than the last and nobody knows why
- The developer who wrote it left and nobody dares touch the code
- You have a team and need a second pair of eyes, not another salary
What people order most often
Each one has an agreed output. You are buying a document, not an hour of talking.
- Technical audit of a site or app. Speed, accessibility, security, dependencies, behaviour under load. Output: findings split into fix now, fix within six months, leave alone.
- Technical SEO audit. Whether the site can be indexed at all: URL structure, redirects, canonicals, hreflang on multilingual sites, structured data, sitemap and Core Web Vitals. Output: the list of faults stopping Google from reading your pages or filing them correctly. I do not do content SEO or link building; for that I will point you elsewhere.
- Code review. I read the code somebody delivered to you, or what your team writes. Output: risks and technical debt with effort estimates.
- Second opinion on someone else's quote. Send the brief and the offer. Output: what the price leaves out and what to ask before you sign.
- An hour on architecture. We compare the options and what each costs to run, not just to build. Output: a direction, and why the rest fell away.
- Ongoing care. A monthly retainer, so somebody who knows your system reviews the bigger changes.
What you get
- Written findings, not a verbal summary nobody remembers a month later
- Findings ordered by impact, not by the order I tripped over them
- An effort estimate in hours or days on every item
- Measured numbers and links to the exact lines, so you can check me
- A call over the findings, and the right to forward the document
How it runs in practice
- 1. Intro call, 30 minutes, free. You say what you are dealing with, I estimate the scope in hours.
- 2. Access and an NDA. I sign before I open the repository. Read access is enough.
- 3. The work, 1 to 2 days. I read the code, measure the running system and note where each finding came from.
- 4. Findings in writing. Ordered by impact, with effort estimates and what I would fix first.
- 5. Call and decision. Then we part ways, agree on fixes, or I point you at somebody better suited.
All of it works remotely, in English, on CET hours. If rebuilding a missing piece turns out cheapest, internal tools and interfaces over your data start at CZK 12,000. New sites have their own page, custom web development.
When I will talk you out of it
- When the system is a month old. The author is usually still reachable and asking them costs nothing.
- When a rewrite is already decided. Auditing code that disappears next month is paid reading. An hour on the new architecture is worth more.
- When you want a rubber stamp. I do not confirm an opinion you already hold. If the other side is right, the document says so.
- When there is no budget for fixes. Findings with no money behind them are a list of worries.
Parameters
FAQ
What does a consultation or an audit cost?+
CZK 1,200 an hour, billed on time worked. A smaller site is 4 to 6 hours, an app with a backend 8 to 16. Other rates are on the pricing page.
What should I prepare?+
Read access to the code, the address of the running system, and one line on each thing that annoys you.
Do I get anything in writing?+
Yes, it is the main output: findings ordered by impact, an effort estimate on each, a suggested order of repair.
Can you review a quote from another company?+
Yes, often. Send the brief and the offer and you get a note on what the price leaves out and what to ask before signing. If the quote is fair, I say so.
Do you implement the fixes after the audit?+
Yes, though you do not have to. The findings are written so your own team can work from them. A paid consultation comes off a follow on quote ordered within 90 days.
How long does an audit take?+
Within a week from order to written findings. The work itself is one to two days.
Do you work remotely, and in which time zone?+
Yes, entirely: video call and a shared document, office hours in CET. I work across the EU in English and invoice in CZK, no VAT added.
Related
- Custom web development, when you want a site built, not advice
- Automation & integrations, when data gets retyped between systems
- Data, RAG & backend, when the question is what the data can carry
- Pricing, rates and lead times in one place
- Projects, what I built and how it turned out
Got an idea for a website or app, or just a question about how to approach it? Write me a few sentences about what you're solving and I'll get back to you within 24 hours.
Write to me