Skip to content

Smart Charge by RiDERgy · Season 2, Episode 10

EV roaming, OCPI, financial clearing, uptime and AI native engineering

Jakob Kleihues

co-founder of ENAPI

27 October 2026 · 1 hr 17 min · English · Host: Claudio Geyken

Chapters (14)

Key takeaways

  • Five hundred operators times five hundred providers gives 250,000 bilateral integrations, each needing a handshake, set-up, testing and maintenance.

  • The roaming hubs before him carried about 80 percent of the integrations but only 20 percent of the transactions.

  • Even five cents a session, at a million sessions a month, creates an incentive to go bilateral.

  • Many partners had not implemented the tariff module, so two parties could connect but could not automatically tell each other what a kilowatt-hour costs.

  • Many in public charging do not believe the booking module scales, while behind-the-fence logistics is where it fits.

Smart Charge Leader · 27 October 2026

Connectivity is free; the money is in the clearing

Jakob Kleihues puts the industry's connectivity problem at 250,000 integrations, and argues that anyone still charging for the pipe has already lost the argument.

By RiDERgy editorial

Jakob Kleihues tells friends, family and investors that charging an electric car at a public station still often does not work, and he says about 90 percent of the people he tells agree with him. He is no critic outside the industry: he co-founded ENAPI, which brokers transactions between charge point operators, the firms that own the hardware, and mobility service providers, the firms whose app a driver taps.

Connectivity between those two sides should be given away, because the fee that pays for it is the very thing that pushes the largest customers to build their own link instead.

The arithmetic is his. Five hundred operators multiplied by five hundred providers produces 250,000 bilateral integrations, each of which needs a handshake, a set-up, testing and then permanent maintenance. Kleihues points at what the roaming hubs did before his company existed: they carried about 80 percent of the integrations but only 20 percent of the transactions, because the biggest operator and the biggest provider had already connected to each other directly. A fee completes the argument. At a million sessions a month, even five cents a session is a standing invitation to route around the broker.

6 min read

Show notes

With 500 players on each side of the market, connecting everyone to everyone takes 250,000 bilateral integrations, and every one of them needs a handshake, testing and maintenance. Jakob Kleihues, co-founder of ENAPI, argues that connectivity between charge point operators and mobility service providers should be a free commodity, and that the real money is in financial clearing.

Jakob explains why connecting to hundreds of partners one by one does not scale: with 500 players on each side of the market, that is 250,000 bilateral integrations, and every one of them needs a handshake, testing and maintenance. ENAPI replaces them with a single connection. Since it started onboarding, it has connected more than 450 partners and over one million charge points, with implementation times that rarely exceed one or two weeks. He also shows why even a fee of five cents per session pushes volume towards direct connections, and how brokering the transaction lets ENAPI check invoiced charge detail records against the sessions it authorized.

The conversation also covers the practical side of pricing, from discounts applied at charge detail record level instead of a flat reduction on the invoice to the new booking module in OCPI 2.3, and what it takes to keep a published 99.998 percent uptime with a very small team where more than 94 percent of production code is written by AI. Jakob explains why the US, Australia and New Zealand followed network by network rather than country by country, and why he wants the industry to think about the size of the pie rather than the slice.

An episode about turning connectivity into a commodity, and about what it takes to make public charging simply work.

Topics covered

  • OCPI and why bilateral integrations do not scale
  • Free connectivity and the business case for financial clearing
  • Validating charge detail records
  • Discounts, variable prices and the booking module
  • Uptime and AI native engineering
  • Growing network by network into the US

Resources mentioned

The guest's company

  • ENAPI

    Jakob Kleihues's company: OCPI-based roaming broker connecting CPOs and EMSPs with free connectivity and financial clearing.

  • ENAPI status page

    Public uptime dashboard showing 99.998% uptime across US and EU infrastructure, referenced as accountability mechanism.

Regulation and standards

  • OCPI (Open Charge Point Interface)

    Open roaming protocol between charge point operators and e-mobility service providers, maintained by the EVRoaming Foundation.

  • OCPI versions 2.1.1, 2.2.1, 2.3.0

    Current relevant OCPI versions discussed; 2.3.0 adds enhanced locations data and booking module for heavy-duty/logistics use cases.

  • OCPP (Open Charge Point Protocol)

    Protocol for communication between charging stations and charge point management systems (CPMS), distinct from OCPI roaming layer.

  • OICP (Open InterCharge Protocol)

    Hubject's roaming protocol, originally proprietary, released as open source in 2019; strong in DACH markets.

  • eMIP (eMobility Interoperation Protocol)

    GIREVE's roaming protocol supporting both hub-based and peer-to-peer connections, managed by the French roaming platform.

  • OCHP (Open Clearing House Protocol)

    Open clearing house protocol managed by e-clearing.net, an older protocol now largely superseded by OCPI.

  • EVRoaming Foundation

    Non-profit foundation maintaining the OCPI standard; ENAPI co-founder Dennis Laumann was among original authors.

  • MCS (Megawatt Charging System)

    High-power DC charging standard (up to 3.75 MW) for heavy-duty electric vehicles like trucks and buses, developed by CharIN.

