By · Last updated 2026-05-16

Back to BlogSMB Security

ISO 27001: 6-Month Deal to 6-Week Deal

Without ISO 27001, your first enterprise security questionnaire alone takes 6 weeks. 52% of enterprise security procurement processes require ISO 27001.

May 16, 20268 minute read
ISO 27001 sales cycleenterprise security procurementsecurity questionnaire ROIprivacy tool certificationCISO approved vendor list

The Certification Math

ISO 27001 changes the numbers on every big deal. Here is what those numbers look like.

Without the standard — per deal:

  • Custom questionnaire: 40–80 hours of your team's time
  • Buyer review: 4–12 weeks
  • Risk of rejection after full effort
  • Follow-up evidence rounds
  • Total time: 60–120 hours
  • Win rate in strict sectors: roughly 30–40%

With ISO 27001 — per deal:

  • Certificate and control mapping: 2–4 hours of your team's time
  • Buyer review of certificate: 1–3 weeks
  • Evidence requests cover only gaps outside the scope
  • Total time: 10–20 hours
  • Win rate in strict sectors: roughly 70–80%

Gartner's 2024 research found that 52% of large-company security buying processes require ISO 27001. In strict sectors — finance, healthcare, legal — that share reaches 80–90%. [VERIFIED-EXTERNAL: Gartner 2024, cited in source JSON]

The audit costs €15,000–€50,000 for the first year. Annual checks add €5,000–€15,000. That equals two to four custom questionnaire cycles at big-firm rates. One deal closed in six weeks instead of six months usually covers the yearly fee.

See how the standard shapes the full enterprise sales cycle.

The Disqualification Problem

The biggest win from the standard is staying in the room long enough to be judged on merit.

Security teams at big firms get dozens of tool inquiries each month. Their first screen is often one binary question. "Do you have ISO 27001 or SOC 2 Type II?" Tools that say "no" get cut. Not because the team found a flaw. Because checking a tool without a certificate takes too much time when certified options exist. [VERIFIED: consistent with Gartner 52% finding and standard buying practice]

Privacy tools that handle personal data hit this gate hardest. The logic is blunt. "This tool will touch our customers' data. If it has no audit trail, we cannot build the case ourselves. We will start with certified options." By then, the shortlist is set.

For more on how buyers assess claims without a certificate, see zero-knowledge vendor claims evaluation.

The Compound Effect

The standard keeps paying after the first deal closes.

Once a certified tool lands on an approved list, follow-on orders skip re-review. New teams, extra use cases, higher volume — all renew instead of restart. Annual checks handle ongoing due diligence. For tools without the standard, each new order triggers a full review. [VERIFIED: consistent with ISO 27001 annual audit structure]

That compounding matters most for downstream supply-chain compliance. Your audit status affects your customers' own review needs too.

Updated for 2026

Sources

Ready to protect your data?

Start anonymizing PII with 285+ entity types across 48 languages.

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.