What it costs, before any work starts.

Scope and testing windows are written down before anything starts. Tests that could knock you offline are left out unless you ask for them in writing, and the plan names who we call and when we pause if something looks like it could affect patients or clients.

A scan is a tool listing known problems. We're people acting like the attacker: we chain small problems together, try the stolen-password tricks, and poke at your AI tools. Then we show which problems actually reach your data or your bank account. A scanner can't hold a conversation with your chatbot or notice a hidden inbox rule.

The models help us try more things in a week than a person could alone. A person picks what to try, reviews what the models propose before it touches your systems, and checks findings by hand before they go in your report.

We aim to keep the least we can to prove a finding, for example a blurred screenshot instead of the record. How evidence is stored, and when it is deleted, is set out in your engagement agreement.

A report whose first page tells you what to fix this week, the technical detail for whoever does the fixing, a walkthrough call, a retest of the issues you fix, and an attestation letter for your auditor, insurer or biggest customer.

If the chatbot can see bookings, orders or customer details, someone will eventually try to talk it into sharing them. The AI risk quiz takes two minutes and tells you whether that applies to you.

It depends on scope and our calendar. We agree start and end dates in the quote, and most small-business tests take a week or two of testing.

Yes. We offer weekly and biweekly plans. Each cycle we look at what changed, try to break it and send a short report. A subscription usually starts with a one-off test so there is a baseline. Cadence, scope and cancelling are set out in the subscription agreement.