Key Takeaways
- The conversation is rarely where networking fails. Most advice optimises the twenty minutes of talking, then compresses everything after into one line about following up within a day.
- Write the context down before you leave the venue. Names survive a week. The reason you agreed to talk again does not, and that reason is what makes a follow-up worth opening.
- Replace "let's keep in touch" with a date. A vague agreement costs two weeks of email tennis. An agreed slot costs thirty seconds in the room.
- One record per person beats one spreadsheet per event. Event-based notes rot because you search by human, not by conference.
- Maintaining contacts, not collecting them, is what shows up in the research.
Most networking guides are written as though the hard part is talking to strangers. For consultants and small service firms, the hard part is the forty-eight hours afterwards, when a promising conversation turns into a name you cannot place and a favour you cannot remember agreeing to.
Why most networking advice stops working the moment you leave the room
The advice that currently ranks here is near-identical: be curious, ask about them, smile, have a short answer ready, follow up within twenty-four hours. None of it is wrong. All of it ends where the work starts.
A 30-comment thread in r/I_DONT_LIKE picks at why organised events feel worse than ordinary work conversations, the general read being that events compress the awkward part rather than remove it. That instinct has research behind it. A 2014 study in Administrative Science Quarterly found that networking undertaken for professional gain made participants feel physically unclean in a way that spontaneous relationship-building did not, and that lawyers who felt it most did it least and performed worse at work.
The discomfort compounds. If an event already feels transactional, every day a follow-up goes unsent raises the cost of sending it, because now you have to explain the delay too.
The second problem is capacity. A 20-comment thread in r/CRMSoftware describes the shape of it: client relationships tracked properly in a work system, personal and prospective connections quietly dropped. One half has a system, the other half has good intentions.
What a networking habit has to survive
Any approach that fails one of these rows will work for a month and then quietly stop.
| Requirement | Why it matters | What breaks without it |
|---|---|---|
Low effort at the moment of capture | You are standing up, holding a drink, with ninety seconds | Notes never get written |
RequirementLow effort at the moment of capture Why it mattersYou are standing up, holding a drink, with ninety seconds What breaks without itNotes never get written | ||
Context, not just contact details | A name and email is not a reason to write | Follow-ups read as cold outreach |
RequirementContext, not just contact details Why it mattersA name and email is not a reason to write What breaks without itFollow-ups read as cold outreach | ||
A committed next step | Intent decays fast on both sides | "Let's keep in touch" becomes nothing |
RequirementA committed next step Why it mattersIntent decays fast on both sides What breaks without it"Let's keep in touch" becomes nothing | ||
One place per person | You remember the human, not the event | Notes scatter across apps |
RequirementOne place per person Why it mattersYou remember the human, not the event What breaks without itNotes scatter across apps | ||
Survives a hundred contacts | Manual tracking collapses somewhere past fifty | The system gets abandoned |
RequirementSurvives a hundred contacts Why it mattersManual tracking collapses somewhere past fifty What breaks without itThe system gets abandoned | ||
Nine networking tips that hold up over a year
1. Choose events by who is in the room
Headcount is a poor proxy for value. Ask the organiser what the attendee mix looks like by role and company size, and skip anything that cannot answer. A chamber of commerce breakfast with forty owners of the firms you serve beats a conference of two thousand people mostly selling to each other.
2. Open on the room, not on yourself
The lowest-risk opener is a shared observation: the venue, the talk that just ended, the queue you are both in. It asks nothing and gives the other person an easy way in. Save your own introduction until it is requested, which usually takes under a minute.
3. Ask the question that costs them nothing to answer honestly
"What do you do?" produces a job title. "What is taking up most of your week right now?" produces a problem, and problems are where consulting work lives. The second question also gives you something specific to reference later, which matters more than it sounds.
Practise one question you can ask anyone in your market. One is enough.
4. Make your own answer repeatable by a stranger
The point of your introduction is not to describe you accurately. It is to be repeated correctly by someone who met you once, to a colleague you will never meet. "I help engineering consultancies fix the gap between winning work and billing for it" survives that relay. "I do operational transformation" does not. Test it on a friend outside your industry an hour later.
5. Write down the context before you leave the building
This is the tip that makes the other eight work, and almost nobody does it. Not the name, which you have on the card, but the three things you will need: what they are dealing with, what you said you would do, and what you noticed that a generic email would miss.
A voice memo in the taxi is fine. A line in your phone between conversations is better. What matters is that it happens before the next three conversations overwrite it. An 8-comment thread in r/smallbusiness on what networking produced for owners keeps returning to specific relationships rather than volume, and specificity is what you lose first.
6. Agree a specific next step, not a sentiment
"Let's keep in touch" is where most networking dies, because neither party has been given anything to do. Replace it with the smallest concrete thing that is genuinely useful: a twenty-minute call about the hiring problem they described, an intro to someone who solved it, a document you mentioned.
Specific beats warm. A 5-comment thread in r/BigLawRecruiting on follow-up messages lands on the same conclusion: the message that gets a reply references the particular thing that was discussed, not the fact that a conversation occurred.
7. Book the meeting while you are both still standing there
If you have agreed to talk properly, put it on a calendar now. Sending your booking link in the moment removes the availability exchange that otherwise eats two weeks and often ends in silence. The same link belongs on your digital business card, so handing over details and offering a slot are one gesture.
For a group that needs to find a common time, an appointment poll does the job without a thread. If you do end up writing the email, be concrete about how you state your availability and keep the meeting request to one decision.
8. Keep one record per person, not one spreadsheet per event
Event-based tracking fails because retrieval is person-based. Six months later you remember a face and a problem, not which conference you were at. A 10-comment thread in r/agencynewbies on how small agencies track contacts describes the tipping point well: once several conversations are live at once, the overhead of keeping them straight becomes the real cost.
Spreadsheets hold up to roughly fifty people. Past that you need something that files the conversation against the human automatically, which is the job a CRM for a small business does.
9. Automate the reminder, never the relationship
Scheduled nudges are the right use of automation here: a reminder before the call you booked, a prompt to send the document you promised, a task with a due date against the person. The message itself should still be written by you.
An 10-comment thread in r/CustomerSuccess on note and follow-up habits makes the distinction neatly: most of what gets dropped needed nothing more than a reminder, not a clever template. Mass-sent "touching base" sequences are the fastest way to confirm someone's suspicion that the conversation was transactional all along.
Tools that help, and where they stop
Your calendar and your notes app will carry you a long way. People reach for something else at the point those threads describe: more live conversations than memory holds, and a follow-up promise that has already slipped once.
meetergo is a Cologne-built scheduling and pipeline tool covering consulting, sales, talent acquisition and other verticals, and the consulting side is the relevant one here. What makes it fit this workflow is that the scheduling layer and the contact record are one system: when someone books for the first time, a contact profile is created automatically, and that person then carries a timeline of every meeting, past and future, including meetings from your connected calendars rather than only meetergo bookings. You can attach notes, tags and files to the contact, and set follow-up tasks with due dates against it. The consulting solution page reports 4,000+ IT consultants and advisors as users and around 35% more billable hours, with reminders cutting no-shows by up to 90%.
Two further pieces matter for networking rather than client delivery. The digital business card is on every plan including the free one, so the hand-over-and-book gesture does not depend on a subscription, and LinkedIn contacts pull into the same record set, which is where most post-event connections land. A mobile CRM covers the note before you leave the venue, and workflows handle the reminder sends.
| Plan | Price |
|---|---|
Free | €0/mo forever |
PlanFree Price€0/mo forever | |
Light | €9.90/mo |
PlanLight Price€9.90/mo | |
Suite (all apps included) | €29.90/mo (regular €34.90) |
PlanSuite (all apps included) Price€29.90/mo (regular €34.90) | |
Premium | €49.90/mo (regular €59.90) |
PlanPremium Price€49.90/mo (regular €59.90) | |
Enterprise (30+ users) | On request |
PlanEnterprise (30+ users) PriceOn request | |
Paid tiers come with a 7-day trial.
Where it stops. The contact record is built around booked meetings, so anyone you meet who never books has to be entered by hand, which is most of a conference. The free plan allows one linked calendar and one active meeting type, so the tracking layer in practice starts at a paid tier. And nothing here flags a relationship that has gone quiet: deal-level alerts exist for stagnant opportunities, but the reminder to call someone you have not spoken to since March is one you set yourself. If relationship decay across a large address book is your core problem rather than scheduling, a dedicated personal CRM will serve you better.
Mistakes that cost the most
Collecting instead of maintaining. The longitudinal research on networking and career outcomes in the Journal of Applied Psychology separates building contacts from maintaining and using them, and finds networking behaviour tracks with both salary level and salary growth across three years. The maintenance half is the half people skip.
Treating the follow-up as a formality. A message referencing nothing specific reads as a mail-merge, because functionally it is one. If you cannot name what you discussed, you did not do step five.
Pitching before you have a problem to attach it to. Describing your service to someone who has not said what is broken gives them nothing to say back. Ask first, then connect.
Letting the agreement outlive the memory. Eight days is long enough for both sides to lose the thread. If the next step is not booked in the room, book it that evening.
Going to events you cannot follow up from. Twelve conversations you cannot act on is worse than four you handle properly. Attendance is the cheap part.
How to choose a system for tracking your network
Three things decide this, and the answers differ by how much of your pipeline comes from relationships.
Where the conversation gets recorded. If notes live in a separate app from the meeting, they will drift apart. Prefer a setup where writing the note and seeing the next scheduled meeting are the same screen, whatever tool that turns out to be.
Whether capture happens on a phone. The useful note is written in the ten minutes after the conversation, standing outside. A system that requires a laptop collects nothing from an event.
How it behaves at a hundred contacts. Ask what breaks when the list quadruples. Spreadsheets break at retrieval, inboxes break at search, and tools without a per-person timeline break when you need a relationship's history rather than one thread. A consultant management system is worth a look if your delivery work and your network are the same people.
A fourth, if you work in the EU: check where contact data is stored and under which jurisdiction, because you are holding personal data on people who gave it to you at a drinks reception.
Turn the next conversation into a booked meeting
The cheapest improvement available is removing the availability exchange from the end of a good conversation. Set up a booking link, put it on your card, and send it while the agreement is fresh.
Start free with meetergo and have a working booking page before your next event. No credit card required. To compare tiers first, the plan breakdown lists what each includes, and the calendar link generator produces something usable in a minute without an account.
Booking + video conferencing in one tool.
Booking + video conferencing in one tool.
Frequently asked questions
What are the top five networking tips?
Pick events by attendee mix rather than size. Open on something you both just experienced. Ask what is occupying their week instead of what they do. Write down the context before you leave. Agree a specific next step and book it on the spot. The fifth is the one that determines whether the first four produced anything.
Is it true that 70% of jobs are found through networking?
Treat the figure with caution. It traces to a 2017 LinkedIn survey of roughly 15,900 self-selected members rather than a representative study, and the related claim that 85% of roles are filled through networking has no solid source at all. The better-evidenced statement is narrower: networking behaviour correlates with salary and salary growth in peer-reviewed longitudinal work. Networking matters; the round numbers are not measurements.
What are the three C's of networking?
There is no standard version, worth knowing before you build a strategy on it. The mnemonic circulates as clarity, consistency and contribution, sometimes with community swapped in. It is a coaching device rather than a research finding, and consistency is the only one of the three that reliably predicts anything.
How soon should I follow up after meeting someone?
Within two days, and the content matters more than the speed. A day-two message referencing the specific problem they described will outperform one sent the same evening that references nothing. If you promised something, send the thing rather than a note announcing it. Our guide to reminder emails covers the wording for a second attempt.
How do I network if I find events draining?
Reduce volume and raise the quality of capture. Four conversations you follow up properly beat twelve you forget, and small industry groups ask less of you than large mixers. The research on instrumental networking feeling unpleasant suggests the discomfort is widespread rather than a personal defect, so design around it.
Should I use a CRM for networking contacts?
Past roughly fifty live relationships, yes, because that is where manual lists stop being retrievable. Below that a well-maintained notes file is fine. The test is not the count but whether you can say what you last promised a given person in under ten seconds.
What do I do with contacts that go nowhere?
Leave them in the record with the context attached and stop actively working them. Someone with no need in March may have one in November, and the note explaining who they are costs nothing to keep. What you should not do is drop them into an automated sequence, which converts a dormant contact into an irritated one. If a consultation appointment becomes relevant later, the history is there.
