The MFT renewal that tripled because nobody counted the connections

Whoever signs the MFT contract reads the unit price and skips the unit. The line item says a few hundred dollars per trading-partner connection a year, the first invoice covers twenty partners, and against the budget the total looks fine. The question that sets the three-year cost never gets asked: what does that price do when the partner count doubles, then doubles again?

The trap closes on a quiet assumption — that today's connection count is roughly the count you renew against. Onboarding partners is what a healthy business does, so under per-connection pricing every win is also a line on next year's bill, stacking in a way the signing spreadsheet never showed.

How per-connection pricing compounds with partner onboarding

Per-connection metering ties cost to the single activity a growing operation does most: add counterparties. A retailer wires up a new 3PL. A clinic adds a lab feed. A carrier brings on a broker. Each is a fresh billable connection. Start at twenty partners, grow at a handful a quarter — an unremarkable pace for a company that is winning — and you sail past a hundred and forty connections inside three years without one deliberate spend decision.

In practice it runs worse than linear, because connections almost never retire. Old partners stay provisioned just in case. An AS2 relationship outlives the project that created it. You are not paying for capacity you use; you are paying for a meter that never decrements.

The renewal quote nobody modeled at signing

Renewal is where the counter meets the contract. The escalator buried in the original terms read as harmless — a modest annual uplift, which a finance owner files under noise. But it multiplies a base that has been growing the entire term. A small percentage on a per-connection rate, applied to several times the connections, is not a small renewal. It is the partner curve and the rate curve multiplied together, and the quote that lands can be two or three times the prior term.

By then you hold no leverage. A hundred-plus partners are live, each a tested SFTP or AS2 integration that the partner's own IT team signed off on. Re-papering all of them to switch vendors is a quarters-long project nobody staffed. The vendor knows this. Renewal becomes a price-taker conversation.

Multi-tenant economics versus metered transfer pricing

The honest comparison is not per-connection versus free. Cloud-native metered models are transparent and still scale with the variable you cannot control. Pay-per-protocol-hour endpoints bill you to keep a server reachable, then add a per-gigabyte charge on top. The per-unit price is predictable; the aggregate is not, because volume and partner count both only climb.

Tenant-based economics breaks that link. You price an Environment — your tenant, with its partners, protocols, and audit trail inside it — and partner number a hundred and forty-one costs the same to onboard as partner number two. The vendor's marginal cost of one more connection is near zero, so charging for it prices your success, not their service.

Negotiating predictable cost before you are locked to the partner count

The one moment you hold leverage is procurement, before you strand a hundred integrations on their platform. Spend it on the cost model, not just the headline rate. Pin these down in writing:

Model the three-year partner curve before you sign, not after the quote arrives. If the price tracks your partner count, you are not buying file transfer. You are writing the vendor a call option on your own growth.

xEvolve prices the Environment, not the connection: SFTP and AS2 partners live in one tenant with unified audit, and the hundred-and-forty-first partner leaves the renewal math untouched. If your current quote scales with success, compare the pricing before your next term locks you in.