Contact

Tell us what you are running, and what is worrying you about it

A few lines is plenty for a first message. You will get a straight read on whether an audit is worth doing right now, from one of the two people who would run it — not from a form queue, and not from somebody whose job is to book a demo.

Start a conversation

Nothing here commits you to anything, and we will not put you on a list. If the honest answer is that you do not need an audit yet, that is the answer you will get.

Optional.

Direct
[email protected]

Mail lands in the same place the form does. If you are reporting something urgent about your own estate, put URGENT in the subject and it is seen out of hours.

AnsweringLondon · London
Monday to Thursday
08:30 – 18:00
Friday
08:30 – 16:00
Weekends
Incidents only
Live engagement
Shared channel, any hour

During an engagement you get a shared channel and both auditors in it. That one is answered whenever something is actually happening.

Worth including
  • Which clouds, roughly how many accounts or subscriptions, and which regions you actually use.
  • What is driving it — a customer questionnaire, a funding round, an audit date, or a bad feeling.
  • Whether anyone has looked before, and if so whether you still have the report.
  • Who would own the fixes afterwards, because that changes what we write and how.
What happens next

A person, a call, and a written scope you keep either way

Nothing you send here puts you in a pipeline. There is no sequence of follow-up emails, because a practice that has to chase people is a practice whose first call was not useful enough.

01A person reads it

One of the two people who would run the work, not a form queue. Usually the same working day, always within one.

02A short call

Forty-five minutes, no deck. We ask about the estate and you ask whatever you like about how we work.

03A written scope

What we would look at, what we would not, what it costs and how long it takes. Fixed price. It is yours to keep either way.

Before you ask: the access

This is the first thing every serious engineer asks, so it is answered here rather than in a call. We ask for nothing that can read your data.

What we ask for
A read-only role you create, from a policy we give you in full, with an external id.
What it can do
Read configuration and metadata. It cannot read object or database contents.
How long it lasts
The engagement window plus seven days, then it expires on its own.
Who uses it
The two named auditors on your scope. Every call is logged in your own trail.
Revoking it
Delete the role. Nothing on our side needs to happen, and we will notice within the hour.