Pipeline & Relationships
A pipeline that keeps what happened rather than what was last typed, with every contact's history gathered on one timeline by itself. Why the deal, not the contact, moves through the board, and what that lets a team do that a typical CRM does not.

The question behind Canopy's pipeline: what does it actually mean to say a CRM is the source of truth. For most small-business CRMs the answer is 'whatever the last person typed.' That is the latest belief, not what happened. Two weeks later, when the team is trying to remember whether a deal moved to proposal because the client agreed or because nobody updated it after a stalled call, the latest belief gives the wrong answer to the only question that matters. A CRM that can say what was last typed but not what happened is a mirror of the team's own forgetfulness. Canopy keeps what happened. Every meaningful change is recorded with who made it and when, so 'when did this deal first reach proposal' and 'who changed this contact's status' have answers rather than guesses, and they are the same answers next month. A deal marked lost by mistake comes back with its whole history, and the restoring is itself on the record. What moves through the pipeline is a deal, not a contact, because real businesses have repeat customers. A client who bought in the spring and is weighing a second job in the fall is two deals, not one contact whose status got overwritten. The second engagement is where most of the revenue lives, so the pipeline keeps it in view. The board's columns are stages, its cards are deals, and a contact with three open opportunities shows up three times, which is the truth. The contact page assembles itself. Forms they sent, email in both directions, calls and texts, meetings, notes, quotes, and every move of every deal they are on land on one timeline without anybody copying anything, because there are no other systems to copy from. When a prospect's website has been scanned, what the scan learned about their business sits right on the record.

Around that sits what a sales team expects. Quotes build off a product catalog, where a product can be a bundle with price tiers. More than one pipeline can run at once, each with its own stages, and a deal that has sat too long gets flagged. The forecast rolls up by person and by territory, and each business sets its own stage odds, because a long consulting sale closes nothing like a fast retail one. Duplicate contacts merge cleanly, one search reaches every record, the keyboard reaches every page, a manager decides which panels each role sees, and a business can define kinds of record of its own. The honest exclusion: this pipeline is built for a business with hundreds of open deals, worked by people who keep the records true, not for a floor of reps on a power dialer working tens of thousands. A team at that size has outgrown what Canopy is for, and that is a fine place to be. The consequence the owner feels is continuity. A team member leaves and the history stays. A new one joins and can read what happened and why. And the whole record exports on any day.