Closing

The most frustrating part of sales was never the deal going badly. It was the deal that looks finished and refuses to move. The price is settled, the people who will use the product want it, and the signature doesn't arrive. Ask about it and the same answer comes back every time: it's under review.

Pagedeck ran into this directly. An enterprise customer Sofia was working told her in the second week of August to go ahead. She reported the deal as effectively done in that week's meeting. September arrived with no signature. It turned out that on the customer's side anything over $7,500 triggers a legal review, the legal review is followed by a director's approval, and that director was on vacation for two weeks. Nobody had lied to Sofia. The contact simply had no reason to walk her through his own company's paperwork.

That gap is why this stage carries its own name. Without one, deals like that sit in the negotiation column, and anyone reading the pipeline assumes terms are still being argued. Terms aren't the problem — process is. Giving closing its own column makes it visible on the board that what the deal needs is not more persuasion but a map of what's left.

Product barely comes up during closing. Everyone has seen what they need to see, so what moves back and forth is documents and names. Who signs, who has to look at it first, and how many days each step takes — that's the whole conversation.

New faces show up here for the first time. The people met in earlier stages were the team that will actually use the product; now people outside that team appear. A legal reviewer looks at termination terms and liability. A procurement contact looks at payment terms and unit pricing. A security reviewer asks where the data is stored. None of the three will ever use the product, and any of the three can stop the deal.

So what an account executive (AE) — the person who carries a deal from first conversation through signature — does here is draw a map rather than apply pressure. The ones who are good at it don't ask "any idea when this will land?" They ask "what should we be preparing on our side?" The first question only ever produces "soon." The second produces a list of the steps that remain.

Unpredictable duration is the other marker of this stage. A proposal, the document that lays out scope and terms for the customer, takes a fairly consistent amount of time to put together. Closing doesn't work that way. Two contracts of identical size can take three days or six weeks depending on the buyer's internal process. Pagedeck's team-level deals average four days here; enterprise deals run past three weeks. Blend the two into one average and it serves neither plan.

After closing comes the end of the pipeline. A deal closes either as closed won, where the contract happens, or as closed lost, where it doesn't. Either outcome is fine; leaving it open is the bad option. Deals nobody closes inflate the pipeline total and distort the following quarter's planning.

Three things have to be confirmed for the won side.

1. The signer — who actually signs. It's usually not the contact the deal has been running through, and the later that gets checked, the later the remaining timeline becomes visible.
2. The remaining steps and their dates — how many days for legal, how many for approval, as numbers. "Should be soon" is not a date.
3. Both signatures — a document signed only by the customer isn't a contract yet. The moment both signatures are in is the moment the deal is won. Countersigning often sits with a founder or a finance lead, so a deal can spend two extra days waiting on its own side of the table.

The condition for closing something as lost is worth setting in advance too. Pagedeck marks a deal lost after 30 days without a reply and records the reason. Sometimes one of those deals comes back four months later, and when it does it goes in as a new deal. Holding deals open because they might revive is how a pipeline ends up carrying twenty deals that stopped moving a year ago.

"That one's in closing. Legal has it, and it goes up for approval next Tuesday."

Terms are settled, only the customer's internal process is left, and a date has already been pinned down.

"Five weeks in closing and still nothing. Should we call it lost?"

The process has stalled, so it's time to decide whether to close the deal out.

"Is your CEO the one signing, or does this stop at the director level?"

Checking where the approval chain ends in order to calculate the remaining timeline.

Sofia manages this stage with one habit. Every deal in closing carries a single line naming the next action and its date — something like "Sept 3, legal review response expected." When that date passes she calls that day. A deal with no date written against it isn't in closing; it's been abandoned.

It's also the first column Grace looks at during the end-of-month pipeline review, because whether the month lands on target is mostly decided here. Deals in earlier stages rarely reach signature inside the month. Deals in closing split between this month and next over a matter of days.

The most common misreading treats closing as a persuasion technique. Older sales training is largely responsible, having taught the word alongside high-pressure lines — decide today and the discount applies, that sort of thing. The reason that pressure doesn't work in business deals is simple: the person on the other side of the table has no authority to decide. Pressure just puts them in an awkward position, and a contact in an awkward position stops championing the deal internally. What this stage calls for is help assembling the list of remaining steps.

The other misreading is treating closing as something that starts at the end. It's the last column, so it looks that way. But most of what stalls a deal here could have been asked about far earlier. Approval limits, whether a security review applies, which quarter the budget sits in — all of it fits inside a discovery call. That first conversation exists to understand the customer's situation and problems, and the buying process is part of that situation. Push those questions past the product demo and a deal planned for six weeks takes twelve.