Charging Integrations by Data Flow

Charging on data delivered reframes integrations from a setup fee into infrastructure tied to customer value. In this market, most vendors still charge for connections, instances, tasks, requests, or integration count. Ampersand is trying to charge when data actually moves through a live product workflow, which better fits cases like syncing hundreds of thousands of records per day into a customer’s customized Salesforce or HubSpot environment.

• The push came from a common complaint with unified API pricing. A SaaS vendor can pay for many connected accounts that never become real customers, while the vendor using the integration platform only captures value when production data starts flowing into real workflows.
  1 sacra
• Comparable platforms price on different units. Merge sells tiered plans based on integration breadth and support. Paragon prices by usage volume and number of integrations, often around tasks or requests. Prismatic mixes subscription with per instance usage, where each customer deployment counts as a billable unit.
  2 sacra 3 sacra 4 sacra
• That makes the pricing choice part of the product strategy. Ampersand is built for deep, customer specific enterprise integrations, where one account may involve 170 tenants, custom objects, bulk APIs, and daily syncs of 300,000 records. In that world, a flat per connection fee can underprice heavy use and overprice shallow use.
  1 sacra

If this model works, pricing in integration infrastructure moves closer to cloud infrastructure. The winner will be the vendor that becomes the default pipe for high value data movement, then charges in proportion to the amount of live business traffic running through it, not the number of connectors sitting idle.