Primary Company Lifecycle Sync Direction

Explain association-driven stages without treating contact changes as company updates. Preparation only, not an account action.

What to provide

Contact/company IDs, primary association, lifecycle settings and dated field history.

How it works

1. Identify the primary company, not just any association.
2. Apply documented company-to-contact direction only with sync setting evidence.
3. Keep forward-only behavior and later-stage contacts separate.
4. Return provenance without changing primary associations or stages.

The output

contact | primary_company | sync_enabled | company_stage | contact_stage | direction | unknown

Worked fictional example

Fictional primary company is Lead; contact A Subscriber and contact B Opportunity. With enabled default sync A can advance to Lead, B does not move backwards. A contact-only edit does not prove a company edit.

Checks and limits

Keep source versions and original values. Unknowns stay unknown. Use qualified review for regulated, legal or hiring decisions. No live account compatibility test, send, share, schedule, ledger change or payment is authorized.

More sales workflows · How-to guides

Method: reviewed source. Demand lead: Oct13 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude43, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia103. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured. Checked October 13, 2026.