Fourteen days, clearly divided
Two weeks is only realistic because the split is unambiguous. Here is exactly what we do, exactly what we need from you, and what happens on each of those days.
Fourteen days from order to first booking
The platform is already built and already proven. You are configuring it for your market, not commissioning it from scratch — which is why this takes weeks instead of quarters.
Days 1–2
Kick-off and configuration
We walk through your market, vehicle categories, fare structure and commission model on one call, then configure your platform against it. You send us your logo, colours and app names.
- Your app name, logo and colours
- Your domain
- Your fare and commission model
- Your service area
Days 3–7
Your apps are built and branded
Rider and driver apps are compiled with your identity, your splash screens and your store listings. Payment gateways for your country are connected and tested end to end.
- App Store & Play Console accounts
- Your VPS or cloud server
- Payment gateway credentials
- Maps, SMS and SMTP keys
Days 8–11
Store submission and testing
We submit to Apple and Google under your developer accounts, and you run real test trips on staging — booking, matching, payment, payout and cancellation.
- Review and sign off on test trips
Days 12–14
Driver onboarding and go live
Your drivers are onboarded, documents verified and your office staff trained on the admin panel. Then you switch on and take your first real booking — with our team watching the first week with you.
- Your first drivers
- Your launch marketing
What we bring, what you bring
Delays almost always come from one side of this list, so it is worth reading before you start rather than after.
Omei brings
- Your server provisioned, hardened and deployed
- Your rider and driver apps, branded and compiled
- Store submission under your developer accounts
- Payment, maps, SMS and SMTP providers connected and tested
- Your domain wired to the web app, admin panel and outgoing mail
- Configuration of fares, commission, zones and vehicle types
- Admin panel training for your team
- First-week launch support alongside your ops
- Ongoing maintenance and platform updates
- Custom features and bespoke builds when you need them
You bring
- Your brand: app name, logo and colours
- Your domain name
- Apple Developer and Google Play Console accounts
- A VPS or cloud server in your own hosting account
- Maps API key — Google Maps, Mapbox or HERE
- SMS gateway credentials — Twilio or your local provider
- SMTP credentials for transactional email
- Payment gateway merchant account for your market
- Your fare structure and commission model
- Your first drivers and their documents
- Business licensing required in your city
We will walk you through opening the developer and gateway accounts if you have not done it before — but they must be in your company name, because that is the whole point.
The part most vendors stop talking about
A launch is easy to sell and hard to sustain. Every plan, including Starter, includes maintenance, platform updates and support for as long as you are with us — because software that ships and then rots is worse than no software.
Two weeks from a signed order to your apps submitted and your first drivers onboarded, provided you supply your brand assets, developer accounts and payment gateway credentials in the first few days. Apple and Google review times are outside our control, which is the one variable we cannot compress.
Yours. The apps go into your Apple Developer and Google Play Console accounts, under your company name. Your riders and drivers never see the word Omei anywhere in the product.
You take it. Riders, drivers, trips and transactions are exported to you in a standard format on request, and the accounts you own — stores, gateways, API keys — were always in your name, so they simply stay with you.
Configuration — vehicle categories, fare rules, commission, zones, languages, currencies and payment gateways — is included in every plan. Anything beyond configuration is a Custom build: a module we have not written, an integration with a system you already run, or a whole separate app from your own idea. We scope it, quote it per project, and what we build for you is yours.
No. The admin panel is built for operations people, not engineers. Most of our operators run day to day with an operations person and a manager, and come to us for anything platform-level.
Start the clock
Day one can be this week
Book the demo, agree the scope, and the fourteen days start the moment you sign.