How to Build an Inbound Meeting Workflow That Identifies the Buying Committee and Helps You Close the Deal (with Cal.com, Clay, HeyReach, and Instantly)

Everyone in the sales and marketing space talks about speed-to-lead. Get qualified leads, more meetings, talk to them fast, and ensure an excellent lead conversion rate. They're not wrong. Responding to inbound interest quickly matters.

But what happens after someone books a meeting with you? How do you ensure you convert leads? How do you route leads to the right rep? How do you find the other decision makers involved?

For most B2B sales teams and small business owners who do everything themselves or work with a 1-person marketing and sales team, the answer is not much.

A calendar notification pops up after the lead completes your scheduling process. Your SDR or BDR will then have to pull up the prospect's LinkedIn five minutes before the call.

They scan the company's homepage, try to remember what the prospect's company does, and walk into the meeting hoping they'll figure it out as they go.

That's not a process. That's improvisation. And if you're selling anything that costs more than a few hundred bucks a month, improvisation is going to cost you deals.

TL,DR: the entire inbound meeting workflow

Here's a snap view of what this entire process and workflow should look like. Keep in mind, the final engine is always different depending on your business and ICP. This is more a general version of it should look like.

How most teams waste their best inbound leads by showing up to calls unprepared

So what you do with the time between that booking and the actual call determines whether that meeting turns into pipeline or the polite "we'll think about it and get back to you."

What you do with the other people at that company also matters. We are talking about the ones who didn't book the meeting but will absolutely influence the buying decision. It determines whether that pipeline turns into revenue.

Here's the thing that should bother you. Single-threaded deals (where your rep only talks to one person at the company) close at around 5%, according to data from Gong.

Multi-threaded deals with five or more stakeholders engaged on the other hand close at 30%. That's a 6x improvement. Those numbers come from Gong's analysis of 1.8 million opportunities.

So we don't think the question is whether you should be multi-threading. The question is whether you can afford not to. And the answer to "we'll do it manually" is that most reps simply don't have the time. Which is exactly why we automate it.

That's where the Inbound Meeting Workflow comes in. It's a system we build at Nebor that takes every inbound meeting from booking to a fully enriched, multi-threaded opportunity automatically.

By the time your rep walks into the call, they know everything about the prospect's company, they've already started building relationships with other stakeholders, and the path to a closed deal is dramatically shorter.

This piece is going to walk you through how we build sales automation systems like this from the ground up. We'll cover the why, the tech stack, the specific workflow, and how each tool plays a role.

Inbound Meeting Workflow: from your meeting booking platform to a fully researched, multi-threaded sales opportunity

Let's get into the actual workflow. We'll walk through each step in detail, including which tools we use and why, so you can understand the logic well enough to build this yourself or adapt it to your stack.

Step 1: Understand and be clear on the information you are going to need to close

Before we touch any tools, we get clear on what your sales rep actually needs to know to close the deal. This sounds obvious, but most teams skip it entirely, and that's why they end up with surface-level enrichment that doesn't change how the conversation goes.

For a discovery call, sure, knowing the prospect's title, company size, and industry is enough to ask the right opening questions.

But if you want to walk into that call ready to close, you need to understand a few specific things.

What does the company actually do, and what's their business model?

Who are their customers?

What's their tech stack, and does it create any natural urgency or compatibility for your product?

Have they raised funding recently, and if so, what are they likely spending it on?

Are they hiring for roles that signal a problem your product solves?

What has the specific person who booked the meeting been posting about or engaging with on LinkedIn?

The goal is simple. Your rep should never walk into a call and ask the prospect to tell them about their company. That question tells the prospect you didn't do your homework and it can easily be a dealbreaker.

Step 2: Someone books a meeting through Cal.com and their data automatically lands in Clay

So the first thing we do after setting the Cal.com meeting booking interface your prospects will see is to connect Cal itself to Clay through webhooks.

When a prospect books a meeting through your Cal.com link, Cal fires a webhook. This webhook carries all the booking data. The person's name, email, company, the meeting type they selected, any custom fields you've set up on the form, and the meeting time.

We catch that webhook and that booking data creates a new row in a Clay table automatically. No human touches it. No one copies and pastes from a calendar invite. The moment someone clicks to confirm their booked meeting, the workflow starts running.

We like Cal for this because it's open-source, highly customizable, and its webhook support is rock-solid. You can add custom fields to your booking forms (like company name, role, or how they heard about you) and all of that data flows through to Clay.

Most setups would stop here with a quick enrichment and a Slack notification. That's fine for a starting point. But you can go much further.

Step 3: Clay enriches the contact with everything your sales rep needs to know (and more)

This is where we use Clay's enrichment power to set Clay up to collect every data point your rep will need before the meeting.

We layer multiple enrichment providers in a waterfall sequence so that if one source doesn't have the data, the next one tries. For contact data (verified emails, phone numbers, LinkedIn URLs), we use providers like LeadMagic, Findymail, FullEnrich, and Hunter.

