Contact Master Your Business Podcast
The First SOP Finder: Which Delivery Process Should Your Cyber Consultancy Document First?
Built Beyond You  ยท  Free Tool

The First
SOP Finder.

Find the first delivery process to document so fewer project decisions route back through you.

For cybersecurity consultancy founders only.

If delivery is busy, projects are stacking up, and your team still comes back to you for judgement calls, the answer isn't "document everything."

That's how nothing gets documented.

Start with the one delivery moment causing the most founder interruption, client risk, or quality drift. This tool shows you where.

The 6 delivery moments that usually need documenting first
01
Client onboarding
The client said yes, but expectations, documents, dates, access, or next steps still need founder involvement.
02
Sales-to-delivery handoff
The team doesn't know exactly what was promised, what matters most, what risks exist, or what "good" looks like.
03
Client reporting
Updates, summaries, or recommendations still come back to the founder for rewriting or final judgement.
04
Review points
The team can do the work, but they still wait for the founder to decide whether it's ready to send.
05
Scope and escalation
The client asks for "one more thing" and nobody knows whether to say yes, pause, price it, or escalate.
06
Repeat delivery admin
Follow-up, reminders, file requests, meeting notes, and status updates keep interrupting project delivery.
5 questions. Answer honestly, not aspirationally.
Which delivery task do you personally rescue most often?

The one where the team starts it and you end up finishing it, rewriting it, checking it, or making the final call.

Which task creates the most interruptions on a delivery week?

Count the Slack messages, the quick questions, the calls that shouldn't need you. Highest frequency is highest friction.

Which task, if done wrong, creates the most reputational or client risk?

Quality risk without a written standard is a founder-dependence problem wearing a delivery problem's clothes.

Which task do new team members get wrong first?

If you've hired more than once and the same thing breaks each time, the SOP gap is right there.

Which task stalls when you're unavailable?

If the business waits for you to come back before it can move, that process doesn't exist without you yet.

Run the tree. Your majority answer wins.
If most answers point to

What happens after the yes: expectations, access, documents, or first project steps

Document first

Client onboarding SOP. Welcome steps, what the client must provide, who owns each first action, what good looks like at day 7.

If most answers point to

The team not knowing what was sold, what the risks are, or what the client expects

Document first

Sales-to-delivery handoff SOP. What transfers at point of sale, in what format, and what the delivery team needs before touching the work.

If most answers point to

Updates, summaries, or recommendations coming back for founder polish or sign-off

Document first

Client reporting SOP. Cadence, format, who prepares it, what gets included, and the standard clients expect without knowing to ask.

If most answers point to

The team doing the work but waiting for founder approval before it goes out

Document first

Review point SOP. What the quality bar is, who can sign off at each stage, and when founder review is genuinely required rather than just habit.

If most answers point to

Client requests for extra work landing back on the founder every time

Document first

Scope and escalation SOP. The decision rule for what the team can absorb, what gets priced, and what needs founder involvement.

If most answers point to

Admin tasks (reminders, notes, follow-up, file requests) eating into delivery time

Document first

Repeat delivery admin checklist. A repeatable task list someone else can own and run without asking.

If 2 feel equally urgent

Choose the one closest to client trust. The closer it is to judgement, quality, or client confidence, the earlier it gets documented.

  • Scope and escalation
  • Review points
  • Sales-to-delivery handoff
  • Client onboarding
  • Client reporting
  • Repeat admin (last)
Your result
Your first SOP is the one that removes the most founder judgement from live delivery.

Don't start with the process that feels easiest to document. Start with the one that currently causes interruption, quality risk, client confusion, or delivery delay when you're not available.

That's the SOP that protects the business first. One page. Bullet points. The standard someone else needs to match, not the process you'd follow yourself.

Bonus: write the SOP now
Use this prompt to draft it in 10 minutes.

Once you know which SOP to write first, paste this into ChatGPT or Claude. Replace the brackets with your specifics.

You are helping me document a delivery process for my cybersecurity consultancy so my team can run it without me. The SOP I need to write first is: [paste your SOP name here, e.g. Client Onboarding SOP] Here is what currently happens when this process runs through me: [describe in 2 to 3 sentences what you personally do, decide, or rescue in this process] Write a one-page SOP in plain language that: - States the purpose of this process in one sentence - Lists who owns it (role, not name) - Describes each step in order, written so a new team member could follow it - Flags the 2 to 3 decisions that still need founder input, and under what conditions - Ends with a definition of done: what good looks like when the process is complete Keep it under one page. No jargon. Write it for a capable team member, not an expert.
Reply and tell me which SOP this pointed to.

I'll tell you whether you're starting in the right place, and what to do once you've written it.

Message Deirdre on LinkedIn โ†’
deirdremartin.ie  ยท  The Built Beyond You System