EREBORARental sales + operationsLive production system
Congratulations—you just gave yourself five more jobs.
That is what a new rental meant for me: sell the customer, find the bike, create the booking, brief the staff and remember the follow-up. I built EREBORA because I was sick of doing all that bullshit. In one production conversation, a nine-day automatic-scooter request produced the business’s XMAX recommendation and the price stored for that turn. In another, an unusual Nusa request reached the manager group. After a booking is submitted, staff control the rental in the Hub.
Product screens
The customer and staff software behind a live rental business.
Signed terms, condition photos, receipts and returns can stay with the rental record instead of being split across separate chats.
EREBORA
Customers browse the same bikes and prices staff control in the Hub. 
The selected bike and dates stay visible as the customer continues toward the booking screen. 
The private hub runs customers, money, pricing, leads, GPS, maintenance, and repairs. 
Bookings, WhatsApp, contracts, and active rentals stay in the same hub. 
The rental record keeps each operating stage in one place. 
Choose the dates and pickup time.
Problem
Customers ask questions and change plans in WhatsApp. Staff still need the right bike, price, dates, documents and pickup details. Copying that information between chats and tools creates mistakes.
What I built
I built the public catalog, website and WhatsApp sales flow, booking screens, and private Hub around the same bike, pricing, customer, and rental data.
What this means for your project
If your business lives across messages, spreadsheets, paper, and people’s heads, I can turn it into one operating system.
My role
I designed and built the customer screens, business rules, database, private Hub, integrations, controls, tests, and production deployment.
Related services