Back to blog

ROI

€1 per resolved contact: why outcome pricing is fair

Philipp M. W. HoffmannJuly 18, 202617 min read

Classic helpdesks sell seats. Value is not created by more logins, but by resolved customer contacts. Seat prices reward growth of the organization, not growth of resolution quality. Outcome pricing flips that: you pay when the AI delivers, not when someone is logged in.

For Shopify merchants with fluctuating ticket volume, that is a big difference. Seasonal peaks, launch weeks, return waves after holidays: seat models make those phases more expensive without automatically resolving more. Outcome models follow the result.

“If my company were a bit bigger, I would easily pay €1,000 a month for that.”
Konstantin Singer, Zenbox (about the product)

That kind of feedback shows what this is about: noticeable relief, not feature lists. Konstantin is not describing a widget, but a system that carries most of the work. Returns, order status, claims, email and chat from one engine. That is the context in which €1,000 a month makes sense.

What outcome pricing means

With getease you pay €1 per contact the AI fully resolves. If the AI steps back and your team takes over, you pay nothing for that contact. That aligns vendor and merchant: both want real resolutions, not mere reply attempts.

  • No pressure to hide features behind seat limits
  • No incentive to sell weak automation as success
  • A clear invoice: outcome instead of attempt
  • Scales with volume, not with headcount
  • Transparency: you see what was resolved and what was escalated

Why seat models limp

More seats mean more cost before support gets better. A shop with two people and high ticket volume pays differently than a shop with ten people and little volume. Outcome pricing follows the result. At the same time there is room for humans. The AI should not force everything. It should hand off when quality or responsibility require it.

Seat prices fit if you already work manually and automation is marginal. They fit worse if 90 to 95 percent of standard cases are automatable. Then you pay for logins while the actual work is done by the AI.

“You basically have a customer service that gets 20x as much done. Faster. And only level-2 cases escalate.”
From the conversation about AI support

A simple calculation

Suppose you have 2,000 standard contacts a month. The AI fully resolves 1,600 of them. Your team handles 400 cases that need real judgment. What does that mean financially and operationally?

  • Cost: €1,600 outcome for resolved contacts
  • Savings: hundreds of hours of manual work
  • Team focus: the 400 cases where empathy matters
  • Scale: more volume without proportional seat cost

Whether that fits you depends on hourly rate, volume, and automation rate. The direction is clear: pay for impact. If you see support as a cost center, you calculate differently. If you see support as leverage, you calculate in resolved contacts and time gained.

What “resolved” has to mean

Outcome needs a definition. Otherwise pricing gets unclear and trust suffers. That is why resolved is not the same as answered.

  • A complete answer without human intervention
  • No follow-on escalation ping-pong on the same topic
  • Traceable context in the history
  • For Shopify ops: the action was executed, not just explained
  • When uncertain: a clean handoff to a human without double work

We talk about this openly in demos. Transparency belongs to the model. Draft mode helps at the start: prove quality first, then open auto-reply.

Service as part of the value

Outcome pricing does not mean you are alone with software. Alongside the product, individual support is often the real mode: setup, store configuration, native support set up correctly. GDPR-compliant hosting in Germany and personal guidance are part of the offering.

“Alongside the product, individual support is often the real mode: setup, store configuration, native support set up correctly.”
Philipp M. W. Hoffmann

Software delivers the outcome, people help at the start. That matters especially when returns, claims, and multi-channel support come together. No merchant wants to guess all the rules alone in week one.

When it pays off

If standard questions make up most of your volume, the model often pays for itself after a few weeks. Returns, order status, address changes, recurring product questions: those are the cases where outcome pricing unfolds. Anyone who previously put three full-time equivalents into repetitive replies sees the shift immediately: less seat pressure, more outcome per euro.

Another advantage: outcome pricing makes pilots lower-risk. You start with draft, measure resolved contacts, open auto-reply step by step. Every week you see whether the rate is rising. Konstantin Singer put it from a merchant’s view: with real relief, €1,000 a month would be realistic because the team has time for growth again instead of copy-paste.

More on the strategic view in Support is not a cost center. For concrete ops: Automating returns.

Rethink Shopify support?

In a short demo we show how getease resolves standard contacts and takes the load off your team.