Integration Proof When the Connection Is Not Configured Yet
Published October 21, 2026 · By Kate Steinmeyer · Presales

An integration may not be configured in a demo environment. A team can still explain the workflow, but it must distinguish documentation, simulation, sandbox evidence, and a live buyer-specific connection.
Choose the evidence level openly
Documentation can describe supported setup and limits. A diagram can explain data flow. A simulation can show the expected user experience. A working sandbox can test a configured path. None of these proves the same thing, so label the level before showing the result.
Avoid phrases such as “works out of the box” unless the current integration and required configuration support that statement.
Show what can be verified today
For a hypothetical CRM connection, the presenter might show the source action in the product, a documented field mapping, and a prepared receiving-system result. They should say which part is illustrative. If a test tenant is available, perform the connection there and record the version and prerequisites.
Ask the buyer which field, permission, error condition, or volume matters most to their evaluation. That determines the next test more effectively than a generic integration tour.
Plan the live validation
List accounts, access, sample records, technical owners, and pass criteria. Record the result in writing. If the connection fails or needs custom work, keep that fact visible in the follow-up.
The interactive integration disclosure guide focuses on a self-guided simulated path. This article compares the evidence options available to presales.
Compare the evidence without overstating it
When a live connection is unavailable, use the strongest evidence you actually have and label its limit:
| Evidence | What it can show | What it cannot establish alone |
|---|---|---|
| Current documentation | Supported setup and stated prerequisites | A successful connection in the buyer's environment |
| Diagram or mock | The intended data flow | Authentication, sync, or error behavior |
| Tested sandbox connection | A real exchange under recorded conditions | Compatibility with every buyer configuration |
| Buyer-environment test | Results for that configuration and test case | Scale or untested failure cases |
For a fictional CRM connection, an animated field map can explain the flow. Pair it with current documentation and a sandbox result if one exists, then name the buyer-specific test still needed. Include the version, environment, and sample data behind any test result.