ROADMAP · CHAPTER 02 OF 08
We don't make up progress here. We show you what's done, what we're working on, and what's coming. Every milestone is documented on video and every decision is explained to the community.
The project in numbers
01
Chapters closed
08
Chapters planned
13%
Of development completed
0
Speculations
These metrics reflect the project's actual progress. If a milestone isn't validated on the street, we don't move on to the next phase.
Detailed timeline
Every chapter is a real milestone, not a promise. Some are done. Others in progress. Others are coming. But none are skipped.
01
DONE
DONE
October 2025 — April 2026
The idea goes public
The channel's first videos explaining the core idea, why we started, what the vision is, and what problems we want to solve. Nothing technical yet, just the initial spark.
What we learned
The proposal resonates. People want a different alternative, but logical doubts also come up: "how is this going to work?", "does this already exist?". We started structuring the answers.
02
IN PROGRESS
IN PROGRESS
August 2026 — Present
Website and community
This very page, a space to dig deeper into the idea, show real progress, and bring more people on board. The website is part of the product — if we can't achieve clarity here, we won't achieve it anywhere.
What we're discovering
Building this site forced us to ground everything, the purpose, the model, and the structure of the app. What used to be just an idea in our heads is now a documented plan.
03
IN PROGRESS
IN PROGRESS
August 2026 — December 2026
Research and scouting
Getting out on the streets to explore possible routes. Talking face to face with neighbors, shopkeepers, and drivers to validate where real demand exists and at what times the service is needed.
What we expect to discover
Decisions are made with real data, not assumptions. We need to know how many people travel on each stretch, what they prioritize, and what problems they face today in order to design a service that meets their needs.
04
NEXT
NEXT
2027
MVP and field testing
An initial version of the app before we have the full-size vehicle. It will allow sign-ups, simulated bookings, and a closed technical test on the street (using personal vehicles) to validate the technology and the offline QR before physical operation begins.
Why this order
Developing the app before having the vehicle might seem backwards, but it makes sense — it lets us gauge real interest, organize the passenger community, and have the foundation ready for when it starts rolling.
05
NEXT
NEXT
To be defined
From technology to the street
Getting the first vehicle, permits, and insurance. Before the official debut, we run a technical beta test on the move with selected passengers to calibrate the apps, and close the chapter by filming the first real run.
The real challenge
This is where the model gets validated in practice — seeing if operating costs add up, if the experience delivers on its promise, and if people choose to ride again.
06
NEXT
NEXT
To be defined
Pilot test in the city
Regular operation on a limited route. Keeping the same route and the same schedule every day to measure occupancy, costs, and satisfaction, quickly fixing what doesn't work.
The before and after
This chapter is the turning point — the decisive step to establish the operation as a real, ongoing transportation service.
07
NEXT
NEXT
To be defined
Sponsors on board
Bringing in brands that fund lower fares in exchange for visibility, advertising on the vehicle, internal screens, and presence in the YouTube videos.
Why Chapter 06 comes first
No sponsor joins a project that's just getting started. We first need to prove the pilot operation works consistently on the street.
08
IN THE FUTURE
IN THE FUTURE
Long term
From one bus to a fleet
If the previous seven chapters validate successfully, scaling begins: adding more vehicles, opening new routes, introducing community benefits, and expanding the model.
The final goal
This is where the project reaches its true economic and social purpose. But to get there solidly, every previous step must be validated first.
The next step
The focus is on two fronts at the same time: consolidating our website and advancing route research on the ground.
Close Ch. 02
Website 100% complete, key sections operational, and the community communication channel active.
Advance Ch. 03
Complete the scouting routes, evaluate the first 3 candidate routes, and connect with the first local partners.
Prepare Ch. 04
Finalize the app's interface design and get the technical architecture ready to start code development.
How we build
01
Move forward through validation
Every phase depends on validating the previous one on the street. If something doesn't work, we stop and adjust before moving on. We'd rather have a project that learns than one that just promises.
02
Absolute transparency
Every decision, every mistake, and every change of course is shared openly on the channel. The community knows what's happening in real time, with no filters or surprises.
03
Zero overpromising
If we're not sure about something, we say so. The model has to be economically sustainable to last over time — the roadmap is ambitious, but the language is honest.
Every new chapter premieres first on YouTube. If you want to follow the project's day-to-day in real time, subscribe to the channel.
