Product case study · B2B sales operations · Rupak Ghanpathi, ex-HDFC Bank

100 open leads. 10 actions today.

A mobile To-Do module that tells a salesperson what to act on now, why, and what comes next, without becoming another CRM or a tool for watching people.

Informed by the ownership buckets, approval queues and ageing MIS I worked with at HDFC Bank.

Deals stall between the rep and the approver. Ten Today freezes the follow-up, puts the clock on the approver, and gives them the three numbers to decide in seconds: ask, margin floor and the customer's overdue balance.

The case study's worked example

  • Follow up quoteP1

    ABC Corp · ₹2L · 5 days past target

  • Approve discountP2

    XYZ Ltd · ₹5L · ask 6% off · floor 4% · customer overdue ₹0

  • Qualify leadP3

    Mahesh Electronics · ₹50L · due today; value doesn't lift it

  • Callback16:00

    Patil Traders · customer's time, pinned

12 / 14 UAT passingOpen →
100+open leads, quotes and approvals on one phone
→
4 rulestier · approvals first · days late · value as tie-break
→
10ranked actions today, each with a one-line reason

Six skills, each with its proof · tap one

  1. Problem framingDue isn't the same as urgent
  2. Workflow & state designHow a task lives and ends
  3. Prioritisation rulesOne explicit sort order
  4. Edge cases & UAT15 tests you can run
  5. MVP scopingWhat ships first, what waits
  6. Metrics & guardrailsOn time against the original target

Problem, trigger and proposed design

Why: the problem

On a phone, a list of everything is a list of nothing. The quote going cold looks exactly like the 40 records around it.

When: the trigger

A workflow event: a new lead, a quote sent, an approval needed, a callback agreed.
Todayit joins 100+ open records.
Proposedit becomes a task with a target and a reason.

How: the design
  1. Tasks come from workflow events
  2. Today shows only 10, ranked by rules
  3. Tasks close when the stage moves
  4. Managers see exceptions, not activity

Open the executable specification →

The ranking rule · applied in this order
  1. Priority tier: P1 = 5+ days past target · P2 = 1–4 days · P3 = due today
  2. Blocking stage: within a tier, approvals first
  3. Days overdue: older before newer
  4. Deal value: only a tie-break, so a big deal doesn't jump the queue

Why a cap works: the 1-3-5 method Todoist teaches limits a day to nine tasks because long, open-ended lists cause overwhelm and constant triage (Todoist). Ten Today applies the same idea to sales work, with the order set by rules.

Callbacks are pinned at the time the customer agreed. Future tasks wait in an Inbox. Rules, not AI, in V1: less clever, but a salesperson can see why a task is on top.

How a task lives and ends · created → Inbox → Today → Done, or on hold, auto-closed, escalated
Workflow eventTaskTargetOwner
New leadQualify lead1 working daySalesperson
Lead qualifiedPrepare quotationConfigurableSalesperson
Quotation sentFollow up3 daysSalesperson
Approval requiredApprove or reject1 working dayManager
Callback requestedCall the customerAgreed timeSalesperson

If the stage moves first, the old task auto-closes and the next one is created. From HDFC: completing an action and completing the business process aren't the same thing.

What ships first, and what waits

V1: Today · Inbox · Overdue · Approvals · On hold with reason and revisit date · auto and manual tasks · complete, reschedule, reassign · four push triggers · manager workload view · history.

Later: AI prioritisation, recurring tasks, outcome-based completion, productivity scoring (it would turn a work tool into performance management).

How I'd know it worked · one metric and a guardrail

% of tasks completed within their original target, measured against the original date so rescheduling can't fake "on time". Guardrail: tasks rescheduled 3+ times or on hold past their revisit date. Why it matters: when Todoist launched Smart Schedule, it said a significant portion of its users reschedule up to 70 tasks day after day (MacStories). Rescheduling is how lists lie, so Ten Today measures against the original target and asks for a blocker on the second reschedule. Revenue is a downstream outcome, not the result.

Validate first: shadow three salespeople for a day, review a month of CRM history, test the Today screen as a clickable prototype with five reps.

The original case study · PDF and one-pager

Independent product design case study by Rupak Ghanpathi: a concept, not a shipped product. Targets are configurable defaults; names and figures are illustrative.

Systems of record (the ERP, the CRM, the calendar) record what happened. They don't help at the moment a person has to decide something messy. Three layers for those moments, without replacing the system underneath: Viraam ends the meeting · Every Rupee owns the short-paid difference · Ten Today unblocks the approval. By Rupak Ghanpathi.