# An enterprise plan with a security review starts the review in the first week, not after the price

Template, Enterprise new logo with security review, read 10 Nov 2026

**The short answer.** The twelve-step template puts the security review on the critical path from the start. It names a security owner on each side, sets the questionnaire and findings steps as separate lines, and keeps a span of sixty-three days with the signature gated on the review exit.

## When to use it

Use when the buyer has a security team, will require a questionnaire or an architecture review, and the product will touch customer or employee data.

## The plan, step by step

Day 0 to day 63

| Day | Step | Owner | Side | Done when |
| --- | --- | --- | --- | --- |
| 0 | Confirm the business case and sponsor | Seller: account executive | both | The sponsor is named and the business case is agreed in writing. |
| 2 | Request the buyer's security process | Seller: account executive | seller | The buyer has sent its security policy and review steps, or confirmed there are none. |
| 3 | Name the security owners | Buyer: security lead | buyer | A security owner is named on each side and appears on the plan. |
| 5 | Share the security pack | Seller: security contact | seller | The pack, with the audit reports the seller holds, is in the room and the buyer has opened it. |
| 12 | Return the completed questionnaire | Seller: security contact | seller | The buyer confirms the questionnaire is complete or lists the gaps. |
| 20 | Review findings | Buyer: security analyst | buyer | Each finding is closed, accepted or assigned with a date. |
| 25 | Hold the architecture and data review | Both: solutions architect and security analyst | both | A written decision on data flows is on the plan. |
| 28 | Confirm SSO and provisioning needs | Buyer: IT administrator | buyer | The buyer states whether single sign-on and user provisioning are required, and the seller confirms the plan tier that includes them. |
| 40 | Obtain security approval | Buyer: security lead | buyer | Written approval is attached to the plan. |
| 50 | Negotiate and approve contract | Both: legal contacts | both | Final text is agreed by both legal contacts. |
| 60 | Obtain signature | Buyer: economic buyer | buyer | The signed contract is on the record. |
| 63 | Hand off to onboarding | Seller: customer success manager | seller | The security decisions and exceptions are copied to the onboarding plan. |

## Where plans like this stall

- Waiting for the price to start the review, which pushes the signature past the quarter.
- Answering the questionnaire from memory instead of from the audit reports, which creates follow-up questions.
- Ignoring plan tiers: SSO and provisioning sit on top tiers at several vendors, so confirm before the buyer asks.

## Running it in a tool

The [MAP Tool Matrix](/tools/) shows which tools keep the plan where the buyer already is, send nudges and sync to the CRM; [the tool ranking](/platforms/) weighs the plan at 30 of 100.

## Sources

- MEDDICC, MEDDPICC methodology: decision process and paper process: https://meddicc.com/meddpicc-sales-methodology-and-process (read 10 Nov 2026)
- Dock: mutual action plan page, templates and multi-phase plans: https://www.dock.us/features/mutual-action-plan (read 10 Nov 2026)
- Flowla: pricing page, SSO on the Enterprise plan: https://www.flowla.com/pricing (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://themutualactionplan.com/templates/enterprise-new-logo-security-review/
