Author Topic: Is it possible to track Revenue Per Employee (Revenue Per Worker) in Bitshares?  (Read 1611 times)

0 Members and 1 Guest are viewing this topic.

Offline luckybit

  • Hero Member
  • *****
  • Posts: 2921
    • View Profile
  • BitShares: Luckybit
In startups the RPE is an important metric to determine how efficient the work by the employees is. In our case we have workers but do we have metrics to track how much revenue each worker might be bringing into the Bitshares ecosystem?

For example if the revenue goes up after a certain feature or certain proposal then we know it's having a positive effect. Other changes might result in a loss of revenue or lower volume. So we would want to focus on features which increase volume and through A/B testing we can determine which features are effective.


http://www.investopedia.com/terms/r/revenueperemployee.asp

Though it's not revenue. I think the winner would be Fox in terms of adding/doing something that added value to BTS relative to cost.

His efforts to get BTS added on Azure, gave BTS it's highest volume day in history, (>$6 million)It took us from $10 million to >$20 million at the peak in less than a week and even after the drop off, BTS was/is circa 40% higher. I'm not sure he was even paid for his efforts.

Okay that should go into the database, his efforts should be rewarded by the community, and we should replicate his efforts over and over again.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline Empirical1.2

  • Hero Member
  • *****
  • Posts: 1366
    • View Profile
In startups the RPE is an important metric to determine how efficient the work by the employees is. In our case we have workers but do we have metrics to track how much revenue each worker might be bringing into the Bitshares ecosystem?

For example if the revenue goes up after a certain feature or certain proposal then we know it's having a positive effect. Other changes might result in a loss of revenue or lower volume. So we would want to focus on features which increase volume and through A/B testing we can determine which features are effective.


http://www.investopedia.com/terms/r/revenueperemployee.asp

Though it's not revenue. I think the winner would be Fox in terms of adding/doing something that added value to BTS relative to cost.

His efforts to get BTS added on Azure, gave BTS it's highest volume day in history, (>$6 million)It took us from $10 million to >$20 million at the peak in less than a week and even after the drop off, BTS was/is circa 40% higher. I'm not sure he was even paid for his efforts.
« Last Edit: March 26, 2016, 08:19:12 pm by Empirical1.2 »
If you want to take the island burn the boats

Offline luckybit

  • Hero Member
  • *****
  • Posts: 2921
    • View Profile
  • BitShares: Luckybit
In startups the RPE is an important metric to determine how efficient the work by the employees is. In our case we have workers but do we have metrics to track how much revenue each worker might be bringing into the Bitshares ecosystem?

For example if the revenue goes up after a certain feature or certain proposal then we know it's having a positive effect. Other changes might result in a loss of revenue or lower volume. So we would want to focus on features which increase volume and through A/B testing we can determine which features are effective.


http://www.investopedia.com/terms/r/revenueperemployee.asp
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads