<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nakshata Patel on Medium]]></title>
        <description><![CDATA[Stories by Nakshata Patel on Medium]]></description>
        <link>https://medium.com/@nakshata?source=rss-55811f24adae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7oJgLDk3KNr9McKiOeqtcQ.jpeg</url>
            <title>Stories by Nakshata Patel on Medium</title>
            <link>https://medium.com/@nakshata?source=rss-55811f24adae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 08:58:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nakshata/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Product Case Study | Rapido Commute | Solving Peak-Hour Reliability]]></title>
            <link>https://nakshata.medium.com/product-case-study-rapido-commute-solving-peak-hour-reliability-6a3394afc0bd?source=rss-55811f24adae------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a3394afc0bd</guid>
            <category><![CDATA[rapido-bike-taxi]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-case-study]]></category>
            <category><![CDATA[bike-taxi-app]]></category>
            <category><![CDATA[uber]]></category>
            <dc:creator><![CDATA[Nakshata Patel]]></dc:creator>
            <pubDate>Tue, 16 Sep 2025 20:10:30 GMT</pubDate>
            <atom:updated>2025-09-16T20:15:41.137Z</atom:updated>
            <content:encoded><![CDATA[<h3>Problem Deep Dive</h3><p>During peak commuting hours, riders in high-demand corridors like Sarjapur Road (Bengaluru) face <strong>frequent cancellations, unpredictable fares, and long wait times.</strong> This erodes trust in Rapido and drives churn.</p><p>To validate the problem, I analyzed Play Store reviews and extracted key themes:</p><ul><li><strong>Wait Times and High Cancellation: </strong>Users report waiting 30–60 minutes, with captains often canceling after initially accepting. App ETAs show 5 minutes but actual waits stretch much longer, making commuters late for work.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*95YHOff0vUgykjBwsi83Iw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/1*XFFMynAGmfoqZlWd-DaShQ.png" /></figure><ul><li><strong>Pricing &amp; Trust Issues: </strong>Many captains demand ₹10–₹20 extra to accept rides, creating hidden costs and frustrating users who chose Rapido for affordability.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PDJwrJcEw8WWKbYHVRXysA.png" /></figure><p>👉 Core insight: Rapido is affordable but not reliable during peak traffic hours — reliability is the <em>real problem</em>.</p><p><strong>Indicative Baseline Metrics (from public reviews + assumptions):</strong></p><ul><li>Peak-hour cancellation rate: ~20–25%* (vs &lt;10% off-peak).</li><li>Avg. ETA shown: 5–6 min; actual wait: 12–15 min+.</li><li>Daily commuter churn: ~10–12% per month.</li></ul><p><em>*All numbers in the case study illustrative and assumed, not official, but they help frame measurable targets.</em></p><h3>User Persona &amp; JTBD</h3><p>This problem disproportionately affects <strong>daily commuters</strong> — Rapido’s highest-frequency segment.</p><p><strong>Persona Snapshot:</strong></p><ul><li>Age: 25–40 years</li><li>Working professionals commuting 6–15 km daily</li><li>Income: ₹6–15 LPA</li><li>Location: Bangalore (Sarjapur, Whitefield, Bellandur)</li></ul><p><strong>Job-to-be-Done (JTBD):</strong><br> <em>“Get me to office reliably every morning without stress, cancellations, or price surprises.”</em></p><h3>Solution — Rapido Commute Subscription</h3><p>A subscription product designed for daily commuters.<br><strong>Core Promise:</strong> Reliable, predictable, and stress-free office commute — <em>at the same price they already pay</em>, but with reliability built in.</p><p><strong>Features:</strong></p><ul><li><strong>Pre-Scheduled Rides:</strong> Users can lock morning and evening rides in advance.</li><li><strong>Priority Matching: </strong>Subscribers get access to a dedicated pool of “Prime Captains.”</li><li><strong>Predictable Pricing (Tiered by Distance):</strong> Subscription mirrors real spend, not discounts.</li></ul><blockquote>For example:<br>6–8 km commute → ₹1,800/month (20 rides at ~₹90 each).<br>8–12 km commute → ₹2,400/month.<br>12–15 km commute → ₹3,000/month.</blockquote><ul><li><strong>Captain Incentives:</strong> Higher guaranteed payouts to ensure captains honor subscriptions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i8KAYhymj_EviaYpeRlapQ.png" /></figure><blockquote>While Rapido operates bikes, autos, and cabs, this case study focuses on bikes in Bengaluru. Bikes are the most common choice for shorter office commutes in corridors like Sarjapur–ORR. The subscription model could later extend to Autos and Cabs with mode-specific tweaks.</blockquote><h3>Value Proposition</h3><p><strong>For Riders (Reliability, <em>not Discount</em>):</strong></p><ul><li><strong>Peace of Mind:</strong> Same spend (~₹90/day), but with guaranteed captain assignment and punctuality.</li><li><strong>No Surprises:</strong> No hidden extra charges or surge premiums.</li><li><strong>Convenience:</strong> Pre-scheduled rides mean no scrambling on the app every morning.</li></ul><p><strong>For Captains (based on Bengaluru Zero-Commission Model):</strong></p><blockquote><strong>Baseline Earnings:<br></strong>A 6–7 km ride nets ~₹87–88 today (₹90 fare — ~₹2–3 access fee).<br>A 12–15 km ride nets ~₹117–147.</blockquote><blockquote><strong>With Subscription:<br></strong>Payout per ride is similar (~₹87–90 for 6–7 km) — but demand is <em>guaranteed</em> and pre-scheduled.</blockquote><blockquote>Fewer “hunt rides” = less idle time and lower fuel waste.</blockquote><ul><li><strong>Predictability:</strong> Even 2–3 subscribers can lock a captain ~₹4,500–6,000/month, reducing dependence on ad-hoc demand.</li><li><strong>Bonuses for Reliability:</strong> Complete ≥95% of assigned subscription rides → extra monthly bonus.</li><li><strong>Mitigation for Long Commutes:</strong> Tiered pricing ensures captains on longer trips are not underpaid relative to baseline fares.</li></ul><p><strong>For Rapido:</strong></p><ul><li><strong>Retention:</strong> Commuters who subscribe are highly unlikely to churn.</li><li><strong>Revenue Consistency:</strong> Monthly recurring revenue (MRR) instead of pure transactional volatility.</li><li><strong>Differentiation:</strong> Ola/Uber passes focused on discounts; Rapido Commute focuses on reliability, making it a stickier moat.</li></ul><h3>Pilot Hypothesis</h3><ul><li>Reduce commuter churn by <strong>15–20%</strong> in pilot corridors.</li><li>Raise ride completion to <strong>≥95%</strong> for subscribers (vs ~75–80% today).</li><li>Pilot adoption: <strong>30% of daily active riders</strong> in Sarjapur/ORR within 3 months.</li></ul><p><strong>Pilot Example:</strong></p><ul><li>1,000 commuters on the 6–8 km tier → ₹18L monthly revenue (~₹2.16 Cr ARR).</li><li>Captains: 200 “Prime Captains” covering these subscriptions.</li><li>Rapido earns via daily access fees (~₹20 per captain per day) and stronger rider retention.</li></ul><p><strong>Risks and Mitigations:</strong></p><ul><li><strong>Distance Fairness:</strong> Flat pricing risks over-subsidizing long trips. → <em>Tiered pricing bands solve this.</em></li><li><strong>Captain Dropouts (long ride dissatisfaction):</strong> Bonus structure + distance tiers keep incentives aligned.</li><li><strong>Demand–Supply Mismatch:</strong> Start in dense corridors with uniform commute lengths (e.g., Sarjapur–Outer Ring Road).</li><li><strong>Regulatory Shifts:</strong> If zero-commission model changes, adapt incentives back to %-based margin</li></ul><h3>Metrics &amp; Success Criteria</h3><ul><li><strong>Adoption:</strong> ≥30% of commuters in pilot corridor.</li><li><strong>Completion Rate:</strong> ≥95% rides fulfilled (vs ~75–80% today).</li><li><strong>Wait Time:</strong> &lt;7 min for subscribers (vs 12–15 min baseline).</li><li><strong>Churn:</strong> Reduce by 15–20% over 3 months.</li><li><strong>Captain Reliability:</strong> ≥90% captains completing subscription rides consistently.</li></ul><h3>Roadmap</h3><p><strong>Phase 1 (Pilot — 3 months):</strong></p><ul><li>Launch in Sarjapur with 1,000 commuters (6–8 km tier).</li><li>Onboard 200 high-rated captains as “Prime Captains.”</li><li>Measure completion rate and adoption.</li></ul><p><strong>Phase 2 (Scale — 6 months):</strong></p><ul><li>Add 8–12 km and 12–15 km tiers.</li><li>Fine-tune pricing &amp; incentives.</li><li>Expand to 3–4 additional corridors.</li><li>Roll out reliability bonuses for captains.</li><li>Pilot corporate bundles with tech parks.</li></ul><p><strong>Phase 3 (Future Vision):</strong></p><ul><li>Pan-India rollout across top 10 cities.</li><li>Integrate with employer commute programs.</li></ul><h3>Open Questions &amp; Caveats</h3><p>Even with a strong hypothesis, a few unknowns remain that would shape whether Rapido Commute succeeds at scale:</p><ul><li><strong>Distance Fairness:</strong> A flat subscription risks overpaying for short commutes and underpaying for long ones. Tiered pricing helps, but how sensitive are commuters to “bands” versus one flat plan?</li><li><strong>Captain Behavior:</strong> Will captains consistently prefer predictable subscription rides over occasional surge spikes? Bonus schemes can align incentives, but need testing to avoid gaming.</li><li><strong>Adoption Hesitation:</strong> Commuters in India are used to pay-per-use. Will they pre-commit ₹1,800/month for reliability, or default to ad-hoc rides? Early pilots must test willingness-to-pay.</li><li><strong>Operational Complexity:</strong> Pre-scheduled rides introduce logistics challenges — reassignments if captains are delayed, reserve pools, live monitoring. The ops load may be higher than modeled here.</li><li><strong>Regulatory Overhang:</strong> Bike taxi legality in Karnataka has been challenged multiple times. A policy change could disrupt any subscription product built on bikes.</li></ul><p>👉 These aren’t deal-breakers, but they’re the kind of uncertainties I’d validate in a 500–1,000 user pilot before scaling.</p><h3>Conclusion</h3><p>Rapido already owns <em>affordability</em> in last-mile mobility. With Rapido Commute, it can also own <em>reliability</em> for office goers.</p><p>By keeping subscription pricing aligned with what riders already spend — but guaranteeing reliability and punctuality — Rapido strengthens trust, locks in recurring revenue, and creates a durable edge against larger competitors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a3394afc0bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Case Study | Improve Retention | Housing.com : Pay Rent]]></title>
            <link>https://nakshata.medium.com/product-case-study-improve-retention-housing-com-pay-rent-87f51496768c?source=rss-55811f24adae------2</link>
            <guid isPermaLink="false">https://medium.com/p/87f51496768c</guid>
            <category><![CDATA[user-retention]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[housing]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Nakshata Patel]]></dc:creator>
            <pubDate>Wed, 26 Jan 2022 15:10:21 GMT</pubDate>
            <atom:updated>2022-01-26T15:10:21.036Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Case Study | Improve Retention | Housing.com : Pay Rent</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/258/1*1wIqKUFNeEbRkYuajyC8Iw.jpeg" /></figure><h3><strong>About Housing.com:</strong></h3><p>Housing.com is India’s most innovative real estate advertising platform for homeowners, landlords, developers, and real estate brokers. The company offers listings for new homes, resale homes, rentals, plots and co-living spaces in India. It also offers other services like Rent Agreement, Pay Rent, Home Loans, Property Management, Legal Services etc.</p><h4>Pay Rent:</h4><p>Pay Rent is an online rent payment product by Housing. Users can pay their<br>house/office rent every month using their Credit Card.</p><h3><strong>Problem Statement:</strong></h3><p>80% of the Pay Rent’s payments come via App. Remaining from website.<br>Given below is the retention cohort for Pay Rent:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*vQJBO6q-w9dV00P7L5iGWg.png" /></figure><blockquote>What should we build this quarter to substantially improve our retention<br>cohort?</blockquote><h4><strong>Data Interpretations:</strong></h4><p><em>(Assuming that M1, M2 and M3 users are from the same segment of users who made the payment in the first month)</em><br> → On an average 36% users stop using pay rent after making the first payment<br> → Out of remaining users, 66% stop using pay rent after using for two months i.e., 30% drop<br> → 32% users stop after three months usage<br> → <strong>Maximum churn is seen after two months of using pay rent</strong></p><p>Hence, if we focus on solutions for retention of the users after the second month, it can make a huge impact on the overall retention cohort. Since 80% of payments happen through mobile app, we will focus on improving the app for the time being.</p><h4>Possible Reasons:</h4><p>Some of the possible reasons for customer churn <em>(based on the app’s Google Play Store reviews)</em> can be:</p><ul><li>Slow runtime : Most common reason given was that app was too slow or it hanged quite often. The transactions take a relatively longer time to complete.</li></ul><blockquote>According to an<a href="https://blog.pusher.com/how-latency-affects-user-engagement/"> Apteligent</a> survey, almost 50 percent of consumers say they would uninstall an app if it “regularly ran slowly”</blockquote><ul><li>Lack of other payment options: UPI, Debit card, etc.</li><li>Lack of customer support: One of the ways to improve customer retention is to swiftly resolve customer queries. In the app no instant customer support window or chat box is given. The users are required to write mail or contact directly via phone for that, which can be quite irritating and cumbersome.</li><li>Other competitor products: like Cred or NoBroker</li><li>Less lucrative offers: The rewards might not be lucrative or interesting enough to make customers come back again and again.</li></ul><p>To prioritize which problems to solve, we can take help from the table below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*fQ7iwpLQSeSe4j3WmOgWug.png" /></figure><p>As we can see from the table, making the app run smoothly via backend improvements , improving the reward system and having a great customer support have the highest possibility of reducing churn.</p><p>But since backend improvements are a never ending process and require much effort, we will focus on solving the reward system and customer support.</p><h3>Solutions</h3><ol><li>Payment Streaks for improving the reward system</li><li>AI Chatbot for improving the customer support</li></ol><h3><strong>Payment Streaks</strong></h3><h4>How it will work:</h4><ul><li>When a user pays rent for a certain period of months consecutively, a streak is formed.</li><li>After a certain period, they reach a milestone in which they unlock huge and exciting rewards.</li><li>If the streak is broken, i.e., user fails to consecutively pay then they will have to start all over again.</li></ul><p>In our case, we can set the period for the first milestone as 3 months i.e., if the user pays for 3 months consecutively, they reach their first milestone. Since the users have already paid for two months, they will pay for one more month so as to unlock their milestone. After that, milestones can be created every 3–4 months.</p><p>The rewards can be anything like huge cashback or heavy discount offers based on the profit margin.</p><p>This will add a sense of curiosity in the users and once they have paid for 3 months, a habit is formed and they are less likely to move to other platform or stop using our platform.</p><h4>Wireframe:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/811/1*ei3kYcQn-XIcoOXdEkzuxg.png" /></figure><h4>Performance Metrics:</h4><ul><li>Completion Rate: Number of users who complete the streak</li><li>Retention: Users who do consecutive payments after the introduction of payment streaks</li></ul><h3>Chatbot</h3><p>This is an in-app 24/7 AI chatbot for instant customer support.</p><ul><li>The small issues and FAQs which don/’t need calling or mailing the customer support can be resolved via this bot.</li><li>If the user needs further assistance, the bot will connect user to an agent within a few minutes.</li></ul><blockquote>According to <a href="https://blog.hubspot.com/sales/live-chat-go-to-market-flaw?__hstc=183108537.50a70b823dcaac503a7fe79a5b83a231.1643135610520.1643135610520.1643135610520.1&amp;__hssc=183108537.1.1643135610521&amp;__hsfp=2964097813">Hubspot</a>, 90% of customers rate an “immediate response” as important factor when they have a customer service question.</blockquote><h4>Wireframe:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DrE1olgdzMhIKBsOzHdSKA.png" /></figure><h4>Performance Metrics:</h4><ul><li>Activity Volume: frequency of usage of chatbot, number of users using the chatbot, etc. .</li><li>Bounce Rate: Sessions that fail to get the intended use of the chatbot</li><li>Retention Rate: Users who have used the bot repeatedly</li><li>Goal Completion Rate: Number of total queries solved by the bot</li></ul><p><em>Disclaimer: This case study was part of an assignment and the solutions are for educational purpose only.</em></p><p><strong>Thankyou for reading!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87f51496768c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>