« swipe left for tags/categories
swipe right to go back »
Last week my friends at FullContact announced a new paid vacation policy and wrote a post about it titled Paid Vacation? That’s Not Cool. You Know What’s Cool? Paid, PAID Vacation.
FullContact will now pay an employee $7500 to go on vacation. The rules are simple:
- You have to go on vacation.
- You have to disconnect entirely (no phone, no email).
- You can’t work.
If that whets your appetite, take a look at the presentation about the new policy.
Hiring great people is intensely competitive in my world. While part of this is around recruiting, a bigger part is creating an environment where these great people can periodically disconnect and recharge their batteries. I love the creativity of FullContact’s approach to Paid PAID vacation. And yes – FullContact is hiring.
It’s 2012 and the “contact information problem” is getting exponentially worse. I’ve personally been struggling with this for 20+ years since I remember going from a custom database we built at Feld Technologies (in DataFlex) to Act! to try to manage the contacts across the company. While all the technology has changed, the problem has gotten substantially worse, as every web-based and mobile app now has some kind of contact info associated with it.
Today, there is no single authoritative contact record for an individual. I’ve been through a bunch of different iterations of technology around this such as SAML, FOAF, and Oauth. I remember Firefly and Passport. I’ve been involved in a number of companies who have tried to build “clean contact lists” and tried virtually every service I’ve ever run into. I’ve completely fucked up my address book more than once, especially as I tried to wire in data from other services that use Oauth or an email address to join data across web services. And yet we still have address blocks in emails, vcards, and crappy, incomplete, and incorrect data everywhere. And I still get referred to as Brad Batchelor in physical mail that I get from Wellesley College (which both Amy and I think is cute.)
Nothing works and it’s just getting worse. Fragmented data, incorrect data, changed data, duplicated data – it gets proliferated. All you need to do to see the core problem is look at the same data for a person in LinkedIn, Twitter, and Facebook. Multiple email addresses, lots of different contact info, time-based information that isn’t treated correctly, and huge errors all over the place.
That’s why we’ve invested in FullContact. They are on a mission to solve the world’s contact information problem. Imagine a unified address book in the cloud that has perfect information for every single person with a contact record of any type. This unified address book is continually updated, cleansed, enriched, and validated. It integrates with every web-based or mobile application that uses any sort of contact data, and it is available to every developer via an API.
This is a massive data problem. The team at FullContact is approaching it as such. It’s one where the machines do all the work and don’t rely on us silly humans, or the IT people, to change behavior and systems. For a look behind the curtains watch this short example from FullContact’s Identibase.
If you are a developer, FullContact’s goal is for you to use their cloud address book via their API. If you are an individual, you can use the FullContact cloud address book as your source address book. And if you are a business, you can finally get a unified contact management system across your organization without having to do very much. Data will automagically get cleaned up, enriched, de-duplicated, validated, and backed up, making it easily accessible in any context.
We’ve gone after the world’s contact information problem a number of times in a number of different ways over the years with different investments. We’ve never been involved in conquering it and it’s just gotten worse. This is the first time I feel like we are investing in the right approach to solve the problem once and for all.
Oh – and we love the team. If you want a fun view of why, take a look at From Basements to Brad Feld: The Story of 126 NOs and 1 Big YES.