Contacts
A lifecycle stage from lead to champion to churned, and membership on every account the person really works with. The Leads view is Contacts filtered by stage.
Every piece that makes this work, and what each one is actually for.
A lifecycle stage from lead to champion to churned, and membership on every account the person really works with. The Leads view is Contacts filtered by stage.
Ordered stages, deal shape, scoring, and snapshots so you can see how the forecast moved and not just where it landed.
The account record everything else hangs off. Projects, tickets, contracts, invoices, and the whole interaction history roll up here.
Priced from the shared catalog, sent, tracked, and readable by the client without a login. Accepted quotes carry into contracts.
One price book for quotes, invoices, and reporting, so the same thing does not carry three prices.
Public booking pages that write straight to the calendar and the contact record.
Site conversations that become tickets or contacts without a copy and paste step.
Campaigns, sequences, and journeys that run off the same contact list you sell from, with performance tied back to the deals it produced.
Calls and email threaded onto the account, so the timeline is complete rather than partial.
Matching and duplicate management keep one person on one record, and enrichment fills the fields nobody typed. The pipeline reads cleaner because the data underneath it is.
A won deal converts into a draft contract and its deliverables in one move, and the value it was sold at is frozen at that moment. Every deliverable carries its own billing type, which is what lets one agreement mix fixed fee and time and materials. Invoices point at the deliverable they came from, so recognized, invoiced, and collected stay three separate numbers instead of one hopeful one.
The long version, because this is where the category has real objections.
In a standalone CRM, closed-won is the end of the story. Here it is the middle. A won deal converts into a draft contract and its deliverables in one move, the project that delivers it links back to the account, and the invoices that bill it land on the same record. The salesperson, the delivery lead, and the person chasing payment are all reading one client, not three copies of it.
Nothing about the agreement gets re-typed.
Projects, tickets, and hours on the client record.
Every interaction type, rolled up.
Deals carry ordered stages, deal shape, and scoring, and the forecast weights probability from your own win history rather than a number someone felt good about. Snapshots keep how the forecast moved, not just where it landed, so the Monday meeting is about what changed instead of who remembers what.
Campaigns, sequences, and journeys run off the same contact list you sell from. A campaign touch lands on the contact record, the lead it warms carries its source, and the deal it becomes reports back to the campaign. Segments are built from the fields you already keep, not exported to a second list that drifts.
Matching catches the second copy of a person before it becomes a third, duplicate management merges with an undo that is cheap, and enrichment workflows fill the gaps nobody typed. Lifecycle stages mean the Leads view is just Contacts filtered by stage, one record from first touch to renewal.
Yes. One person, one record, on every account they actually work with. Their history follows them instead of splitting into copies.
Leads are contacts at an early lifecycle stage, not a separate object. Qualify one and nothing is copied, the stage just moves.
Yes. Quotes price from a shared catalog, clients can read them without a login, and an accepted quote carries into the contract and its deliverables.
Yes. Campaigns, sequences, and journeys run off the same contact list you sell from, with audience segments built from your own fields and results tied to the deals they produced.
Matching flags likely duplicates, merging keeps the full history, and a bad merge is built to be undone. Record quality is a workflow, not a cleanup weekend.
Yes. Calls, email, meetings, tickets, projects, and invoices roll up to one account timeline, so nobody assembles the history by hand before a renewal call.
Scrambl is one workspace, so the records here are the same records the rest of the platform reads. These pair with it most often.