Building a Working Network That Actually Survives Real Life
Most people treat contact exchange like a numbers game. Collect business cards, add LinkedIn connections, send generic follow-ups. Then wonder why nothing ever comes of it. I stopped doing that about six years ago when I was managing supplier relationships for a mid-size logistics operation and realized half my "network" was just digital clutter nobody remembered. The core issue is that exchanging information without a clear context for why it matters turns every contact into noise. A properly maintained contact list is not a Rolodex of names and phone numbers. It is a structured record of people you have a functional relationship with, including what you know about them, what they know about you, and what you last discussed. That distinction matters more than anyone admits.The Practice Of Making Contacts And Exchanging Information
The practice itself is straightforward if you strip away the networking-event theater. You identify people relevant to your work or interests, you have a direct conversation with them, and you immediately capture the key details in a system you will actually use later. The part everyone skips is the immediate capture. You do not remember the third thing someone mentioned about their current project three weeks from now. You need to write it down while it is fresh, in a format that lets you search it later.
I used to rely on CRMs built for sales teams. They were terrible for this purpose. They force you into rigid fields and pipeline stages that have nothing to do with genuine professional relationships. I switched to a simple tag-based system in Obsidian about three years ago, and it handles the workload better than any custom CRM I have seen people build. Each contact gets a markdown file. The front matter contains structured data: company, role, location, source, and tags. The body contains free-form notes about conversations, interests, and follow-up items. Tags let you filter across everything at once. A single person can be tagged #logistics, #supplier, #chennai, and #potential-partner simultaneously. That is where the system beats a spreadsheet. Here is the workflow I actually use, not the polished version people post on blogs. When you meet someone new, you get their contact details immediately. Email is better than a business card. Cards get lost. Business cards are a nostalgia prop at this point. After the meeting, within the same day, you create the note. You write the basic details at the top and then jot down whatever stood out during the conversation. Not everything. Just the specific details that make this person different from every other person in your field. The projects they are working on, the problems they complain about, the people they mention by name. These are the anchors that make a follow-up email possible months later.The follow-up is the second most neglected part of the entire process. Send a brief message within forty-eight hours referencing something specific you discussed. This takes thirty seconds and separates you from ninety percent of the people who never follow up at all. Do not send a generic "great meeting you" template. Reference the concrete topic. If you talked about a supply chain bottleneck at their company, mention that. If they mentioned an upcoming conference they are attending, ask how it goes. Specificity signals that you were actually paying attention.
I ran into a real problem with this a while back. I was maintaining contacts across multiple industries and my note files grew to over four hundred entries. Searching through tags became slow and unreliable. I had people with similar names, outdated roles, and no recent interaction history mixed together with active relationships. The system was collapsing under its own weight. The workaround was relatively simple but forced me to restructure how I thought about contacts. I introduced an explicit status field to each note: active, dormant, or archived. Active contacts are people I have spoken to in the last six months. Dormant contacts are people I have not reached out to recently but still might need. Archived contacts are people whose role or company has fundamentally changed or who are no longer relevant. Once a year, I run through the dormant and active lists and either advance or archive them. This cuts the searchable surface area down to maybe eighty genuinely useful contacts instead of four hundred noisy ones. One counter-intuitive thing about contact management that beginners miss is that having too many active contacts is worse than having too few. A network of two hundred active relationships requires maintenance that scales non-linearly. You cannot realistically keep meaningful conversations going with more than fifty people at any given time. The rest become background noise. I learned this the hard way when I tried to maintain a broad tech industry network and ended up sending hollow check-in emails to forty people, which damaged my credibility with everyone. Now I keep my active list capped around sixty and let the rest sleep or die. Another nuance people overlook is the difference between transactional and relational contacts. Transactional contacts exist for a specific purpose: a vendor you need, a contractor you hired once, a client you are currently serving. Relational contacts exist because you genuinely enjoy working with them and want to stay connected regardless of immediate utility. Your system should handle these differently. Transactional contacts need structured data: contract dates, payment terms, service scopes. Relational contacts need personal context: family mentions, career aspirations, opinions you discussed over coffee. Mixing these up produces awkward follow-ups where you ask a vendor about their kid's birthday or ask a friend about invoice status.There is also the question of where you store this information. Email alone is insufficient because it is unstructured and hard to search reliably. Spreadsheets are rigid and kill the narrative quality of your notes. Dedicated CRM tools are expensive and over-engineered for most professionals. A local knowledge base with markdown files and tags is lightweight, searchable, portable, and free. If you prefer cloud storage for sync purposes, Obsidian with a git remote or SimpleNote with bulk editing both work adequately. The tool does not matter nearly as much as the habit of immediate documentation.
Get the Full Details
