<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Whatsup folks? - Medium]]></title>
        <description><![CDATA[We’re on a mission to help you and your team bring your network in one place to get things done - Medium]]></description>
        <link>https://medium.com/folkhq?source=rss----661ca27397eb---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Whatsup folks? - Medium</title>
            <link>https://medium.com/folkhq?source=rss----661ca27397eb---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:39:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/folkhq" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Bringing back the “Personal”​ in Personal CRM]]></title>
            <link>https://medium.com/folkhq/bringing-back-the-personal-in-personal-crm-9cfd93ca4731?source=rss----661ca27397eb---4</link>
            <guid isPermaLink="false">https://medium.com/p/9cfd93ca4731</guid>
            <dc:creator><![CDATA[Simo Lemhandez]]></dc:creator>
            <pubDate>Fri, 15 May 2020 08:47:14 GMT</pubDate>
            <atom:updated>2020-05-15T08:46:05.977Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/931/1*toJAsn7Yc2cXbD0hSAOL8A.png" /><figcaption>Superpowers for contact management</figcaption></figure><h3>The Personal CRM’s anti-manifesto</h3><p><em>TL;DR: One-size-fits-all solutions don’t work when it comes to contacts. Contacts are multi-layered, living objects. And the relationships each one holds is unique. With Folk, we’re creating a flexible framework to turn contacts list into a productivity tool the way that works for you.</em></p><h3>Your network is your net worth</h3><p>It’s common wisdom that your network is your net worth. Relationships are your most valuable asset: opportunities, introductions, partnerships, PR, hiring, fundraising — to name just a few — can be unlocked by activating your network. So it comes as no surprise that the search for a solution to better manage relationships is so widespread.</p><p>In short, the way people currently manage their network is short-term. They only turn to their network to answer their immediate needs. This approach yields few results: the lack of a comprehensive, deliberate effort to maintain relationships is at fault. Could technology be the answer to better track interactions across multiple channels and better nurture relationships? Perhaps. Folks keep asking Twitter about the mythical Personal CRM. The pain is so real they even try bootstraping homemade solutions using a combination of Zapier, Notion, or Airtable. Is the personal CRM really the silver bullet to end networking woes?</p><h3>Why you shouldn’t look for a Personal CRM</h3><p>If the idea of a Personal CRM is appealing on a hypothetical level, no one wants to track relationships like data on a spreadsheet. Or dictate their reach out through if-this-then-that style logic. Or send automated “happy birthday”, “congrats on the new job”, or “it’s been one year since we last spoke” messages to their networks. The Personal CRM, considered in the cold light of day, simply isn’t the answer as it will compromise on the depth of your relationships</p><ul><li>Contacts aren’t simple data points. They are multi-layered objects. The full spectrum of contact-related information includes: contact details, background, job, last interaction, and a handful of topics that they are relevant for (like expertise, School alumni, or Friends in SF). Spreadsheets can’t render this complexity.</li><li>Contacts are a living data object. Relationships grow through interaction. A static list of emails, phone numbers, and names that is disconnected from your communication channels is of little use, as are native address books on your phone. Spreadsheets aren’t designed to be multi-directional. And they can’t possibly keep up with real life.</li><li>Your network is unique. Your relationships are unique. There is no single way to manage a network. Or even a single way to manage a relationship. With little customization, spreadsheet — or an improved “Personal CRM” — is not fit for purpose.</li></ul><p>Trying to capture the complexity of contacts using generic software is a near impossible task. Contacts aren’t neat and orderly. They can’t be fit into columns. They can’t be stored in a static repository. And they can’t be managed in a one-size-fits-all solution.</p><p>But it gets worse… The truth behind the phrase “Personal CRM” is multi-faceted. Every single person has their own idea of what an ideal Personal CRM should be and should do. The buzzword hides many different needs — like <a href="https://twitter.com/rrhoover/status/1181727165185810432?s=20">here</a>, <a href="https://medium.com/swlh/my-homegrown-personal-crm-87dffbcf54d7">here</a> or <a href="https://jamesonstartups.substack.com/p/the-peculiar-case-of-personal-crm">here</a> — that no single product could possibly address.</p><h3>Getting personal</h3><p>Before anything, a Personal CRM needs to be, well, personal. The way you manage your relationships is unique. No one wants their social interactions to be dictated by the tool they use. Pre-defined workflows are a no-no.</p><p>Second, a Personal CRM is the anti-CRM. What sales people are looking for when setting up a CRM is to make sure their sales process are framed with very clear steps to be rigorously followed by all their teammates. But when it comes to managing your personal network, the last thing you need is a single, funnel-like approach to contacts.</p><p>So we decided to build Folk unlike existing tools — whether it be spreadsheets or an actual CRM:</p><ul><li>Folk is contact-centric. We think contacts should be treated differently from other types of data, and built Folk around the challenges that are unique to manipulating contact data.</li><li>Folk is a dynamic repository for contacts. Contact management can generate a lot of data entry and repetitive tasks. We imagined Folk as a way to automatically synchronize your contacts in real-time from all your sources and activate your contacts through our integrations with your favorite communication tools. It was also natural to make Folk collaborative. We believe managing your network can be a multiplayer experience — so long as it doesn’t infringe on the individual’s privacy. We designed Folk to reflect this complexity, allowing users to share subsets of their network based on their needs.</li><li>Folk is fully-customizable. Folk is flexible. Instead of pre-defined workflows, systematic reminders, and standardized contact cards, we want to empower users to build an experience that makes sense for them.</li></ul><h3>Superpowers for contact management</h3><p>Our goal is to bring the power of a productivity tool, and automate what can be, while allowing our users to adapt folk to their specific needs. You’ll feel as if it was tailor-made for you to help you do more with your network, with less efforts. To give you superpowers.</p><p>In our vision, a personal CRM is only a start for our users. Networking can become a multi-player game, and it was then very natural for us to shape Folk with built-in collaboration features. It’s not simply a powerful personal CRM designed for you, we go further and we’ve built a contact management solution for your team.</p><p>The challenge is real, and we’re putting all of our efforts towards building the best contact management experience ever made. If you’d like to apply to our closed beta, <a href="http://folk.app/personal-crm/#shapeit">you can request priority access here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cfd93ca4731" width="1" height="1" alt=""><hr><p><a href="https://medium.com/folkhq/bringing-back-the-personal-in-personal-crm-9cfd93ca4731">Bringing back the “Personal”​ in Personal CRM</a> was originally published in <a href="https://medium.com/folkhq">Whatsup folks?</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A story of contacts and comebacks]]></title>
            <link>https://medium.com/folkhq/a-story-of-contacts-and-comebacks-9b9e64ac9609?source=rss----661ca27397eb---4</link>
            <guid isPermaLink="false">https://medium.com/p/9b9e64ac9609</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[personal-crm]]></category>
            <category><![CDATA[contact-management]]></category>
            <dc:creator><![CDATA[Thibaud Elziere]]></dc:creator>
            <pubDate>Wed, 06 Nov 2019 15:01:35 GMT</pubDate>
            <atom:updated>2019-11-06T15:01:35.527Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xzpoMj69eujL2qBTvCC9yg.png" /></figure><p>Contact managers are among the most commonly installed apps. Hundreds of millions of instances exist on nearly every phone, PC or Mac. Yet nobody uses them, except as address books when looking for a phone number or email. This is something of a paradox: it’s a product that everyone has, but that nobody needs.</p><p>So, why are we convinced that there is an opportunity in reinventing the contact manager? We believe that a network is one of the most important assets both for individuals and for organizations. But we think that extracting value from a contact book requires it to be organized, up-to-date, and to make it easy to activate contacts. Current contact managers are dead contact lists unable to deliver this value. Our ambition is to enable individuals and companies to tap into their network’s value by turning their contact book into a smart and actionable database of contacts.</p><h3>Humble beginnings</h3><p>It all started as an internal tool custom-built for our needs at eFounders. Back in 2013, we realized that one of our greatest assets as a studio was our network and we developed, with François and Vianney, a tool to help us manage it collaboratively. ContactX — as we called it — was little more than a shared address book for everyone of eFounders to connect their contact sources and share their network. Contacts could then be organized into groups — which we used for investors, journalists, pilots, and candidates. We also implemented campaigns — defined as a subset of contacts intended to be actioned — the advancement of which could be tracked through a Kanban view.</p><p>ContactX ended up becoming the hub for our network and our secret weapon to grow and activate it. Finally, in 2017, we decided to open it up as an independent project. We partnered up with a team of brilliant entrepreneurs — Noe and Ronan — and built the first public version of the product for over a year. Folk was born. However, it wasn’t long until we decided to put the project on hold: after several months and many attempts to get pilots on board, Folk still hadn’t reached product market fit.</p><h3>Key learnings</h3><p>With the benefit of hindsight, there are two main reasons why Folk failed the first time.</p><ul><li>First, faulty product design. Folk worked like a shared address book which fit our needs at eFounders perfectly — we work in a small, high-trust environment — but didn’t work for other kinds of organization. Very few people were willing to automatically share their contacts, even in a small group.</li><li>Second, wrong go-to-market strategy. The design of the product induced a top down strategy. Folk had to be deployed within a team or an organisation. However, when it comes to productivity software it’s always complicated to find the right person internally to implement it.</li></ul><p>After putting the project on hold, we kept the landing page up with a message warning visitors that we wouldn’t be giving access any more and that the product wouldn’t be maintained. Despite that, we continued to get a lot of leads coming from the website, watching the screencast, and insisting for access. It was very frustrating for us to not be able to open the product to those who requested it — however doing so would have been impossible without a proper product. We continued using it internally, but temporarily closed off all external users.</p><p>A year later, motivated by the constant flow of people asking for access to a dead product and inspired by the rise of a new wave of bottom-up productivity tools like Notion, Airtable, Superhuman or Slite, I decided to try again. I started to rethink the application from the ground-up and have worked during a few weeks wire-framing a brand-new Folk. Once again, I started looking for a CTO. I found Cyril who started coding the new version from scratch in June.</p><h3>Rebooting Folk</h3><p>We didn’t just flip the lights back on onto the old product, we completely redesigned the way Folk works:</p><ul><li>First, we built Folk for individuals first. When you start using Folk, you’ll import your contacts from your own sources to unify your network in one place. Then, you can create groups of contacts and decide which of these groups you share with the rest of your team. It might seem like a small detail, but it completely shifts our way of addressing the market: starting with individuals instead of organizations.</li><li>Second, groups help organize your contacts. Whether they are personal or shared groups, they can be modified and viewed by members who have access to it — creating a collaborative object, like pages in Notion, channels in Slack, or Inboxes in Front.</li><li>Third, Folk is more than just an address book. We’ve thought of it more as a productivity tool to be used every day when you action contacts. That’s how we came up with the notion of “views”. A view can be derived from a group to make it actionable — like a Kanban view, a calendar view, or a database view. A view is a visual representation of a contact list geared towards action. Our table view provides a database representation of a list of contacts with the possibility of adding custom fields. Our Kanban view provides a flow representation. The whiteboard view gives a spatial representation. An org-chart view represents a hierarchical structure. And our calendar view allows for a time-based visualization. These views turn Folk into a contact-centric application for a large range of use cases.</li></ul><p>This redesign is instrumental in helping Folk reach an audience that will start using the software for themselves, and then use it in their organization for many different use cases.</p><p>But it’s still a bet. Even though we’re already using the new Folk for eFounders, we still haven’t put the products in the hands of a large numbers of users. We have thousands people waiting to become pilots — and should have a better idea of whether we’re delivering the value we want pretty soon.</p><p>If you’re looking to get the most out of your network and experience first-hand our new approach to contact management, <a href="https://www.folk.app/#truestory">you can sign up to our beta</a>. The Folk beta is on invitation-only, for now 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b9e64ac9609" width="1" height="1" alt=""><hr><p><a href="https://medium.com/folkhq/a-story-of-contacts-and-comebacks-9b9e64ac9609">A story of contacts and comebacks</a> was originally published in <a href="https://medium.com/folkhq">Whatsup folks?</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>