A clear scope. A known next step.

We agree the scope before the review starts. Most communication happens in writing. You know what we need and when to expect the report.

HOW THE AUDIT WORKS

  1. Tell us about the product.

    Describe the product, the concern, and any timing constraints. We’ll confirm whether the audit is a good fit.

    At this stage: product context, without credentials or confidential source code.

  2. Scope & paperwork

    We agree the scope, fixed fee, payment terms and target dates. We then prepare the agreement for signature and issue the invoice.

    If confidential information is needed to define the scope, we address confidentiality before it is shared.

  3. Share the agreed materials.

    After the contractual stage, we request the access and context needed for the review. We confirm the start and delivery dates with you.

    The five working days start once the signed agreement, agreed payment and all required materials are in place.

  4. Receive the findings and plan.

    The report explains the main risks, supporting evidence, and suggested order of work. An optional 30-minute Q&A is included.

    You can use the plan yourself or share it with a developer. Implementation with us is discussed separately.

The context that makes the review useful.

The product and the decision

What you want to understand about the product and which journeys matter most to its users.

The agreed materials

The access and information needed for the agreed scope, shared after the contractual stage.

Answers to context questions

You or someone who knows the product can answer questions as they arise. Most communication happens in writing.

Clear access rules before we begin.

How information may be used

We agree what can be reviewed, who can access it, and how tools may be used. Any restrictions are part of that conversation.

What could be verified

The report distinguishes observed findings from questions that need more verification. If materials are missing, we agree the next step before starting the review clock.

A plan you can put to work.

The recommendations explain what to improve first, what to keep, and where technical help is needed. We state the limits of the review so you can see where questions remain.

See how this looks in the report →

Start with what is happening.

A short description of the product and the concern is enough for the first enquiry.

Request audit availability

Analytics & session replay

Detailed privacy settings

Your saved choice: Not selected

Allow PostHog EU to measure visits, form outcomes, browser errors and page performance, and record masked sessions to find usability problems?

Analytics and session recording are optional. Their software loads only after you allow them. You can use the site and contact form without them.

A random browser ID links repeat visits, events and recordings to a pseudonymous profile. These data are not fully anonymous.

Cloudflare estimates your country from the network connection. We send only the country code to PostHog; city, precise location and the original IP are not stored in analytics events.

Session replay reconstructs interactions with this website. We mask all page text and exclude the entire contact form before transmission. Form entries are not sent to analytics. We do not sell your data.

We save your allow/refuse choice for 180 days. This is not the retention period for analytics data. Change your choice at any time through Privacy & choices in the footer. Your theme is also stored locally.

Do not allow stops future analytics and recording. To delete analytics linked to this browser, select Request deletion of analytics data in Privacy & choices; PostHog processes the request under its data-deletion procedures.

Hosting, form security and operational server measurements continue separately.

Read Privacy Policy ↗

Closing with ×, Escape or a click outside saves a refusal and stops analytics and recording.