In this short, Jason M. Lemkin explains why the "closed‑won" stage of a sale must be treated as a repeatable, governed checklist as a company scales. He outlines the essential admin steps—terms of service, provisioning, onboarding enrollment, invoicing, and org‑mapping—required for a smooth customer experience. Lemkin highlights the cross‑functional ecosystem that supports these steps (Deal Desk, Legal, RevOps, Customer Support) and the chaos that arises when approvals are handled via ad‑hoc DMs and scattered knowledge. He describes the unhealthy cycle of reps chasing approvals across time zones and how the organization re‑engineered the process: recognizing the dual role of supporting functions (enabling sales while protecting the company) and investing in tooling—particularly Jira—so that systems surface to reps instead of reps having to chase them. The overall message is that a disciplined, tool‑enabled governance model is critical to scaling sales without sacrificing customer experience.
Chapters
Closed one is my favorite dopamine hit. It's reliable, it gets me every time, it never gets old, I never get sick of it, but it's a checklist. And when we're growing as quickly as we are, the governance of closed one really matters. You need to make sure you have terms of service in place, you have a provisioning path for the customer, they're getting enrolled in onboarding, they're receiving an invoice, we have mapped their orgs correctly. We're a complex business. We're available on first-party services as well as through cloud partners. And sometimes just getting all of the little admin pieces in place can accidentally create a horrible customer experience if you don't get them all right. I have personally spent many late nights inside of our billing system trying to reconcile invoices when customers get locked out. This is a very important part of the cycle. And so we have one still per step for closed one so that Claude can work across the cross-functional systems and ensure that everything is in place. We do this for self-service too, to get the customer's account closed, provisioned, billing set up, and getting them on— enrolled in an onboarding training. Again, sales is not an island. There are so many supporting functions that needed to have the same elasticity we were trying to build in the AE org in order to meet the demand. This is Deal Desk, This is legal, this is RevOps, this is customer support. And we had had, I mean, we still do, but it was a gnarly system. It was a sea of DMs. You needed to have the institutional knowledge or just simply be co-located on the same floor. A lot of AEs would just walk by RevOps and DealDesk desk to try and get quotes approved. A lot of people on the East Coast and definitely in Europe, were staying up very late chasing approvals. We were creating a very unhealthy cycle. And reps— so what we did is we looked at this and said, these functions play dual roles. They are there to support the sales team and enable a customer an excellent customer experience, but they're also there to protect the company and to provide governance to ensure you're doing good deals that are in policy that you can stand behind in the future. So with the supporting functions and all of the systems that they leverage, which are honestly even many more than I had laid out, but Jira is a critical one for us, we structured this and invested in our tools so that reps stopped going to their systems and rather their systems came to them.
