What Is Integration Requirements?
The technical specifications for connecting your product with the prospect's existing systems, covering APIs, data formats, authentication methods, and data flow.
Integration requirements define how your product talks to everything else in the prospect's stack. Which systems need to connect? What APIs are involved? What data moves between systems and in which direction? What authentication method is required (OAuth, SAML, API keys)? How often does data sync? What happens when the integration fails?
These questions come up in every enterprise deal. Buyers almost never purchase a product that operates in isolation. Your product needs to integrate with their CRM, data warehouse, identity provider, ticketing system, or some combination. The complexity of those integrations often determines both the deal timeline and the implementation cost.
Why It Matters for SEs
Integration complexity is one of the top reasons enterprise deals stall or die. A prospect who discovers during the POC that a critical integration does not work will walk away regardless of everything else your product does well. SEs who surface and validate integration requirements during technical discovery prevent this.
Integration requirements also feed directly into the solution architecture. The SE maps the integration points, identifies gaps between what exists natively and what requires custom development, and communicates the effort level honestly. Underestimating integration work during the sales process creates implementation nightmares after the deal closes.
How SEs Use This
Maintain a deep understanding of your product's native integrations, API capabilities, and known limitations. During technical discovery, ask specifically about every system the prospect expects to connect. Do not assume. A prospect who mentions "Salesforce integration" might mean real-time bi-directional sync or a nightly CSV export. The details matter enormously.
For each integration, document: the source and destination systems, data direction, sync frequency, authentication method, expected data volume, and error handling requirements. Share this documentation with the prospect and your post-sales team. Clear integration specs set up both the deal and the implementation for success.
Frequently Asked Questions
When should integration requirements be discussed?
During technical discovery, before the POC. Discovering a critical integration gap during the POC wastes time and damages credibility. Identify all required integrations early and validate feasibility before committing to an evaluation.
What if the prospect needs an integration your product does not support?
Be transparent. Explain what is available natively, what can be built via API, and what would require a partner or custom development. Provide a realistic effort estimate. Hiding gaps only creates bigger problems later.
Who handles integrations during implementation?
The SE defines the integration requirements during the sale. Professional services or the customer's engineering team builds them during implementation. A clear handoff document from the SE prevents the post-sales team from re-discovering requirements.