Sales

4 articles

Sales covers the work before an engagement exists: finding companies worth approaching, working them until one becomes a customer, and tracking the deals in play until they are won or lost.

It is two halves that meet in the middle. Prospecting works through companies that are not customers yet. Deals tracks a sale you are actively working, against a customer that already exists. Converting a prospect is what turns the first into the second.

A deal is three things

A deal is a customer, an amount, and the stage it has reached. Nothing else is required, and two of the three are enforced: a deal cannot be created without a customer attached, and the stage always defaults to the first open one rather than being left blank.

That deliberate thinness is what makes the pipeline readable. Everything else — the contact, the owner, the expected close date, the notes — is there when you want it and never blocks you from recording that a sale is in play.

Two views of the same deals

  • Pipeline is a board, one column per stage, and it shows open deals only. It is where you work: drag a card between stages as the sale progresses.
  • List is a table, and unlike the board it includes every deal that has been won or lost. It is where you look afterwards.

A closed deal leaves the board and lives in the list. See Deals and the pipeline.

Closing is a drop, and it is reversible

Below the board sits a closing strip with Won and Lost. Dropping a card on either closes the deal — no confirmation dialog, because an Undo appears immediately afterwards. Marking a deal lost asks why, from a fixed list of reasons, with an optional note.

See Closing a deal, which also covers what reopening does and does not restore.

Who can use it

Access is governed by three roles, in increasing order of what they may do:

  • Sales Viewer — read.
  • Sales Operator — the everyday selling role.
  • Sales Manager — full control of the pipeline.

Example use cases

  • Work a list of companies you have never contacted, logging each call and reply as you go.
  • Turn a prospect that replied into a customer and a first deal, without retyping their contacts.
  • See what is genuinely in play this month, separated from what has already closed.
  • Find the deals that have gone quiet before they go cold.
  • Record why a deal was lost, so the pattern is visible later rather than remembered vaguely.

Connection map

Part ofDerived fromRefers to
Documented hereDocumented elsewhere
lead-list contains lead. lead-activity logged against lead. lead converts to deal. lead becomes counterparty. deal sold to counterparty. deal sits in pipeline-stage. deal closed with lost-reason.containslogged againstconverts tobecomessold tosits inclosed withPProspect list — A finite group of companies to work through. It tracks how many are done against the total, so the work has an end.Prospect listPProspect — A company you are working but that is not a customer yet. It sits at New, Contacted or Qualified, and everything done to it is logged against it.ProspectAActivity — One recorded contact with a prospect — a call, a message, a reply, a bounce, a meeting — attributed to a channel.ActivityDDeal — A sale in progress: a customer, an amount, and the stage it has reached. It cannot exist without a customer, and its stage is never blank.DealCCounterparty — The other side of a financial document — a client billed, or a supplier owed.CounterpartySStage — A step in the pipeline, carrying a probability. That probability is what weights the pipeline total — which is a measure of quality, not a forecast.StageLLost reason — Why a deal was lost, chosen from a fixed list so the answer can be counted later rather than re-read.Lost reason