Many, many, many years ago now I wrote one of the very early GUI HTML editors while still a junior in high school. This predates Frontpage, Homesite, and most commercial offerings from the major players so it was relatively successful in terms of market share. It was shareware though, and fully functional apart from the occasional annoying popup. A payment of $5 would remove the popups. Over the course of a year I increased the price from $5 to $10, and then to $15 dollars.

I can't remember the exact numbers, the the downloads per month were still in the thousands but the number of people that had paid for the product since I released it I could still count on one hand. That didn't bother me too much as I built it for myself primarily, anything else I deemed a bonus.

Then one day I decided to up the price to $99, I figured zero people at $99 was just as profitable as zero people at $15. The next day I woke to find I'd had at least 10 orders overnight, and the trend continued for quite a few months until the product started to noticeably lag the new offerings from Microsoft and Co.

It was a very early and valuable lesson, the price you put on a product signals to your potential customer how valuable you think it is.

One of my most recent client sells a SaaS product that allows people to do market research. It's not the cheapest in the market, but by no means expensive. A large part of their customer base are consultant types who use the tool for when doing work for their own clients. Many of them lament the fact that there wasn't an "Enterprise" edition of the tool. No requirements for additional features, it already meets their requirements, they just don't want their clients thinking they can have access to the same tools for $100/month.

For slightly different reasons, it was price guiding the perceived value of the offering.

Just something worth considering. Obviously without knowing the product it's hard to say what value I'd prescribe to it on a monthly basis.