Salesforce Acquires Quip: Who, What, and Why?

Share this article...



Quip set out on a mission in 2012 to end messy document maintenance in enterprises – and they’ve done just that, proudly announcing that they provide the “marriage of communication and content”.

The two founders of Quip, Bret Taylor and Kevin Gibbs, have an impressive set of experience between them, so it’s no wonder that Quip has grown in leaps and bounds, all the way to an acquisition by CRM giant


Quip can be likened to a love child of Google Docs and Slack – it’s easy to use, organised and has a slick UI.

Finally, after decades of mounds of content being separated from their relevant feedback/amendment discussions, we can breathe a sigh of relief. Content such as reports, marketing material and spreadsheets can be discussed and edited in a succinct, intuitive way and all in real-time.

Gone are the dark days of long email threads and the nightmare of version clashes!
The app is free for a team of up to 5 users, then paid as the team grows bigger. Once your company explodes, you can opt for the Enterprise level package.  



Quip caught Salesforce’s eye, and they quickly snapped it up for $750mil on August 1st.

Let’s face it – Salesforce Documents and the CRM Content features are the more… underutilised features.

Although there are a number of fantastic document generation tools on the Salesforce market, none can compete with the control and speed that Quip could potentially deliver. Attaching documents could now be considered a hassle in a world where Salesforce has streamlined pretty much everything else in our working lives.

It could take Chatter to the next level. Since it’s birth in 2010, it’s not received a lot of TLC – but that could be about to change.

Could Salesforce trying to wean themselves away from being dependant on Microsoft? Rumour has it it may be a dig at Microsoft’s core (Office 365).
Quip follows the Salesforce core themes of increased efficiency, visibility and accountability (feed tracking), so it’s clear now it was a no-brainer. I, for one, am definitely looking forward to testing out this neat addition when it finds its way into my org.

Add Comment