Four situations we see in young companies.

Four situations we see at growing companies, written as illustrative scenarios. Each one covers the situation, what we would look for and what we would change.

Illustrative scenarios, not client case studies.

Tenders and procurement

Example: sustainability consultancy, around 50 people, Amsterdam

Losing tenders, and the pitch isn't the reason.

They win the room every time. Then the procurement security annex arrives and there is nothing to put in it: no device management and no documented access controls.

Read the scenario

The situation

Picture a sharp pitch, a credible team and expertise that enterprise clients want. Somewhere between the final presentation and the purchase order, deals keep slipping. Price and capability aren't the cause. The four-page security annex attached to every procurement process is, and there is nothing to fill it with.

What we would look for

A baseline audit would likely show about 50 people on unmanaged devices, SaaS tools bought by whoever needed them that week, and no single record of who has access to what. No identity provider, no MDM, no offboarding process and no documented controls. That wouldn't be a security crisis. The company grew fast and nobody owned IT.

What we would change

We would enrol and manage the device fleet, move sign-in to single sign-on with phishing-resistant MFA, and automate offboarding so access ends in minutes. We would build and document an access matrix, plus a checklist mapped to the security annexes the company keeps receiving, so completing one takes an afternoon.

What good looks like

A completed security annex is ready on the first day of the next tender window, and the checklist becomes part of every bid. The settings exist, they are documented, and they hold up when a procurement team checks.

Enterprise sales

Example: B2B SaaS, around 60 people, selling to financial services

A six-month deal nearly dies in security review.

Legal has signed off. Then procurement sends 180 security questions with a five-day deadline, and the answers are spread across Slack, two former employees and one engineer's memory.

Read the scenario

The situation

Six months of sales work: a champion inside the account, budget approved, legal moving. Then a 180-question security questionnaire arrives with five days to respond. The answers sit in three Slack channels, with two people who have already left, and with one engineer who half remembers what was set up two years ago. The deal is a week from falling through.

What we would look for

We would expect no central identity provider, unmanaged devices, and nothing written down about who can reach which systems or how access is removed when someone leaves. The questionnaire is reasonable. The controls don't exist yet, and the ones that do aren't documented anywhere a bank's security team can see.

What we would change

We would consolidate the identity setup, enrol the devices with encryption enforced, and build an access matrix from scratch. Then we would write a questionnaire answer template based on the controls now in place, with every claim backed by a log or a policy document.

What good looks like

The questionnaire goes back on time with an evidence trail behind each answer. The next enterprise prospect's questionnaire starts from the template instead of from zero.

IT ownership

Example: deeptech startup, around 40 people, Series A, Amsterdam

The IT person quits, and three engineers start on Monday.

One person ran devices, SaaS accounts and new-starter setup. After two weeks' notice they are gone, and nobody knows which systems exist or who can access what.

Read the scenario

The situation

Buying devices, creating SaaS accounts, setting up new starters, the IT inbox: it all lives in one person's head. They give two weeks' notice and leave, with no handover document and no list of systems. Three engineers are due the following Monday and nobody knows how to get them working.

What we would look for

We would expect dozens of SaaS apps, most set up by whoever needed them first, and former employees whose accounts are still active. No identity provider tying it together, and devices tracked in a spreadsheet and in people's memory. Nobody was careless. The company grew quickly and no one owned the infrastructure.

What we would change

We would audit all access and close the old accounts. We would set up an identity provider with single sign-on for every major tool, enrol the devices, and connect account creation and removal to HR, so they run from the same workflow as contracts and start dates.

What good looks like

New starters have a working laptop and the right access on day one. Offboarding takes minutes and leaves an audit trail. The company has a written record of what exists, who owns it, and what happens when someone joins or leaves.

Investor due diligence

Example: healthtech, around 45 people, before a Series B, Amsterdam

The lead investor asks about IT security. Nobody has an answer.

The term sheet arrives on a Tuesday. By Thursday the due diligence list is in, with a section on IT security controls that nobody can answer.

Read the scenario

The situation

Two days after the term sheet, the lead investor sends a technical due diligence list. Halfway down is a section on device management, access governance, incident response and encryption. Nobody on the founding team has a documented answer to a single item.

What we would look for

We would expect devices with no enforced encryption and no proof of it, no formal access governance so people hold admin rights they've forgotten about, and no record of onboarding or offboarding. The team means well and the controls that exist are real, but none of it is organised or provable to an investor's technical team.

What we would change

A baseline audit gives a precise map of what exists and what is missing. Over a few weeks we would enrol the devices, enforce encryption, formalise access governance, structure the audit logs and put together an evidence pack built around the questions investors and auditors ask.

What good looks like

The due diligence pack goes back with every control documented and verifiable, and no items left for later.

Recognise one of these?

Most companies we talk to aren't in a crisis yet, but they can see one coming. A 30-minute call is enough to tell where you are.

Book a free call