BookMyAuto Proposal
Development Proposal & Quotation

Auto-Rickshaw Ride Booking Platform

An on-demand ride-booking platform for auto-rickshaws — real-time booking, live tracking and in-app payments — delivered as native-quality iOS & Android apps for riders and drivers, an admin panel, and a public website.

Prepared for Deepak Petkar · Mob. 9503558111 Prepared by Silverstone Labs · silverstonelabs.in Date 24 September 2026 Quote Ref Q-2026-0924-BMA Valid until 9 October 2026 (15 days)
01 — Overview

Executive summary

Riders book an auto in seconds, see the fare upfront and track the driver live. Drivers receive trip requests, navigate and manage earnings. The business runs everything — KYC, fares, zones, payouts and support — from an admin panel. One product, four surfaces: rider app, driver app, admin panel and a public website, all on one real-time backend.

4
Surfaces — Rider app, Driver app, Admin, Website
2
Platforms — iOS & Android from one Flutter codebase
16wks
Delivery timeline
₹6,00,000
Total project investment
02 — Deliverables

Scope & modules

Feature scope covered under this quotation (see Quotation for the fixed price).

📱

Rider app

  • Mobile OTP login and profile
  • Pick-up & drop selection on map, saved places
  • Upfront fare estimate before booking
  • Nearby autos and real-time driver tracking
  • Payments — cash, UPI, cards and wallet
  • Trip sharing, masked calling, SOS & emergency contact
  • Ride history, invoices, ratings & feedback
  • Promo codes, referrals, push notifications
  • English + Hindi/Marathi (multi-language ready)
🛺

Driver app

  • Registration & KYC upload — licence, RC, permit, Aadhaar, photo
  • Online / offline toggle
  • Incoming request with sound alert, accept / reject
  • Navigation hand-off to Google Maps
  • Trip flow — arrived, OTP start, end trip
  • Background live-location tracking
  • Earnings dashboard, wallet, commission ledger & payout requests
  • Ride history, ratings & support
🛠️

Admin panel

  • Dashboard — live rides, revenue, active drivers, KPIs
  • Live map of drivers and ongoing trips
  • Rider & driver management, block / unblock
  • Driver KYC verification and approval workflow
  • Fare configuration — base, per-km, waiting, night, surge
  • Zone / city management, manual ride assignment
  • Commission & payout management
  • Coupons, banners, push / SMS campaigns
  • Complaints & SOS handling, reports with CSV export
  • Role-based access — super admin, support, finance
🌐

Website

  • Home, How it works, Fare info, About & Contact
  • "Drive with us" driver lead form
  • App download links for Play Store & App Store
  • Blog / announcements, policy pages
  • SEO, sitemap, analytics, responsive design
⚙️

Backend & platform

  • REST APIs and WebSocket real-time channel
  • Geo-spatial nearest-driver dispatch with timeout & re-dispatch
  • Fare engine and ride state machine
  • Payment gateway, wallet ledger, webhooks
  • OTP, push, SMS and email services
  • JWT auth, rate limiting, audit logs, API docs
03 — Delivery plan

Roadmap

A 16-week build in 2-week sprints with a demo at the end of each sprint. Modules run in parallel so the first end-to-end ride is working by around week 9.

Discovery, requirements & architecture

Wk 1–2

Product backlog, PRD, user flows, database and API design, staging environment and CI/CD set-up.

UI/UX design

Wk 1–3

Wireframes, design system and about 60 high-fidelity screens across rider, driver, admin and website, with a clickable prototype.

Core foundation

Wk 3–6

OTP auth, profiles, driver KYC upload, maps & location, fare engine, zone set-up, admin base with driver approval.

Ride engine

Wk 6–10

Booking flow, driver matching & dispatch, WebSocket live tracking, OTP trip lifecycle, cancellations, ratings. Beta build around week 9.

Payments, wallet & admin suite

Wk 9–12

Razorpay, wallet and commission ledger, payouts, promo codes, SOS, reports, campaigns, roles & permissions.

Website

Wk 8–12

Marketing pages, driver lead form, blog, SEO and analytics.

QA & UAT

Wk 12–14

