work / cabdost

Cabdost

Tax filing for 50,000 gig drivers, built for low digital literacy

FintechDesign Product Consultant · 2018–2019

Led Hired & oversaw 3 devs, 1 QA

50,000 Applications processed
~₹1.5 Cr Recovered, early post-launch
35x Business growth
TL;DR
  • Surveyed 100 drivers before designing a screen: they forget passwords, distrust forms, and live inside their cab apps
  • Key decision: borrowed the UI patterns of Uber/Ola, the apps drivers already trusted, instead of inventing a new "finance app" language
  • In the alpha test, the first driver completed his application in 3 minutes without reading English; in the early post-launch months the platform recovered ~₹1.5 Cr for 5,000 drivers, with 35x business growth
  • Filing volume scaled from ~3,000 offline applications to 50,000+ processed on the platform

The real problem

Gig workers don’t lack income, they lack the tooling and financial literacy to file returns, claim deductions and stay compliant. Talking to 100 drivers surfaced the real constraints: low digital literacy, forgotten passwords, fear of official-looking forms, and a daily life spent inside one or two cab apps. Above the drivers sat an agent workflow run on vulnerable Excel sheets, processing roughly 3,000 applications a year by hand.

Goal

Empower gig workers with simple, guided tools for tax filing, income tracking, and financial literacy at an accessible price point.

Outcome

Simplified ITR filing, expense tracking, compliance guidance, and tax-savings education. ~₹1.5 Cr recovered for 5,000 drivers in the early post-launch months, with 35x business growth, and filing volume has since scaled to 50,000+ applications processed.

Tax applications processed annually
~3,000 (offline, agent-run) 50,000+ (on the platform)

Measured by: Cabdost operations data, pre- vs post-platform

What was considered

A conventional finance-app UI
Why considered Standard patterns, faster to design
Why it didn't ship Forms-and-tables language is exactly what drivers distrusted and abandoned
shipped Cab-app-familiar patterns (chosen)
Why considered Drivers already navigate Uber/Ola daily; familiarity collapses the learning curve to near zero
Trade-off accepted Less conventional for the agents and accountants who also used the system
Driver self-serve only
Why considered Cleanest product story
Why it didn't ship The agents doing the actual filings were drowning in Excel; an agent dashboard was where the operational leverage lived

What was built

A minimal, guided filing flow for drivers, plus an agent dashboard that replaced the Excel-sheet operation behind them. The roadmap extended to vernacular languages, a payment gateway and team chat.

Core features

Tax FilingGuided ITR workflows with document collection and filing support
Financial TrackingIncome, expenses, and profit analytics in one dashboard
Compliance ToolsStay compliant with tax and regulatory requirements
Financial LiteracyLearn deductions, savings strategies, and tax planning