Key takeaways
- One shared record beats two synced lists that drift apart.
- Every field needs one owner, even if many people can read it.
- Lifecycle stage changes need written rules both teams agreed.
- A short weekly review of exceptions catches problems early.
Why do sales and marketing data drift apart
Data drifts because each team updates the records it touches and nobody owns the gaps. Marketing changes lifecycle stages from form fills and email clicks, sales changes them from calls, and neither sees the other's edits in time.
The symptoms are familiar: a customer receives a prospecting email, a lead a seller disqualified is added back to a nurture list, or a contact who left the company months ago is still in a campaign.
Who should own each field
Give every field one owner team, and let others read it but not overwrite it without a rule. Ownership follows who learns the fact first.
- Marketing owns source, campaign history, consent and email preferences.
- Sales owns qualification notes, deal stage and next steps.
- Whoever spots a job or company change first updates it, with a note of where they saw it.
- Operations or RevOps owns the field definitions and the lifecycle stage rules.
What rules should govern lifecycle stage changes
Lifecycle stage changes should follow written triggers that both teams signed off, so a stage means the same thing to everyone. For example, a lead becomes marketing qualified when it fits the ideal customer profile and has asked for something, and becomes sales qualified only after a seller confirms the need in a conversation.
Write the reverse rules too. If a seller disqualifies a lead, say whether it returns to nurture and after how long, so marketing does not re-engage it the next day.
How do you keep the review from becoming a chore
Keep it short by reviewing exceptions, not the whole database. A brief weekly look at new duplicates, bounced emails, contacts with no owner and stage changes that skipped a step is often enough.
Name one person to run it, and fix the rule behind a repeated error rather than only the error itself.
How to coordinate data updates, step by step
Set the rules once, then keep them alive.
- Choose one system as the shared record for contacts, companies and deals.
- List the fields both teams use and name one owner for each.
- Write the triggers for every lifecycle stage change, forwards and backwards.
- Agree how job changes, bounces and duplicates are reported and fixed.
- Run a short weekly review of exceptions and change the rule behind any repeated error.
Where Pebbles Ai fits
- CapabilityProspecting & customer recordsKeep contacts, segments and deals in the CRM (in Beta), with admin-defined custom fields, saved views, filters and a merge for duplicate records.
- FoundationAgent memoryTell an assistant a field rule your teams agreed, such as which team updates deal stages, and keep it in Company memory, where colleagues' assistants use it too; ask an assistant to correct it in plain words when the rule changes.
Common questions
Should sales and marketing use the same CRM?
Yes, where possible. One shared system removes the sync step that causes most drift; if two systems are unavoidable, decide which one wins for each field.
How do you handle a contact who changes jobs?
Mark the old record to show they left, create or link a record at the new company, and tell marketing so the old address leaves active campaigns.
Who should run the data review?
One named person, often in sales or revenue operations. A review that everyone shares usually ends up run by nobody.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
