Lessons in Competitive Comms from the Plaid-Stripe Kerfuffle

Now that the dust has settled on the Plaid-Stripe thing (initial news and its HN discussion, retraction, response from Stripe), I wanted to take up Shreyas’ call to his Twitter Super Followers to learn lessons from this episode, not as a form of criticism of Plaid OR Stripe, but simply as practice/exercise in second order thinking.


This sort of “competitive comms” recurs throughout history - Slack vs Microsoft Teams, Apple vs IBM, Sourcegraph vs GitHub. If you are at all successful at working on something valuable, expect competition, and expect to have to handle it gracefully in public.

I found this a very useful exercise and figured I would write stuff down as a reference for myself. This isn’t armchair quarterbacking - I view this as something I might have done - so I am eager to “review the tape” so to speak.

Likely Outcome

Assuming the facts of the matter were accurately represented by Zach (seems unlikely now), he could have backchanneled his complaints to Patrick first, who from all appearances could have shut down this program if it were truly tainted by bad faith. Misuse of confidential information would have been enforceable under NDA as well. Either of these could have led to a private settlement that was ruled out by public tweeting.

In the extremely likely chance that he was not going to have any impact (such as Stripe publicly reversing course/shutting down its launch) then all he was going to do was just tweet words to a small group of extremely-online Twitterfolk. In that case, he should have tried to go for a humorous take, highlighting Plaid’s strengths (from being in this game longer), rather than starting drama that would have gone nowhere and just reflected badly. Highlight the differences, not the similarities, on things the buyer cares about.

For a “funny” take on being cloned I like thinking about how Ricky Gervais talks about the US version of The Office.

Bad Look

The actual “bad look” here is that Plaid seems to be admitting they disclosed way too much valuable information during the interview process.

  • This could have been covered by NDA, which is certainly enforceable if the facts of this case were true
  • But it also points to a certain naivete/laxness in disclosure - the best way someone put this was “if you disclose too much info to an interviewee that’s a you problem”

Playing victim as CEO isn’t strong leadership.

(Other words used to describe this were: “lack of maturity”, “not being intentional”, “optics of CEO attacking a PM”

Second Order Effects

Most of these have to do with induced paranoia.

  • Future partnerships with Stripe are now less likely. Future partners of Plaid may also hesitate.
  • Executives who may work on adjacent/competitive products in the past/present/future are less likely to interview with Plaid
  • Plaid employees get distracted? and become much more suspicious of interviewees/generally paranoid in bizdev/partnerships
  • Future acquirers/investors in Plaid get worried about how easy it is to clone

The “loss” by Plaid (because Stripe had the last word) also further eroded confidence in Plaid’s leadership.

Less interesting arguments

There were some responses I did not agree with:

  • You shouldn’t acknowledge a competitor: It’s Stripe. Not some no-name company. Still, I acknowledge that some part of this is true - it presents Stripe’s product as viable competition
  • Demonstrates fear of Stripe: I don’t know about that. Generally I defend people’s right to tweet whatever they want (within bounds of professional behavior) and be personally relatable. You’re allowed to complain without being read as “fear”… but perhaps you have less room to complain if you run a $13b startup.

Tagged in: #pr

Leave a reaction if you liked this post! 🧡
Loading comments...

Subscribe to the newsletter

Join >10,000 subscribers getting occasional updates on new posts and projects!

I also write an AI newsletter and a DevRel/DevTools newsletter.

Latest Posts

Search and see all content