A founder opens LinkedIn on a Tuesday morning and sees 40 notifications. Two comments. Eleven reactions. A few profile views. One note from a recruiter.
He spends 20 minutes deciding which ones deserve a reply. He answers the loudest one. Then he closes the tab.
Nothing comes of it. By Friday he has a full calendar and no new conversations with buyers.
The problem wasn't effort. It was the unit of analysis. He read 40 people. He should have read 4 companies.
That shift, from reading signals one person at a time to stacking them by account, is the difference between a notification queue and a pipeline view. I've watched founders skip it for years, usually because LinkedIn never shows them the account view in the first place.
Why Single Signals Mislead Founders
A like is an event. A purchase is a decision. Those live at different altitudes. Treating the first as a down payment on the second is how founders end up with an engaged audience and an empty pipeline.
The reason is structural. B2B purchases are group decisions. Gartner's research on the B2B buying journey puts a complex purchase at about 11 stakeholders, and finds buyers spend just 17% of their journey meeting with potential suppliers. Each stakeholder has a different question. Each one can say no.
On a 2,000-follower account, a strong post produces maybe 8 to 12 engagers. Grouped by company, those 8 to 12 usually collapse into 3 or 4 accounts. That gap is where the signal lives.
So when 1 person at a target account likes your post, you're watching 1 node inside a group of 11. You have evidence of interest. You don't have evidence of demand. That's 9% of the committee, and 9% is not a trend.
The standard response makes this worse. Most founders DM the person who liked the post. That person is rarely the buyer. They're usually the practitioner who found the post useful, and they can't move budget. You spend your best outreach energy on the person least able to help, and you learn nothing about whether the account is in market.
I've tested both readings on the same week of activity more than once. The account view wins every time.
Account-level reading fixes the altitude problem. Stop asking who engaged with you. Start asking which company keeps showing up, through different people, inside a short window.
That question has a better hit rate. I've run this read on accounts at every stage, from seed to public, and the pattern holds. A buying committee researching a problem doesn't coordinate its LinkedIn activity. It just behaves like a group thinking about the same thing at the same time.
What the Account Signal Stack Is
The account signal stack is one timeline of every observable interaction from a single company, read as a pattern instead of a list of events. It has three layers, and each answers a different question.
The identity layer answers who. Every engager, commenter, profile viewer and sharer gets mapped to a company domain. This part is bookkeeping. It's also where most founders quit, because LinkedIn shows you people, not accounts. I've watched people build the sheet once and never open it again.
The sequence layer answers what order. Who showed up first. Who came back. Whether the same post reached two people at one company within a few days. A share inside a company is a stronger event than a like, because sharing requires a small act of advocacy. Someone forwarded your thinking to a colleague.
The timing layer answers how fast. Signals that cluster inside 30 days describe an active conversation. Signals spread across 8 months describe slow familiarity. Both have value. Only one is a reason to reach out this week.
The Stack Rule
Read the company, not the person. One person is curiosity. Two people is distribution. Three people inside 30 days is a buying committee forming in public, and it's the highest-value pattern available to a founder who publishes consistently.
This is where the VCO equation earns its keep. Visibility times time times relevance equals opportunity density. Account stacking is how relevance gets measured at the level where money moves. Your content can reach 1,000 people and be relevant to none of them. It can't be relevant to a buying committee unless it reaches more than one member.
The Three-Person Rule
Three is the smallest count that can't be explained by coincidence.
One person at a company engaging is normal in any market where you publish. Two people is interesting, and it usually means one forwarded something to the other. Three distinct people at one account inside 30 days needs a shared reason underneath.
Not all three people carry equal weight, and I rank them differently depending on the account. The economic buyer gets 3 points. The practitioner gets 2. The skeptic gets 2. A share gets 3, because it costs the sharer something. The practitioner tells you the problem is real at the working level. The skeptic, usually someone in finance, security or operations, is the most informative of all. Skeptics don't read content about problems they don't have.
I don't count likes anymore. I count accounts with 3 or more signals, because that's the number that turns into conversations. When all 3 types show up inside 30 days, you're not looking at an audience. You're looking at an account that already started an internal conversation, and your content got pulled into it.
In practice, an account with 11 people in the buying group behaves like this. A practitioner likes a post on a Tuesday. A second person views your profile on Thursday. Nine days later, a third shares the post with the note that this is what they've been saying in planning. Under volume reading, that's 1 like, 1 view and 1 share. Under account reading, it's 3 of 11 stakeholders moving in the same direction inside 2 weeks. Same events. Different decision.
How to Build It in Twenty Minutes a Week
You don't need a platform, a dashboard tool or a new hire for this. It needs one recurring block of time and one place to write things down. Here's the version that works for a founder who already publishes.
- Pull the week into one list. Post engagers, commenters, sharers and profile viewers. LinkedIn gives you all four, in four different places. Put them in a single sheet with name, title, company and date.
- Group by company domain. Sort by company, not by date. This is the step that changes what you can see. The sorting is mechanical. The insight shows up in the clustering.
- Score each account on three counts. Distinct people, distinct interactions, and whether a share happened. Three people is tier one. Two people plus a share is tier one. One senior title with a repeat visit is a watch item, not a priority.
- Write the account line before the person line. Before any outreach, write one sentence describing what this company appears to be working on, based only on the pattern. If you can't write that sentence, you have a fan, not a signal.
- Route the account, not the lead. Hand the cluster to whoever owns outreach with the thread and the context attached. A single contact record loses the reason the account mattered, which is the pattern across three people.
The loop takes about 20 minutes a week once the sheet exists. The real cost is the discipline of not replying to a like in the moment. That's exactly what most founders do instead of building the view that would tell them whether the like matters.
What Changes When You Route Accounts Instead of Leads
The best case study on this pattern is also the most quoted one on this site. A single LinkedIn post generated a $340,000 enterprise deal. The post never mentioned a product. It named an expensive problem in the language buyers use internally.
What usually gets left out is the account mechanics, and that's the part I care about most. A VP of Sales read the post and didn't like it or comment on it. She sent it to her CEO with a note saying this was exactly the problem they were dealing with. The CEO read it, followed the account, and spent three weeks working through the content backlog before reaching out.
That's a two-person account stack inside a single week, and it was invisible in the notification feed. Neither person produced a like you could count. The most valuable signal in the whole deal was a share that happened in a direct message, where no analytics tool can see. What made it findable was the follow-on behavior: repeat visits and backlog consumption from the same company over three weeks.
"The most valuable signal in the deal was a share that happened in a direct message where no analytics tool can see it."
I've seen the same pattern in the 4-opportunity quarter that came from 6 months of consistent publishing. One of those four traveled through a board member who shared a post with a portfolio CEO. That CEO rarely opened LinkedIn. The signal moved through the network, landed at an account, and produced a warm introduction weeks later. Read as separate events, none of it was remarkable. Read as an account pattern, it was the clearest demand signal of the quarter.
There's a line to hold here, and the tactic fails without it. Account stacking is for prioritization, not for the opener. Telling a prospect that three of their colleagues read your posts is surveillance. It ends the conversation before it starts. The pattern tells you which account to prioritize and what problem to lead with. The conversation still has to be about their work, not your tracking.
The Two Failure Modes
Most founders who try account-level reading fall into one of two traps, and I've made both. They stay at the volume layer and call it signal work, or they over-read the stack and treat three clicks as a forecast.
- Success measured by total likes and impressions
- Outreach goes to the loudest engager
- Pipeline counted in conversations started
- Resets every Monday with a new notification queue
- Every signal is a separate event with no history
- Success measured by accounts with three or more signals
- Outreach goes to the economic buyer with context
- Pipeline counted in accounts opened and advanced
- Compounds week over week as account history builds
- Every signal is a data point on a single company timeline
I've made the over-reading mistake myself. The trap is subtler than it looks. Three people from one company engaging in a month is a strong pattern. It isn't a purchase order. It tells you the account is thinking about the problem. It doesn't tell you budget exists, that a project is funded, or that timing is right. The stack changes where you spend attention. It doesn't replace qualification.
Keep the read honest by pairing it with the decay curve, which is the other half of how I read an account. Every signal has a half-life. A cluster that goes quiet for 6 weeks is no longer a live pattern. That's why the thirty-day window matters, and why a stack that stopped growing should move down the list instead of sitting at the top on the strength of an old month. The signal decay curve and the account stack are two halves of the same read. One tells you how fresh the interest is. The other tells you how wide it runs inside the account.
The Thirty-Day Account Signal Test
I keep 1 number in front of me: accounts with 3 or more signals. If you want to know whether this changes anything, run it for 30 days before you change the rest of your routine. That's the test I give every founder I work with. The test is deliberately small.
Week one: establish the baseline. Build the sheet, group by company, and count how many accounts produced two or more distinct people in the last thirty days. Most founders are surprised by how few there are, and by how many of those accounts they have never contacted.
Weeks two and three: publish to the committee's shared problem. Pick the problem all three roles would recognize, then write one post that names the cost of getting it wrong. Don't write to the practitioner, the buyer or the skeptic. Write to the thing they argue about internally. That's the relevance variable in the VCO equation doing real work instead of sitting in a framework.
Week four: review movement, not volume. Count the accounts that moved from one signal to two, and the ones that crossed three. Then open exactly one conversation, at the account with the strongest cluster, with an opener about their problem and no reference to your tracking. The goal is 1 account opened, not 10 messages sent.
My rule is simple. Open 1 account, not 10. A 10-message day feels productive. A 1-account week builds pipeline.
What Good Looks Like After Thirty Days
You should be able to name 5 to 10 accounts that are actively reading, rank them by how many people inside each one has appeared, and explain what each account appears to be working on. That's the difference between a notification queue and a pipeline view. The view is the asset. The posts are the fuel that keeps it current.
I've run this test with founders in SaaS, services and recruiting, and every one reports the same thing afterward. The account view was always available. They never looked at it because LinkedIn presents people. The platform is built to show you individuals, so the burden of aggregation falls on you. 20 minutes a week is a small price for seeing what your buyers already do.
I've watched a 3-person cluster turn into a meeting in 6 days. I've also watched a 40-like week produce nothing. The difference was never effort. It was whether the founder could see the account forming underneath the noise.
Visibility creates opportunity, but only if you can see where the opportunity is forming. The account signal stack is how you see it while there's still time to matter.
Want the account view built into your week?
The 90-Day Executive Visibility Program pairs a publishing system with a signal operating rhythm, so the right accounts surface while they're still deciding. You leave with the sheet, the scoring rule and the routing habit.
Book a Strategy Call →