The irritation
Teams often expect a relationship recorded on one CRM object to appear everywhere it is operationally relevant, but that mirroring is not automatic.
ProductRetiredRetired
Association Mirror
A CRM relationship-syncing tool retired after exploring the edge cases hidden inside apparently simple associations.
- Current state
- Retired — Retired
- Jack’s role
- Workflow design, CRM engineering, Operations
- Find it in the workshop
- Archive Yard · Two-sided archive marker
Built because…
The real build story.
What I built
I built event-driven synchronization around CRM associations and the safeguards needed to avoid loops and duplicate relationship changes.
The hard part
Mirrored updates can recurse, race, arrive out of order, or collide with human edits, turning a convenient rule into a data-integrity problem.
Under the casing
Proof, not decoration.
Build evidence02 items
- Event-driven CRM relationship synchronization
- Loop prevention and idempotent update work preserved from the build
- HubSpot
- Node.js
- Event processing
Scope of work
What I owned.
- Workflow design
- CRM engineering
- Operations
No victory-lap math
Outcome and lesson.
Where it landed
The product was sunset, and the archive keeps the operational lessons visible instead of quietly erasing the attempt.
What stayed
Synchronization needs a clear source of truth and an exit strategy. Symmetry in the interface does not imply symmetry in the data model.
This project has a physical address.
In the playable workshop, Association Mirror lives in the Archive Yard as a two-sided archive marker. You can inspect it without unlocking anything.