{
 "name": "The MAP Template Library",
 "edition": "2026-11-10",
 "read_date": "2026-11-10",
 "source": "https://themutualactionplan.com/datasets/",
 "license": "CC BY 4.0",
 "cite": "The Mutual Action Plan, The MAP Template Library and the MAP Tool Matrix, edition 10 Nov 2026, https://themutualactionplan.com/datasets/",
 "description": "12 mutual action plan templates by deal type: step, owner, side, day and exit criterion.",
 "rows": [
  {
   "template": "smb-self-serve-upgrade",
   "deal_type": "SMB self-serve upgrade",
   "n": 1,
   "step": "Confirm the reason for upgrading",
   "owner": "Seller: account executive",
   "side": "both",
   "day": 0,
   "exit": "The buyer states the limit or feature they hit, in writing, and the seller has copied it into the plan."
  },
  {
   "template": "smb-self-serve-upgrade",
   "deal_type": "SMB self-serve upgrade",
   "n": 2,
   "step": "Name the buyer owner and approver",
   "owner": "Buyer: team lead",
   "side": "buyer",
   "day": 0,
   "exit": "One owner and the person who can pay are named and both appear on the plan."
  },
  {
   "template": "smb-self-serve-upgrade",
   "deal_type": "SMB self-serve upgrade",
   "n": 3,
   "step": "Agree the go-live date",
   "owner": "Buyer: team lead",
   "side": "buyer",
   "day": 1,
   "exit": "A date is on the plan, and the buyer has said what it is tied to."
  },
  {
   "template": "smb-self-serve-upgrade",
   "deal_type": "SMB self-serve upgrade",
   "n": 4,
   "step": "Share the plan link and pricing",
   "owner": "Seller: account executive",
   "side": "seller",
   "day": 1,
   "exit": "The buyer has opened the link and the quote matches the plan chosen."
  },
  {
   "template": "smb-self-serve-upgrade",
   "deal_type": "SMB self-serve upgrade",
   "n": 5,
   "step": "List the users to be added",
   "owner": "Buyer: team lead",
   "side": "buyer",
   "day": 2,
   "exit": "The user list, with roles, is attached to the plan."
  },
  {
   "template": "smb-self-serve-upgrade",
   "deal_type": "SMB self-serve upgrade",
   "n": 6,
   "step": "Confirm the data or content to migrate",
   "owner": "Buyer: team lead",
   "side": "buyer",
   "day": 3,
   "exit": "The buyer has stated what moves across, or has marked nothing as moving."
  },
  {
   "template": "smb-self-serve-upgrade",
   "deal_type": "SMB self-serve upgrade",
   "n": 7,
   "step": "Approve the purchase",
   "owner": "Buyer: approver",
   "side": "buyer",
   "day": 4,
   "exit": "The approver has agreed by reply or in the tool, and the reply is linked to the plan."
  },
  {
   "template": "smb-self-serve-upgrade",
   "deal_type": "SMB self-serve upgrade",
   "n": 8,
   "step": "Send the order form and pay",
   "owner": "Buyer: approver",
   "side": "buyer",
   "day": 5,
   "exit": "The order form is signed or the card is charged, and the receipt is on the plan."
  },
  {
   "template": "smb-self-serve-upgrade",
   "deal_type": "SMB self-serve upgrade",
   "n": 9,
   "step": "Run the 30-minute setup session",
   "owner": "Seller: customer success manager",
   "side": "both",
   "day": 6,
   "exit": "The new users have signed in and the first workflow runs on screen."
  },
  {
   "template": "smb-self-serve-upgrade",
   "deal_type": "SMB self-serve upgrade",
   "n": 10,
   "step": "Check the first week of use",
   "owner": "Seller: customer success manager",
   "side": "seller",
   "day": 9,
   "exit": "At least half of the added users have used the product, or a follow-up date is set."
  },
  {
   "template": "smb-self-serve-upgrade",
   "deal_type": "SMB self-serve upgrade",
   "n": 11,
   "step": "Record the upgrade reason for the team",
   "owner": "Seller: account executive",
   "side": "seller",
   "day": 9,
   "exit": "The reason, plan and date are written to the CRM record."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 1,
   "step": "Confirm goal and success criteria",
   "owner": "Seller: account executive",
   "side": "both",
   "day": 0,
   "exit": "Goal and two success criteria, each with a measure, are on the plan in the buyer's words."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 2,
   "step": "Map the buying group",
   "owner": "Seller: account executive",
   "side": "seller",
   "day": 2,
   "exit": "Every role in the buying group has a name or a marked gap in the stakeholder map."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 3,
   "step": "Describe the decision process",
   "owner": "Buyer: champion",
   "side": "buyer",
   "day": 3,
   "exit": "The champion has listed the steps and the people involved, and the seller has copied them in."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 4,
   "step": "Describe the paper process",
   "owner": "Buyer: champion",
   "side": "buyer",
   "day": 3,
   "exit": "Legal, security and procurement steps are listed with an owner for each."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 5,
   "step": "Run the tailored demo",
   "owner": "Seller: solutions engineer",
   "side": "seller",
   "day": 7,
   "exit": "The buying group has attended and the recording is in the plan."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 6,
   "step": "Meet the economic buyer",
   "owner": "Seller: account executive",
   "side": "both",
   "day": 10,
   "exit": "The economic buyer has attended a call and stated the budget source."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 7,
   "step": "Agree evaluation criteria",
   "owner": "Buyer: champion",
   "side": "buyer",
   "day": 12,
   "exit": "A written list of criteria is on the plan with a pass test for each."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 8,
   "step": "Run the pilot or hands-on trial",
   "owner": "Buyer: evaluation lead",
   "side": "buyer",
   "day": 14,
   "exit": "Each success criterion has a result recorded."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 9,
   "step": "Send the proposal",
   "owner": "Seller: account executive",
   "side": "seller",
   "day": 21,
   "exit": "The proposal is in the room and matches the criteria agreed."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 10,
   "step": "Complete the security questionnaire",
   "owner": "Buyer: IT or security lead",
   "side": "buyer",
   "day": 24,
   "exit": "The questionnaire is returned and findings are closed or accepted."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 11,
   "step": "Agree contract terms",
   "owner": "Both: legal contacts",
   "side": "both",
   "day": 35,
   "exit": "Both legal contacts have confirmed the final text."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 12,
   "step": "Obtain signature",
   "owner": "Buyer: economic buyer",
   "side": "buyer",
   "day": 42,
   "exit": "The signed contract is on the record."
  },
  {
   "template": "mid-market-new-logo",
   "deal_type": "Mid-market new logo",
   "n": 13,
   "step": "Schedule kickoff",
   "owner": "Seller: customer success manager",
   "side": "both",
   "day": 45,
   "exit": "The kickoff date is in both calendars and the success criteria are copied to the onboarding plan."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 1,
   "step": "Confirm the business case and sponsor",
   "owner": "Seller: account executive",
   "side": "both",
   "day": 0,
   "exit": "The sponsor is named and the business case is agreed in writing."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 2,
   "step": "Request the buyer's security process",
   "owner": "Seller: account executive",
   "side": "seller",
   "day": 2,
   "exit": "The buyer has sent its security policy and review steps, or confirmed there are none."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 3,
   "step": "Name the security owners",
   "owner": "Buyer: security lead",
   "side": "buyer",
   "day": 3,
   "exit": "A security owner is named on each side and appears on the plan."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 4,
   "step": "Share the security pack",
   "owner": "Seller: security contact",
   "side": "seller",
   "day": 5,
   "exit": "The pack, with the audit reports the seller holds, is in the room and the buyer has opened it."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 5,
   "step": "Return the completed questionnaire",
   "owner": "Seller: security contact",
   "side": "seller",
   "day": 12,
   "exit": "The buyer confirms the questionnaire is complete or lists the gaps."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 6,
   "step": "Review findings",
   "owner": "Buyer: security analyst",
   "side": "buyer",
   "day": 20,
   "exit": "Each finding is closed, accepted or assigned with a date."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 7,
   "step": "Hold the architecture and data review",
   "owner": "Both: solutions architect and security analyst",
   "side": "both",
   "day": 25,
   "exit": "A written decision on data flows is on the plan."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 8,
   "step": "Confirm SSO and provisioning needs",
   "owner": "Buyer: IT administrator",
   "side": "buyer",
   "day": 28,
   "exit": "The buyer states whether single sign-on and user provisioning are required, and the seller confirms the plan tier that includes them."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 9,
   "step": "Obtain security approval",
   "owner": "Buyer: security lead",
   "side": "buyer",
   "day": 40,
   "exit": "Written approval is attached to the plan."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 10,
   "step": "Negotiate and approve contract",
   "owner": "Both: legal contacts",
   "side": "both",
   "day": 50,
   "exit": "Final text is agreed by both legal contacts."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 11,
   "step": "Obtain signature",
   "owner": "Buyer: economic buyer",
   "side": "buyer",
   "day": 60,
   "exit": "The signed contract is on the record."
  },
  {
   "template": "enterprise-new-logo-security-review",
   "deal_type": "Enterprise new logo with security review",
   "n": 12,
   "step": "Hand off to onboarding",
   "owner": "Seller: customer success manager",
   "side": "seller",
   "day": 63,
   "exit": "The security decisions and exceptions are copied to the onboarding plan."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 1,
   "step": "Confirm the decision is made",
   "owner": "Buyer: economic buyer",
   "side": "buyer",
   "day": 0,
   "exit": "The economic buyer has stated a decision to proceed, in writing."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 2,
   "step": "Get the buyer's paper process",
   "owner": "Buyer: champion",
   "side": "buyer",
   "day": 2,
   "exit": "The champion lists the legal, procurement and finance steps with owners."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 3,
   "step": "Register as a vendor",
   "owner": "Seller: sales operations",
   "side": "seller",
   "day": 5,
   "exit": "The vendor record is created and the buyer confirms receipt."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 4,
   "step": "Submit tax, insurance and bank forms",
   "owner": "Seller: finance contact",
   "side": "seller",
   "day": 8,
   "exit": "Procurement confirms the forms are accepted."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 5,
   "step": "Send the draft agreement or ask for the buyer's paper",
   "owner": "Seller: account executive",
   "side": "seller",
   "day": 10,
   "exit": "Both parties have agreed whose paper is the base document."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 6,
   "step": "Return first legal comments",
   "owner": "Buyer: legal counsel",
   "side": "buyer",
   "day": 20,
   "exit": "A redline is received and logged on the plan."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 7,
   "step": "Respond to redlines",
   "owner": "Seller: contracts manager",
   "side": "seller",
   "day": 25,
   "exit": "Each redline is accepted, countered or escalated with a reason."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 8,
   "step": "Resolve open terms in a call",
   "owner": "Both: legal contacts",
   "side": "both",
   "day": 35,
   "exit": "A list of open terms is empty or every remaining item has an owner."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 9,
   "step": "Approve internal exceptions",
   "owner": "Seller: deal desk lead",
   "side": "seller",
   "day": 38,
   "exit": "Written approval for any non-standard term is attached."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 10,
   "step": "Procurement confirms pricing and purchase order",
   "owner": "Buyer: procurement manager",
   "side": "buyer",
   "day": 45,
   "exit": "A purchase order number or written exemption is on the plan."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 11,
   "step": "Finance approves the budget",
   "owner": "Buyer: finance approver",
   "side": "buyer",
   "day": 50,
   "exit": "Written budget approval is attached."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 12,
   "step": "Route for signature",
   "owner": "Buyer: contracts administrator",
   "side": "buyer",
   "day": 55,
   "exit": "The document is with the authorized signatory."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 13,
   "step": "Obtain signatures",
   "owner": "Both: signatories",
   "side": "both",
   "day": 60,
   "exit": "Both signatures are on the final document."
  },
  {
   "template": "enterprise-procurement-legal",
   "deal_type": "Enterprise with procurement and legal",
   "n": 14,
   "step": "Record the contract and hand off",
   "owner": "Seller: account executive",
   "side": "seller",
   "day": 62,
   "exit": "The contract, exceptions and renewal date are in the CRM and onboarding plan."
  },
  {
   "template": "expansion-upsell",
   "deal_type": "Expansion or upsell",
   "n": 1,
   "step": "Review value delivered to date",
   "owner": "Seller: customer success manager",
   "side": "seller",
   "day": 0,
   "exit": "A one-page summary of agreed success criteria and results is ready."
  },
  {
   "template": "expansion-upsell",
   "deal_type": "Expansion or upsell",
   "n": 2,
   "step": "Confirm the new goal",
   "owner": "Buyer: champion",
   "side": "buyer",
   "day": 3,
   "exit": "The champion states the new need and a measure, in writing."
  },
  {
   "template": "expansion-upsell",
   "deal_type": "Expansion or upsell",
   "n": 3,
   "step": "Identify new stakeholders",
   "owner": "Seller: account manager",
   "side": "seller",
   "day": 5,
   "exit": "Any new budget holder, administrator or business-unit lead is named on the plan."
  },
  {
   "template": "expansion-upsell",
   "deal_type": "Expansion or upsell",
   "n": 4,
   "step": "Scope the expansion",
   "owner": "Both: account manager and champion",
   "side": "both",
   "day": 8,
   "exit": "The seats, modules or units are listed and agreed."
  },
  {
   "template": "expansion-upsell",
   "deal_type": "Expansion or upsell",
   "n": 5,
   "step": "Check technical fit",
   "owner": "Seller: solutions engineer",
   "side": "seller",
   "day": 12,
   "exit": "Any integration or configuration change is listed with an effort estimate."
  },
  {
   "template": "expansion-upsell",
   "deal_type": "Expansion or upsell",
   "n": 6,
   "step": "Check security impact",
   "owner": "Buyer: IT or security lead",
   "side": "buyer",
   "day": 14,
   "exit": "The buyer confirms the review is not required, or lists what is."
  },
  {
   "template": "expansion-upsell",
   "deal_type": "Expansion or upsell",
   "n": 7,
   "step": "Send the amendment",
   "owner": "Seller: account manager",
   "side": "seller",
   "day": 18,
   "exit": "The order form or amendment matches the scope."
  },
  {
   "template": "expansion-upsell",
   "deal_type": "Expansion or upsell",
   "n": 8,
   "step": "Approve the budget",
   "owner": "Buyer: budget holder",
   "side": "buyer",
   "day": 25,
   "exit": "Written approval is attached to the plan."
  },
  {
   "template": "expansion-upsell",
   "deal_type": "Expansion or upsell",
   "n": 9,
   "step": "Sign the amendment",
   "owner": "Buyer: authorized signatory",
   "side": "buyer",
   "day": 30,
   "exit": "The signed amendment is on record."
  },
  {
   "template": "expansion-upsell",
   "deal_type": "Expansion or upsell",
   "n": 10,
   "step": "Plan the rollout of the new scope",
   "owner": "Both: customer success manager and champion",
   "side": "both",
   "day": 35,
   "exit": "The rollout steps, owners and dates are added to the customer plan."
  },
  {
   "template": "expansion-upsell",
   "deal_type": "Expansion or upsell",
   "n": 11,
   "step": "Review adoption of the new scope",
   "owner": "Seller: customer success manager",
   "side": "seller",
   "day": 75,
   "exit": "Usage against the stated measure is reviewed with the champion."
  },
  {
   "template": "renewal",
   "deal_type": "Renewal",
   "n": 1,
   "step": "Open the renewal plan",
   "owner": "Seller: customer success manager",
   "side": "seller",
   "day": 0,
   "exit": "The plan exists with the term end date and the current contract value."
  },
  {
   "template": "renewal",
   "deal_type": "Renewal",
   "n": 2,
   "step": "Check the champion and sponsor are still in role",
   "owner": "Seller: customer success manager",
   "side": "seller",
   "day": 3,
   "exit": "Both are confirmed, or a replacement is named."
  },
  {
   "template": "renewal",
   "deal_type": "Renewal",
   "n": 3,
   "step": "Collect usage and results",
   "owner": "Seller: customer success manager",
   "side": "seller",
   "day": 10,
   "exit": "A summary against the original success criteria is ready."
  },
  {
   "template": "renewal",
   "deal_type": "Renewal",
   "n": 4,
   "step": "Hold the results review",
   "owner": "Both: customer success manager and champion",
   "side": "both",
   "day": 20,
   "exit": "The champion has seen the results and agreed or disputed them in writing."
  },
  {
   "template": "renewal",
   "deal_type": "Renewal",
   "n": 5,
   "step": "Capture changes in scope",
   "owner": "Buyer: champion",
   "side": "buyer",
   "day": 25,
   "exit": "Added or removed seats, modules and goals are listed."
  },
  {
   "template": "renewal",
   "deal_type": "Renewal",
   "n": 6,
   "step": "Confirm the renewal owner and signer",
   "owner": "Buyer: procurement or contract owner",
   "side": "buyer",
   "day": 30,
   "exit": "The person who signs and the process to reach them are on the plan."
  },
  {
   "template": "renewal",
   "deal_type": "Renewal",
   "n": 7,
   "step": "Send the renewal quote",
   "owner": "Seller: account manager",
   "side": "seller",
   "day": 45,
   "exit": "The quote reflects the agreed scope and term."
  },
  {
   "template": "renewal",
   "deal_type": "Renewal",
   "n": 8,
   "step": "Resolve pricing or terms",
   "owner": "Both: account manager and procurement",
   "side": "both",
   "day": 60,
   "exit": "Open items are closed or escalated."
  },
  {
   "template": "renewal",
   "deal_type": "Renewal",
   "n": 9,
   "step": "Obtain approval and purchase order",
   "owner": "Buyer: budget holder",
   "side": "buyer",
   "day": 75,
   "exit": "Approval and any purchase order number are attached."
  },
  {
   "template": "renewal",
   "deal_type": "Renewal",
   "n": 10,
   "step": "Sign the renewal",
   "owner": "Buyer: authorized signatory",
   "side": "buyer",
   "day": 90,
   "exit": "The signed renewal is on record at least two weeks before the end date."
  },
  {
   "template": "renewal",
   "deal_type": "Renewal",
   "n": 11,
   "step": "Set the next review",
   "owner": "Seller: customer success manager",
   "side": "seller",
   "day": 95,
   "exit": "The next results review date is on the new plan."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 1,
   "step": "Agree the hypothesis",
   "owner": "Both: champion and solutions engineer",
   "side": "both",
   "day": 0,
   "exit": "One sentence says what the pilot will prove, written on the plan."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 2,
   "step": "Write the pass test",
   "owner": "Buyer: evaluation lead",
   "side": "buyer",
   "day": 2,
   "exit": "Each success criterion has a measure and a pass mark."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 3,
   "step": "Set the time box and decision date",
   "owner": "Both: account executive and champion",
   "side": "both",
   "day": 3,
   "exit": "Start, end and decision meeting dates are on the plan."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 4,
   "step": "Name the pilot group",
   "owner": "Buyer: evaluation lead",
   "side": "buyer",
   "day": 4,
   "exit": "Named users, with roles, are listed."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 5,
   "step": "Confirm data and access needs",
   "owner": "Buyer: IT contact",
   "side": "buyer",
   "day": 5,
   "exit": "Access is granted or a date is set."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 6,
   "step": "Set up the pilot environment",
   "owner": "Seller: solutions engineer",
   "side": "seller",
   "day": 7,
   "exit": "The pilot group signs in and sees their own data or content."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 7,
   "step": "Run the kickoff session",
   "owner": "Seller: solutions engineer",
   "side": "both",
   "day": 8,
   "exit": "The group has attended and the pass test is reviewed with them."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 8,
   "step": "Check progress at the midpoint",
   "owner": "Both: solutions engineer and evaluation lead",
   "side": "both",
   "day": 15,
   "exit": "Each success criterion has a status."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 9,
   "step": "Fix blockers",
   "owner": "Seller: solutions engineer",
   "side": "seller",
   "day": 17,
   "exit": "Blockers are logged, assigned and dated."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 10,
   "step": "Record the final results",
   "owner": "Buyer: evaluation lead",
   "side": "buyer",
   "day": 28,
   "exit": "Each criterion has a result recorded against its pass mark."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 11,
   "step": "Hold the decision meeting",
   "owner": "Both: account executive and economic buyer",
   "side": "both",
   "day": 30,
   "exit": "A decision to buy, extend or stop is recorded."
  },
  {
   "template": "proof-of-concept",
   "deal_type": "Proof of concept",
   "n": 12,
   "step": "Convert to the contract plan",
   "owner": "Seller: account executive",
   "side": "seller",
   "day": 32,
   "exit": "The pilot results are copied to the contract plan, with the paper process steps added."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 1,
   "step": "Identify the buying route",
   "owner": "Seller: bid manager",
   "side": "seller",
   "day": 0,
   "exit": "The route (tender, framework, direct award or quote) is confirmed with the buyer contact."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 2,
   "step": "Obtain the requirements and timetable",
   "owner": "Buyer: procurement officer",
   "side": "buyer",
   "day": 3,
   "exit": "The documents and all formal dates are on the plan."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 3,
   "step": "Decide to bid",
   "owner": "Seller: sales director",
   "side": "seller",
   "day": 5,
   "exit": "A bid decision is recorded with the reason."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 4,
   "step": "Submit clarification questions",
   "owner": "Seller: bid manager",
   "side": "seller",
   "day": 8,
   "exit": "Questions are sent by the buyer's deadline and the receipt is saved."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 5,
   "step": "Receive the buyer's answers",
   "owner": "Buyer: procurement officer",
   "side": "buyer",
   "day": 12,
   "exit": "Answers are logged on the plan."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 6,
   "step": "Draft the response",
   "owner": "Seller: solutions architect",
   "side": "seller",
   "day": 20,
   "exit": "A complete draft is reviewed internally against every requirement."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 7,
   "step": "Complete security and data protection forms",
   "owner": "Seller: security contact",
   "side": "seller",
   "day": 25,
   "exit": "All forms are complete and checked by a second person."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 8,
   "step": "Obtain legal and pricing approval",
   "owner": "Seller: deal desk lead",
   "side": "seller",
   "day": 28,
   "exit": "Written internal approvals are attached."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 9,
   "step": "Submit the response",
   "owner": "Seller: bid manager",
   "side": "seller",
   "day": 30,
   "exit": "The submission receipt is saved before the deadline."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 10,
   "step": "Attend the evaluation or presentation",
   "owner": "Both: account executive and evaluation panel",
   "side": "both",
   "day": 45,
   "exit": "The presentation date is held and any follow-up questions are logged."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 11,
   "step": "Receive the award notice",
   "owner": "Buyer: procurement officer",
   "side": "buyer",
   "day": 60,
   "exit": "The notice is on the plan, with any standstill period dates."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 12,
   "step": "Agree contract text",
   "owner": "Both: legal contacts",
   "side": "both",
   "day": 70,
   "exit": "The final text is agreed under the buyer's terms."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 13,
   "step": "Obtain signatures and purchase order",
   "owner": "Buyer: authorized signatory",
   "side": "buyer",
   "day": 80,
   "exit": "The signed contract and order number are on record."
  },
  {
   "template": "public-sector",
   "deal_type": "Public sector",
   "n": 14,
   "step": "Plan the start of service",
   "owner": "Both: customer success manager and buyer lead",
   "side": "both",
   "day": 85,
   "exit": "The kickoff date and onboarding steps are added."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 1,
   "step": "Agree the bundle goal",
   "owner": "Buyer: executive sponsor",
   "side": "buyer",
   "day": 0,
   "exit": "One goal is on the plan with a measure for the whole bundle."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 2,
   "step": "List the products and their buyer owners",
   "owner": "Both: account executive and sponsor",
   "side": "both",
   "day": 3,
   "exit": "Each product has a named buyer owner."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 3,
   "step": "Set the go-live order",
   "owner": "Both: account executive and sponsor",
   "side": "both",
   "day": 6,
   "exit": "The order and the reason for it are on the plan."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 4,
   "step": "Confirm technical dependencies between products",
   "owner": "Seller: solutions architect",
   "side": "seller",
   "day": 10,
   "exit": "Dependencies are listed and ordered."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 5,
   "step": "Run a demo per product",
   "owner": "Seller: solutions engineer",
   "side": "seller",
   "day": 14,
   "exit": "Each product owner has attended their demo."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 6,
   "step": "Agree the pricing structure",
   "owner": "Both: account executive and procurement",
   "side": "both",
   "day": 24,
   "exit": "One price sheet shows each product and the bundle total."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 7,
   "step": "Complete security review for all products",
   "owner": "Buyer: IT or security lead",
   "side": "buyer",
   "day": 30,
   "exit": "One review covers all products, or exceptions are listed."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 8,
   "step": "Negotiate one contract",
   "owner": "Both: legal contacts",
   "side": "both",
   "day": 45,
   "exit": "The final text covers all products."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 9,
   "step": "Obtain signature",
   "owner": "Buyer: economic buyer",
   "side": "buyer",
   "day": 55,
   "exit": "The signed contract is on record."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 10,
   "step": "Create a plan per product",
   "owner": "Seller: customer success manager",
   "side": "seller",
   "day": 58,
   "exit": "Each product has an onboarding plan with a buyer owner."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 11,
   "step": "Start the first product",
   "owner": "Both: product owners",
   "side": "both",
   "day": 60,
   "exit": "The first product is live in test or production as agreed."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 12,
   "step": "Start the dependent products",
   "owner": "Both: product owners",
   "side": "both",
   "day": 75,
   "exit": "Each dependent product starts on its date."
  },
  {
   "template": "multi-product-bundle",
   "deal_type": "Multi-product bundle",
   "n": 13,
   "step": "Review the bundle goal",
   "owner": "Seller: customer success manager",
   "side": "seller",
   "day": 90,
   "exit": "The goal measure is reviewed against actual results."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 1,
   "step": "Agree the deal route and roles",
   "owner": "Both: channel manager and partner lead",
   "side": "both",
   "day": 0,
   "exit": "A written note says who sells, who contracts, who supports and who invoices."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 2,
   "step": "Register the deal",
   "owner": "Seller: channel manager",
   "side": "seller",
   "day": 1,
   "exit": "The registration is confirmed and any conflict is resolved."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 3,
   "step": "Confirm the customer's goal",
   "owner": "Both: partner lead and account executive",
   "side": "both",
   "day": 5,
   "exit": "The goal and success criteria are on the plan."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 4,
   "step": "Name customer-side stakeholders",
   "owner": "Buyer: customer champion",
   "side": "buyer",
   "day": 7,
   "exit": "The stakeholder list is on the plan."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 5,
   "step": "Agree who attends which meeting",
   "owner": "Both: channel manager and partner lead",
   "side": "both",
   "day": 8,
   "exit": "A meeting list names the attendee from each firm."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 6,
   "step": "Run the demo and scoping",
   "owner": "Seller: solutions engineer",
   "side": "seller",
   "day": 14,
   "exit": "The customer has attended and the scope is recorded."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 7,
   "step": "Confirm the partner's services scope",
   "owner": "Partner: services lead",
   "side": "seller",
   "day": 20,
   "exit": "The partner's tasks and the vendor's tasks are separated and dated."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 8,
   "step": "Agree pricing and margin terms",
   "owner": "Both: partner lead and deal desk",
   "side": "both",
   "day": 25,
   "exit": "Pricing for the customer is agreed internally and approved."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 9,
   "step": "Complete customer security and legal review",
   "owner": "Buyer: IT and legal contacts",
   "side": "buyer",
   "day": 40,
   "exit": "Findings are closed and the contract text is agreed with the contracting party."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 10,
   "step": "Sign the contract",
   "owner": "Buyer: authorized signatory",
   "side": "buyer",
   "day": 55,
   "exit": "The signed contract is on record with the party named."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 11,
   "step": "Hold the joint kickoff",
   "owner": "Both: partner lead and customer success manager",
   "side": "both",
   "day": 60,
   "exit": "The customer has met both teams and holds one plan."
  },
  {
   "template": "channel-partner-led",
   "deal_type": "Channel or partner-led deal",
   "n": 12,
   "step": "Review the partner handoff",
   "owner": "Seller: channel manager",
   "side": "seller",
   "day": 70,
   "exit": "Open items between partner and vendor are listed with owners and dates."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 1,
   "step": "Agree the outcome and go-live driver",
   "owner": "Buyer: executive sponsor",
   "side": "buyer",
   "day": 0,
   "exit": "The outcome and the event that sets the date are on the plan."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 2,
   "step": "Run the scoping workshop",
   "owner": "Both: solutions architect and business lead",
   "side": "both",
   "day": 7,
   "exit": "A scope document lists in-scope and out-of-scope items."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 3,
   "step": "Name the customer project team",
   "owner": "Buyer: project lead",
   "side": "buyer",
   "day": 10,
   "exit": "Named people and their hours per week are on the plan."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 4,
   "step": "Name the delivery team",
   "owner": "Seller: services lead",
   "side": "seller",
   "day": 12,
   "exit": "Named roles and their hours are on the plan."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 5,
   "step": "Draft the statement of work",
   "owner": "Seller: services lead",
   "side": "seller",
   "day": 18,
   "exit": "The draft covers scope, deliverables, dates and assumptions."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 6,
   "step": "Review assumptions and dependencies",
   "owner": "Both: project lead and services lead",
   "side": "both",
   "day": 24,
   "exit": "Each assumption has an owner and a date to confirm."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 7,
   "step": "Complete security review",
   "owner": "Buyer: IT or security lead",
   "side": "buyer",
   "day": 30,
   "exit": "Findings are closed or accepted."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 8,
   "step": "Approve the statement of work and contract",
   "owner": "Both: legal contacts",
   "side": "both",
   "day": 40,
   "exit": "The final documents are agreed."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 9,
   "step": "Obtain signature",
   "owner": "Buyer: economic buyer",
   "side": "buyer",
   "day": 48,
   "exit": "The signed contract is on record."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 10,
   "step": "Create the project plan from the deal",
   "owner": "Seller: project manager",
   "side": "seller",
   "day": 50,
   "exit": "Phases, milestones and owners are copied from the deal plan without re-entry."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 11,
   "step": "Hold the kickoff",
   "owner": "Both: project lead and project manager",
   "side": "both",
   "day": 55,
   "exit": "The project team has attended and access requests are sent."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 12,
   "step": "Deliver customer inputs",
   "owner": "Buyer: project lead",
   "side": "buyer",
   "day": 65,
   "exit": "Data, access and decisions are supplied by the planned dates."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 13,
   "step": "Complete the first phase",
   "owner": "Both: project manager and project lead",
   "side": "both",
   "day": 90,
   "exit": "The phase exit test is met and signed off."
  },
  {
   "template": "services-heavy-implementation",
   "deal_type": "Services-heavy implementation deal",
   "n": 14,
   "step": "Review the plan and risks",
   "owner": "Seller: project manager",
   "side": "seller",
   "day": 95,
   "exit": "The plan is updated and risks are logged with owners."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 1,
   "step": "Find out why the buyer is considering a switch",
   "owner": "Seller: account executive",
   "side": "seller",
   "day": 0,
   "exit": "The reason is stated by the buyer and recorded on the plan."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 2,
   "step": "Get the incumbent's contract end date",
   "owner": "Buyer: procurement contact",
   "side": "buyer",
   "day": 2,
   "exit": "The date and notice period are on the plan."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 3,
   "step": "List what must be replicated",
   "owner": "Buyer: current administrator",
   "side": "buyer",
   "day": 5,
   "exit": "A list of required features and integrations is attached."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 4,
   "step": "Map the current users and data",
   "owner": "Buyer: current administrator",
   "side": "buyer",
   "day": 8,
   "exit": "Counts and data types are recorded."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 5,
   "step": "Confirm the comparison criteria",
   "owner": "Buyer: champion",
   "side": "buyer",
   "day": 10,
   "exit": "Written criteria, each with a pass test, are on the plan."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 6,
   "step": "Run a side-by-side evaluation",
   "owner": "Both: solutions engineer and evaluator",
   "side": "both",
   "day": 18,
   "exit": "Each criterion has a result recorded."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 7,
   "step": "Plan the migration",
   "owner": "Seller: services lead",
   "side": "seller",
   "day": 25,
   "exit": "Steps, owners, downtime and fallback are on the plan."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 8,
   "step": "Present the case to the economic buyer",
   "owner": "Buyer: champion",
   "side": "buyer",
   "day": 32,
   "exit": "The economic buyer has seen the comparison and stated a decision date."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 9,
   "step": "Complete security review",
   "owner": "Buyer: IT or security lead",
   "side": "buyer",
   "day": 36,
   "exit": "Findings are closed or accepted."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 10,
   "step": "Agree contract and start date",
   "owner": "Both: legal contacts and procurement",
   "side": "both",
   "day": 48,
   "exit": "The start date is set after the incumbent's notice period."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 11,
   "step": "Obtain signature",
   "owner": "Buyer: economic buyer",
   "side": "buyer",
   "day": 55,
   "exit": "The signed contract is on record."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 12,
   "step": "Run the migration",
   "owner": "Both: services lead and administrator",
   "side": "both",
   "day": 65,
   "exit": "Users and data are moved and checked against the counts."
  },
  {
   "template": "competitive-displacement",
   "deal_type": "Competitive displacement",
   "n": 13,
   "step": "Switch off the incumbent",
   "owner": "Buyer: current administrator",
   "side": "buyer",
   "day": 80,
   "exit": "The old tool is closed and its notice is given before its end date."
  }
 ]
}