For company data (size, industry, tech stack, funding history, recent news), we pull from sources like Apollo, BuiltWith, and Clay's native integrations. For LinkedIn activity data on the prospect, we use Clay's native LinkedIn scrapers.

The waterfall approach is the only way to get consistent 85%+ enrichment rates instead of the 40-50% you'd get from any single tool.

Step 4: Clay + LeadsFactory.io identifies the buying committee at the prospect's company so you can multi-thread from day one

So immediately after enriching the primary contact, we have Clay identify other stakeholders at the same company who are likely part of the buying committee.

We do this by using Clay's people search capabilities combined with LeadsFactory which uses LinkedIn data to find colleagues who match titles and roles that typically influence purchase decisions.

What makes LeadsFactory so great is the title doesn't have to be the exact match for it to find the person or the people you need. It's AI powered and understands context to automatically search for the right people even if the title you gave doesn't match.

For example, if your product is a sales automation tool and the person who booked is a VP of Sales, we'd also want to identify the Head of RevOps, the CRO, the VP of Marketing (because they care about pipeline), and possibly the CFO (because they care about cost-per-lead).

We don't reach out to all these people on day one. That would be chaos, and it would probably annoy the person who booked the meeting. There's a sequence to this.

But having these contacts identified and enriched before the first call means your rep can reference specific people during the conversation.

Step 5: Clay generates a sales dossier and pushes it to your team before the meeting

While the multi-threading campaign gets ready to launch, we prompt Clay to compile everything it gathered into a structured sales dossier. This is the document your rep reviews before the meeting.

The dossier includes a summary of what the company does and who they sell to, recent company news and signals, the prospect's LinkedIn activity and anything notable they've posted or engaged with, tech stack data relevant to your product, and a list of the buying committee members the workflow already identified along with their roles and contact details.

That last part is very important. Your rep walks into the call knowing not just everything about the person they're meeting with, but also the broader org they'll need to sell to.

We push this dossier to your team through Slack, your CRM, or as a PDF attachment to the calendar invite. The delivery method depends on how your team works, but the point is the same. Your rep has zero excuse to show up unprepared.

Step 6: HeyReach sends LinkedIn connection requests to buying committee members so you start building relationships across the account

Now we move into the multi-threading execution. Once the buying committee has been identified and enriched, it's time to start building relationships with these people. And LinkedIn is the natural starting point.

We use HeyReach for LinkedIn outreach because it's built for exactly this kind of scaled, multi-sender automation. It integrates natively with Clay, which means leads flow directly from your Clay table into HeyReach campaigns without any CSV exports or manual imports.

Here's an example of how we set up the LinkedIn multi-threading campaign.

The primary contact (the person who booked the meeting) gets a LinkedIn connection request from the rep who's running the meeting. The message is personalized and references the upcoming call, which usually drives a higher acceptance rate.

The secondary contacts (other buying committee members) get connection requests from other team members. A VP of Sales might send to other VPs, an AE might send to peers, and so on.

Spreading the outreach across senders mirrors how a real human network grows and avoids the "everyone is being approached by the same person" pattern.

By the time your rep is on the call with the primary contact, two or three additional stakeholders have already accepted LinkedIn connections from Nebor. When the primary contact loops them in later in the cycle, those people already have context.

Step 7: Instantly.ai runs a short email sequence to buying committee members that complements the LinkedIn outreach

LinkedIn is one channel. Email is another. Using both together is how you create the kind of multi-touch presence that makes your company feel bigger and more established than a single cold email ever could.

After the LinkedIn connection requests go out through HeyReach, we trigger a short email sequence through Instantly that targets the same buying committee members. This is not a five-email drip campaign with heavy pitches.

It's one or two emails, max, and they're simply designed to add value and build familiarity.

The first email is typically a soft, value-driven touchpoint. Something like sharing a relevant case study, a blog post, or an insight that would matter to someone in their specific role.

If the Head of RevOps is on the list, send something about CRM automation or data quality. If the CFO is there, send something about ROI on outbound spend. The goal is awareness, not pitching.

Email sequencing through Instantly handles deliverability, inbox warming, and rotation, so the multi-threading campaign doesn't burn the domain you actually need for sales. We wrote a full breakdown on email deliverability if you want to go deep on that piece.

Step 8: Response-based routing creates different paths depending on how each stakeholder reacts

Most workflows stop after sending the messages. We don't. Once outreach goes out across LinkedIn and email, we build conditional routing based on how each person responds or doesn't respond.

If someone doesn't reply to the email but accepts the LinkedIn connection, we push them back to HeyReach to start a LinkedIn conversation. The message picks up where the connection request left off, but goes slightly deeper.

Maybe it asks a question related to their role, or shares something specific about their company that Clay surfaced. LinkedIn conversations tend to be more casual and have higher response rates than email for this type of warm outreach.

If someone replies positively to the email, great. We send them a LinkedIn connection request to expand the network and maintain an additional channel.

