- 1) give ranges of price estimates
- 2) communicate the uncertainty around different parts of the estimate
- 3) show what size team you are estimating will be working on your project
- 3b) have a slider so that people can play around with the team size (and explore the team-size / price / time tradeoff)
- 4) show an estimate of what kind of volume the finished mvp can handle
- 5) show real-life estimates you've gotten on a set of projects. possibly include how much it would have cost to build this very website at both a large institutional design agency and a well-regarded boutique agency.
The former scheme is hard because time, as the Ithaca HOURS currency experiment shows, isn't exactly fungible in the same way that money is. Being able to redeem 'an hour' assumes that all people can do the same level of work at all tasks.
The latter, however, requires a different way of thinking about pricing.
For instance, service providers might set their rates as multiples of one's hourly wage: a tennis teacher might charge 1x, a pro-tennis teacher might charge 3x, and a low-income psychotherapist might charge .85x... Such a scheme could work with a sufficient number of clients -- essentially one is sampling from the income distribution -- but the system is more equitable to income differences.
From this point, one can think of more complex schemes, like a non-linear mapping function that can prevent high-income individuals for paying drastically more than others.
Yes, one big issue is one of trust and verification of income... but if it were a culturally accepted practice, it could work. The other issue is the incentive to only target high-income people. Perhaps there could be a set of tax breaks for those whose distribution of client's incomes met some basic requirements.