| > People are also generally not that good at figuring out what they're willing to pay for something. I like to think about it this way: 1) what is the highest price I could charge without looking like an idiot for charging too much? 2) what is the lowest price I could charge without looking like an idiot for charging too little? Now I have a price interval. If it's SaaS, I set the highest price for the shortest subscription period (ex., 1 month), and the lowest price for the longest subscription period (ex., 12 months), while adding additional options in-between (ex., 3 months, 6 months). This way, I feel like both sides are getting a fair deal, and nobody loses. |
If we distill this whole "pricing before product" idea down I think it's just a specific part of orienting to the needs and behaviors of users before designing the solution. Price is sometimes awkward to fit into something like user-centered design, perhaps because it affects users/needs, business viability, etc. but really it's one important factor among many. Maybe it's a very important, hard-to-change factor (likely true in luxury autos) but it can sometimes be a fairly insignificant or easy-to-change one (e.g. technology offerings with few substitutes).