Loading
By Latha Kumaresan · DirectorReviewed 23 September 2026
In short
What is a deal record in a CRM?
A deal record is the entry for one sales opportunity: its value and currency, owner, stage, expected close date, the company and contacts involved, quotes, and activity. In Treepie Flow every change to a deal is kept, so you can see not just the current value or close date but how and when each one changed, and who changed it.
- Holds
- Value, currency, owner, stage, close date, company, contacts
- History
- Every change to every field, with who and when
- Attached
- Quotes, activity, splits, scoring, win/loss reason
- Hands over to
- Loop projects and Books billing when won
Why this exists
Why the deal is usually the thinnest record you own
Because in most systems the deal is a row with a number on it. When the quarter is reviewed nobody can say when the close date slipped, who moved it, or what the value was before somebody rounded it up.
What it does
What a deal carries
The deal is the record of one opportunity: value, currency, owner, stage, close date, the company and contacts attached to it, and the full history of how each of those changed.
Every field change is written to the deal's own history with the actor and the timestamp. The deal shows its current state and, on the same page, the path it took to get there.
In practice
Reconstructing a deal a quarter later
A £41,900 expansion at Kanaka Foods closed a month late. The history shows the close date moved twice, both times the day after a rescheduled review — which is a procurement problem, not a sales one.
Specifics
ReadsThe company and contact records
WritesValue, stage, owner, close date, history
PermissionsRole, team and record level
What it does not do
It holds what the deal is worth to you, not what it costs to deliver. Margin lives in Loop and Books, because that is where the time and the invoices are.
How it connects
See the Flow journeys →What else reads the deal
Quotes price against it, Loop opens delivery phases from its sold lines, Books drafts the billing schedule from its terms, and every pipeline report is an aggregate of these rows.
Setting it up
Flow · Moving your pipeline in takes four days.Day 1Decide the stagesBefore any import. Stage names are the one thing here that is genuinely painful to change in month three.
Day 2Import into a sandboxDeals, contacts and three years of closed history, mapped and checked before anybody logs in.
Day 3Wire the routingForms, inbox and owner rules, so a new lead lands on a person rather than in a queue nobody reads.
Day 4Let the team inSales first, then whoever reads the forecast. The old CRM stays readable for a month.
Who it is for
One deal, read the same way by everyone.
Account executivesKeep everything about the opportunity in one place, including every email and call.“When did the close date last move?”
Sales managersSee slippage: which deals changed value or close date, and how often.“Which deals have pushed twice this quarter?”
FinanceRead the agreed value and terms directly when the deal is won.“What exactly was sold to Halstead?”
DeliveryStart the project from the deal, with the sold lines already attached.“What did we promise in the proposal?”
Tracking an opportunity, three ways.
| Spreadsheet rows | Basic CRM deals | Treepie Flow | |
|---|---|---|---|
| Field history | Overwritten | Current values only | Every change kept |
| Close-date slippage | Invisible | Hard to report | Reported per deal and owner |
| Contacts involved | In someone’s head | One primary contact | Every contact, with their role |
| After it’s won | Retyped into other tools | Exported | Opens the project and billing directly |
| Currency | Mixed in one column | Converted on entry | Stored as sold, converted in reports |
Can we add our own fields to a deal?
Yes, on any object, with types and validation. They appear in the API and in reporting like the built-in ones.
Who can change the value of a deal?
Whoever you permit. Every change is recorded with the previous value regardless of role.
What happens to a deal when it is won?
It stays as the record of the sale. Loop and Books open delivery and billing from it rather than copying it.
What fields does a deal have?
Name, value, currency, owner, pipeline, stage, expected close date, company, contacts with roles, source and any custom fields you add.
Can a deal have more than one contact?
Yes. Attach every contact involved, each with a role such as budget holder, champion or technical buyer.
Can we see how a deal changed over time?
Yes. The history shows every change to value, stage, close date and owner, with who made it and when.
How is close-date slippage reported?
Reports count how often and how far each deal’s close date moved, by owner and by pipeline.
Can deals be in different currencies?
Yes. A deal is stored in the currency it was sold in and converted for reports at the rate you choose.
What happens when a deal is won?
A close reason is required, then the sold lines can open a Loop project and a Books billing schedule.
Can a deal be reopened?
Yes. Reopening is recorded in the history, and the original close is kept for reporting.
Can we bulk-edit deals?
Yes, with a preview of every change before it’s applied, and each change recorded in the history.
More in Pipeline & deals
Full feature list →Pipeline & dealsWeighted forecastingWeighted forecasting multiplies each open deal by the probability of its stage and totals the result, showing that figure alongside the unweighted pipeline it came from.Pipeline & dealsDeal splitsPipeline & dealsWin/loss reasonsPipeline & dealsDeal scoringPipeline & dealsMultiple pipelinesPipeline & dealsStage automation
Easier to see Deal records running on your own records than to read about it.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.