Run a focused 90‑minute workshop (who, what, outputs)
Invite one person from sales, one from marketing, the ops owner and whoever runs your accounting or admin (30–60 minutes). The aim is practical: agree the authoritative source for the 6–8 fields that actually drive automations and handoffs.
Start by shortlisting fields (15 minutes). Typical list for small UK teams: owner, lifecycle stage, contact source, consent/subscription, billing contact, canonical phone, canonical email, and one business‑specific field (e.g. account status). Keep it to the ones your automations read.
Outputs you should leave with: a one‑page field decision table, explicit precedence rules you can paste into workflows, and named owners for each field so someone is accountable for future changes.
Three practical steps to decide and record per‑field truth
1) Shortlist and decide (30 minutes). For each shortlisted field, record: authoritative system (e.g. HubSpot, Salesforce, Xero, spreadsheet-derived), whether it can be derived by a rule, and whether a human edit is allowed. Example decisions: billing contact = Xero; canonical email = HubSpot form capture if present, else spreadsheet import; lifecycle stage = derived rule with sales override.
2) Record precedence and edit rights. Use this lightweight template per field you can paste into a workflow or doc:
- Field: Owner
- Authoritative source: CRM (HubSpot/Salesforce)
- Precedence order: 1) CRM value with provenance, 2) Derived rule (activity-based), 3) Manual edit (only by Sales Lead)
- Who may edit: Sales Lead
- Validation: non-empty, email/phone format checks
3) Assign owners and short governance. Give each field a named owner (person or role) and a simple rule: "If you're changing source precedence, log it and notify the automation steward." That keeps fixes local to Fareham/Hampshire teams and stops ad‑hoc edits from breaking downstream automations.
Quick guards you can implement same day + smoke test and examples
Add these four low‑code guards (implement in HubSpot, Salesforce, Marketo, Pardot or a sheet):
- One provenance field per key field (e.g. owner_source) to store where the current value came from.
- A trust flag (e.g. phone_trusted = true/false) that gates automations.
- Simple validation rules: email regex, UK phone normaliser, required billing contact for invoicing automations.
- Daily reconciliation check: export the 6–8 fields into a sheet, compare authoritative system vs downstream values, and flag mismatches for the field owner.
30‑minute smoke test to confirm automations read the chosen source:
- Pick one record and change the authoritative system value (e.g. change owner in HubSpot or billing contact in Xero).
- Confirm provenance field updates and trust flag status.
- Trigger the automation (or run a no‑op/dry‑run) and confirm it used the authoritative value. If it didn't, block the automation and fix the precedence rule.
Practical examples:
- HubSpot ↔ spreadsheets: Keep HubSpot as the primary for owner and lifecycle; store a "import_source" provenance when a spreadsheet import writes values. Build the precedence: HubSpot form > import (if import_provenance != 'manual') > manual edit. Add a simple list to reconcile nightly.
- HubSpot ↔ Xero: Make Xero authoritative for billing contact and billing address. When Xero writes to HubSpot, set billing_contact_provenance = 'xero' and billing_trusted = true; any HubSpot edit must flip provenance to 'manual' and set trusted=false until reviewed.
- Salesforce ↔ marketing platform (Marketo/Pardot): Let Salesforce hold canonical owner and account status; marketing platform writes campaign_source and consent. Use a derived lifecycle_stage in marketing: if Salesforce.status = 'Customer' then lifecycle='Customer' (marketing may suggest but not overwrite without a provenance flag and approval).
If you want a one‑page decision table template, a small precedence snippet for workflows, or a 30‑minute smoke test checklist run for Fareham or across the South Coast, see our CRM & marketing data optimisation (Fareham) page for a hands‑on session. If you prefer help running the 90‑minute workshop and implementing the quick guards, Optira can join as a practical helper.