Process intelligenceSource-backed brief

How did Celonis make measurable customer value its sales motion?

Alexander Rinke’s 2020 interview traces Celonis to a university project in Munich investigating an inefficient IT help desk. The CIO became the first customer, and the team bootstrapped for five years. This is a concrete problem-to-customer sequence, although the supplied record does not establish the first contract price. The starting point was an operational difficulty that a specific buyer already recognized. [1]

Evidence and interpretation

This story condenses a source-backed brief. Some historical details and internal metrics are not established. [Inference] marks analysis. Source numbers keep the numbering of the full case, and the evidence is from the 10 Nov 2026 research edition. Read the research method.

The first sale began with the customer’s own process

[Inference] Process intelligence is easier to evaluate when the buyer can compare findings with a familiar operating problem. A help desk offers recorded activity and identifiable delays; the commercial case can start with what actually happens rather than a broad promise of transformation. That does not make implementation trivial. Data access, interpretation and the changes required to realize value are separate pieces of the buying decision.

Rinke recounts waiting outside a conference VIP area to speak with SAP’s founder, which led to a major relationship. Celonis’ 2015 announcement says its software became the first SAP Startup Focus product added to SAP’s master price list. The story combines founder persistence with a specific distribution milestone, without disclosing the relationship’s channel-specific acquisition cost or revenue contribution. [1][2]

[Inference] SAP access could provide relevance and legitimacy inside an established enterprise environment. It still leaves Celonis responsible for showing why a particular process owner should act. A partner can help open a door; the customer’s own economic problem supplies the reason to proceed. Confusing those roles would overstate distribution as a substitute for a measurable value case.

Enterprise execution became a broader organizational responsibility

Miguel Milano joined as CRO and co-owner in 2020 after leading Salesforce international businesses and previously working at Oracle. His stated remit included sales, success, solution engineering, delivery, demand generation and partners. In 2022, Chris Donato brought Oracle applications and consulting experience, while Gene Reznik brought Accenture ecosystem experience. These are documented appointments, not proof that any individual alone caused subsequent growth. [3][4]

Celonis describes Value Engineering as a team spanning discovery, presales, value realization, renewal and expansion. Angelica Cabellos, SVP of international Value Engineering, discusses business cases, stakeholder management and security conversations in its careers profile. This makes the service model unusually explicit: the company publicly connects the promise made during selling with work needed after the contract. The source describes the organization, rather than independently evaluating its effectiveness. [5]

[Inference] That continuity addresses a common weakness in complex selling: one team calculates potential value, while another inherits responsibility for producing it. Keeping the lifecycle connected can make assumptions easier to revisit. The practical test is whether customer owners, baselines and actions remain clear after purchase, rather than whether a value estimate looks persuasive in a presentation.

Potential savings must become realized operating value

Rinke warned that enterprise founders often charge too little for a difficult sales process. The supplied research does not verify current negotiated prices, CAC or customer-level service margins. His warning is therefore an operating principle from an experienced founder, not a disclosed minimum contract value or a formula for pricing every enterprise product. [1]

[Inference] A high-touch sale needs enough contribution to support data work, stakeholder alignment and continuing delivery. The main scaling risk is a consulting-like engagement that repeatedly discovers opportunities without making implementation repeatable. Separating potential savings from realized changes would help expose that risk. So would recording which customer owner is responsible for each action and how much provider effort remains necessary.

[Inference] Celonis offers a useful pattern when a customer’s process contains measurable economic friction: sell through the evidence of that problem and preserve accountability through renewal. The university project, SAP relationship and value-engineering organization show different stages of that pattern. Its limits are equally important: a compelling analysis is not yet a realized outcome, and intensive service cannot be assumed to carry software margins.

GO DEEPER

Celonis: the full GTM case

The complete case holds the named people, the economics, the available historical evidence, the critique and the open research questions.

Read Celonis’s full GTM case

Terms in this story

ImplementationEcosystemRenewalCustomer acquisition costEngagement

Questions behind the story

How do I choose between product-led and sales-led growth?Why does the site leave CAC and retention blank for some companies?All 104 GTM questions answered

Sources

Numbers match the source list of the full Celonis case. A source’s publication date and the date of the event it reports can differ.

  1. Alexander Rinke interview Matt Turck · 2020-08-13
  2. TUM entrepreneurship award and SAP partnership Celonis · 2015-10-19
  3. Miguel Milano appointment Celonis · 2020-02-26
  4. Executive appointments Celonis · 2022-01-20
  5. Value Engineering team profile Celonis