If the primary point of contact goes dark later in the deal, you now have an email thread AND a LinkedIn connection with another stakeholder. That's insurance.

If someone doesn't reply to either channel, we don't push harder. We add them to a long-term nurture list. Maybe they see your company's LinkedIn ads down the line. Maybe they get a quarterly insight email.

The point is we keep the door open without being annoying. Some of these people will become relevant later when the deal moves forward and they get pulled into the evaluation.

If someone responds negatively or opts out, we respect that immediately. They're removed from all sequences. No exceptions. Burning a bridge with a potential committee member can kill a deal just as fast as losing your primary contact.

This routing happens automatically through webhooks between HeyReach, Instantly, and Clay.

When a response event triggers in HeyReach (connection accepted, message received) or Instantly (email reply detected), that event fires a webhook back to Clay or n8n, which updates the lead's status and triggers the appropriate next step. No manual sorting or anyone checking spreadsheets. The system handles it.

Why multi-threading at the inbound stage is so much more effective than doing it later

Most sales training teaches multi-threading as something you do midway through a deal. We are sure you've probably heard the typical "once you've built a champion, start expanding." That advice isn't wrong, but it's slow.

When you start multi-threading from the moment a meeting is booked, three things happen that wouldn't happen otherwise.

First, you build familiarity before it matters. By the time your rep has the discovery call and the prospect starts socializing your product internally, those other stakeholders have already seen your name.

They've connected on LinkedIn. They've read an email or two. When your champion mentions you in a meeting, the response isn't "who is that?" It's "yeah, I've heard of them, they reached out to me too."

Second, you shorten the sales cycle dramatically. Most deals slow down or die in the late stages when the procurement team or the finance team gets involved without context.

They ask questions your champion can't answer, they push back on pricing because they have no perspective, and they introduce friction.

When those stakeholders have already had touchpoints with your company before the deal hits their desk, the process is much smoother.

Third, you create resilience across the account. Champions leave companies. They get reassigned to new projects. They go on parental leave. Single-threaded deals collapse when this happens. Multi-threaded deals don't, because you've built a network across every department in your buying committee.

If your deal depends on a single person and that person leaves, you're done. Multi-threading from day one means you always have backup channels. If your main contact goes dark, you've got three or four other people at the account who know your name.

Tech stack: Cal.com + Clay + HeyReach + Instantly (and how each tool plays its part in this workflow)

Let's recap the role of each tool so you can see how they fit together. Keep in mind that the tools are not set in stone. It always depends on your business and what tools you already have. This is purely for example purposes for this article.

Cal.com is the entry point. It captures the meeting booking and fires a webhook with the contact's information.

We like Cal.com because it's open-source, highly customizable, and its webhook support is rock-solid. You can add custom fields to your booking forms (like company name, role, or how they heard about you) and all of that data flows through to Clay.

Clay is the brain. It receives the webhook from Cal, runs enrichment across multiple data providers, identifies buying committee members through LeadsFactory.io, compiles the sales dossier, and triggers the multi-threading campaigns.

It's also where the conditional routing logic lives, so when responses come back from email or LinkedIn, Clay updates the lead's state and decides what happens next.

HeyReach is the LinkedIn execution layer. It handles connection requests, follow-up messages, and the multi-sender campaigns across your team. Its native Clay integration means you don't have to do CSV exports or manual setup for every campaign.

Instantly handles the email side. Deliverability infrastructure, inbox warming, sending throttles, response detection. It plugs into Clay through webhooks the same way the other tools do.

n8n is the glue. It connects Cal.com to Clay, routes webhook events between tools, handles conditional logic, and makes sure data flows where it needs to go without anyone touching a spreadsheet.

So, here what the whole thing should look like:

Hire Nebor to Build the Inbound Meeting Workflow for you

If you're technical and you have the time, you can absolutely build this yourself. Start with the Cal.com to Clay webhook connection. Get your enrichment waterfall set up. Then add HeyReach and Instantly one at a time.

Test each piece individually before connecting them. Start with 10 meetings worth of data, verify the enrichment quality, and then scale.

But most sales teams don't have the bandwidth to build, test, and maintain a system like this while also running their actual sales process.

The workflow we described here touches multiple tools, multiple API connections, conditional routing logic, and ongoing optimization. It's not a weekend project.

That's what we do at Nebor. We build these systems so your team doesn't have to. We handle the Clay setup, the enrichment waterfall configuration, the HeyReach and Instantly integrations, the response routing, and the ongoing maintenance.

You get a sales infrastructure that runs on autopilot and keeps getting better.

We don't rent you a service you can't control. We build it inside your accounts. When we're done, the Clay tables, the automations, the integrations, everything lives in your accounts. You can run it yourself, modify it, or bring us back to expand it. That's how it should work.

If you want to skip the trial and error and get an inbound workflow like this running for your team, book a 15-minute call and we'll scope what it would take for your business specifically.