I've got a use case where the user wants to get a price based on a specific number of units as opposed to a typical straight cost/sale scenario. The backend manages the number crunching/heavy lifting based on a dynamic set of variables in order to deliver a single price back to the user.
In this scenario pricing decreases based on the number of units sought. The user typically requires a specific number of units and there's not a lot of common ground in terms of average units required across the customer base.
The idea here is to deliver the most relevant price to the user and provide a personalised experience that better suits their own use case - they need a unique number of units and a price for that amount, not a from - to amount.
An alternative is to provide a cost matrix, however that seems kind of primitive. There are also conversion factors at play that could be influenced by analysis paralysis etc.
Here are our early ideas. I wanted to get some feedback on what you make of it and given the use case detailed above, what you'd do differently.
Here are the challenges as I see them:
- Provide an intuitive way for a user to get a per unit price
- Make that pricing information easy to understand and act on;
- Funnel price into a conversion event that makes sense to the user and can be acted on.