I don’t care what software you build or how you deploy it, the lessons and pitfalls described by Jason Fried in this post apply to you:
Definitely worth a full read, but here’s a key nugget:
In the traditional software world, new releases were bundled up into distinct versions. And it was up to the customer if they wanted to upgrade or not. If they didn’t like the opinions of the new version, they could stick with the old, familiar version. If the new version didn’t solve any new problems they had, they could keep using the version they already had.
Not so with SaaS. When updates are deployed, they’re deployed instantly for everyone. That’s not always the case – sometimes you phase in a release – but for the most part the end game is the same: This is new and it’s making its way into the product. This means customers often don’t get the chance to opt out of changes in the SaaS world.
. . .
This is why change gets really hard as a SaaS product matures. Existing customer expectations are some of the strongest forces pushing back at a company with new ideas.
Even the best software, some might argue iOS or OS X fits this claim, is not immune. To make good software, you have to break some eggs. Or something.
Find the comments.