Customer Discovery Plan: Salesforce integration absence is blocking enterprise adoption and upgrades

Problem Statement

The absence of a native Salesforce integration is acting as a hard blocker for enterprise and mid-market adoption, full team rollout, and upgrade decisions on FlowPilot. Multiple users across both segments describe Salesforce as their system of record and cite the gap as either a personal dealbreaker or an organizational requirement that prevents budget approval. At least one account has already chosen a competitor explicitly because of this missing integration, indicating active revenue loss.

Evidence Summary

Of 20 evidence items, 7 are HIGH severity and 13 are MEDIUM severity, spanning both Enterprise and Mid-market segments. HIGH-severity signals include direct statements such as 'we evaluated FlowPilot but Salesforce support is a hard requirement for our ops team' (Mid-market), 'the product looks useful, but we cannot adopt it without Salesforce integration' (Enterprise), and 'we're mid-market and Salesforce is our system of record' (Enterprise). MEDIUM-severity signals reinforce organizational gatekeeping: 'my manager won't sign off without Salesforce' and 'our sales ops manager won't approve a tool that doesn't connect to Salesforce.' At least one Enterprise account confirmed switching to a competitor: 'we went with a competitor because they had Salesforce integration.' Several users describe it as the sole missing feature ('Salesforce sync is the only missing piece for us'), indicating high overall product satisfaction with a single critical gap. The requested functionality clusters around contact sync, deal stage sync, and native bi-directional integration rather than lightweight workarounds.

Priority Rationale

This signal scores 87/100 with high confidence, reflecting both the volume and severity of evidence across the two highest-value customer segments: Enterprise and Mid-market. The evidence demonstrates three compounding risks: blocked new adoption, stalled upgrades from lower tiers to Enterprise plans, and confirmed churn to competitors. The fact that multiple users frame Salesforce as an organizational requirement, not a personal preference, means individual champions cannot unblock deals unilaterally, making this a structural sales obstacle. Addressing it is directly tied to revenue expansion and competitive positioning.

Acceptance Criteria

• At least 5 of the interviewed accounts confirm that a native Salesforce integration would remove their current adoption or upgrade blockerInterviews reveal consistent, specific data sync requirements (e.g., contacts, deal stages, activity logging) rather than vague integration requests, allowing scoped feature definition
• At least one account currently blocked from upgrading confirms they would sign an upgrade contract contingent on Salesforce integration delivery
• No more than 1 of 7 interviewed accounts describes a lightweight workaround (e.g., Zapier) as an acceptable substitute for a native integration
• Discovery interviews surface whether bidirectional sync, read-only sync, or specific object types (Contacts, Opportunities, Accounts) are the minimum viable scope for unblocking adoption

Hypothesis

If FlowPilot ships a native Salesforce integration covering core objects (Contacts, Opportunities, and deal stages) with bidirectional sync, then the majority of enterprise and mid-market accounts currently blocked from adopting or upgrading will remove their objection and move forward, because the evidence consistently shows Salesforce is their system of record and the integration gap is cited as the single or primary blocker to purchase and rollout decisions.

Target Accounts

• ·Enterprise accounts that submitted feedback explicitly stating Salesforce integration is a hard blocker for adoption or full team rollout
• ·Mid-market accounts where a sales ops manager or organizational gatekeeper, not the individual user, is blocking approval due to the missing integration
• ·Enterprise accounts currently on a lower-tier plan that have indicated they would upgrade to Enterprise if Salesforce integration were available
• ·Accounts that evaluated FlowPilot but chose a competitor specifically because of Salesforce integration, to understand what the competitive bar looks like and what it would take to win them back

Discovery Questions

1. Can you walk me through how your team currently uses Salesforce day-to-day, and where you expected FlowPilot to fit into that workflow?
2. When you say Salesforce integration is a hard requirement, what specifically needs to sync, contacts, deal stages, activity logs, something else, and in which direction?
3. Who in your organization made the final call that FlowPilot couldn't move forward without Salesforce integration, and what were their stated reasons?
4. If we shipped a Salesforce integration in the next 90 days, what would need to be true about it for you to get sign-off to adopt or upgrade, are there specific objects, sync frequency, or security requirements?
5. Have you tried any workarounds like Zapier, manual exports, or a middleware tool to bridge FlowPilot and Salesforce? If so, why wasn't that sufficient?
6. Are you currently evaluating or using a competitor product that has Salesforce integration? What has that experience been like compared to FlowPilot?
7. Beyond Salesforce, are there any other blockers that would prevent full team rollout, or is this genuinely the only thing standing in the way?

Open Questions

1. What is the minimum viable scope of Salesforce integration, specifically which objects (Contacts, Opportunities, Accounts, Activities) and sync direction (read-only, write-only, bidirectional), needed to unblock the majority of affected accounts?
2. Who is the actual decision-maker blocking adoption, the individual user, sales ops manager, or IT/security team, and what are their specific technical or compliance requirements for a Salesforce integration?
3. Are any of the affected accounts currently using a third-party workaround such as Zapier or manual CSV export, and if so, is that reducing urgency or creating an additional pain point?