From 1a3a2d680324b41ddc0ebe73f051e4d7b5c88d73 Mon Sep 17 00:00:00 2001 From: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com> Date: Thu, 5 Feb 2026 16:44:19 -0600 Subject: [PATCH] Add Customer promises pre-sales policy (#39376) Closes https://github.com/fleetdm/confidential/issues/14138 --- handbook/sales/sales-playbook.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/handbook/sales/sales-playbook.md b/handbook/sales/sales-playbook.md index e1843af332..d8b7133d4b 100644 --- a/handbook/sales/sales-playbook.md +++ b/handbook/sales/sales-playbook.md @@ -3,10 +3,15 @@ ## Rules of engagement +### Customer Promises pre-sales policy + +Fleet's [customer promises pre-sales policy (confidential)](https://docs.google.com/document/d/1XzKtuZOFsn8ndH75XCqTP2Vbr8rSphTPCM4QhhZcVfo/edit?tab=t.0#heading=h.44oj4nd4b9my) governs when and why we may make binding delivery commitments (Customer promises) to prospects during the pre-sales process. Customer promises are formal commitments to deliver specific capabilities by defined dates as a condition of purchase. They carry significant organizational weight and must be used judiciously to maintain Fleet's credibility and operational integrity. + + ### Opportunity splits between AEs