How can you afford to offer such a service, completely free? What is your business model?
Pivotal Labs is a software development consultancy, we get paid to build software, from web applications for startups to large-scale enterprise systems. We built Tracker to support our own projects, and now share it with the agile community, but it is not a primary source of revenue for our company.
[1]Wonder what changed?
[1] http://webcache.googleusercontent.com/search?q=cache:V05_lTO...
They generally do a mediocre job at best, so their clients didn't renew their overpriced consulting contracts.
Interesting. Twitter seemed quite enthusiastic about their two "Pivots": When we began working with Pivotal last year, we knew they'd be a big help but we didn't expect how much they would contribute to a healthy and attractive work culture.
http://blog.twitter.com/2009/03/pivotal-means-of-crucial-imp...
On the other hand, Pivotal's price is steep, and you have to hire their programmers in pairs: It’s about $15,000 a week for a pair. And so what we came up with was, “Look. You don’t have much money...” But we came up with this idea that if we do a six week run, and he gave me a very slight bit discount, so like a six week was going to be $84,000 we could get a minimum viable product up and launched.
http://mixergy.com/oneforty-laura-fitton/
Given the price of hiring Pivotal Labs, it sounds like Twitter and Laura Fitton were pretty enthusiastic. I wonder how to reconcile that with what you've been hearing—has Pivotal Labs gone through a growth spurt in the last year or two?
Perhaps the biggest thing here is that you must hire a pair, so it actually comes to about $374/h, but if it's true that you get the job much more quickly with a pair then I don't see the issue.
But my point still stands as Twitter did not renew their contract...
It's also not what I've "been hearing"... I've had to work directly with Pivotal people.
Software consultancy gets old quickly. You trade your steady paycheque being told what to do, for a not-so-steady paycheque being told what to do. Even at $15K per week, the revenue is not as scaleable as the potential revenue from charging for Tracker would be.
Again, I can't speak to your first-hand experience. But it struck me as sounding a bit mean spirited. I'm not sure if that was your intention. If they can churn out Tracker, which is pretty good, but are doing a mediocre job with some contracts, there's a correlation there. It doesn't mean they are necessarily the cause for the mediocrity. The cause might boil down to "fit" and this may be the reason why the contracts were not renewed.
EDIT: Actually, on further investigation (which I should have done before posting this), Pivotal Labs is a lot bigger of a consultancy than I thought. It's more than probable that only a small handful actually touch Tracker. I was always under the impression that their consultancy was a lot smaller, so they could ensure consistently high quality.
Many clients do come back to us, but we actually try hard so that they don't ever "have" to - by leaving them with a maintainable, tested codebase, and effective engineering practices like TDD/BDD, pairing, aggressive refactoring, etc. We even help hire and train their own developers.
We kept Tracker free for almost three years, and over 180,000 people have signed up for it so far. We use it on all our projects, and the widespread adoption has been a great calling card for our consulting business. The decision to begin charging for it was not an easy one, but the reason is simple - we want to make Tracker better, faster, and establishing a revenue model for Tracker will allow us to devote more resources to it, including a larger dev team, support staff, and operational/hardware capacity.
Our goals are not to transition from a consulting company to a product one, but to do both equally well, and it's hard to do that when one side of the business has to fund/support the other.
* markdown (code blocks, anyone?)
* editing or deletion of comments
* grouping stories
* replying to comments by email
[Edit: list formatting]
http://skitch.com/benatkin/rkecs/pivotal-tracker-story-view
Also, why not have an expanded, non-editing view? The <input> elements do take up extra space when just viewing the extra fields.
It seems to me that they're missing some of the finer points of Single Page Application design. I wish I had a good guide I could point them to.
Again, though...they're totally nailing other parts of single-page application design. It's an amazing app that could be made a lot better with some refinement.
However I read that they are going to require you to pay for the upper tiers to use JIRA sync and other such features... wasn't JIRA support built into Pivotal Tracker by the community/3rd party or is this now their own implementation?
It would be wrong, imo, if they were charging a higher tier to use a community built plugin.
(why anyone would want to use JIRA is another matter, however)
The nature of contributing to OSS is that you are spending your time for the benefit of for-profit companies. That is, very possibly, a poor business decision if you are not being compensated directly while doing it. If you aren't being compensated, then you should expect to receive everything the MIT license lists under Section 42: Stuff The End User Owes You.
And the idea with these integrations is that your team can do focused collaboration (with Tracker) on some subset of issues/bugs that are stored in a larger, more widely used tracking system at your company (eg JIRA).
Have been a very loyal user of pivotal tracker, I have 11 projects with 12 collaborators. The smallest plan I could choose is $50 per month. That was shocking me a bit, before I knew I can archive my old projects :P
In my past life as a freelancer, I might have 10 or 20 projects going, each with a couple collaborators, but it still only added up to 40 hours of work for me, and the collaborators were negligible.
Now at my startup we only really need one project with 4 collaborators, but we're getting 2-3x the value out of it.
I don't have trouble paying for full-time dev collaborators, but the head count could become a pain point once you roll in various tangential roles such as management, support and sales, etc. I'm not sure the best way to handle this without opening loopholes, but I'm hoping they reach out to some of their users who aren't quite so developer heavy as pivotal labs to discuss options.
"Choose a plan with annual billing on or before February 19, 2011, and receive an additional 20% discount for the first year. That’s 18 months of use for the price of 8."
$7/mo * 12 * 80% * 80% = $53.76 with the discounts. Price of 8 months without the discounts is $56.
If you pay for 8 months today, you'll be good for the next 18 months. It's a stretch, but not really wrong.
$7/mo * (12 - 2) * 80% = $56.00
That being said, they put a heavy penalty on having clients on board as part of the process. I have three projects, five part-time coders, five clients, and 1 virtual assistant to keep it all running. I have to pay $100/month to keep going?
I don't need Jira or Zendesk, so why should I pay $50/month? I could probably setup two $7 accounts and one $18 account and be fine - but then I have to deal with the pain of logging in and out just to do work?
I would happily pay $25-$30 a month, but $100 seems off the mark to me.
I'm charging $20/month for unlimited everything (users/projects/storage/etc), and can't shake the feeling that some customers find this to be a hefty price tag and others would pay $200 or more.
BTW - I'm glad they're charging - it's a great product and they deserve to make some scratch from it.
The other thing is the feature set seems to be a terrible way to segment users. I'm not sure the price people are willing to pay has much to do with the number of projects/users/etc they need. I'm looking for a way to segment based on willingness to pay, not my own convenience.
For example, one customer was a utility company. They didn't care at all about price. A freelancing shop was skittish at $8. Neither one needed a boatload of features.
Pricing starts at $7 for up to three collaborators, so does that mean individuals and up to two others? Looks like they'll stay free for public projects, but I don't see any mention of individual accounts save on the pricing page's "free for individual use (no collaborators), with up to 2 private projects."
@rubyrescue: agree with you 100%
I just hate paying for more users than I would need or, integration with JIRA.
They have a good tool and don't have problem paying a reasonable price for it.