A commitment in sales execution is a promise — explicit or implied — made between any parties involved in a deal, that creates an expectation of action and a timeline for delivery. It is the fundamental unit of work in technical sales.
Why Commitments, Not Tasks?
Tasks are one-directional and decontextualized. "Send spec to customer" is a task. It tells you what to do. It doesn't tell you who made the promise, when it was made, what was discussed, what the customer expects, what deal it affects, or what happens if it's late.
A commitment is bidirectional and contextual. It captures what was promised, who promised it, who it was promised to, the deal context, the timeline, and the downstream dependencies. Commitments are made and received — an SE makes commitments to customers and receives commitments from engineering, support, and other stakeholders.
This distinction matters because deals don't move forward on tasks. They move forward on fulfilled commitments. When you tell a customer "I'll have the security documentation to you by Thursday," that's not a to-do item on your list. It's a promise that shapes the customer's evaluation timeline, their internal discussions, and their perception of your reliability.
The Two Directions of Commitments
Most sales execution tools focus on what the rep needs to do. But half the commitments in any active deal are made by other people — and they're the ones most likely to be dropped.
Commitments made: Promises the SE makes to customers, colleagues, or leadership. These are typically more visible because the SE initiated them.
Commitments received: Promises made to the SE — by a customer who said they'd share the evaluation criteria, by engineering who said the feature would be ready, by an SDR who promised the prospect a specific capability. These are the commitments that create silent momentum loss when they're not tracked.
Explicit vs. Implicit Commitments
Not every commitment is stated clearly. In a meeting, someone says "we should probably loop in the security team." That's an implicit commitment — it creates an expectation without a clear owner or deadline. Implicit commitments are the most dangerous because nobody formally acknowledged them, yet both sides may assume action was taken.
Execution intelligence treats the commitment as the atomic unit of work — detecting them (explicit and implicit), contextualizing them against deals and relationships, scoring them by impact, and tracking them through resolution. This is what separates execution governance from task management.