Closing a deal: won and lost
Closing writes a terminal outcome on the opportunity with the reason behind it. Won hands the relationship forward to onboarding and post-sale work; lost keeps the record and the reason rather than deleting anything. Neither outcome tidies the commitments the deal made — the follow-up queue is a separate record and has to be walked.
What each outcome records#
| Outcome | What is written | What it means later |
|---|---|---|
| Won | The terminal stage, the value as agreed, the date, and who closed it | The organisation moves into onboarding and post-sale; the deal becomes history rather than work |
| Lost | The terminal stage and the reason | The relationship continues; a lost deal is not a lost customer, and the reason is what makes a future approach sensible |
The reason is the part people skip and the part that pays. A lost deal with no reason tells the next person nothing except that somebody gave up. A reason turns the same record into the shortest possible briefing for the next conversation with that organisation.
What a win starts#
Winning is a handover, not an ending. The person and organisation carry on into the part of the relationship that decides whether they buy again.
- Onboarding work is recorded against the relationship rather than against the closed deal.
- Support cases opened afterwards belong to the person and appear on their timeline beside the sales history.
- The lifecycle stage of the relationship moves, which is a different axis from the deal's stage and is worth setting explicitly.
- Anything promised during the sale that is still outstanding stays outstanding — the win does not discharge it.
The full path, including who picks up what, is in handing a won deal to onboarding.
What a loss does not do#
- It does not delete the deal
- The record, its value, its history and its documents stay. A pipeline that forgets its losses cannot be reasoned about.
- It does not block the person
- Blocking is a deliberate directive against a contact, not a side effect of a commercial outcome.
- It does not stop the relationship
- The person keeps their timeline, memory and lifecycle stage. Losing one purchase is an event in a relationship, not the end of one.
- It does not cancel commitments
- Follow-ups are keyed to the person and the thread. Walk the queue and close what the outcome has made pointless.
Closing one properly#
Record the outcome with its reason, in the customer's terms rather than yours.
Result 'Chose a competitor on lead time' is usable next year; 'no' is not.
Confirm the value is what was actually agreed.
Result Totals across the board are only as honest as the last figure written to each closed deal.
Walk the follow-up queue for that person: complete, cancel or leave each row deliberately.
Result Nothing goes out afterwards that contradicts the outcome.
Write anything durable into memory or Knowledge.
Result A reason recorded on one deal explains one deal; a fact about how this organisation buys changes every future conversation with them.
Reading closed deals afterwards#
Closed opportunities remain on the deals sheet in #/data, where they can be grouped by reason, by organisation or by period, and exported. Counts and totals are computed in the database rather than over the page in front of you, so a figure over closed deals describes the workspace and not the current view — the distinction that made an earlier conversation list report an empty tab that was not empty.
Questions#
Should a stalled deal be closed as lost?
Usually yes, with 'no decision' as the reason. A pipeline full of deals nobody is working on makes every total meaningless, and the relationship is unaffected by closing the opportunity.
Can a closed deal be reopened?
Deliberately, yes — it is a stage move like any other and the stage rules apply. What does not happen is a closed deal drifting back open because somebody dragged a card.
Does winning a deal change what Connect may say to that customer?
Not commercially. The rule against inventing terms is the same before and after a sale. What changes is the context: onboarding and support work now sit alongside the sales history in everything it reads.