Functional, regression and device testing on Android/iOS, load test at 1,000 concurrent users, security checks, client UAT.

Launch & store release

Wk 15

Production set-up, App Store & Play Store submission and review handling, domain, SSL and monitoring.

Stabilise & handover

Wk 16

Post-launch monitoring, hotfixes, admin training, documentation, source code and credentials handover.

Apple review times and third-party approvals (Razorpay KYC, SMS DLT registration) sit outside the build timeline; we start them in week 1 to avoid delays. A 30-day post-launch support window follows week 16.

04 — Technology

Tech stack

One Flutter codebase for both mobile apps and the admin panel, on a modular real-time backend with geo-spatial matching.

Mobile apps

Flutter + DartRiverpod / BLoCGoRouterFirebase Cloud Messaging

Maps & location

Google Maps SDKPlaces & Directions APIGeolocatorBackground location service

Backend & real-time

Node.js + NestJSREST + WebSocketsSocket.IOBullMQ (job queues)

Data & storage

PostgreSQL + PostGISRedisAWS S3 + CloudFront

Payments & messaging

RazorpayWallet ledgerMSG91 (OTP / SMS)SendGrid / SES

Admin & website

Flutter Web (admin)Next.js (website)Tailwind CSSHeadless CMS

Cloud & DevOps

AWS ECS / RDSDockerGitHub Actions CI/CDNginx

QA & monitoring

JestPatrol (Flutter E2E)Firebase CrashlyticsSentry + CloudWatch
05 — Investment

Quotation

Fixed-price quotation for the full scope outlined in this proposal.

ComponentAmount
Rider app — Flutter (Android + iOS), store release₹1,50,000
Driver app — Flutter (Android + iOS), store release₹1,50,000
Backend & APIs — ride engine, payments, notifications₹1,20,000
Admin panel & website₹70,000
UI/UX design₹50,000
QA, DevOps & launch₹60,000
Total (excluding GST)₹6,00,000

Figures in INR, exclusive of GST (18% = ₹1,08,000; ₹7,08,000 including GST). Two separate Flutter apps — Rider and Driver — share one backend and one codebase foundation. Third-party usage costs are billed separately — see Assumptions & exclusions.

06 — Terms

Payment milestones

Payment schedule against the total quoted fee of ₹6,00,000.

MilestoneShareAmountTrigger
Project kickoff50%₹3,00,000On signing & purchase order
Core build — alpha20%₹1,20,000Ride booking engine, backend and mobile alpha functional end-to-end
UAT / beta release20%₹1,20,000Feature-complete build passes client UAT
Go-live & handover10%₹60,000Production launch, source code & documentation handover
Total100%₹6,00,000
07 — Fine print

Assumptions & exclusions

Included

  • Full scope as described in this proposal
  • Launch in one city, single vehicle type (auto-rickshaw), INR
  • Two revision rounds per design stage
  • Infrastructure for ~1,000 concurrent users and ~500 active drivers
  • 30-day post-launch support, 48-hour response on critical issues
  • Full source-code ownership, documentation & handover

Excluded / pass-through

  • Apple Developer ($99/yr) & Google Play ($25 one-time) accounts
  • Hosting and usage bills — AWS (~₹8–15k/month), Google Maps, Razorpay (~2%), SMS (~₹0.15–0.25 each), domain
  • Scheduled / outstation rides, extra vehicle types, fleet-owner dashboard, driver subscriptions, web booking
  • Bidding / fare negotiation, AI surge pricing, live human chat
  • Legal & compliance — aggregator licence, insurance, policy drafting
  • Marketing, ASO and driver acquisition

Client provides feedback within 2 working days per review, brand assets, website content and the business documents needed for store and payment accounts. Scope changes after design sign-off are handled as change requests. Optional annual maintenance: ₹8,000–₹12,000/month.

08 — Getting started

Next steps

01

Review & align scope

Walk through this proposal together and confirm the scope.

02

Sign & kick off

Countersign the proposal and clear the kickoff milestone.

03

Sprint zero

Kickoff workshop, environment setup, backlog grooming.

04

Development begins

Sprint cadence starts per the roadmap above.