Check your own setup.

The questions I would ask in a first conversation, as tools you can run yourself. They run entirely in your browser: nothing you enter is stored or sent anywhere unless you choose to email it to me.

Recurring work calculator

What the repetitive work costs you a year

List the tasks someone does every week that follow the same rules every time. The examples are typical; change them to yours, or remove them.

Wage plus taxes and benefits. If you do not know, 1.3× the wage is a fair guess.

60%

An assumption, not a promise. Most tasks keep a human step somewhere.

96 h/yr
80 h/yr
200 h/yr
Hours a year
376
Working weeks
9.4
Cost a year
$13,160
Could come back
$7,896

Calculated at 48 working weeks a year and 40-hour weeks. This is what the work costs you now. It is not a quote, and it runs entirely in your browser.

Email me this list

Cloud foundation check

How bad would a bad day get?

Ten questions about the basics that decide how far an incident reaches. They apply whether you are on Microsoft 365, Google Workspace, Azure, AWS or a mix.

  1. 01Is multi-factor sign-in required for every account, admins included?

    Stolen passwords are still how most small-business incidents start. MFA everywhere stops most of them for very little effort.

  2. 02Do admins use a separate account for admin work?

    If the account that reads email is also a global admin, one phishing link reaches everything.

  3. 03Has a backup been restored, as a test, in the last year?

    A backup nobody has restored is a hope. The test is what tells you how long a bad day would really last.

  4. 04Could you list everyone with admin access today, from memory or one screen?

    Access accumulates. Contractors, former staff and “temporary” grants are where the surprises are.

  5. 05When someone leaves, is their access removed the same day?

    Offboarding that depends on someone remembering is offboarding that sometimes does not happen.

  6. 06Are there no shared logins in daily use?

    Shared accounts mean no MFA you can enforce and no record of who did what.

  7. 07Does your email domain have SPF, DKIM and DMARC set up?

    Without them, anyone can send mail that looks like it came from you, and your real mail is more likely to land in spam.

  8. 08Are sign-in and audit logs kept long enough to investigate something months later?

    Default retention is often 30 to 90 days. Incidents are frequently found later than that.

  9. 09Are system passwords and keys kept in a vault, not a spreadsheet or config file?

    Credentials in documents travel with every copy of the document.

  10. 10Is it written down how your setup works and who to call when it breaks?

    If the one person who knows is unavailable, everything waits for them.

Answer the questions above and your score, with what to fix first, appears here. Nothing you choose leaves this page.

Next step

If a number above surprised you, that is usually where discovery starts. Email me the result, or just the one that bothers you most.

brevin@bbclouddevelopments.com