3 ms·

The logic we followed when pricing it so cheap was: we are just getting started, this will help get some revenue in quickly, etc. Will think hard and perhaps re

• skynode 7y ago
  It's usually much more difficult to increase prices later after you've gathered more data. The Web is a much bigger, diverse place today than it was 10 years ago. Start at higher prices as a rule for [esp for non-technical audiences], measure, tweak and repeat.
• throw_14JAS 7y ago
  Your first customers will be sold to in person. Let them tell you when something is too expensive (then discount to make the sale). If they aren't commenting on your pricing, you are charging too little. Also reconsider your pricing model. Charging per user per month will place a limit on how many people use the service, limiting what you can learn. Get them focusing on the value you're adding more than optimizing price. What you learn from them will be hugely valuable.
• anthonys 7y ago
  One thought I have on your model is make your entry price some sort of bundle. Your product is designed for workflows and you can't really have a workflow with 1 user so already you are at 2 users to start. I am sure you can play around with this but it feels like this product would benefit from getting into as many users hands as possible when you are establishing yourself in a client business. Atlassian is an example of this where all of their products (or almost all of them) are $10/10 users and once you hit 11 users, it goes up quite a bit. That might seem like quite a jump but imagine what you are paying in salaries at 11 people vs. what your JIRA subscription now costs?