Dror · Gurugram · Seed · 2020–2021
Two products, one pivot, eleven months
Sole PM and designer at Dror — through a full product lifecycle: a 0→1 consumer launch, a COVID-forced B2B pivot, and a lesson about what PMF looks like when it's rented from an external event.
Role
PM · Designer · Frontend
Team
10 people
Duration
11 months
Revenue
₹1.98Cr lifetime
Product Journey
Act 1 · May–Oct 2020 · 6 months
Consumer Safety App
India's Life360 · B2C freemium · real users
⚡ Forcing Function
COVID-19 Lockdowns
Citizens stop moving. B2C use-case evaporates.
Pivot · Oct–Nov 2020 · 6 weeks
The B2B Pivot
3-day prototype · 5 enterprise clients · commit
Act 3 · Nov 2020–Apr 2021 · 5 months
B2B Workplace Safety SaaS
Bluetooth · Smart cards · React dashboard
₹1.98Cr
Revenue
2
Products
$494K
Raised
The Story
Three acts, two forcing functions, one lesson about building products whose market exists only because of the conditions that created them.
Act 1 · May–Oct 2020 · 6 months
India's Life360
Built and launched a consumer citizen safety app from 0→1. B2C freemium. Real users, near-zero revenue.
⚡ Forcing function · March 2020
COVID lockdowns. Citizens stop moving. Safety-while-moving use case evaporates. B2C growth stalls.
Pivot · Oct–Nov 2020 · 6 weeks
The Pivot Decision
CEO identifies B2B inbound. We prototype a workplace safety product in days, validate with clients, commit.
Act 3 · Nov 2020–Apr 2021 · 5 months
B2B SaaS Rebuild
Bluetooth proximity + smart cards + factory manager dashboard I designed nights and coded afternoons in React.
⚡ Forcing function · Late 2021
COVID gets controlled. Restrictions lift. Enterprise clients stop renewing. The urgency that created the market disappears.
Wind down · Post Apr 2021
PMF was real — but rented
Company hits ₹1.98Cr lifetime revenue, eventually winds down. The market we'd built for stopped existing.
Context
The product didn't fail. The world changed — twice.
Most startup failures are internal — wrong team, wrong execution, wrong market. Dror's story is different. We built the right product twice. Each time, an external event made our market disappear.
Forcing function #1 · March 2020
COVID-19 locks everyone home
We were 6 months into building a citizen safety app — location sharing, SOS alerts, safety circles for people moving through cities.
Citizens stop moving. Our core use case — safety while in transit — becomes irrelevant indefinitely. B2C growth stalls. Revenue near zero.
Forcing function #2 · Late 2021
COVID gets controlled. Restrictions lift.
We had pivoted to B2B workplace safety. Enterprises were paying for Bluetooth-based social distancing tools. Revenue was real. Contracts were signed.
The urgency disappears. Offices reopen fully. Clients stop renewing. The problem we solved no longer exists at the severity that made people pay.
Role Reality
There was no time to be a PM in the traditional sense
In a 10-person team under survival pressure, I collapsed the PM → Design → Dev handoff into a single person across three time blocks per day.
A typical 24 hours
Night
UX Design
Designed flows, screens, and prototypes for the next day's dev work. Figma. No handoff process — I was the handoff.
12pm Standup
PRD Delivery
Detailed PRDs to the tech team every morning. Had to be precise — a vague PRD meant broken builds by afternoon.
Afternoon
React Frontend
Coded the B2B dashboard frontend in React.js alongside the full-stack dev. Frontend would have blocked shipping without me.
Full team — 10 people
Dhiraj Nauhbar
Co-founder & CEO
Amritansh
PM · Designer · Frontend
2 co-founders
Operations & CTO
2 full-stack devs
Backend + full stack
2 app developers
Android + iOS
1 dev intern
Support
1 marketing intern
Growth
Act 1 — Consumer App
Building India's Life360 — from scratch
The CEO had an early MVP and initial seed funding. Life360 existed but wasn't built for India.
Why Life360 didn't work for India
Gap 01
Connectivity assumption
Life360 required persistent internet. In tier 2/3 India, patchy connectivity made real-time sharing unreliable exactly when it mattered.
Gap 02
English-first UI
Life360's onboarding was English-heavy and jargon-dense. Our primary users in smaller cities needed icon-first, low-literacy design.
Gap 03
Family tracking ≠ safety in India
The ‘track your family’ framing felt invasive in Indian social dynamics. We repositioned as a safety circle — opt-in, mutual, trust-first.
Gap 04 · Research
68% drop-off in Life360 onboarding
Ran Life360 with 15 Indian users. Primary drop-off: confusing permissions flow, English UI, assumption all members have active smartphones.
Life360 onboarding drop-off rate · 15 Indian users
68%
drop-off
Primary reasons: confusing permissions flow, English-heavy copy, assumption that all family members have active smartphones.
The commercial reality of Act 1
The consumer app launched. We got real users. But the revenue model was broken from the start — B2C freemium in India in 2020 meant most users never paid. The product was validated socially, not commercially. Then COVID hit and citizens stopped moving. We had a live product, real users, and almost no revenue.
Act 1 Decisions
Full Safety Suite or Single Reliable Action?
Problem
We had requests for community reporting, live tracking, in-app emergency calls, and driving behaviour tools for V1. Shipping everything would delay launch and create a support surface we couldn't sustain.
Decision
Shipped a single core action: one-tap SOS trigger + safety circle setup. Everything else deferred with documented rationale. In a trust-sensitive category, one failure destroys retention permanently.
Tradeoff
A less feature-complete V1 than stakeholders expected — but zero post-launch critical failures in the category that mattered most: emergency response.
Impact
SOS reliability became the product's trust foundation. Fewer features, rock-solid core — what early retention data confirmed.
No Confirmation Screen for SOS
Problem
A two-step confirmation would prevent accidental triggers. But usability testing showed it added 3× the completion time under simulated stress conditions. Those seconds aren't recoverable.
Decision
One tap = SOS sent. Accepted false positives. Emergency use demands speed over precision. The confirmation step was removed entirely.
Tradeoff
Higher rate of accidental triggers in calm conditions. Worth it for the seconds saved in genuine emergencies where confirmation adds nothing but friction.
What we cut from V1
Prioritisation is what you don't build.
Community reporting
V1
Trust risk — users feared false alerts and abuse
Live location sharing
V1
Privacy concern; battery drain on low-end devices
In-app emergency call
V1
Latency made it slower than native dialer every time
Driving behaviour tracking
Roadmap
COVID made this irrelevant — no one was driving
The Pivot
The decision that changed everything
Dhiraj was in conversations with enterprises about employee safety. The signal was clear: companies with essential workers needed exactly what we'd built — but packaged for B2B. We validated fast.
Rebuild for B2B or Keep Iterating on Consumer?
Problem
COVID lockdowns made our core use-case irrelevant indefinitely. The B2C freemium model had near-zero revenue. The team needed a path to commercial viability or it would run out of runway.
Decision
Pivoted to B2B. Rebuilt for enterprise workplace safety with Bluetooth proximity detection and a management dashboard. Kept the consumer app live but stopped investing in it.
Tradeoff
6 months of consumer work became a foundation we weren't building on anymore. Required a full product rebuild with the same team, no extra resources, in 6 weeks.
Impact
First enterprise contracts signed within the pivot window. Revenue went from near-zero to real recurring contracts in a quarter.
Validation pipeline before committing
Act 3 — B2B Rebuild
Rebuilding for enterprise — Bluetooth, smart cards, and a React dashboard I partly coded myself
Act 1
Consumer Safety App
Act 3
B2B Workplace Safety SaaS
Primary user
Citizens moving through cities
Primary user
Factory managers + essential workers
Revenue model
B2C freemium — mostly free
Revenue model
Enterprise contracts — recurring
Core feature
SOS trigger + safety circle
Core feature
Bluetooth proximity + compliance dashboard
Tech
GPS, mobile app (Android + iOS)
Tech
Bluetooth + smart card hardware + React
What I built
Full UX, PRDs, app design
What I built
UX, PRDs, React.js frontend dashboard
How the product worked — 4 layers
Layer 01 · Hardware
Smart cards for every worker
Each essential worker carried a Bluetooth-enabled smart card. Cards detected proximity to other cards. When two workers got too close for too long, both devices vibrated and logged the event.
Layer 02 · Mobile
Phone-based detection for managers
Workers with smartphones used the mobile app as a secondary detection layer. This reduced hardware cost for enterprises where some workers already had devices.
Layer 03 · Dashboard
Real-time compliance view for managers
Factory managers got a web dashboard showing active worker count, proximity events, compliance score, and at-risk zones. This is what I designed nights and coded afternoons in React.
Layer 04 · Reporting
Exportable reports for enterprise compliance
Enterprises needed documentation for regulatory compliance. Weekly PDF reports with distancing metrics, event logs, and trend lines — added after the first client asked.
drorapp.com/dashboard · Factory A
Live safety overview — today
● Live247
Active workers
14
Proximity events
94%
Compliance score
Zone compliance heatmap
Factory floor AFactory manager dashboard — React.js, designed and coded by me
Impact
What the numbers actually say
These are company lifetime numbers, not just my 11 months. The B2B pivot is what generated real revenue — the consumer app validated the concept but couldn't monetise it.
Lifetime revenue
₹1.98Cr
mostly B2B
Total funding
$494K
4 rounds · seed
Competitor rank
23rd
of 215 active
Products shipped
2
in 11 months
Time to pivot
6 wks
idea → first client
Market position
23rd of 215 active competitors
#23
Top 10.7%
Revenue trajectory — company lifetime
The pivot from B2C to B2B is the only moment revenue grew meaningfully
Honest assessment
₹1.98Cr sounds like a success. In context it isn't. The company raised $494K (~₹4Cr) and generated ₹1.98Cr in lifetime revenue. The B2B pivot worked commercially — but only for as long as COVID made social distancing a compliance requirement. Once restrictions lifted, the problem we'd built for stopped being urgent enough for enterprises to pay for. We proved we could sell. We didn't prove the market would last.
Reflection
“We didn't fail because we built the wrong product. We built the right product for a temporary world. The lesson isn't ‘don't pivot.’ It's ‘understand what your market is made of — and whether it exists without the forcing function that created it.’”
The correlation that ended us
Our revenue tracked COVID severity — not product quality. When restrictions lifted, revenue fell.
What I'd do differently
Build for the post-COVID use case in parallel. Workplace safety as a category doesn't require a pandemic — but we never found the non-emergency version of our product. If we'd started that search in early 2021, we might have had something before the urgency disappeared.
The PMF lesson
PMF tied to an external forcing function is not durable PMF. Our retention was high, our NPS was strong, clients were happy. But none of that mattered when the underlying reason to buy disappeared. True PMF survives when the conditions that created it change.
What this changed in how I work
I now ask ‘what happens to this product when the forcing function goes away?’ before committing to any product direction. It's the question we never asked at Dror — because the forcing function felt permanent at the time.
The operational learning
Designing nights, writing PRDs at noon, coding afternoons — that rhythm worked because I refused to be a bottleneck. But it's not scalable. In a lean team, the PM has to be willing to do whatever the product needs, not just what's in their job description.
Keep reading