Krishna Dey Shipped · Strategic integrations
Salesforce Reverse Sync
A configurable reverse-sync system for pushing contract and workflow data back into Salesforce, shaped to be extensible across triggers, conditions, object mappings, and future automation use cases.
Engineering Manager / technical lead
Shipped.
Salesforce Native: surpassed SpotDraft's internal target of more than $1M in revenue impact.
Challenge
The immediate request could have been solved as a narrow, hardcoded sync flow, but the real product surface was larger: multiple events, different objects, conditional behavior, and evolving field-mapping needs.
Approach
I pushed the design toward a more reusable automation model with configurable triggers, conditions, find-or-create behavior, and field mapping across Salesforce objects instead of another isolated integration path. The design landed on a generic trigger-condition-mapping-action engine: a trigger starts an execution, conditions decide whether it continues, a find-or-create step locates or creates the target Salesforce record, and a mapping layer resolves which SpotDraft fields write to which Salesforce fields — built with the Strategic Integrations pod and Staff frontend engineering rather than as a Salesforce-only code path.
Outcome
The result was a stronger integration foundation that could support richer CRM workflows and became a better base for future automations than a one-off reverse-sync implementation. Salesforce Native has surpassed SpotDraft's internal target of more than $1M in revenue impact. The trigger-condition-mapping-action model behind it is now the starting point for SpotDraft's broader 2026 Automation Platform: the same engine extended to HubSpot reverse sync, other external actions, and future SpotDraft-to-SpotDraft automation.
What it taught
The highest-leverage technical decisions often come from resisting locally optimal delivery when the future surface area is large and predictable.
More projects
All projectsNative integration and platform work spanning CRM, procurement, and collaboration systems, with emphasis on reusable primitives, metadata-aware design, and integration surfaces that stay coherent as the catalog expands.
Replaced SpotDraft's fixed two-party contract assumption with configurable party roles, so contract creation, questionnaires, and publishing could support more than one organization or individual on either side of an agreement.
A product-systems arc that started with self-serve questionnaire setup for template workflows, was extended to third-party paper on the same foundation, and then evolved into the current Workflow Manager.