Which technical buying signals matter, and which mislead
Open any sales tool and you will find a long list of signals: funded, hiring, new executive, mentioned a competitor, visited a page. A long list makes you busier, not smarter. You end up with 80 accounts that each have "something going on" and no way to rank them.
Here is a stricter test. A signal earns a place on your list only if it changes one of three things: whom you call, what you say, or whether you call at all. If it changes none of them, drop it. This article sorts the signals that pass that test into three groups: timing, fit and blockers.
Three kinds of signal
| Kind | The question it answers | Examples |
|---|---|---|
| Timing | Why this week and not next quarter? | A new leader, a funding round, a launch, a migration visible in job posts |
| Fit | Would they use what I sell? | Tools named in job posts, public repos, engineering blog topics |
| Blockers | Should I skip this account? | A requirement you can't meet, a preference to build in-house, a budget freeze |
Most "intent" lists mix the first two and leave out the third. The third is where you save the most time. Skipping a bad call costs you nothing. Making it costs you the hour and some credibility.
Timing signals
Timing signals say something changed. None of them says the company is ready to buy. Treat each one as a reason to ask a question, not as a prediction.
A new leader
New leaders often review tools and teams early, and many don't. The signal is stronger when the leader used your kind of product at a previous company. They already know the category and may arrive with opinions about it. Look for the start date and the previous employer in the announcement or the company's own post.
A funding round
Money means there is budget to spend and pressure to grow. It does not tell you what they will spend it on. Use it to decide how soon to call, and use fit signals to decide what to say.
Hiring for the role that owns the problem
This is one of the best timing signals for a technical sale, because a company pays for headcount only when a problem is real. If you sell reliability tooling, the first reliability engineer posting is worth a call. Read the posting. The list of duties often describes the problem in the company's own words.
A launch or a migration
A new product means new systems to run and watch. A migration shows up in job posts that ask for experience with both the old tool and the new one. Both mean the team is making decisions about tools right now.
Incidents on a public status page
A run of outages shows pain. Be careful with it. Opening a call with "I saw you had three outages" sounds like a gotcha. Use it to shape a question about how they handle incidents, not to criticize.
Fit signals
Fit signals tell you the account looks like the customers you serve well. Public technical sources give you plenty:
- Job posts that name tools. Someone wrote the tool down as a requirement. That tends to be more reliable than a directory that says a company "uses" something.
- Public repositories. Dependency files show which libraries and clients a team uses. Recent commits show which projects are alive.
- Engineering blog topics. A post about debugging slow queries tells you what the team worries about. A post about rewriting a core system tells you where the effort is going.
- Filings, for public companies. Annual reports describe how a company sees its risks and where it plans to invest.
- The status page vendor. A company that runs its own status page for its own customers cares about uptime. The vendor behind it is also a hint about the tools they like.
One fit signal is a hint. Two separate ones are something you can build a call on.
Blockers: three questions to ask before you call
A blocker means a good-looking account is a poor use of your week. Check these before you spend time on the rest.
- Do they need something you don't have? Look at the company's trust or security page, its job posts and its customer list. If they sell to a regulated buyer, they may require a certification from vendors, such as a government cloud authorization. If you don't hold it, the call goes nowhere, however good the fit.
- Have they decided to build it themselves? A new leader who prefers building in-house, an internal tool described in an engineering post, or a repository for something in your category all point this way. You can still call, but your question changes from "Do you need this?" to "What would make buying better than building?"
- Is it a bad quarter, and are you the most expensive choice? Layoffs, a cut forecast or a cost-saving memo change what a team can buy. If you are also the priciest option in your category, the odds fall. Check the news and filings for these before you reach out.
Each of these is a question you can answer from public sources in a few minutes. Write down the answer and the date, like any other signal.
Read the age of every signal
A six-month-old post is history, not news. Every signal needs a date, and the date decides how you use it. A working rule, not a law:
- Weeks old: recent enough to mention on a call.
- Months old: useful background. Ask a question about it. Don't state it as current.
- Older: treat it as a lead to confirm. Look for something newer before you rely on it.
- No date: treat it as the oldest of all until you find one.
Dates also protect you from your own memory. A signal you saw "recently" may be older than it feels.
Turn one signal into one opening line
A signal is only useful once it changes the first thing you say. Two examples, both about invented companies:
Example 1: Harbor Ledger (invented)
Signal: A job post on Oct 6 for the company's first staff reliability engineer. Main duty: design the on-call rotation.
Weak opener: "Congrats on the growth! We help teams like yours with monitoring."
Stronger opener: "I saw you're hiring your first staff reliability engineer to own on-call. Is that role meant to fix who gets paged at 3 a.m., or something bigger?"
Example 2: Brightwave Labs (invented)
Signal: A new vice president of engineering started in September. Their announcement names the previous company, which ran on your category of tool.
Weak opener: "Congrats on the new role! Do you have 15 minutes?"
Stronger opener: "At your last company you ran a team on this kind of tooling. Are you planning to keep that approach at Brightwave, or start fresh?"
Both stronger openers end in a question. They claim only what the source says and leave the rest open. That keeps you from stating a guess as a fact.
Where Repclose fits
Repclose looks for fit and timing signals in public sources such as job posts, GitHub and filings, and it links each one so you can check it. A plan's Why now section holds the timing reasons, Green flags lists the signs of fit, and Risks holds what could stand in the way. Each point shows its source links with the publication date where one is available, and the word "undated" when there is none.
Accounts you choose to watch are rechecked every week. Repclose does not tell you an account is ready to buy. It gives you signals and sources, and you decide which ones matter for your product.
The sample brief shows how a finished page reads. When you want your own accounts checked, start here. The research method in the first article shows where signals fit in a full account brief.