3 ms·
> I don't know about this. How am I locked in? I think the article is referring to much bigger implementations - I'm just finishing up a 3,000+ employee implem
by ktr 14y ago
> I don't know about this. How am I locked in?
I think the article is referring to much bigger implementations - I'm just finishing up a 3,000+ employee implementation with all kinds of crazy things going on that cost my client an arm and a leg. To put it into perspective, the implementation took ~ 3mos to go-live for employees across almost all 50 states and another 2mos to fix the issues that cropped up during the first few payrolls. It's unlikely they'd be willing to switch anytime soon regardless of how unhappy they are up to this point.
- tatsuke95 14y ago>"I think the article is referring to much bigger implementations" Absolutely. I can imagine the kind of work an implementation like that entails. Maybe I misunderstand "lock-in". Nothing is preventing me from switching providers, since there is no reliance on proprietary measures anywhere along the line. Switching from one implementation to a different one is as easy as re-doing the labour (not that that is "easy", as you point out). But that's the bare minimum that I can expect to do anyway. I certainly can't have less work to do the second time.
- ktr 14y agoYes, I would agree with that statement as well. There is certainly nothing stopping us (nothing proprietary, etc.) other than a lot of work. But, to your point, it should be less the 2nd time around!