Deals & CRM
Pipeline + custom fields + close-reason tracking — without the Salesforce overhead.
Deals & CRM is the pipeline built into Autocloz, so a deal already knows which sequence the lead is on and which channel they replied through. You drag deals across stages, attach custom fields per deal type, and record a close reason and category on every win and loss. Forecasting is weighted by each stage's own probability, with nothing to export to a separate CRM.
- ·Drag-and-drop pipeline by stage
- ·Custom fields per deal type
- ·Close-reason categories — won + lost
- ·Forecast view with weighted pipeline
- ·Auto-link to sequence + lead
The detail.
CRM that lives where outreach lives
When the deal page knows which sequence the lead is on, which channel they replied to, and what the AI thinks about the latest message, your pipeline meeting is half over before it starts.
Stages you define, with a probability attached
Pipeline stages are yours to name and reorder, and each one carries a default probability plus a won or lost flag. The weighted forecast is that probability applied to the deal value, so changing what a stage means changes the forecast immediately instead of waiting for someone to update a spreadsheet formula.
Close reasons are a category plus the sentence
Every won or lost deal records a close-reason category and the free-text reason behind it. The category is what makes loss reporting possible at all — "price" thirty times is a pricing problem, whereas thirty differently-worded notes are an anecdote nobody can act on.
The gotcha: forecast category is not stage
A deal sits in a stage and separately in a forecast category — pipeline, best case, commit or omitted. They are deliberately not the same field: a late-stage deal a rep does not believe in belongs in omitted without being dragged backwards through the pipeline, and an early deal with a signed intent can be committed without faking its stage.
Specific to this feature.
Do I still need Salesforce or HubSpot alongside this?
+
Not for running outbound. Deals, stages, custom fields, close reasons and the weighted forecast are built in, and a deal links back to the lead, the sequence and the conversation. Teams that keep an external CRM as system-of-record usually push closed deals out by webhook rather than duplicating the pipeline.
Can I add fields specific to one kind of deal?
+
Yes — custom fields are attached per deal type, so a renewal and a new-business deal do not have to share one flattened schema of mostly-empty columns.
How is the forecast weighted?
+
Each stage carries a default probability, and the forecast applies it to the deal value. Deals can also be placed in a forecast category — pipeline, best case, commit or omitted — independently of the stage they sit in.
Does a deal know how the lead was reached?
+
Yes. The deal is linked to the lead and therefore to the sequence they are enrolled in and the channel they replied on, so the pipeline review does not need a second tab open to answer "where did this one come from?".
The full story.
The reason outbound teams end up with a CRM that nobody trusts is rarely the CRM: it is the gap between where the conversation happened and where the record lives. A rep who has to leave the inbox, find the right record and retype what just happened will do it for the deals that are already going well and skip it for the rest — which is exactly backwards for forecasting.
Keeping the pipeline in the same product as the sequences closes that gap by removing the step. The deal is created from the lead that replied, the channel and sequence come with it, and the close reason is captured at the moment the stage flips rather than reconstructed at quarter end. What you get out of that is not a prettier board — it is a loss report with enough signal to change the next month's messaging.
Try it free.
No credit card. Every feature on this page included.