Building Integrations Print

  • guide, howto, solution, zillionkinghost, hosting, support
  • 0

Connecting to other systems.

WHY THEY MATTER

Products that fit into existing tools are adopted; products that stand alone are abandoned.

WHAT TO BUILD FIRST

Integration with whatever your customers already use most.

HOW TO KNOW

Ask them.

WHAT AN IMPORT CAPABILITY PROVIDES

A route in from whatever they use now.

WHY IT MATTERS MOST

The largest barrier to adoption is existing data elsewhere.

WHAT TO SUPPORT

Spreadsheet import, always.

WHY

It is the universal format, whatever the source system.

WHAT AN EXPORT CAPABILITY PROVIDES

Confidence that they are not trapped.

WHY THAT INCREASES SALES

Buyers are wary of lock-in, and visible export reduces the objection.

WHAT TO OFFER FOR CONNECTIVITY

Webhooks, notifying other systems of events An API Prebuilt connections to common tools

WHAT WEBHOOKS REQUIRE

Retries Signatures, so receivers can verify Visibility of failures

WHAT TO AVOID

Integrations built for one customer Dependence on interfaces that change without notice Maintaining more integrations than you can support

WHY THAT LAST POINT

Each one breaks eventually, and every break is a support incident.

WHAT TO MEASURE

Which integrations are actually used.

WHAT TO RETIRE

Those that are not.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot