Launching your own sharing project step by step
From the first enquiry to the public launch: six steps, what happens in each and where projects actually stall.
Between "we are considering offering carsharing" and the first vehicle a customer unlocks themselves lie six steps. None of them takes months – but each has a purpose. This article describes what happens in each phase and what you contribute.
1. Enquiry
It starts with a conversation. We want to know what you have in mind: how many vehicles, at which locations, for which audience? Do the vehicles already exist or will they be purchased? Is telematics installed?
From that it usually becomes clear whether station based or zone based makes more sense and which hardware fits. If we see that a plan will not work as intended, we say so at this point – before costs arise.
2. Demo
We show you the software applied to your case, not to a generic example. You see the mobile app from the perspective of your future users, the scheduler view and the admin dashboard.
Bring the people who will actually work with it. In our experience that is where the questions that really matter come from – how a booking is cancelled, or what happens when someone returns a vehicle late.
3. Setup and configuration
Now the standard software becomes your system. Among the things set up:
- Your appearance: logo, colours, wording, optionally your own apps in the stores
- Vehicles, locations and zones
- Rates, user groups and booking rules
- The onboarding process: which documents are required and who approves
- Integrations: telematics, payment provider, accounting
What we need from you is manageable, but it requires decisions: prices, terms of use and who holds which rights in daily operation. In our experience this is where projects stall – not on the technology.
4. Internal test phase
Before anyone from outside gets access, your own team tests. Everyone creates an account, books, unlocks, drives and returns. That surfaces the things you overlook while configuring: unclear wording in the app, too little buffer between two bookings, a vehicle linked to the wrong location.
This phase is short but should not be skipped. Mistakes found here cost nothing. The same mistakes after launch cost trust.
5. Extended test with a small group
Then the first real users join – ten to thirty people who fit the project: employees, association members, neighbours. They go through registration without assistance and use the vehicles in everyday life.
This shows whether the explanations are understandable and whether the process works for people who do not know how the system is built. Collect the feedback in a structured way – usually two or three points come up repeatedly, and exactly those are worth fixing before launch.
6. Launch
Now the service goes public. A launch campaign helps – free trips in the first weeks or an opening voucher code. What matters is that the vehicles move from day one: a sharing service that looks empty does not get tried.
It does not end there. We go through the first reports with you: which locations work, which vehicles sit idle, where registrations break off. From that the next steps follow – usually fine tuning of rates and locations.
How long it takes
A manageable project with a few vehicles at one location is ready within a few weeks, provided the vehicles are there and the hardware is installed. It usually takes longer for three reasons: the vehicles have not been procured, the telematics is not yet fitted, or internal decisions on pricing and terms are pending.
The part we control – setup, integration, training – is rarely the bottleneck.
More articles
The work between two bookings
Between two bookings sits the work that decides availability. How Lanterne turns it into tasks – and where the limits are.
Learn more →I LOCK IT: how a bicycle becomes a sharing bike
A bicycle has no electrical system to power a telematics unit. So the technology sits in the lock. What I LOCK IT does, when tracking is needed and what to settle before you start.
Learn more →Analysing driving behaviour: a look at INVERS Driving Analysis
Speed, harsh braking, hard cornering: what the INVERS analysis measures, what operators do with it – and what data protection requires.
Learn more →