1. Home
  2. Services
  3. Consulting, audit & code review

Web, marketing and advice

Consulting, audits and code review without the fluff

Before you invest in a bigger project, check that you are heading the right way. I review your website, app, architecture or AI idea and you get a clear recommendation: what to fix, what to leave, what pays off first and what does not pay off at all.

Who it is for: For owners and managers who need a second opinion before deciding, for companies whose website or app was built by an external supplier, and for teams that want a code or architecture review.

Price
CZK 1,200 / hour
Typical timeline
Within a week
You get
A written summary with priorities
Commitment
None; you can stop after the first hour

01

This is probably what hurts.

  • You received a quote for tens of thousands and do not know whether it is reasonable.
  • Your site or app was built by someone who is no longer reachable and nobody knows what is inside.
  • You have an AI idea but do not know whether it makes sense or where to start.
  • The site is slow or not found and you do not know the cause.
  • The team is slowed by technical debt and architectural decisions that keep getting debated.

If you nodded at least twice, it is worth a conversation.

02

What we actually solve.

Typical cases clients bring. Yours may look different; we always start from what you need.

01

Technical and SEO website audit

Speed, mobile usability, accessibility, structure and technical SEO including metadata, structured data and indexing. You get a list of findings ordered by impact and effort.

02

Code review and architecture review

I go through the code or system design, point out risks (security, performance, maintainability) and propose concrete fixes.

03

A second opinion on a quote or solution

I assess a supplier’s quote or the chosen technologies. I say what is proportionate and where you are paying for needless complexity.

04

Assessing an AI idea

We check whether AI makes sense in the process, what it would cost and where the risks are. You get a realistic plan, not a marketing promise.

05

A plan for next steps

We turn a vague intention into a brief that can be priced and delivered, with me or with another supplier.

03

How it works, step by step.

For each step you see what I do, what I need from you and what you hold afterwards. No black box.

  1. 01

    Intro call

    Within 24 hours

    I do

    I learn what you are dealing with and what you need to decide. I tell you whether a consultation is worthwhile and estimate the scope.

    You do

    Briefly describe the situation and send links or access to what is to be assessed.

    You get

    An agreed scope and an hour estimate.

  2. 02

    Investigation

    1–3 days

    I do

    I go through the site, code, documentation or quote. I verify what can be measured (speed, indexing, security headers, load).

    You do

    Answer follow-up questions.

    You get

    Working notes and first findings.

  3. 03

    Walk-through with you

    Agreed date

    I do

    We go through the findings online. I explain them in plain language, without jargon, with examples.

    You do

    Ask questions and say what your priorities are.

    You get

    Shared understanding and priorities.

  4. 04

    Written summary

    Within 2 days of the walk-through

    I do

    I prepare a short document: findings, recommendations, priorities and effort. What can be done now, within a month and what can wait.

    You do

    Decide what comes next.

    You get

    A prioritised list of steps you can hand to anyone.

04

What it can look like in practice.

Model situation: a quote for a new site at sixty thousand

A small-business owner received a quote to rebuild the website and wants neither to overpay nor to buy something that does not help.

Before

  • Unclear what in the price is necessary and what is not.
  • No comparison with an alternative.
  • Fear of a traffic drop after the rebuild.

Process

  1. I review the current site and the quote.
  2. I measure speed, SEO and what current content contributes.
  3. I compare solutions and propose a scope.
  4. I write up recommendations and risks.

After

  • You know what is needed and what is not.
  • You have arguments for the supplier negotiation.
  • You decide on facts.

An illustrative scenario, not a specific client. The recommendation always rests on your actual situation and may well conclude that a rebuild does not pay off.

05

What I build with, and why.

Measurement tools
Lighthouse, PageSpeed, Search Console, header and sitemap analysis. Where possible I rely on numbers.
Code review
TypeScript, React, Node.js, Python. I focus on security, performance and maintainability.
SEO and content
Structure, metadata, structured data, internal linking, indexing.
AI assessment
Checking suitability, costs and risks before anything is built.

What you get at the end.

  • Investigation of the site, code or proposal
  • A walk-through of findings with explanations
  • A written summary with priorities
  • An effort estimate and solution options
  • A plan of next steps usable with any supplier

06

What it costs and how long it takes.

from CZK 1,200 / hour

Typical timeline: Within a week

Before starting I estimate the hours and will not exceed them without your approval. If after the first hour we find further work pointless, we stop.

Full price list

What moves the price

  • Size and condition of the site or code
  • Depth (quick overview vs. thorough audit)
  • Whether you need a written output
  • Availability of material and access

When it does not make sense.

I would rather say so now than have you pay needlessly.

  • You want me to do everything straight away. A consultation is analysis and a plan; delivery is a follow-up project.
  • You are looking for confirmation of a decision already made. I will tell you uncomfortable things too.
  • You need a formal security certification or a legal opinion. That requires a specialist.

07

What people ask most.

Is a consultation useful without a finished brief?

Yes. We can start from the problem you face and turn it into a realistic brief together. That is often the most useful output.

How many hours will a website audit take?

A quick overview takes 1–2 hours; a thorough technical and SEO audit of a medium site usually 4–8 hours. I estimate the hours before starting and do not exceed them without agreement.

What do I get at the end?

A short written summary: what is fine, what to fix, in what order and how much effort each takes. You can pass it to anyone who will implement it.

Do I have to keep working with you afterwards?

No. A consultation is a standalone service with no obligation. If delivery with me makes sense I will offer it; if not I will say what to hand to whom.

Can you review code from an outside supplier?

Yes. I need access to the code or repository and a short description of the context. I focus on risks and what could cause trouble in further development.

How soon can we meet?

Usually within a few days. You get a first reply within 24 hours.

08

Let’s talk it through.

Write a few lines about what you are dealing with. I will reply within 24 hours with a view on whether and how it makes sense, before you commit to anything.

Drop a message

Tell me about your project. The button opens your email app with a prepared message.

Prague time. I will confirm availability with you.