Plug Inn: The Original Peer-to-Peer Charging Platform

Read the campaign story

Renault announced the original Plug Inn application on 13 March 2023. It connected electric-vehicle drivers with owners of private charging points, allowing users to locate and reserve available access. The launch invited owners to join the community and described the service as a complement to public charging. Publicis Conseil and Publicis Sapient are credited in the agency’s contemporary account. The idea was both a digital product and a message about expanding practical access.

The historical boundary is essential. When reviewed, the original service website stated that the application was no longer available and directed visitors towards Plug Inn fast charge. The reused name does not mean the peer-to-peer model remains operational. This case therefore analyses the original 2023 proposition without recommending it to drivers today or treating later charging services as evidence of the original app’s sustained adoption.

Editorial interpretation: an apparent infrastructure shortage may partly be a coordination problem. Capacity exists, but the person needing it cannot discover, trust or book it. A platform can make that hidden supply useful only if availability and conditions are reliable. A map filled with theoretical locations may look persuasive in an advertisement while offering little practical value to someone who needs a confirmed stop at a particular time.

Editorial interpretation: the two sides have different reasons to hesitate. Drivers need compatibility, access and confidence that plans will hold. Hosts need clarity about visitors, payment, responsibilities and disruption. Recruitment must therefore explain a reciprocal exchange rather than merely celebrate community. The campaign’s promise is fulfilled in the smallest transaction: one person arrives, obtains the agreed service and leaves without unresolved friction. Network scale is meaningful only after that interaction works.

Validate availability rather than counting assets

Before promoting a shared-capacity idea, distinguish ownership, willingness to participate and actual bookable availability. Interview both sides about timing, reliability and fallback needs. A large addressable supply figure can hide a very small useful network. Start with a dense, bounded area where failed matches can be investigated. Measure successful transactions before using aggregate asset counts as evidence that the access problem has been solved.

Design the agreement between participants

Explain eligibility, access, payment, cancellations and responsibility in ordinary language. Consider privacy and safety before making private locations discoverable. A platform should not rely on goodwill to resolve predictable disagreements. Establish support and a fair process for failures. For an electrical or transport service, qualified technical and legal review is necessary; a marketing team should not improvise operating rules merely to launch a compelling community story quickly.

Keep service history visible

When a platform changes or closes, update educational and promotional material so people are not sent to an unavailable service. Separate the original concept from subsequent products sharing its name. Analyse discontinuation as a boundary of the evidence rather than assuming either failure or success without operational data. A creative idea can remain instructive even when the service is no longer offered, provided the case does not confuse a past proposition with current utility.

A small test for another brief

Pilot sharing of a low-risk resource, such as bookable meeting space within a trusted organisation, before considering a public marketplace.

Compare successful access and administrative effort with the existing informal process. Count active usable capacity, not every listed resource.

Stop if availability cannot be trusted, private-location exposure is inappropriate or responsibilities remain unclear.

• Confirm real available hours and interview both resource owners and prospective users.
• Publish access rules, a booking confirmation process and an accountable support contact.
• Track completed bookings, cancellations and unresolved problems before adding more supply.