Gurugram home-services startup, 40 staff, seed-funded, bookings via WhatsApp and a Google Form, Razorpay payment links, Google Sheets for scheduling
Weeks 1–2DiscoveryMap the booking journey, interview 8 customers and 5 technicians, list integrations: Razorpay, Google Maps, WhatsApp BSPScope signed: customer app, technician app, admin panel; Flutter for both platforms
Weeks 2–5UX and UI designFigma prototype of booking, slot choice, payment and tracking, tested with 5 users on budget Android phonesApproved screens and component library
Weeks 3–9Backend and adminAPIs for slots, pricing and technician assignment; ops admin panel; Razorpay UPI and cards with verified webhooksStaging API and admin panel used by ops
Weeks 5–11App buildTwo-week sprints on both Flutter apps, push via Firebase Cloud Messaging, analytics event plan implementedTestFlight and Play internal builds every sprint
Weeks 10–13QA and closed testTesting on a 3 GB RAM Android phone and iPhones, Play closed test with the Play Console pre-launch report, refund edge cases, OWASP MASVS checksRelease candidate with crash data from Crashlytics
Weeks 13–14Store launchStore listings, Play Data safety form, Apple privacy labels, phased rollout; most common delay: a reviewer demo login that has expired or needs an OTPBoth apps live on App Store and Google Play
Weeks 15–20Stabilise and growFix top crashes, add rebooking nudges, move WhatsApp customers into the app with deep linksPrioritised backlog for next quarter
Where it starts1,800 bookings/month, 70% arriving as WhatsApp chats, 12% cancellations, no customer app, technicians coordinated by phone
Where it endsCustomer app, technician app and admin panel in the client's own accounts. Weekly watch: share of bookings via app, crash-free users, repeat booking rate.