KPIs for dashboard - Githubissues

notdrone commented 6 years ago

Originally reported by: Droan Malik (Bitbucket: notdrone, GitHub: notdrone)

Customers (Total, Eko Verified, Unverified, Mandate initiated, Mandate Confirmed, Mandate Rejected)
Time to complete transactions (with daily, weekly and monthly average (including and excluding holidays))
Time taken to complete the first transaction after mandate confirmation
Transactions amount (Failed, Success, Pending)
Number of transactions (Failed, Success, Pending)
Monthly Retention rate
Summary at end of the day about pending transactions, completed transactions and customer stats for that date sent on slack as a link (like fabric does)
Revenue, Profit
Customer & Beneficiary IFSC region (for demographics)

Add Comment

Bitbucket: https://bitbucket.org/inkredo/91paisa-web/issue/5

notdrone commented 6 years ago

Original comment by Droan Malik (Bitbucket: notdrone, GitHub: notdrone):

Splitting these into separate issues

kumartanmay commented 6 years ago

Profits come from creativity. Companies with similar products in the market are profitable in their own ways - it's never the same. Revenues are a result of investments and profits are born out of creativity. That's why shareholders risk their money. So is it safe to keep profit as a KPI out of sight until we find something creative?

inkredo / 91paisa-dashboard

KPIs for dashboard #5