Deal

Ask a sales team what they're working on and, for a long time, the answer came back as a story. "That account got a new contact so we're re-explaining everything, and the other one is sitting with their VP." The listener nods, and still has no idea how much money arrives this month.

That becomes a problem in three specific moments: when a founder plans next quarter's hiring, when a rep leaves, and when two people discover they've been calling the same company separately. All three have one cause — the work in progress lived only in somebody's head, where nobody else could count it.

A deal is the unit that cuts those stories into countable pieces. One customer, one transaction in progress, one row, with an amount, an expected date, and a marker for how far along it is. "Things are going well" turns into "there's a $9,000 deal at the proposal stage targeting the end of this month." The first sentence supports nothing; the second can be added up and divided.

Where to draw the line between one deal and two is a company's own call. If the same customer buys a team plan now and evaluates a company-wide rollout six months later, that's usually counted as two deals, because the contracts are separate and so are the amounts and the timing.

A deal lives as one row in a CRM, the system that tracks contact history with customers, and that row always carries four things.

1. Account and contact — who the transaction is with. Keeping two people from working the same company separately is part of this field's job.
2. Amount — the money that arrives if it closes. For an annual contract, this is usually a year's worth. The figure gets summed later, so an estimate goes in rather than a blank.
3. Deal stage — how far it has come. Most companies order it as first call, demo, proposal, negotiation, and closing.
4. Expected close date — roughly when it resolves. Without this date, nothing separates this month's deals from next quarter's.

A deal always closes. It gets marked closed won if the contract lands, closed lost if it falls through, and either way it comes off the active list. Losses are recorded rather than deleted because they're worth counting later. Tag each one by reason — price, timing, a competitor — and at the end of the quarter it turns out twelve of the thirty losses shared a cause.

The most common way this unit breaks is deals that never get closed. A row with no reply for six months feels too valuable to give up, so it stays, and its amount keeps landing in the total. When $150,000 of a $450,000 pipeline is that kind of row, the forecast built on it is wrong by a third.

Once deals are a real unit, numbers sit on top of them. Average deal size is the mean amount per deal, and win rate is the share of worked deals that close. Together they turn a money target into a count of rows: a $150,000 quarterly target at a $7,500 average means closing twenty deals, and at a 30 percent win rate that means more than sixty in progress.

Inside sales, the deal is the subject of nearly every sentence. Outside it, the word shows up when someone comes looking for a number.

The first place is the weekly pipeline review. Active deals get sorted by amount and walked one row at a time. Anything at the same stage as last week gets a question about why it hasn't moved, and anything whose close date has slipped twice gets a decision about whether to close it out.

The second is the sales forecast, the estimate of next period's revenue based on the pipeline. The usual method multiplies each stage by its historical close rate and sums the results — ten deals of $15,000 at a proposal stage that historically converts at 40 percent produces an expectation of $60,000. The math only holds if the amounts and stages on each row match reality.

The third is asking another team for help. When sales needs something from engineering or product, naming the deal it's attached to changes how the request gets ranked. "When will this feature be ready?" and "a $22,000 deal is stalled on this feature" are prioritized differently.

"Five of our twelve deals this quarter are still at the first-call stage."

Close to half the pipeline is unlikely to land in the time remaining. It's a signal to revisit the target.

"That deal hasn't moved in a month. No answer this week and I'm closing it."

A commitment to keep the record matched to reality. Not surrender — bookkeeping that makes the total honest.

"I can't run this deal alone. Their security questionnaire came in."

One transaction now needs time from another team.

At Pagedeck, Sofia sorts the active deals by amount every Monday and goes through them with Grace. Enterprise deals take three or four months while team-plan deals close inside one, so mixing the two makes the month's forecast swing hard. They read the list in two groups for that reason.

Mia reads the same list for a different reason. When the stall reason on three or more deals names the same missing feature, she treats it as a product gap rather than one customer's request. The deal record is a sales tracker and a map of where the product catches, at the same time.

People often use "deal" and "contract" interchangeably. Both point at a transaction, so the confusion is natural. But a contract is a document that appears once at the end, while a deal is the record covering everything from the first email to the signature. Three months before any contract exists, the deal already exists and already has an amount and a stage. Collapse the two and the record only gets created right before signing, which leaves the pipeline holding nothing but nearly-done work and no view of the quarter after this one.

Reading more deals as better is the second mistake. A large pipeline total looks like health, and that total often goes into a board update, so reps keep low-probability rows alive. The trouble is that the same number becomes the basis for the forecast and the hiring plan. A company that hires against an inflated pipeline carries both the missed target and the payroll two quarters later. The point of having a unit to count is accuracy, not volume.