Splash for Salesforce
Product lead for Splash's managed Salesforce package. Guided setup, two-way authenticated connections, real-time event and guest sync, and Flow components admins can wire up without code.
Event marketers live in Splash and their sales team lives in Salesforce. The integration between them had grown into a set of one-off syncs that every customer configured differently. This was the rebuild as a managed AppExchange package. I was the product manager at Splash, with Appiphony as the build partner.
The scope was defined by what an admin has to do on day one. A setup assistant walks them through the package in one guided wizard instead of a long install doc and shows what’s complete. A system connections step authorizes both directions, so the package gets a token to call Splash and Splash gets OAuth access to call the org, and nothing depends on a shared password. An Apex web service acts as a landing pad, so event and guest data lands in packaged objects in near real time instead of on a schedule. Instead of hardcoding the sync, the package ships Flow components (an invocable method with a custom property editor and starter templates) so an admin can decide which guests go to which event under which conditions in the tool they already use. Package logging with configurable levels shipped in the first release, because the first support ticket on any integration is “what happened?”
The decision underneath all of it was to make the package configurable. Every Salesforce org models events and contacts a little differently, and a sync that assumes one model is a sync half the customers can’t use.