Begin with a disputed decision
Instead of scheduling a broad alignment workshop, identify one recurring disagreement: which accounts deserve attention, what makes a lead acceptable or why pipeline reports differ. Gather recent examples so the discussion concerns observable work rather than impressions about another team.
ABM guidance emphasizes coordination between marketing and sales. The same operating discipline is useful outside an account-based program. A shared target is insufficient when each team interprets the customer, stage or next action differently.
Write a compact agreement
| Agreement | What to document |
|---|---|
| Customer focus | Inclusion, exclusion and priority rules |
| Stage definitions | Evidence needed to enter or leave a stage |
| Ownership | Responsible person for each action and exception |
| Response | An achievable expectation by enquiry type |
| Feedback | Required disposition and reason codes |
| Escalation | How blocked or disputed cases are resolved |
Define the boundaries as well as the ordinary path. Existing customers, partner enquiries, duplicates and unsupported requirements may need different routing.
Make disagreement informative
Review accepted, rejected and stalled examples together. Ask which criterion was applied and whether the underlying evidence was available at the time. If a field is required but no one can obtain it reasonably, the process may need revision. If a definition changes, preserve the date so historical reports remain interpretable.
Connect incentives to the whole process
A team measured only on raw volume may optimize for responses that another team cannot use. A team measured only on closed business may ignore the evidence needed to improve early acquisition. Retain each function’s responsibilities while reviewing shared progression and customer outcomes.
Do not force a single metric to represent every contribution. Use a small set of measures that reveals where work is progressing and where it fails. Include capacity and data quality when interpreting results.
Give the review a decision output
At each review, choose a concrete change: revise a qualification rule, repair routing, create a missing asset or investigate a segment. Record the owner and expected evidence. A recurring meeting without decisions can create the appearance of alignment while the same operational problem continues.
Keep the agreement maintainable
Assign an owner and review trigger. A new product, territory, sales structure or CRM workflow can invalidate assumptions. Alignment is durable when people can inspect and update the agreement, including colleagues who were not present when it was first created.
A practical next step
Agree the customer choices, lifecycle definitions, response responsibilities and review process together. Trace real records to test the agreement. Alignment becomes operational when exceptions have an owner and both teams can change the rules using evidence.
Discuss the question with Nancy, or continue with the related guides below.