11–14 of 14 posts
Pricing is a big interest of mine (30,000 words into writing a guide on it). Understanding your ideal pricing depends upon understanding your customers and your value proposition. We need more information before we can tell you what to charge and how to charge it.
Earlier quoted context omitted.
Nice! I see your guide here: http://taprun.com/pricing/ . I'll check it out, thanks! I think the Github vs. Bitbucket question is a proxy that I can easily translate into my scenario. So in that case, what are the relevant factors?
It would definitely help if you said more about what your product is. But generally speaking, from the customer's perspective, you should charge for the thing that the customer can predict better up-front, so that it's easier for them to assess your value proposition. You might want to take into account your own costs as well, if applicable. The interesting thing about Github vs. Bitbucket is that both usage patterns…
Disclaimer: I have no slightest idea about economics. And I'm not sure the following is a good idea. So, don't listen to me. As I get it, you probably want to let users start for free when their requirements are small, and start changing as they grow. I suppose everyone has different needs, though — some value ability to spawn a dozens of tiny private repos, but some want just one for a relatively large team. Then —…
Bitbucket has better pricing for closed-source projects, Github has better pricing for open-source projects. It really depends on the structure of your market and your competitors. There's not enough information in your post to say anything more helpful than that.
Thanks for your reply. You're right, of course. But rather than try to explain my market, target user, competitors, etc., I think I can translate discussions of Github vs. Bitbucket fairly well into my situation. So, can you elaborate? Why is Bitbucket better for closed-source and Github better for open-source projects?
BitBucket is free for private repos up to 5 users. This is better for closed-source projects.