Companies and tools

  • Bonnet

    EMSP app founded by Patrick and Elliott from Imperial College London; Jakob worked there before founding ENAPI; acquired by OVO Energy.

  • OVO Energy

    UK energy supplier that acquired Bonnet; the Bonnet team now operates as Oval Drive within OVO.

  • Project A Ventures

    Berlin-based early-stage VC fund where Jakob worked for 4.5 years; invested in ENAPI's pre-seed round.

  • Seedcamp

    European seed-stage VC fund headquartered in London; co-invested in ENAPI's pre-seed round alongside Project A.

  • Voyager Ventures

    US-based early-stage climate tech VC firm (co-founded by Sierra Peterson and Sarah Sclarsic); led ENAPI's seed round.

  • Climate-KIC

    Europe's leading climate innovation agency (formerly EIT Climate-KIC); Jakob interned there at the Olive Campus in Berlin.

  • InnoEnergy

    EIT Knowledge and Innovation Community for sustainable energy; Claudio Geyken worked there, parallels Climate-KIC model.

  • e-clearing.net

    Roaming hub operating the OCHP protocol; hosted an event in Aachen where Jakob and Dennis Laumann met.

  • ChargePoint

    Largest US EV charging network; Daniel Brown (ENAPI's Director of Growth) was Global Head of Roaming there.

  • Daniel Brown

    Former Global Head of Roaming at ChargePoint; joined ENAPI as Director of Growth leading US/UK commercial efforts.

  • Fastned

    Dutch ultrafast charging network (CPO); cited as example of infrastructure-fund-backed 'Charging League' players.

  • IONITY

    European HPC charging network joint venture of BMW, Ford, Hyundai, Mercedes-Benz, Volkswagen Group; cited as 'Charging League' example.

  • Electra

    French fast-charging startup operating in France and Europe; cited as 'Charging League' infrastructure-fund-backed CPO.

  • Powerdot

    Portuguese CPO operating 7,500+ charge points across 6 European countries; cited as 'Charging League' example.

  • Nationale Leitstelle Ladeinfrastruktur

    German national coordination office for charging infrastructure; hosted electric truck conference Claudio attended.

  • Honda e

    Battery electric supermini (sold 2020-2024 in Europe); Jakob's father drives one, used for testing charging transactions.

  • Tesla

    Only full-stack EV player (hardware, CPO, CPMS, EMSP, car); Jakob contrasts with rest of industry that must collaborate.

Cite this episode

Geyken, C. (host), Kleihues, J. (guest). "EV roaming, OCPI, financial clearing, uptime and AI native engineering." Smart Charge by RiDERgy, Season 2, Episode 10, 27 October 2026. www.ridergy.com/podcast/s2-ep-10-jakob-kleihues-co-founder-of-enapi-ev-roaming-ocpi-financial-clearing-u

Transcript

12,823 words · machine transcript

  • Claudio Geyken, host
  • Jakob Kleihues, guest

Cleaned up from a machine transcript. Translations are machine-generated and may contain errors.

Opening and founder background

Claudio Geyken

Welcome to the Smart Charge by ridergy.com podcast. This is Claudio geyken, founder and CEO of ridergy.com. This is your show to learn about all things energy management and smart charging innovation for electric vehicles and fleets. Connect to 450 partners and you build 450 handshakes or you build one. That is the idea behind in Appi. And my guest today is its co founder, Jakob Kleihus.

In two and a half years, his company has connected more than 1 million chargepoints. And it did so with a claim that sounds almost provocative. Connectivity between ChargePoint operators and mobility service providers should be free. The money, he says, is made somewhere else. We talk about where, about what financial clearing really involves, and about how a very small team keeps its infrastructure running at 99.998% uptime. Let's get into it. Right.

Jakob, nice that you are here today. How are you?

Jakob Kleihues

Yeah, thank you so much for the invite. Yeah, I'm a little bit stressed, as you know. I was late,. Rushing from the airport, but other than that I'm fine. Thank you so much.

Claudio Geyken

No worries.

Claudio Geyken

You made it from the Netherlands today. So that I think I didn't have so. Far. I guess that made it so far in the same day.

Jakob Kleihues

Yeah, exactly.

Jakob Kleihues

Especially because I'm home in Berlin as you are, so. Right. It's strange. But anyways, very good and thank you so much for the invite.

Claudio Geyken

Yeah.

Claudio Geyken

And great to also know that you are a true Berliner. Born here. Born and raised. And your parents as well. So it's something I didn't know as I also was raised here in Berlin, so.

Jakob Kleihues

True.

Jakob Kleihues

Yeah, yeah.

Jakob Kleihues

I grew up in Berlin. I mean I lived for quite a lot of years kind of in other cities all across Europe still. Studies studied in the south of Germany and in Copenhagen, then worked in London for a short time in Amsterdam. So I kind of know some other places as well. But like I'm back in Berlin for. For quite a lot of years already now and building a napi from Berlin as well.

Claudio Geyken

Yeah.

Claudio Geyken

And maybe you can share a little bit more about your background. What? What? Also I also decided to go from Berlin to the south of Germany. Funny enough to study what there's. But I think a lot of Berliners like to stay as well in Berlin. What's your motivation? What was your motivation? To go to the south and to study.

Jakob Kleihues

Oof.

Jakob Kleihues

I mean this is going back to when I was 18. Right. Like, I wonder if I can even. If I can even recollect kind of why that was. Right. To be honest, I Think a very natural. Let's go as far away as possible. And maybe my horizon back then was a little bit Germany, kind of focused, to be honest. But yeah, so that was south of Germany. So I studied at Zeppelin University and had a great time there. Constance. No, it's Friedrichshafen.

Yeah, but like Lake of Constants. Exactly. So. And yeah, had a great time there. To be honest. I. I sometimes wonder how much I'm actually applying from. From what I learned at university or school in general in my normal life. And it's close to zero, but I definitely have a lot of. Yeah, my closest friends from that time still, so very much kind of would do it again.

Claudio Geyken

What did you study?

Jakob Kleihues

I studied.

Jakob Kleihues

It's.

Jakob Kleihues

It's like a. Like a general studies between sociology, politics, culture and economics for the first year. And then you focus. And I focused for corporate management and economics. Yeah. So that was essentially my study at Lake of Constance. And then I went for a pretty standard Master in Business Administration for the Copenhagen Business School for my masters.

And obviously in between, like a lot of internships at different startups, different companies, I never worked. And we briefly spoke about that kind of just before we started taping here. But like, I never worked for a big company, so I essentially don't have any experience with kind of corporates and how it is working for corporates. And that's why I think I'm on a kind of ongoing basis learning a lot about kind of how these organizations work. But.

Claudio Geyken

Yeah,.

Jakob Kleihues

But in general, no. Yeah, that essentially. Yeah, what I studied.

Claudio Geyken

And what did you do in your past jobs? What were your.

Jakob Kleihues

So I.

Jakob Kleihues

So as I said, I did a lot of internships in different companies and I think. Like what? Like, like then there was one company where we were actually, there was one company that was maybe interesting for this podcast as well. And there was a Climate Kick. I did an internship with Climate Kick that was at Olive Campus, where obviously a lot of infamous kind of European German companies are kind of headquartered by now.

But yeah, back then they had like a green garage there and they essentially incorporated some. Some startups there, which was very exciting. And I was just part of the team there trying to help founders kind of get shit done, essentially. But that was maybe an interesting first step. But like, I think the first. Step that was relevant for my future kind of job was at Project A Ventures, where I more or less did an internship in 2018.

But it was very intense. And what I loved about it is you're talking to people who are excited about what they are doing. Every day because you're talking to founders. And I think that was what I had missed in a lot of other positions that I held before. So. So, yeah, that's a way.

Claudio Geyken

As I was at InnoEnergy. So also the other kick in the climate was more broader climate topics and inno energy, very much on energy. And. And then I could also feel the energy of the founders we were supporting. So I can totally relate.

Jakob Kleihues

To the point. Yeah, exactly. And then I decided, okay, fast paced environment. I learn a lot. I'm not bored at all, and the people around me are not bored. So let's spend some more time here and essentially start working for venture capital funds. And I did that for four and a half years, so actually quite some time, always in the earliest stages.

So essentially, startups that had nothing or close to nothing, essentially the founders themselves and their commitment to build something big and trying to figure out, do they have chances to actually make it right? Super exciting time. What.

Claudio Geyken

Did you learn to be able to distinguish that. That maybe also is relevant today for your founder being like,.

Jakob Kleihues

I mean, it's hard to break it down like that, probably. But I think one thing, like, I believe I learned is that, for example, a lot of startups investing into startups is essentially investing into a potential outlier, as in, like a company that returns significantly more money than any other company kind of in the industry. So what you want to invest into is something that has the potential to become really, really big. Right?

And I think what, what, what you learn quite quickly is everyone has a kind of huge incentive to kind of do that based on data, right? And historic kind of performances of other companies. But a lot of these outliers are actually not following kind of the normal path of other startups because otherwise they wouldn't do something different and therefore wouldn't be an outlier. Right? Maybe that's oversimplifying here. Right?

But, like, a lot of the most exciting companies, I think are built from first principles without kind of trying to mimic another company. Right? Like, so this, we are the Airbnb for, I don't know, for phone sharing or something like that, right? How crazy. Boring, right? Like, I'm trying not to swear, right? Like, so that was a little bit what I learned for myself, right?

Like, think yourself to a certain extent, because most likely, if you dare to think yourself, maybe this can be more successful than kind of if you don't. And I think that was one of the things. The other thing was it's definitely to some extent about, okay, do I work Hard and am I able to kind of understand the contexts. But a lot of, kind of starting and kind of scaling a company is also luck and energy, right?

Define ENAPI’s execution philosophy

Jakob Kleihues

Like how much energy am I able and willing to kind of invest every single day? And I think that's something that. Yeah, we also learned. I also learned kind of working in the venture capital idea.

Claudio Geyken

Versus execution, which I saw you had a point. I don't know, I remember if it was in the blog post or in a social media post. So maybe can you elaborate on how you apply it in your day to day as well like this. And then we will come back to also how you got the idea, but then. And maybe pivoted from the initial concept at all or if at all.

Jakob Kleihues

Yeah, I'm always surprised how little we actually pivoted to be honest. But like we can totally speak about that. But yeah, I mean you spoke about execution and I think what, what our view on this as an RP team would be is kind of we are the challengers in an industry, right?

As a startup, you kind of get into this industry, you essentially have no logo, you have no brand, you have no team, you have no, you don't even have capital in the beginning, right? Like, I mean we were able to rise quite quickly, but like essentially the entire world is against you, right? And the one thing that you kind of potentially have is execution, right?

Because you will always be faster, you will always be able to kind of react quicker and you will always care more than kind of the companies that, that are so far kind of the incumbents, right? And, and therefore, I mean we face a lot of situations. I mean for example, these stealth startups or something like that, right. That come out of stealth and launch themselves. Like I never understood this, right?

Because from our perspective, like it's, it's all about execution. And I'm happy to share with anyone essentially what we are trying to build here and all of the secrets that we have, right? Because what it comes down to is we need to execute better than everyone else, right? And I see that a lot kind of happening in this industry. For example, we are being asked a lot to sign non disclosure agreements, right?

Which is something we are open to do, right? And we also do have a lot of NDAs. I always need to be careful what kind of names I dropped anywhere. But like long story short, we never asked any company for an NDA. Same reason, right? At the end of the day, execution is going to kind of matter and not who knows what about secrets that you have an idea about. Or something like that. So what is good.

Claudio Geyken

Execution for you? Like, what would you say? Like, if you have to, the first things that come to mind where you say, yeah, this is definitely what we believe is good execution that we foster every day in the team.

Jakob Kleihues

Yeah.

Jakob Kleihues

I mean, maybe that sounds a little bit too easy now, but like, what that is is focus, right? So knowing what you want to own in the value chain and then being 10x better than everyone else in owning that and building that. Right. And.

And it sounds easy, but in this industry, like, I mean we are by now, and we'll probably speak about that later on, but like working with, have contracts with slash have onboarded in production, like the vast majority of the industry, right. Especially in Europe. And everyone has problems and we love to hear about them, right.

Because it's really sometimes surprisingly hard to get good quality kind of feedback on what it is that we could solve for them. Right. At the same time, we need to say no to 90, 95% of these requests and ideas that we have to be able to focus on what we actually want to kind of execute on and own. Right. And only if we can actually get this focus in can we actually execute in the next step because then we know kind of what is our mission, right.

And so, yeah, my easy answer would be focus. And maybe what I would add to that is we have an insane team, right? So this is a team that is remote first for the engineering team. And essentially my co founders and me had like five people in mind who we wanted to bring on board when we started dinarpi, like the day after we signed our kind of first running round and knew, okay, we can hire some people.

Explain the EV connectivity problem

Jakob Kleihues

We essentially had five profiles in mind and four of them we onboarded in the meantime. Nice. So for us, it's like the dream team to a certain extent. And I think that also helps to execute, right? Because like, everyone is kind of pushing in the same direction and everyone pushes themselves, but also like has a goal oriented way of working together. Right. Like, so we can also tell each other, okay, this was not good. Right.

And so far, yeah, just have a lot of fun working together. And I think that's the second thing. So focus and having fun to work with great people.

Claudio Geyken

Makes sense now. I can totally relate. And is it before we deep dive into inapi? In a sec. I know you worked for bonnet. How did you get into Bonnet or in the E. Mobility industry? What was the path?

Jakob Kleihues

Yeah, I mean, Bonnet, maybe for some people who are listening to this, this is like they know the Brand Bonnet is a. I really don't want to lie now, but like it's an EMSP that was started, I would think around 2020 or something like that out of Imperial College London by two amazing founders, Patrick and Elliot, who literally out of a university project, kind of started at EMSP because they said, okay, out there, there's no fancy MSPs with a good brand.

Right. And, and I got to know them kind of quite early, I think maybe four, five months into their journey because they applied for funding from the venture capital fund I used to work for and I hopped on a call with them. Essentially we did the deal, quite a small investment and I started working with the team essentially to build the company. And in this time I think we spent quite some time together.

They definitely struggled to raise the next round and so on and we worked a lot to kind of get that done. And then suddenly it's always like a little bit of the catch up effect, right. Like essentially everyone wanted to invest because the company grew quite quickly and they raised money from Lightspeed and Google Ventures to quite well known and renowned kind of investors.

And, and then Patrick and Elliott asked me to come on board full time and that's what I did. I mean, I don't want to get into the details of kind of what happened at Bonnet. The company was a little bit later, like one and a half years later sold to OVO Energy and today the team works as Oval Drive. Amazing team as well. But when the acquisition happened I already knew I would like wouldn't want to work for a big corporation in the uk.

And also I had kind of experienced this kind of connectivity pain that we're trying to solve with INAPI firsthand, both from a commercial but also to a certain extent from a technical point of view. And that's why I dropped out and started in API.

Claudio Geyken

Yeah.

Claudio Geyken

And then maybe let me just explain the. Set some context, set the scene. So that we're on the same ground. So the connectivity problem, as far as I understand, and please elaborate or correct me if I'm missing something that you identify is there are plenty of players around in the industry. We have CPOs, we have MSPs, that's the most important roles, I would say. And underneath the CPOs there's a CPMSS. So that's the software that CPOs use.

And then there were traditionally roaming hubs that were created to connect those different players. I don't know now the exact number that there was and that there is right now in terms of numbers of CPOs and MSPs, but significant, maybe you can update if you have them on top of your mind. And so this connectivity layers from traditional hubs, that's what you identify.

There are quite a lot of issues with it or there are a lot of ways that can be done better. And that's what INAPI essentially is building. Right. And maybe you can elaborate now with a bit more detail.

Jakob Kleihues

Yeah, yeah.

Jakob Kleihues

So maybe, maybe first of all, because I think as an industry we are not doing this often enough to maybe look at this. I think it's best to look at it from a kind of customer point of view. Right. Like also EV driver point of view. The EV driver wants accurate data about the availability of charge points. Right. And then they want to pay the lowest possible price. And that's very much not how EV drivers charging, public EV charging works today.

Claudio Geyken

Yeah.

Claudio Geyken

Yeah.

Jakob Kleihues

And now we can get into. Okay, why is that? Right. And I think then you quite quickly arrive at, okay, there's a lot of different companies in this industry. You already elaborated. There's different roles, right, like CPO, CPMs, EMSP, whatever. Right. There's then also fragmented kind of markets. So there's a lot of different CPOs, also a lot of different kind of strategic interests in the market.

But long story short, these companies need to work together in an efficient way to make this customer experience actually work at scale. And at Bonded, what we learned quite quickly is this is not working at scale, right? So we're very classic EMSP and essentially wanted to connect to all relevant CPOs in Europe. And essentially back then there was 20, 22 summer, there was essentially two ways to connect, right?

Like what I would call legacy roaming hubs. So platforms that were pioneers 15, 14 years ago, right. When they started essentially trying to standardize the communication between different, between CPOs and EMSPs in the market. Right. And when I started in this industry, they already like, they still did like something like 80% of the integrations, but they already only did 20% of the transactions.

Scale OCPI interoperability

Jakob Kleihues

Because the big volume integrations with the, with a lot of transactions, the big EMSP with the big cpo, they already, back then kind of started to go bilateral, build bilateral CPI integrations. And that's essentially the second option, right? So legacy roaming hubs and bilateral CPI integrations. So at Bonded, we in the beginning thought, okay, why not working with the hubs, right? And the alternative, as I said, was bilateral OCPI integration.

So bonded started building a lot of bilateral OCPI integrations. So we had like, I think over 50 OCPI integrations, right? And what I can recall is like on average 10 or something like that of those were always down. And that was not because of Bonnet. They had an amazing team, right? Like the reason was not even technical issues, but more operation issues, right?

Like something doesn't work, some config doesn't work, some tokens weren't synced, something just like some small thing, some small interpretation of the OCPI protocol implementation didn't work. Right. And then you need kind of the other person on the other side of the aisle to kind of debug that. Right?

Claudio Geyken

Let's stop there for a second because I think it might be not so obvious for everyone, like if you are not an deep IT integrations person. So there's two sides to do this integration, obviously. So there's two systems that need to integrate and two software layers that need to integrate. And there's a. Protocol, this ocpi. Then I think there's a couple more that are. But these are the hops that I'm managing the protocols, right. If I'm.

If I'm correct me, then if I'm wrong. But. So the OCBI is, let's say the free independent one. And there it is like in many other protocols. And I think the OCPP faces the same issue where the charger talks to the Charge Point Management system. But this is not really the core focus of this podcast. That's the interpretation of this protocol and the implementation of the protocol. If one stakeholder messes things up, that's when things go sideways.

Am I correct in putting it this way?

Jakob Kleihues

Kind of.

Jakob Kleihues

Exactly.

Jakob Kleihues

So let me. Maybe it's a little bit of a historic kind of breakdown, and I'm definitely going to be in some ways wrong here. I'm in this industry for five years, right? Like, I think since then I understand it quite well. But like back then, I have no idea what happened before that. Right. But long story short, essentially there's these platforms that back then tried to standardized communication, as I said, as pioneers in this industry, right.

And they started essentially defining protocols to standardize it. Right. So Hubjack came up with oicp. Maybe there was something before it, but like, that's what we know. All right. Like G ref came up with eMib, I think eclear came up with OCHP, right. And I think out of the Netherlands mainly.

And I think that because my co founder, Dennis Laumann was one of the original authors of OCPI, essentially there was this willingness, especially among ChatPoint operators, to get independent. Right. And essentially launch a protocol that is independent of these commercial non neutral players. And that's why the EV Roaming foundation was launched in rp, is today part of the EV Roaming Foundation.

So is a lot of other kind of relevant players in this industry. And what the EV Roaming foundation does is it's essentially coming together to define the OCPI standard. The most relevant OCPI versions today are OCPI 2.11 and 2.21. There is the OCPI version 2.30 launched already and implemented by very few players. Happy to speak about that in detail, but essentially OCPI is the answer of a lot of CPOs to get independent of proprietary protocols.

So that's the core open source protocol. And obviously the kind of platforms that I just mentioned, they have adopted OCPI by now. So from our perspective, it very much becomes kind of the standard not only in Germany or Europe, but actually across the world. So I read a statistic recently that more than 95% of the public charge points outside of China actually communicate OCPP data.

And then the vast majority of these charge point could charge points could also kind of use the OCPI protocol. So that is, I think the high level summary of these protocols. Right? And ocpi, to just answer your question, was launched initially with the idea of building bilateral integrations. Now I think in your initial kind of introduction you already said, right, the markets for ChargePoint operators and EMSPs are fragmented, right?

So there's hundreds of players on both of these kind of market sides. And if you would have three players on the CPO side and three on the MSP side, it's quite easy. Everyone connects with each other. And you have nine integrations right? Now if you have like 500 players on the MSP side and 500 players on the CPO side, then there's 250,000 B ledger integrations, right?

And I think there you already kind of start understanding, okay, this is all integrations that need a handshake, they need to be set up, they need to be tested and then they need to be maintained. And now we are talking a lot of different versions of OCPI that are obviously not interoperable with each other, right? So it gets very, very messy very, very quickly. Let me maybe tell to say it like that, right?

So I think what the industry faced to go back to kind of when I entered the industry was essentially I believe connectivity should be a commodity, should be a freely available good, but actually it's a constant pain in the and so on Right. And that's the main reason for us at Bonnet, where we kind of had a hard time delivering on a really good customer experience. And most of the costs kind of coming from that, even indirect costs.

So for example, customer success costs were created because of exactly these connectivity issues. And that's why we said, I said, okay, there needs to be a better way to kind of do that, and started looking into other industries. Right. And yeah, that was summer 22. I reached out to my two co founders and essentially we started thinking about what would a model look like that actually.

Yeah, would bring together the huge advantages of one single integration and at the same time, essentially good data quality and without significant transaction costs. And the answer to that is inapi. But I guess we'll get there now.

Build and grow ENAPI

Claudio Geyken

Yeah, yeah, let's get into this second. But as you mentioned, the co founders, one thing that struck me also, because personally. Speaking, it took me also quite some time to find my co founder and I find especially finding technical co founders, as we are both CEOs, it's very difficult. And you managed, if I remember correctly, you had one person in mind that you really wanted to co found the company with.

And it turns out that this person said yes, which is quite impressive or incredible. How did that maybe story. Can you elaborate on this co founder matching, which is so important as a foundation for the company?

Jakob Kleihues

Yeah.

Jakob Kleihues

So I mean, I had experienced the problem, right. I had negotiated a lot of roaming contracts. I had like kind of tried to escalate a lot of problems with connectivity on the commercial side to a certain extent. Right. But I knew kind of what we wouldn't want to build. But to me, it wasn't super obvious. Kind of if we can even build it like the way that I envisioned kind of in API back then. Right.

So what I did as a very first step is essentially I put together kind of a memo, maybe a little bit old investor kind of mindset, but yeah, kind of a memo on what would this company do. Right. Like five pages or something. I need to search for it again. It's somewhere on my, on my computer. And, and I essentially sent this to I think four or five people, to be honest. All of them, like I just did a cold outreach, right.

I literally looked up in GitHub, okay, who wrote the OCPI protocol. And what you find then is, and I hope I can say these names here, but like, so essentially Olga Vanier, then Patrick Rademakas and Dennis Laumann, always kind of the. Among the three names that kind of the godfathers. I Love that. Actually, that's probably from one of my pitch decks, but the godfathers of ocpi. Exactly.

And I actually spoke to all, wanted to speak to all three of them, spoke to Olga as well. But then, like, Dennis and me met and had a very funny, coincidental kind of second meetup in Aachen at the E Clearing event, or an E Clearing event.

And I can just remember, like, we were already both quite excited about the memo, and we essentially used the two days in Aachen just to kind of lock ourselves in a room and kind of think, okay, how could this be built? Right? And how could we do that? Now, Dennis back then was the managing partner, I think they called him at Ihoma, I think one of the leading tech consultancies in the. In the industry. Built a lot of CPMSs before and so on.

Had a really talented team there as well. And therefore it wasn't easy for him to drop out. Right. Like, for me, it was quite obvious that I want to start this company. So essentially, I think we worked for three, four months quite intensively next to our day jobs. And then we came to a point where I was like, okay, let's try this for three, four months, right? And if we haven't raised until end of Q1 23, then you go back to your job.

And that's how we started. So I think what a lot of investors always say is like, oh, a founding team where the founders don't know each other from a daily work or where they're not friends essentially is risky. Right? And we even had like this one guy who said no in our first round where we had a lot of investors who wanted to invest but said no because of exactly those vibes. Right. Like that we didn't know each other well enough.

And we were considering kind of sending him a Christmas card kind of every year. We work together now because we are so close. So long story short, Dennis is amazing. It's like he's based out of the Netherlands. That's why it was always 100% clear that we would build this remote first. We are trying to hire the commercial team in Berlin, but everything else is kind of remote first.

But no, it's really like on the first days kind of we trust each other, love each other, and yeah, we've experienced a lot together now, so quite excited about it.

Claudio Geyken

Exciting.

Claudio Geyken

Very cool background story as well, I think. Inspiring for founders out there. So you said you created the company more or less than end of 2022 and. Right, yeah,.

Jakob Kleihues

Yeah, yeah, yeah. So we officially incorporated the company, I think January 23rd. And then also we already had signed a term sheet. So essentially the. Yeah. Had talked to investors in. In December 22nd. So yeah, it was, it was super quick. It was literally two weeks after we started fundraising. We had like five term sheets, six term sheets and had to decide and then raised a very first funding round, literally based on a.

On a pitch deck with Project Aventures and Seedcamp from. From. From London. Yeah.

Claudio Geyken

And that was a 2.5 million round. Right. And then. And then it's. January 25th was a 7.5 million round.

Jakob Kleihues

Yeah.

Jakob Kleihues

Yes.

Jakob Kleihues

So I think announced. I think there was more or less discussed in November. December. Exactly. 25. Sorry, no, 2023. Yeah. Am I getting this right now? Yeah, I think so. No, 24. Of course, this was January 24th. Sorry, I was. We were one year too early here the entire time. So January 24th we launched in API and in.

In January 24th we also announced our 2.55 million pre seed round and then announced in January 25th our seed round of seven and a half million that we had closed in December 24th. So essentially 10 months after we raised our first round, we raised an around. Yeah, exactly.

Claudio Geyken

Time flies.

Claudio Geyken

Yeah.

Claudio Geyken

And then I read that you had 600,000 charge points connected by the end of 2025. But then now, by now, I think most recent post was like 850 already something.

Jakob Kleihues

No, you.

Jakob Kleihues

I mean, like, to be honest, no hard feelings because it's moving fast, but like we are now, I think when this is coming out, I can say that already we are now announcing a million charge points connected in production and actually we are already at 1,050,000. So yeah, we're just growing like super fast. We've onboarded more than 450 partners since we started. That's.

I think on average, if you calculate that, like two and a half years, a little bit more since we started onboarding. Yeah, two per week or something like that. A little bit more. And that is literally with one team member who's mainly doing that. Right. Of course others can do it as well, but essentially one person who's kind of more or less full time testing, onboarding and pushing on the technical side. And the rest is widely automated.

So I think that's one of the reasons why we were able to grow so fast. The timing was perfect when we started in rp. Right. It was literally exactly that time where people were fed up with the legacy roaming hubs. They ran into issues with kind of building bilateral integrations and they had an OCPI ready API. So essentially we could connect them right away without kind of any significant friction. Right.

And of course like building 450 handshakes, right. You come across a lot of, I don't want to judge, but maybe a little bit weird interpretations and implementations of ocpi. And that's the big problem about ocpi, that it's essentially implementable in many different ways, let's say like that. Right. And we have built workarounds, so by now we rarely see kind of implementation times of more than a week, two weeks.

Claudio Geyken

Yeah, from a. Maybe, maybe that's a stupid question. But also as I'm not so deep into that, it would be interesting to understand that better. So like fundamentally the API quality of one of the stakeholders can mess things up. So putting yourself somehow in between these stakeholders and ensuring that this connectivity works well still, if one stakeholder messes it up, how do you prevent these mess ups?

Is it because of are you able to identify those quicker, the mess ups or how is your role, so to say, how are you enabling that the mess ups don't occur?

Automate technical onboarding

Jakob Kleihues

Yeah.

Jakob Kleihues

So I think what's the obvious, maybe low hanging fruit value proposition that we have here is you're not doing 450 handshakes anymore, you're doing one right within RP and then you can scale from there essentially without any technical on top work. Right. You just in our portal essentially click I want to send them an offer. Send them an offer. If they accept your PY data as a CPO are pushed to the MSP and you can pull the tokens from nrp.

So super straightforward, super kind of little technical overhead. Right. But to answer your question, I think that's important actually. We play a huge role in harmonizing the OCPI ready APIs of our partners. So OCPI is set up in different modules and not every single one of these modules is necessary to kind of make a connection work. Right. So when we started, a lot of our partners, for example, had not implemented the so called Terrace module yet.

So they essentially had a hard time automatically communicating the terrorists with each other. Right. This creates friction and therefore what we always kind of motivate everyone to do is to actually implement the entire OCPI protocol. Right. Having said that, I think we play a huge role in harmonizing in that sense that a lot of EMSPs tell us that they have significantly better success rates within RP than they have in bilateral CPR integrations.

And I think that's counterintuitive. Right. A lot of People in the industry are like, ah, but I'm adding an additional stakeholder in the chain. Like it's going to create more friction, there's another kind of party or something. But this is just not how in reality it works, right? Like we have a very sophisticated alerting system. More than 90% of our customer success interactions are outbound and not inbound, right?

So we actually are the ones cleaning up the data and helping partners to get on top of their shit, right? And as a next step, we, we therefore see a lot of very successful transactions. So yeah, another issue that you see a lot in bilateral integrations is, for example, sync jobs failing, right?

So some token doesn't arrive at the EMSP, at the CPO and therefore it cannot be authorized the session when the token tries to charge there or some EVSE somehow isn't in the mobile application of an msp. And you wonder why, right? And what we help kind of partners to do is to kind of get visibility into the success of their sync jobs and to get flexibility into how they want to sync, right?

Do they want to push, pull the data, when do they want to do this, what is the cadence and so on, right? All of these things kind of help the entire industry to streamline actually connectivity. And I think why I'm putting so much kind of emphasis on this is Inapi from day one wasn't built to kind of replace the legacy hubs, right? They probably, like we are growing also in part because people are migrating from them.

But our most direct competition is not these legacy hubs. Our most direct competition is bilateral CPI integrations, because that's where the big volumes are. And our ambition is that 100% of the volumes of one specific CPO or MSP are migrated to Inapi. Now, obviously, I know this is going to take time and a lot of trust in the industry, but this is what we're here for, right? And that's how we have built in APPI from day one.

So it's super important for us that, for example, success rates for Napier integrations are higher than in a bilateral setup and that people understand that this is actually kind of the new normal going forward. Right? And what is also super important for us is that we see the first bilateral integrations being migrated to in rp, actually. Right?

So it's one thing to onboard all of the logos, but it's another thing to kind of make them migrate all of the integrations to. And we are, we are getting there right now. Got it.

Claudio Geyken

And one stakeholder or connection type that we haven't talked about that. I think is quite common in the industry is the platform, the platforms, which I think are mostly the backends, the cpmss that are also facilitating integrations. Right,. So how do you look at that stakeholder type and maybe you are even able to say which share of the integrations is done via platforms and which one is done via bilateral roaming hubs and then now inapi.

Map market participants

Jakob Kleihues

Yeah.

Jakob Kleihues

That's a good question, man. No, no,.

Claudio Geyken

If it's difficult, I know sometimes I'm just getting.

Jakob Kleihues

Ahead of myself. What comes into my head when thinking about that is like our pitch deck for the precede round in January 24th, right. That was essentially we did a little bit of a customer segmentation and we essentially set the ChargePoint operator side. So if you want in our model, the supply side that can be separated in three different kind of groups of companies. The first one is strategic multinational players.

Oil and gas companies, utilities, car manufacturers. Right. OEMs, essentially companies that have a strategic interest in this market that have very, very deep pockets and tend to be slightly slow moving, although we love all of them who are working with us. But you know what I mean.

The second bucket is essentially the most capable players probably in the industry today and that is the infrastructure fund backed joint ventures and startups in this industry. Right. They are really good at leveraging their data. They are really interested in optimizing their processes. Good examples for that is the Charging League, for example, right. Fastnet, Atlanta, Ionity, Electra, those kind of players, right. Power Dot maybe? Right.

Like those kind of players come into mind. These players tend to not have the biggest networks, but they have a lot of transactions because it's really high quality networks and because they are scaling really fast. And then the last bucket I think is like the long tail being aggregated through ChargePoint Management Systems. Right, so exactly.

And how that looks like is that these ChargePoint Management Systems act as the kind of contractual partner with emsps. So for us they are the cpo, if you want to think of it like that, right. Because they have the roaming contracts with the MSP and then they essentially invoice the MSPS as well and kind of distribute the money between the CPOs kind of afterwards. Right.

So for us, the stakeholder or the kind of player we are integrated with is the ChargePoint management system and they also have the account within RP if they kind of are the contractual partner for the msp. So we always look for is like we really don't care who you are essentially. Are you the kind of party in the roaming contract. Right. And if you are, you are our customer.

And we love a lot of CPMSs like we have partnerships announced with more or less all of them by now. We are very close with them. I, I don't want to lie, but I think there's no CPMs that, that we don't have any integration with in Europe. Obviously also these CPMSs you can again segment into a little bit kind of older, a little bit slower moving startups and so on. Right.

I don't want to do that now because as I said, we work with all of them but a lot of amazing technology and a lot of amazing companies and people that we're working with there.

Claudio Geyken

Yeah, essentially.

Claudio Geyken

Also, if I understand correctly, when we talk, you integrate between CPOs and MSPs, it's your integrating CPMs implementation of OCPI. Right,.

Jakob Kleihues

Exactly.

Jakob Kleihues

So I mean sometimes the CPOs have their own complex. Right. So there's CPOs who built their own CPMs. There was a little bit of a trend maybe two, three years ago. Right. Like then there's CPOs, sorry, CPMs who are just ChargePoint management systems. So essentially software as a service companies. Right. And they, they don't own the roaming contracts. Never. Right. From our perspective, oftentimes in the interest of the CPO.

Then there are some CPMSs who essentially have a long history in kind of doing the entire financial clearing and the entire kind of heavy lifting for their CPO customers. Right. And all of them have a right to exist. Right. Like so it's really complex. But you're right. After all, obviously we have technical integrations and therefore we connect to ChargePoint management systems.

But as I said, right, like there's very big chargepoint operators who own their, have their own charge for management system. There's very small charge operators who suddenly have their own charge for management system. So this market is just like. Yeah. Have.

Claudio Geyken

All different flavors. And talking about the business model, I think you already hinted to it that connectivity should be free. So I understand this is also a fundamental difference between INAPI or other stakeholders that are trying to do the same thing that INAPI does where connectivity is not for free. I understand. And your business model is entirely now based on the financial clearing.

Jakob Kleihues

Exactly.

Claudio Geyken

Maybe you can also elaborate on this clearing aspect and how you do it better than other stakeholders that are focusing on the clearing aspects.

Jakob Kleihues

So I think I hinted briefly towards that, that from day one and that's also a little bit where I'm always surprised that we haven't really changed our identity and mission since day one, right? But from day one, what our ambition was is that we replaced bilateral direct integrations, direct OCPI integrations, because they didn't work at scale for us at Bonnet. And some people tell us they work, some people are like, okay, they don't work at all.

Develop financial clearing

Jakob Kleihues

But long story short, think if you look at success rates and everything involved, then essentially connectivity should be a commodity, right? And, and it's not a commodity today, right? Because like everyone has like a tech team sitting there controlling data. Everyone builds their own a little bit scrappy kind of validations in house. They need to look at charge detail records.

So it's essentially building relevant transaction data to kind of look at this, right? And all of this doesn't work, right? And we always said, okay, we want to kind of build product for 100% of the volumes of a CPO or EMSP, right? Not for the long tail. And if you say that, then you need to look at, okay, why do they broker 80% of their transactions through bilateral integrations, right? And for us the reason is quite obvious.

It's significant transaction costs, right? If you charge transaction costs for connectivity, then people have an incentive to go bilateral, right? Because even, even if you only charge 5 cents a session, right? At 1 million charging transactions a month, there's quite obvious significant kind of incentive to go bilateral, right?

And, and therefore from our perspective, in a mass market in the future, connectivity there will not, there won't be any connectivity costs. No one who charges for connectivity will be able to win in the future. Right? And I think this was a little bit surprising to the market two and a half years or three years ago when we started, but by now the vast majority of the market agrees with us on that, right?

And then the obvious question is, okay, how do we then do connectivity? Because as, as, as already stated, bilateral integrations don't scale, right? So how do we then do connectivity? And what is the next biggest problem? Right? And I think our answer to that is let us commoditize connectivity, make it a freely available good.

Make sure that everyone who invests even one engineering hour into internal connectivity that they wouldn't need to invest is essentially wasting time and money because they should be investing into something where they can build differentiation, right? It's a commodity, it's free of charge, right? And then let's look at the next biggest problem. And from our perspective, the next biggest problem is financial clearing.

Claudio Geyken

Right.

Jakob Kleihues

CPOs have a very hard time and essentially getting paid and emsps have a very hard time validating charge detail records. So getting relevant transaction data, then approving invoices and paying them in a scalable way. Right? The biggest EMSPs out there, they receive like 450 invoices every month. Right? And actually not every month, but every 2, 4, 6, 8, 12 weeks sometimes with CDRs without CDR, different currencies, different VAT rates, it's messy.

And, and, and this is what we are tackling here. Now why do we have an unfair advantage to solve that? We only have an unfair advantage to solve that if we actually broker the transaction. Right? Because what we can do is we can validate the transaction at a different level than kind of horizontal players who are doing this in many different industries. Code. Right?

Because we can look at the charge detail records that are invoiced and can say hey, there's some CDRs on there where we didn't authorize the session, this didn't happen, the CDR. Or we can say hey, there's some missing CDRs or there's some duplicate CDRs, right, with different CDs. But we know that because we authorized the session. Right? And there's millions of details now what we can validate.

But long story short, only because we broker the transaction can we actually build the best financial clearing product out there. And our strong belief is that the vast majority of the market won't be doing their financial clearing in the future themselves. Right now there's not a standard that people use, it's scrappy in house kind of processes based on CSV files and so on that we are competing against with our financial clearing products.

But in the future this is going to get more complex because we'll have variable pricing, we'll have discounts, we have a lot of kind of things that add complexity to this. And it doesn't make sense that 450 companies in Europe kind of build their own kind of solution in house. And this is where we come in.

Claudio Geyken

So, so.

Claudio Geyken

The clearing is mostly done also. In. House or there are a lot of third parties that are doing it with, let's say legacy tech. That would be the, the.

Jakob Kleihues

I don't want to be so judgy with legacy tech and whatever. But like what I can say is maybe as always, and I think that's a steady thing throughout our talk so far. Obviously there's everything in this industry, people who do it themselves, people who do it with, I don't know, some random companies from outside, people who just don't do it at all and essentially just Pay invoices, however they come and they don't validate anything. Right.

So there's really everything we've come across everything also. But it's definitely a obvious problem that everyone faces. And also everyone kind of, you can talk to every CPO and MSP out there, they'll kind of agree with you that the validation of the billing relevant transaction data, then the approval of the kind of payments and then the payments themselves are supermanual processes.

Apply cloud infrastructure and AI

Claudio Geyken

Yeah, I can confirm as well from conversations I've had. And also you said that an impressive KPI which was 99.998% uptime and under 20 milliseconds latency in 2025, which is quite impressive. It sounds impressive. How are you able to achieve such great KPIs, which I understand. Yeah, that's what we are competing against legacy tech. With such advanced tech, then good arguments to be made to adopt your technology.

Jakob Kleihues

I think what is very much true and an easy argument is an insane, insanely talented team. Right. We are still a very small team and we are very conscious about that. Right. Like we believe if we're an intermediary and we don't want to charge connectivity costs. Right. Like we can build this with a very lightweight team. At the same time we have incredible talent on the team.

The other honest answer is in difference to kind of the legacy hubs that I just kind of spoke about. Right. We didn't start 14 years ago, we started in 2024. And our cloud infrastructure is probably the heart of our product. It's state of the art technology and yeah, that's how we can achieve that. Also one thing that I want to share is we indifference to most of the players out there actually publish our uptime at all times.

So everyone can click on status.inapi.com and we'll see kind of the uptime of our infrastructure both in the US and in Europe. So I think we hold ourselves accountable by making this public as well. And so far this has been working really well. So super happy with the team, but I think there's many reasons for that and there's a lot of work involved to be honest as well.

Claudio Geyken

And also a lot of AI as it's the name of the game, at least it's on my mind every day. And how are you looking at AI as a. Probably a native company somehow?

Jakob Kleihues

Yeah.

Jakob Kleihues

So first of all, yes, right. I think, I mean I would need to look it up again, but I think since January 16th or something like that, I believe that was when the new model of Cloud was launched.

Claudio Geyken

New Fable, you mean?

Jakob Kleihues

Yeah, Fable was more recently. I think that was Opus back then in January 15th of January 2016. I think there was something like that. Anyways. I think more than 94% of our production code was AI written. Obviously it speeded us up like crazy. Right. And definitely this helps, right? What I will also say though is we are not your next kind of AI rocket ship company that just like throws whatever comes their way kind of into a pull request and let's go.

Right. And there's very good reason for that, right. If you essentially want to build trust with big corporations as a company, as a startup, right. The one thing that they will look for is is this product working? Right. And you can just not afford, if you are infrastructure relevant for CPO and MSP and that is direct ROI relevant, right. To be down for, I don't know, 20 minutes or an hour like the Legacy Hub sometimes are. Right.

This is just something we just cannot afford as a startup. Right. And therefore there's parts of our product and our engineers are very aware of that, that we only touch with utmost care. Let's say like that. And where AI is helpful but like obviously not kind of solving. Yeah. Kind of the really good or the really important kind of second and third and fourth look for humans. Right. So that's the one comment.

But yeah, AI definitely a huge topic for us, obviously enabling us. And then maybe last but not least, I think on the commercial side, it's crazy, right? I mean we are today. One of my co founders spends a lot of time in product, but he's also quite involved in kind of with customers. But other than that, it's me and our newly hired director Growth, Dennis Brown. Daniel Brown from chargeburn, former Charge Fund, who. Who are doing our.

Our commercial kind of scaling. So I think yeah, by now we work with the vast majority of the industry, but you know, we haven't run like crazy outbound campaigns and have reached out to them because it just doesn't work. I was more or less alone on the commercial side. Right. And. And AI helps there a lot. Right. So that's another kind of dimension. But with that, whoever never talked to me in the past, please reach out, especially CPOs and MSPs.

Promote industry collaboration

Jakob Kleihues

I think we are sometimes surprised by some of the players, especially in the Spanish region, France, but also in the Nordics who never heard of us, right. And are a little bit like, ah, okay, sounds a little bit like H. We're like, yeah, all right. But like let's talk. Right. So yeah, I think would love to.

Claudio Geyken

Interesting.

Claudio Geyken

Yeah.

Claudio Geyken

And you said in the past that there's a problem in collaboration in the industry, that you feel like we should collaborate more. What did you mean with that?

Jakob Kleihues

I, to be honest, I don't know in what context I said that. To be honest. I'm surprised sometimes how open people are for cooperation but. Or collaboration. But I think there's very little alternatives for us. Right. Like most of the companies are not the Tesla out there who essentially have a full stack kind of solution from hardware to charge operator to CPMs to EMSP to essentially car for plug and charge and so on. Yeah. There's only Tesla essentially.

Right. And other than that, people have to collaborate and cooperate. So I think that's not really an option. So. Yeah, not sure when I said that. But, but I agree. As much collaboration as possible is kind of helpful for the industry, I think.

Claudio Geyken

And then there was a post you made and maybe you can elaborate in your own words. Again, is this size of the pie over slice of the pie, if you remember your blog post.

Jakob Kleihues

Yeah.

Jakob Kleihues

So from our perspective, and to be honest, I can feel that in the vast majority of the conversations I have, if the industry wins, everyone wins. Right. And that is our mindset. We're not trying to kill a competitor.

Claudio Geyken

Diesel is the enemy.

Jakob Kleihues

Yeah, exactly.

Jakob Kleihues

Diesel is the enemy. Right. Like the tanker. But is the enemy in Germany. No, like, you know, like at the end of the day we want to kind of play a role in enabling the green mobility revolution. Right. And we're just not yet there. I mean, 17% growth, right. Like sounds good for old school industry, but what the hell, right? Like we need to, we need to make this kind of transformation work. Right.

And, and I think if the entire industry is focused on that, then we'll just make it work much quicker and everyone will kind of benefit from that. And that is what I want to say with that. Right. We are not optimizing for. Okay, we now want to, I don't know, kill another company or we want to optimize for this percentage or something.

We just want to make sure that we actually solve connectivity for the industry to kind of help it help the industry scale. Right. And I think so far this mindset has helped us quite a lot to kind of do the right things oftentimes.

Claudio Geyken

Makes sense.

Claudio Geyken

And then let's talk pricing, which is a topic that I'm also particularly interested in, in the smart charging space and flexibility space,. Which will come as a last bit, is you, you also wrote about it that there's different levers that can, that CPOs could play. There's the volume incentives or fleet rates, other types of surcharge on traffic routes through aggregators. Maybe you can elaborate what your view is.

What will be the future pricing, which now is, I mean everybody probably knows it's still quite static. It's just depending on speed of charging. If it's DC charger, usually it's higher, but not too many dynamic rates. Where do you see the industry going in? And maybe also then as a. Thinking of, as a segue for flexibility. What would be the ideal pricing, if you have any thoughts on that?

Jakob Kleihues

Yeah, I recently, I recently heard like. Talk of the Fakas Museum, talk about, of the Transportation Ministry or whatever it's called, talk about flexibility. This would be exciting. Imagine, right, and, and I had a little bit this kind of Angela Meake Internet kind of, of remembrance. I don't know if you know what I mean, what this mean, but like essentially for us it's quite obvious, right? Like I read a stat, need to look this up again.

But something like 75 of the battery capacity until 2030 is electric cars driving around, right? How can we actually lift this potential, right. Lift this treasure? And, and I think a lot of very smart people, you included, kind of essentially spent a lot of time on this question. Right, thank you. We are starting, we are starting. And I think that I'm coming back a little bit to this focus point, right.

We could now be thinking a lot about how, how do we implement that, how can we orchestrate that whatever, right? Like this is, this is not how where I'm spending my time right now, right?

Like where we are spending our time is like how can we help companies that we are working with to come to, to run the business model that they want to run because otherwise they again will have an incentive to go bilaterally if they cannot do it for us, if what they want to do, right? And a lot of them want to test out a lot of things. I think this starts with variable prices, right? I mean very easy start would be two different prices a day.

Nighttime pricing. This can be communicated through the terrace module. As I said, the first challenge, right, we need to help. But then obviously what we also see is for example for heavy duty vehicles, quite a lot of discounts because it's quite attractive for CPOs, right? So how do you implement these discounts, right? Because it gets really messy if you like.

What we see in the industry a lot is like chargeable operators just applying 10% discount to the invoice. But then one CDR is kind of challenged and suddenly like the whole thing kind of breaks, obviously. Right. So you want to get this to the OCPI level and to the charge detail record level to be able to really kind of have control. Right. And that's what we're enabling for a lot of companies.

So what we have in place today is what we call discounts can also theoretically add a surplus. But essentially what we do there is we enable CPOs to define a discount for a given partner. Right. Our system then re rates the TEROS module, adds a routing header to the terrace module to the specific partner that they want to give a discount to, and then also re rates the CDRs so that the EMSP receives the correctly rated CDRs from them.

This is a product we natively kind of support today. And it's quite an exciting product potentially. But I think now to go over to your next question, right, this kind of a little bit more fancy thinking. I mean, I always feel like what sounds good is like essentially how do we implement a incentive scheme via price mechanism from energy provider throughout the chain to the EV driver? Right.

With obviously the goal that the EV driver has a kind of incentive reacts to the price signal. And I think this is future music where we are happy to play a role. But like right now of clear focus is on enabling our partners.

Claudio Geyken

But one could say you enable it through better implementation of connectivity of CPOs and implementation of certain modules like the pricing module, in a better way. This also is the foundation at the end of the day for fancier stuff if you want.

Jakob Kleihues

100% Agreed.

Jakob Kleihues

Right.

Jakob Kleihues

Like it's a little bit like if you go for the US for example, and it's super exciting market, a lot of super interesting people who we are working with there right now. Right. Like, but everyone is talking about autonomous driving and we agree obviously. Right. But like our focus mindset is always like, okay, but what about kind of making the charging transaction today work? Right. And, and I think by thinking like that, we actually get to enable that.

So I couldn't agree more.

Claudio Geyken

Yeah.

Claudio Geyken

By the way, I saw your trip to the us which was I think quite recent as well. And you also mentioned autonomous driving being. A big part of the trip as well. So you are active already in the US as a solution right now. And is there any. You also said that there are quite a lot of differences, but for you as a product, would you say is there a big difference now to operate in the US compared to Europe?

Expand internationally

Jakob Kleihues

Yeah.

Jakob Kleihues

Our product is theoretically scalable across the world today. Right. OCPI is a standard. Maybe first like to get it straight, OCPP is a standard, but then OCPI is to a certain extent a standard as well. And we have launched a North American infrastructure and we are actively onboarding partners right now.

It's the early but like we already have signed, I don't want to lie, but I think it's something like 13 contracts now and onboarded like eight partners or something.

We have brought on board a person I always wanted to work with, Daniel Brown, former global head of roaming at ChargePoint and, and he's leading our US efforts as far as the UK efforts and he was recently there, I was there quite a lot because we also raised from the US venture capital fund our seed round, the Voyager. Voyager Ventures, exactly. Probably the leading.

They always don't want me to say transact transatlantic, but the leading climate vc, I think now they don't want to call it climate anymore. Now it's resilient like that. But anyway,.

Claudio Geyken

They also have a community. I think I'm also part of the community in the Voyager. Community.

Jakob Kleihues

They're amazing.

Jakob Kleihues

I don't know about the community, but they're amazing, amazing people who understand electricity and electrons like better than anyone else I met and who are exactly as the other two vcs that are invested in nrp interested in financial return. What I want to say by that is we don't have any strategic investors, right? So there's no one who will tell me, hey, Jakob, can you please build this and that? Because this big company would want that, right?

And that's so important for us to be neutral and be just solely focused on kind of financial return. So they're amazing. But that's why I spend a lot of time in the us. We like it a lot in the us it's different, but I think our product is kind of scalable right away. I think what is the kind of main difference, and that is an interesting one, is we don't want to, we don't want to force anyone. Also not in Europe, right?

Like the very idea of INAPPIA is you own your own contracts and commercials and therefore you have kind of control. Right? But in the US that argument is even more important because no one wants to be forced into roaming or anything like that, Right?

We believe to optimize your utilization, to optimize your unit economics, it's a good idea to work with other partners, but hey, right, like we give you the infrastructure if you want it, but you keep control and that's very important in The US and that's something we learned. So I think going really well. So you're open for.

Claudio Geyken

Business everywhere.

Claudio Geyken

In the world right now. So like.

Jakob Kleihues

You're taking me at a good one because like I speak a lot about focus and like the honest answer is probably yes. And there's a world where we say no to some things that are really out of our scope right now. But I think maybe to take a step back and think about that like is what are our growth patterns? Right? And I think a lot of startups have this city to city, country to country, region to region, currency to currency growth kind of.

That's not how we grow. Right. Like we grow network to network. And if ionity with 24 countries, well, chargepoints in 24 countries tells me, hey Jakob, can you please onboard these five EMSPs in the new country that I'm entering? Obviously I'm doing it right, so, so, so that's, that's the nature. And that also brought us to onboarding partners in the us but also brought us to onboarding partners in Australia, New Zealand and other kind of regions.

Support heavy-duty charging

Jakob Kleihues

So it's a careful or it's a, it's a, it's a, it's a yes. And yeah, let's not, let, let's, let's keep the focus. But yeah, it's a yes.

Claudio Geyken

And yesterday I was at the electric truck conference or one leading topic was the electric trucks at the National Leidstell in Germany. So the Electric Mobility association linked to the government. So electric trucks are quite a hot topic right now. Does it affect your business in some way like booking or. Mcs? Yeah,.

Jakob Kleihues

You're throwing nice. Yeah. So okay, so we have a feature, for example that we call OCPI version interoperability, where we enable different kind of partners to for example be connected to us via 2.21 OCPI 2.21 and then roam with partners who are 21 1. Right. That is quite helpful for some partners who essentially are still stuck with 21 1. For example, now there's a new version of OCPI and I really am not the one OCPI expert.

Like we have probably out of 20 team members. Probably yeah, 11 node better than me, but probably even 15. Anyways. But what I can say is like OCPath 230 essentially has two main features, why people are adopting it from our experience so far, that is on the one hand in the locations module you have some more kind of ability to communicate more sophisticated data.

For example, how big is the charging lot and stuff like that and secondly, the booking module. The booking module is a essentially add on that lets you book a slot in the future. Right. We believe that is highly relevant for logistics companies and especially highly relevant for behind the fence kind of charging situations. But in public charging, this is in part at least.

A lot of people who I discuss about that with tell me that they don't really believe in this at scale because there's potential operational issues that kind of arise. Right. Like, for example, there's another car park there right now. Right. Like, so what do we do? Right. And those kind of things kind of make it quite complex to deliver on a really good customer experience around booking sometimes. We are part of the Eurome Foundation.

We are fans of the new protocol, don't get me wrong. But what I'm saying is like, we don't spend crazy time on booking and for public charging where today still focuses, like, we don't feel like it's like the top of mind right now. Heavy duty vehicles, though, are totally top of mind. Right. And we have onboarded the core players in the field.

I don't want to name the names now, but like both on the MSP and CPO sides, I think we have all of the players connected and we're happy for them to roam for us. Why is it interesting? Because of crazy volumes and because trucks are always driving. Right. And therefore, yeah, also need to charge a lot. So maybe. Last comment on that. When I entered the industry five years ago, right.

Like there was still a lot of kind of players in this industry running around and saying, yeah, hydrogen, like, yeah, for passenger cars, maybe electric is now is going to be the new normal, but hydrogen for trucks is, I'm pretty sure. Right. And Bavaria was kind of funding some hydrogen ideas around mobility with 200 million or whatever. Right.

And it's just like quite funny sometimes to kind of take a step back and look at this again and see how this industry is now so obviously going for electrification as well. Right. And, and, and maybe, yeah.

I mean, for us, that is the reason why it's sometimes frustrating to discuss things like, I don't know, we have these buzzwords in German politics like technologies for technology, and you're just like, yeah, all right, we can keep, keep this open and kind of lose even more ground than we already have because it's so obvious first principles that electric mobility is going to win. Right? Totally.

And again, that's one of the big kind of messages I want to put out there, right. Like size of the pie rather than slice of the pie, please let's all understand there's no alternative and it's also not going to change. Let's, let's go. And there's enough or a lot of people in Germany and Europe who still haven't understood this.

Consider future charging models

Claudio Geyken

Yeah.

Claudio Geyken

And just looking at the future, the last question before we end on a personal note, the bi directional charging, do you see it in public. Charging or only in private charging? And, and do you also, now that you focus clearly on the public charging, do you see a big role for INAPI also in private charging?

Jakob Kleihues

Yes, focus.

Jakob Kleihues

Right.

Jakob Kleihues

I don't think about it too much. No, I do obviously. So we like, I would argue I can just tell you what I hear from our talks with sea levels at more or less all relevant CPOs out there. Right. And I think they are thinking about it quite actively also for public charge points and that's interesting for me to hear because obviously their identity is selling electrons. Right.

And now suddenly they're going into, okay, we're not optimizing utilization, we're actually kind of trading flexibility in the meantime. It's like, okay, there's some kind of end questions there, right. How this is going to be implemented, we don't know but we do believe it's at least something that public CPOs spend time with.

And for your question and I think for a lot of these connectivity topics like we are there kind of preferred partner to talk to. Right. And we are very happy to kind of discuss with them how to implement certain ideas again. And for private charging. Yeah, of course. Right. Like we already have a lot of private charge points connected. We, we know that roaming is obviously a topic for private as well.

And yeah, we believe that we are quite obviously the, the best solution out there for, for connectivity today. And that's both for public and private too. Right. Why am I not talking about it a lot and why am I not reaching out to, I don't know, cpmss who are focused on, on private charge points and behind the fence charge points right now. Focus. I cannot do everything. And I think we want to leverage network effects.

We very clearly see these network effects in public EV charging right now and we want to leverage on that.

Claudio Geyken

All right.

Claudio Geyken

And I don't know if you actually drive an electric vehicle, but yeah, if you had to drive an electric vehicle, any funny or also worse public charging story that you had. Engaged with and one very pleasant one.

Jakob Kleihues

Okay, that's a good question. So first of all, I, I currently don't have a, have a car but like actually I have two electric cars in Berlin available to me. My dad drives the Honda E, my brother drives the Tesla. And I've obviously used both of these cars a lot to test charging transactions. I think the most delightful one, maybe to break it down, is a recent. Yeah, what is it called?

Close with reliability themes

Jakob Kleihues

Like, essentially trip that we did at one of our on sites in Berlin where most. Most of our team members came to Berlin. And our new team member, Daniel Brown essentially did a tour with us through. Through Berlin from ChargePoint to ChargePoint. And obviously our engineers kind of took their computers with them and kind of tracked everything a little bit. And that was fun. That was very nice. Two cars, eight people just enjoying themselves. And then.

Yeah, do I have a bad story? To be honest, I obviously hear about bad stories everywhere, right? Like, I mean, I tell my family or friends of my family or my parents or whatever, right. Like, or investors. I tell them kind of connectivity doesn't really work. And there's like more or less, I would say 90 of the people who I tell. This is like, yeah, that's true. I was on holiday once somewhere and I had an electric car and it was really awful. Right.

And I heard like 20 of these stories more or less in the last two weeks again. So, yeah, I'm looking forward to fixing it, but I don't want to add to more stories.

Claudio Geyken

Well then.

Claudio Geyken

And with that, we end in a good, positive note. You're doing your best to fix it very quickly, I'm sure. Thanks a lot, Dzeco, for your hard work and for being here today.

Jakob Kleihues

Thank you so much. Thanks for the invite.

Claudio Geyken

Three things stay with me from this conversation. First, the price of connectivity. Even a fee of 5 cents per session adds up at 1 million sessions a month. And that gives partners every reason to build their own direct connections instead of Jakob's. Conclusion. No one who charges for connectivity will win in the long run. Second, clearing.

Because in APPI brokers the transaction itself, it can compare invoiced CHARGE detail records with the sessions it actually authorized and find duplicates or missing records. Third, AI, more than 94% of Inapi's production code is now written with AI. Yet the parts that cannot go down are touched only with utmost care. And the uptime is public for anyone to check. Jakob's word for all of it is focus. Thank you for listening to Smart Charge.

If this episode was useful, share with someone who works on charging infrastructure or give us five star. See you next time. Sa.

S2 Ep. 10 · Jakob Kleihues

0:00 / 1:17:22