Krishna Dey Shipped · Platform and integration architecture
Salesforce, HubSpot, Coupa, Slack, and native integration work
Native 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.
Senior Software Engineer (2024 foundation), then Engineering Manager directing HubSpot/Slack, hands-on on Coupa
Shipped.
Salesforce and HubSpot native integrations: each surpassed SpotDraft's internal target of more than $1M in revenue impact.
Challenge
Every CRM/procurement/collaboration integration needs the same underlying capability — discover an external system's objects and fields, let a user map them to SpotDraft data, then read and write through that mapping — but a naive implementation hard-codes each provider's object model directly into the mapping logic, so every new integration re-solves the same problem from scratch.
Approach
Starting in 2024 as a Senior Software Engineer, I designed and built a shared, provider-agnostic mapping platform for native integrations: a way to discover an external system's objects and fields, map them to SpotDraft data, and read and write through that mapping — with each provider's specific fetch/write logic isolated behind its own adapter so the mapping layer itself never needed to know about any one provider's data model. Salesforce Native launched on that foundation. After moving into engineering management, I directed the specs, configuration design, and architecture reviews that let HubSpot and Slack build on the same primitives instead of increasing long-term fragmentation. For Coupa, I stayed hands-on and personally built the out-of-the-box integration on that same architecture against Coupa's GraphQL API — ramping up on how their API and callout model worked from scratch in about 1-2 days before shipping it as something customers could self-serve rather than a one-off custom build.
Outcome
Each new integration became a matter of adding a provider adapter rather than rebuilding object/field discovery and mapping from scratch. The Coupa integration shipped as a self-serve product surface on the shared architecture rather than a bespoke customer project. Salesforce and HubSpot native integrations have each surpassed SpotDraft's internal target of more than $1M in revenue impact.
What it taught
Integration work compounds only when the platform underneath it gets clearer with each delivery cycle — a shared foundation instead of a parallel implementation per provider.
More projects
All projectsReplaced 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.
Researched and implemented the OAuth 2.0 Device Authorization Grant (RFC 8628) as reusable authentication infrastructure, built for the Gmail integration but designed to back "Login with SpotDraft" from any constrained or limited-input client.