I admittedly don't know a lot about this situation beyond what I've read in the news the past day or so. However, isn't it the case that Zenefits is simply building an interface on top of ADP's payroll data? And, from what I've read, it seems like they did this without following the proper procedures (did they write some kind of web scraper?). So if that is the case, ADP has every right to block them. If the situation was reversed and a large company was scraping a startup's data to integrate into their own platform, the outrage would be directed quite differently. So Zenefits is plugging into ADP's data, not paying them for access, not following the proper procedures to get access, and selling an interface on top of that data for a 10% fee, and then they complain that ADP blocked them?
EDIT: Also, all of their press releases sound very immature.
ADP has for years, and still does, allow bookkeepers, accountants, and HR services firms similar to Zenefits to access client accounts via 3rd-party administrative logins that clients themselves set up in their payroll.
The way this works is that you, as an ADP client, call them up and says "hey, I've asked my HR firm, XYZ-HR, to manage my payroll. Can you create an account for them to access my payroll system?" ADP creates this account, and XYZ-HR then handles all the payroll admin work going forward -- adding employee, terming them, inputting hours worked, managing deductions, etc.
This is how this has worked for years, and it's how thousands of companies do this via ADP. Even today, as an ADP RUN client, you can call in and add any third-party person you want as an admin to your payroll system -- as long as it's not Zenefits. ADP has marketing materials that describe this feature, both for companies and HR / bookkeeping / accounting firms. This is how Zenefits was accessing client's payroll, and doing so in order to take on all the administrative work related to payroll that you don't want to handle. We weren't "hacking" anything. We were doing this at our customers' request, with their full knowledge of what we were doing, and ADP set up these accounts with @zenefits.com email addresses, knowing it was Zenefits.
There is nothing improper about how we were doing this.
> There is nothing improper about how we were doing this.
You were automating it, weren't you?
With bookkeepers, accountants, etc. the login and work done on the system was manual. It was an actual person doing it.
In your case, a computer is doing it instead.
Virtually every site out there, from Facebook to Twitter, prohibits the use of bots and scraping. Not surprising ADP isn't a fan.
What is surprising is that you feel you're entitled to access their system however you want? It's their system. If they want to prohibit bots and allow only people, that's their biz. If you think ADP is full of it, create your own system with a public API and put them out of business.
> you can call in and add any third-party person you want as an admin to your payroll system
So they will create an admin account for a person - a single, human individual.
> In addition, Zenefits’ method of extracting data from ADP’s RUN system via “screen-scraping” put excessive demands on ADP’s servers, potentially impacting service delivery to the entire client base.[1]
If you weren't using the API, and instead were having a machine log in to access the data, that is pretty much the definition of scraping. There is a difference between a person using an admin account setup for them to log in and perform a certain set of actions and hundreds of accounts setup for the purposes of continual automated logins.
How many requests did you make? Do you rate-limit your queries to the rate of a human-being (maybe 1 click every couple of seconds)? Do you only login to one or two accounts at a time?
I still don't see a valid reason why any company (big or small) should have to invest resources in supporting a third-party that wants to use its data in an unsupported manner. Of course you can argue that they allowed it in the past, but an entire business shouldn't rely on unsupported access to something without the assumption that it could disappear at any minute.
Parker when are you going to do another ADP post on Zenefits blog that contains more information on the email that was forwarded to you? I think it could be helpful if you included the screen shots and additional materials the ADP sales rep mentioned. If that was not included in the email, than it seems like that rep knew you would get that email, and you were just baited.
Zenefits has their users create an admin ADP user. Then zenefits uses those credentials to pull whatever data they want. They chose this route instead of working with ADP's third party system (without giving any justification as to why). I might sympathize if ADP's API access was severely limited or extremely expensive, but it appears as if Zenefits made no efforts to go this route.
I'm not speaking for or against Zenefits and their methods, but ADPs API is severely limited and extremely expensive. I worked with their Dealer Services division when I was at a startup in the automotive space and ADP had one of the worst crafted APIs I have ever seen. I made a comment about it on an earlier Zenefits post, but the gist was that the "stable, production API" was a constantly moving target that changed without notice or reason.
I believe we had incurred over $50,000.00 in fees before we ever reached the testing stage or purchased the right to use the API (that license is on a client by client basis, too). That $50M number was fees directly to ADP, and does not include our own payroll and expenses.
We were completely bootstrapped and started with about $70M in the bank, yet we were still able to complete that integration. I can't see how a company with over $500MM in funding[0] couldn't unless they were prohibited by ADP.
From having been there, ADP is a tin-plated nightmare to work with for third-party API access. I'd do the exact same thing in Zenefits' shoes; ADP knows that they are eternally your competitors and will screw you at the first opportunity.
Of course, ADP doing that is not doing right by their customers, but who cares, they're just cash cows.
How smart is it to build a business on unofficial, non-API access to a system maintained by someone who you know will try to screw you at the first opportunity? If I were ADP, I'd probably be intentionally breaking those types of integrations just to make it clear that they don't intend to hamstring themselves by supporting interfaces they never published. The fact that it's someone in a market they intend to enter is gravy.
The "right way" is hard, and more likely to be painful, certainly. But when you're done, you're done. The "forgiveness>permission" way has the added downside of your customers getting screwed too, and likely considering litigation.
By "worked" I meant building a large business. Sort of undeniable that Uber has done that. That lawsuit, despite its merits, isn't going to slow Uber's growth a whit.
Every U.S. business gets sued, it's the American way.
As a gratuitous side-note: despite the HN hatred of Uber (and I'm one of those who hate the company), the company wouldn't be growing if it's users didn't love it. Unlike the other most hated companies--mainly airlines, cable TV providers, and telecomms--users of Uber can very easily choose to use an alternative. Here in NYC, the alternative--flagging down a yellow cab--is probably actually easier to use than Uber, yet everyone I know uses Uber anyway. They're clearly doing something right.
I didn't say it was smart, but it's smarter than ADP's jokestore of an official API. If you want to talk to ADP customers--and, functionally, you very close to need to talk to ADP customers--those are your options.
I feel like maybe the point of my post was not completely clear, though: this would not be a problem, and Zenefits would not be doing this, if ADP was good (not good in the "not poor software" sense, but good in the moral sense). And we should be faulting ADP for not being good to its customers, not Zenefits for trying to bring good to ADP's customers.
ADP's customers are most definitely not the third party developers, though. Because of that, you can't really conflate the two into one argument. ADP can easily be "good" to their customers while still having shitty APIs. Hell, plenty of companies do this every day, why should we chastise ADP for running a business?
Furthermore, a profit-seeking corporation shouldn't really be on the moral scale to begin with. At best, they should be amoral, that is, not involved at all in morality. Their primary goal is, and should be, to earn more money, not to be good citizens of the world.
"At best, they should be amoral" companies are still run by people. So, your suggesting people should be amoral while at work, which is an unusual stance.
I would suggest it's much better for the laws and regulations to be setup so a profit seeking company would end up being a net benefit. But, suggesting company's should for example try and corrupt politicians in the name of profit seems rather dystopian.
Amoral != immoral. Amorality simply is the disconnection from morals, while immorality is doing something you know to be wrong. The people in charge would still be held by their own moral beliefs, but we should not be chastizing or congratulating companies for their moral contributions because, as an entity, their decisions should not be based on morals, but on profit.
You just contradicted yourself. If the CEO is unwilling to start a bio-weapons division duo to lack of profits or excessive risks etc then that's a amoral decision because morality did not come into play. However, if they decide it may be profitable, but it's immoral so there not willing to go there then the company was constrained by morality.
PS: It could even go the other way where a CEO feels it's his patriotic duty to aid his government so he wants to start a bio-weapons division. The point is not the choice the point is why it was made.
> Furthermore, a profit-seeking corporation shouldn't really be on the moral scale to begin with. At best, they should be amoral, that is, not involved at all in morality. Their primary goal is, and should be, to earn more money, not to be good citizens of the world.
You are very much mistaken. Society provides the corporation with legal protections and recourses as a fictive person with the understanding that the corporation's existence betters the society, betters the people within it. When this agreement is breached, the society can--though, unfortunately, rarely does, due to globally weird veneration of toxic behavior as "just business"--destroy it. (It has happened before. It should happen more often.)
And let's be really real for a sec: if you look at the stretch of history, neutrality is effectively tacit support for bad behavior. And from a practical perspective, a call for "amorality" is tacit support for immorality.
A public web app is an official API, thought primarily to be used by humans; but built using protocols such that it's possible to be used by programs on behalf of humans ..
You access HN by your browser, the same as Zenefits' customers accessed ADP services indirectly ..
The point is where to put the line between what's a good allowed access, and a bad too-much-indirection access
Ok, let's for the sake of argument grant you that a public web app is an official interface (I'm not saying API because it's not a "programming" interface). The implied contract is that humans will continue to be able to use the web app to access the functionality it's intended to provide. Anything in the HTML is an implementation detail, not part of the contract, and is subject to change at any time, so long as the contract (human usability) is still fulfilled. This is why web scraping is such a risky proposition: the structure of the page may change at any time without violating the implied contract of a human being able to use the web page.
The existence of a public interface usable by humans (a web app) does not in any way imply the existence of a machine-usable protocol for accessing that same functionality. If you infer one, you do so at your own risk. By the same token, the existence of a machine-usable interface that is not public does not imply a contract that it will continue to exist.
If you build your business on an imagined contract, be prepared to have a bad day when the other "party" to the non-contract "violates" it.
> The existence of a public interface usable by humans (a web app) does not in any way imply the existence of a machine-usable protocol for accessing that same functionality.
Is that non-implication better for consumers? For people?
If it makes money, it's smart. If you're filling a need, then it's smart. Sure it's risky but anything you do has some measure of risk. It might even be worth it because it's risky and therefore less competition.
Exactly. If I found a third-party company that was having users create accounts on my systems for the purposes of pulling data out, I would block it too, probably more quickly than ADP did.
Imagine if a company asked for your Google password instead of using the proper API channels. I don't know many users who would do that.
> Imagine if a company asked for your Google password instead of using the proper API channels
This would be more like creating a new Google Apps email account for someone, and allowing them to use it to (e.g.) manage things on your Google Drive (by sharing a group folder with them).
How many companies hire a 3rd party accounting / HR firm (or person) to manage their bookkeeping? How many of them create an ADP admin account for these people so that they can manage payroll? How is this that much different than Zenefits?
Ironically, this is typical in the Google Apps reseller arena, where the reseller creates your domain for you under their Google account, and then also administer it using a superadmin account they create in your domain for that purpose.
It actually works a bit differently; it's not all scraping. People enter data into Zenefits and then it populates that data into ADP.
I don't think the issue is as cut and dried as the typical web scraping situation and I wonder how HN readers feel about this kind of thing. The data belongs to the client. The client chooses to use both services. Should it matter how the client accesses their own information from the service? Are they required to use a web browser? Would you feel the same about them using their own wget script to automate interactions ADP? At what point does it become improper to access a service differently than that service wishes you to access it?
> Should it matter how the client accesses their own information from the service?
I don't think so either. Would people feel the same if a store banned wheelchairs? You can write a EULA however you want, but I don't think you should be able to enforce arbitrary provisions which harm customers and potentially violate the Americans with Disabilities Act. Probably this has nothing to do in practice with accessibility for disabled people, but it is related to accessibility and user experience for everyone.
(Disclosure: I write web scraping software... nothing related to this. Also I'm speculating about general circumstances, not individual companies, so please no libel lawsuits :)
>it matters at the point when you choose to build a business on the method of accessing a 3rd party service.
Why? They are having to pay them and then buy your services for data entry. This is no more unethical than hiring someone to do your banking for you.
Violating an EULA by doing this may be unethical, but in that case, it is violating the EULA that is unethical, not the general practice of providing a new interface.
Are accountants who access ADP on behalf of their clients doing something unethical? Does it matter if that accountant uses their own scripts or wget to access ADP?
> Improper access matters when you start using the service.
This is getting ugly. Going against a ruthless goliath should help garner public support, but the way they are doing it is very unattractive to me. And as someone currently evaluating payroll solutions for small businesses, I'll be steering clear of them.
Reading this story, the lawsuit story and in trying to keep up with this entire fiasco...
You end up feeling both sorry and a sour taste in your mouth for both companies. They're both obviously very good at "spin" and drumming up PR to win support of their audience.
I previously thought things would get settled amicably, out of court, with Zenefits saying "sorry", ADP saying "its okay" and the 2 companies settling on some decent structure to use ADPs API (or whatever thing they use for 3rd party access).
Now we are dealing with a situation where this is basically corporate-warfare hitting the "lala-land" of Silicon Valley.
Google, Apple, Microsoft and other tech companies generally have this corporate warfare amongst themselves and they also sometimes move in on other industries, catching those players off-guard.
With that in mind, and also the fact that Zenefits can no longer be classified as a startup - with +50 (or is it +100 employees) and a startup valuation of US$+4,5 billion - this is just another case of corporate warfare.
I shall now neither pity or care for either party of this story, because no matter how good the "spin" from each side is, this is just business as usual.
Any wall-street raider using HN may agree.
Edit: I'd also like to see how much longer this "post" stays as link number 1 on this platform, instead of getting "washed away" like yesterdays ADP link. Then we can also know for a fact that YC is actively pushing the agenda with their corporate interest in Zenefits (and proof that not all "good links eventually surface to the top", without someone pulling some admin-user strings at the top)
> With that in mind, and also the fact that Zenefits can no longer be classified as a startup - with +50 (or is it +100 employees)
Ha, because of all of the manual entry they have to do as of February 2015 Zenefits had over 500 employees. When the CEO went on TWiST just a week or two ago he said they were over 1,000 and hiring 100 new employees a month.
A vast majority of insurance brokers / providers simply don't have an API or even an easy way to send insurance information. It's surprising how many HR related tasks are still very manual in 2015 especially considering you should be able to offload everything minus employee relations and hiring in HR.
I believe that this is called a 'free market'. Also, called 'underestimating your competition'.
This common misconception that big companies are hide-bound dinosaurs is dangerous for any start up to hold. Most large companies are indeed oblivious, but some elephants - if you tweak them hard enough - turn around and stomp you.
Always respect your competition. Some of them may be smarter than you think.
Something I've noted about the Silicon Valley startup mentality, and I'm seeing in this discussion, is a lack of understanding of just how difficult enterprise projects actually are. The attitude is often that big companies work so hard for so long and spend so much on projects and still have crap, that they must be lazy and stupid. This is not at all the case. The enterprise is full of smart, hardworking, determined people - as good as Silicon Valley - and they still wind up with crap and failure most of the time. That's not a reflection on the enterprise, that's a reflection on the difficulty of the problems the enterprise tackles.
Like I told someone at a Silicon Valley enterprise/health meetup last year... if you saw a startup with $50M annual revenue, you'd think they're huge, right? I've worked on three different projects larger than that, and they're all small potatoes in their enterprises.
I had never heard of Zenefits but I've read the articles that have come across HN thus far. From the standpoint of a non-customer they come across as more consumed with proving a point than just proving they are better.
With all the attention why not try and turn the message into a positive one (highlight what you do and why it's better).
A positive message would give people who don't know you a reason to check you out and your existing customers confidence that you are competent to overcome the current situation.
Right now it feels like they are just trying to justify why they failed... even if the succeed in blaming ADP they still fail.
I think the whole thing stinks from both sides. Zenefits' blog post does seem to walk the narrow line between informing their customers and defaming ADP. Meanwhile, ADP files a defamation lawsuit then turns right around and releases their competing platform, which could damage their case (to my non-lawyer mind, so I could be completely off base there).
I can see merit in both parties' cases against the the other, but I can see a ton of shenanigans on both their parts as well.
How is what ADP doing (blocking access to their service from Zenefits so they can sell Opum), any different from what twitter does when it blocks services like meerkat from accessing their service when they want to build a business around periscope? I'm not saying that either organization (ADP or Twitter) is acting benevolently (obviously, they are both acting in a competitive manner) - I'm just trying to see if the two are acting in a similar manner.
As far as I understand Zenefits is doing both screen scraping and manual entry into the ADP systems and they may have never even talked to ADP. So instead of hitting an API directly where ADP may expect a large amount of requests Zenefits is hitting their normal website requesting hundreds or thousands of users every hour.
I would have blocked them too. It looks far too much like malice from the ADP side of things where it could be bot nets or something else versus a legit company.
In terms of Twitter blocking Meerkat - it's the same exact situation. What is different, though, is that Twitter didn't then sue Meerkat for defamation, when Meerkat complained after getting blocked.
1)Zenefits has always known this could happen or at least they should have. You have to play nice with ADP. Because if they don't work with you, you are dead.
2)Zenefits has a super young CEO who doesn't know what he is doing. Where is David Sacks in all of this? Isn't he the adult supervision here? Maybe he hasn't run anything at this scale before? Maybe he and his Yammer gang don't know how benefits and healthcare work?
3)What were the VCs who invested at $4.5B thinking? Any technical due diligence would have brought this up. You had to clear this as a diligence item before you put a dollar into the company.
4)The lawsuit is a shakedown. Its time for ADP to collect its dues. Its nothing more than that. I expect ADP to extract a huge premium and then play nice with Zenefits in an out of court settlement. Everyone will have a face saving PR release after that. But isn't it interesting that this happens after they pick-up their $500M round? I have heard rumors this was going to happen in September last year. ADP waited until now. What a pest.
4)Time for Parker to go and be replaced with someone who has run billion dollar software companies before. And that's not Sacks.
Frankly, the simple fact that there is a headline on the Zenefits site that says "ADP Begins to Roll Out a Zenefits Competitor" shows that they have seriously lost their focus.
I can understand that many people probably don't feel Zenefits is totally in the right in this dispute as a whole, but I struggle to see how you can dispute that ADP is being ridiculously two faced. I'm not sure how thinking ADP is better than Zenefits or that web scraping is bad or whatever people saying about Zenefits is relevant to the fact that ADP filed a lawsuit in federal court saying they're NOT making a Zenefits competitor and then sent out emails to customers saying explicitly that they ARE making a Zenefits competitor. Whatever else you think about this situation, that is obviously pretty screwed up.
I guess it really depends on what ADP's terms of service say. It is their site and service. Clients can choose to stop using them. The Zenefits teams seems very immature, maybe they should pivot and start offering more full services.
IANAL but I belive the stock advice when you are facing a lawsuit is to shut up about it. "We don't comment on matters under litigation" is the standard line, and for good reason.
This is pretty bad on ADPs part. But after reading the other HN discussion on this topic[1], it seems like this is a company destined for as fast of a fall as it rose. I hate to see big companies muscle out little ones, but I guess if you're going to rustle the feathers of so many, you're bound to make some powerful enemies.
It's interesting, because if Zenefits had already IPO'd they absolutely would not be able to take this approach. Too much shareholder risk. And this is just as much a David Sacks thing as it is a Parker thing. I have to believe after my 10+ years in Financial Services that David Sacks already disliked ADP from his PayPal days. Zenefits is going to lose this battle, but it's about the war.
Blatant FUD from Zenefits. ADP's new product is an online payroll/HR SaaS that integrates across its entire product line.
Zenefit's product is a glorified remote bookkeeping service in which you enter data into the Zenefits website and they re-enter it manually, and usually incorrectly, into the ADP website and scrape the results, usually incorrectly, so they can post a response several days later to your Zenefits account page.
One is a SaaS (ADP) and the other is a remote data-entry service (Zenefits). Completely different. It's hard to argue that Zenefits should even be considered a tech company, since most of their "integration" functionality is driven by manual human labor and not technology. At best, Zenefits is a data-entry service with a nice, shiny UI.
EDIT: Also...the new product is actually just an offshoot of an existing product that my firm has been using for nearly a year. The new product, Opum, is simply the small-to-medium business version of one of ADP's existing enterprise cloud payroll/benefits products. It even uses the same (new) interface as the enterprise product.
If they are so "completely different" then why would the ADP rep say:
> “We are coming out with a product to compete with Zenefits, a full service integrated online payroll and benefits solution.”
I can't seem to argue with Zenefits stance that they are being sued for complaining that their access was cut off in an attempt to kill them off while ADP launches a similar product... On top of that who is ADP to cut off access that their clients are paying for? It doesn't matter if a human logs in or a computer, the cost to ADP is the same. Here they are blocking access for no legitimate reason while launching a competing product. This whole things stinks and I think the smell is coming from ADP....
> I can't seem to argue with Zenefits stance that they are being sued for complaining that their access was cut off in an attempt to kill them off while ADP launches a similar product...
That's not their claim. Their claim is that the reason they were cut off was because of this product launch. They haven't presented any proof of this.
Simple fact is, the claim is coming from a company that has already made it clear they are doing things they should not be doing. They have the burden of proof. They have a mountain to climb.
Edit: As mentioned in the GP comment, this claim is also false:
"Within the same hour they filed suit, an ADP sales rep started selling a brand new Zenefits competitive offering — called “Opum” — to our shared clients."
> the claim is coming from a company that has already made it clear they are doing things they should not be doing
I'm troubled by this assertion. I know firsthand that ADP will actively fight attempts to integrate with them; their APIs are bad, poorly documented, and have reliability problems. Should somebody attempting to do well for the customer--and, yes, make some money, but it's not like Zenefits is inventing problems to solve--not do well by the customer first and foremost?
Like, from my perspective: forget ADP, forget Zenefits. Is this better for the customer?
> I'm troubled by this assertion. I know firsthand that ADP will actively fight attempts to integrate with them; their APIs are bad, poorly documented, and have reliability problems.
I'm sorry, but I've seen numerous comments to the contrary.
Regardless, that they have APIs and documentation, regardless of your opinion of their quality, only supports my assertion.
The word "simply" does not belong in the same sentence with "implement ACH".
Signed,
Someone who worked on ACH for nine years.
ps: I'm pretty sure they're trying to do just that. But you have to consider just how incredibly difficult ACH is - not just from a coding perspective, but from a regulatory perspective. Banking and accounting legal entities need created.
pps: ADP knows good and well that Zenefits is working on their own ACH implementation with their buckets of cash. This is a preemptive strike.
On a side note, can we name[0] these strategies just as they do with chess moves so that when someone says "pulled an XXXX", it encapsulates the move and references it. On a long run there could be a website which defines these and references all the previous attempts and responses. I think it would be very useful for founders/team when they are short of time and are brainstorming counter moves. Also perhaps we would internalize these patterns just as a GM does.
[0]: If there is already a resource I would like to know about it.
It stinks but this is why you don't form a company based around another company's product. You will either get bought by them or screwed over, and you often won't find out which one it is until it's too late.
> It doesn't matter if a human logs in or a computer, the cost to ADP is the same
In the response that ADP posted a couple days ago, they said that the traffic from Zenefits was several orders of magnitude higher than what normal customers were using. If that's true, then the cost could well be higher for them.
I just saw this for the first time, they are claiming while only .25% of users used Zenefits it was responsible for 25% of all traffic which if true is very damning.
ADP attorneys file suit accusing Zenefits lying about plans for competing products, and then mandate that they state a product is, in fact, competing? Then the blog post is exactly right.
I don't understand the product or companies well, however what you explain is exactly how I felt after reading their post. This kind of thing doesn't even need to be public, let alone posted on the company blog. Calling ADP out about their "corporate value" at the end was unadulterated mud slinging.
It's understandable that they're upset but they should work to keep these problems from spreading outside of their legal team and not get flustered with their competition. From the sound of it they've completely taken their eye off the ball for this distraction and it could easily pave the way for ADP to steamroll them competitively while they sop up their tears.
Yeah -- I'm having a lot of trouble having much sympathy for Zenefits here, not least because of the really moronic spam I've been getting from them recently. And the ______'s keep sending it via Google, so I can't even reasonably blackhole their mail.
I wish one of the YC tests for "how smart are these founders?" was "do you think spam is a good growth hack?"
A shame you're getting downvoted, as your point is relevant. AirBnB did this in the early days- spamming craigslist users looking for hosts (from female sounding email addresses on gmail-- sounds like the "spam from gmail" tactic is a YC "best practice"????)
To be honest, the obvious first growth hack is spamming... anybody can do it. Finding a way to leverage an existing audience without cheating or engaging in slimy behavior takes real thinking....YC companies doing this at some point starts to reflect on YC (And these are not the only two instances of this, it seems like every YC company does it to some extent.)
This strongly suggests that the shutoff AND the defamation lawsuit were part of a planned strategy - that they're deliberately goading Zenefits' notoriously outspoken CEO.
Which does not bode well for their lawsuit, but I don't think they're out to win that anyway.
I think you should give ADP more credit. Even if they don't have the best product, I would assume they would've foreseen competitors in the front-end benefits field and have adjusted their business plans long before this back and forth. Companies that have been in an industry for a long time can often see industry changes coming, even if they don't have the agility to react quickly.
"We call on ADP to stop making life more difficult for small business customers and live up to its corporate value: “integrity is everything.”"
See: Twitter, Facebook, and even Google. All of these companies have destroyed 3rd party companies by basically using them as a test base for new ideas and features and then directly competing (and many times, cutting off the 3rd party completely).
If you are going to base your entire company off of a 3rd party, you better have a plan B if they completely cut you off.
This isn't that situation - Zenefits didn't build their entire platform on top of ADP; they simply offered an integration for a portion of their customer base that uses ADP.
EDIT: Also, all of their press releases sound very immature.