The FlowQ idea

A reason to buy leaves traces. The skill lies in reading the right two or three together.

This page explains the method behind FlowQ. It shows why a list of companies on its own rarely leads to a conversation, what we mean by a signal and why it takes several signals together to make a case. It also shows how an observation becomes a concrete task for your sales team. By the end, you should understand the idea well enough to ask any provider the right questions.

A signal is an observable event with a source and a date.
A single signal has too many explanations. Only two or three signals together make a case you can justify.
Meaning: what does this mean for this company, in relation to your offering? The inference is kept apart from the fact.
Sales task: whom you contact, how you open, and by when.

Why lists fail

A list answers a single question: who might be a fit for you? Industry, size, region, role. That is useful, but it is a question without a clock. Of the companies that fit on paper, most have no issue today to which your offering is the answer. Demand does not arise in an industry. It arises at a point in time, in a single company, for a specific reason.

This leads to three problems every sales team knows:

The order is down to chance. If you work through a list from top to bottom, you only reach the company with a need if it happens to sit near the top.
The first sentence has nothing to say. Without a trigger, all that is left is a pitch for your own product. The person you call hears a salesperson, not someone worth talking to.
Your competitors have the same list. Company attributes can be bought. Anyone who filters on the same attributes calls the same companies, with the same lines.

Probability scores that express purchase readiness as a percentage do not solve this either. They do not reveal what has happened at the company. If you do not know why a number is high, you cannot open a conversation with it.

What a signal is

A signal is an observable event with a source and a date that makes your offering urgent for a specific company. Every part of this definition has a job:

Observable. A signal is something that has happened, not something someone suspects. A company advertises a position, changes its management, applies for planning permission, wins a tender, opens a new site. “Interest” or a “mood of growth” are not signals.
With a source. Anyone can check whether it is true. A signal whose origin nobody can verify is a claim.
With a date. A trigger ages. A change of leadership is a reason to talk in the first few months. Later it is history, and the new priorities have long been set.
Urgent for your offering. The same event means different things to different providers. That is why a signal is never good or bad in general. It is good for a particular offering.

Attributes that do not change, on the other hand, are not signals: industry, headcount, legal form. They describe who is a fit. A signal describes why now.

Why one signal alone proves little

Anyone can find a single trigger today. A search engine returns open positions in seconds, a chatbot summarises press releases. If a single signal were the value, nobody would need help.

The problem: a single signal has too many explanations. A job advert can mean growth, or simply that someone has resigned. A new managing director may rebuild everything or leave everything as it is. Anyone who calls on the strength of a single signal is often wide of the mark and only notices during the conversation.

Every further signal from a different direction rules out explanations. Only two or three signals together make a case you can justify.

An example. A provider of shift-planning software sells to manufacturing plants.

A plant is looking for several shift supervisors. On its own, that can be normal staff turnover.
The same plant has brought a new production hall into operation. Now it becomes clear: this is about additional capacity, not replacement.
Recently, a new head of HR has taken over there. Now there is also a person who is new in the role and putting processes in order.

Together, a picture emerges: the plant is growing, reorganising its shifts, and a responsible person is open to new solutions. None of the three signals would have shown that on its own.

Which combination counts for your offering is a question for your market and your past deals, not for a search engine. This mapping is the real core of the work. It is built afresh for every client, and it becomes more precise with every piece of feedback from real conversations.

From signal to sales task

A signal is only the beginning. For it to become a conversation, two more steps are needed.

Signal: what has happened? The fact, with source and date. Nothing is interpreted here.

Meaning: what does this mean for this company, in relation to your offering? This is where inferences are drawn, and an inference can be wrong. That is why it never belongs in the same sentence as the fact. In the example: the plant is building capacity and has to reorganise its shifts.

Sales task: what do you do now, specifically? Three answers turn an insight into a task:

Whom you contact. Not the company, but the person who owns the issue. In the example, the new head of HR, and alongside them the plant manager.
How you open. The first sentence picks up on the trigger, not on your product. Someone who talks about the new hall is heard differently from someone presenting a piece of software.
By when. A trigger opens a window and closes it again. Once shift planning has been set up anew, the question has been answered, with or without you.

Without the third step, a signal ends up as an interesting piece of news that nobody follows up. Without the second, your team calls with a fact but no reason why it should concern the person on the other end.

Two questions you can ask any provider

Whether a provider works with signals or just with lists shows in two questions:

Which two or three triggers together make my offering urgent, and why these in particular? Anyone who answers by simply listing individual event types is selling hits, not cases. At FlowQ, this question comes at the start of every engagement. We answer it with you before the search is built.
What about this hit is observed, and what is your inference? Anyone who cannot separate the two cannot tell you when they are wrong.

What the idea deliberately is not

It does not guess intent from anonymous behaviour.
It does not replace the conversation. It gives it a reason.
It is not a ready-made catalogue of triggers that you buy once. Which signals count depends on your offering and changes with what your conversations reveal.

Where to go next

What happens to a signal before it reaches you is described under Signalradar. How signals become a continuous process, from target market to evaluation, is shown under Sales Operations. Which kinds of trigger exist and the industries they matter in is set out under Sales triggers.

Which signals make your offering urgent?

In an orientation call, we look for the first combination for your market.

Book an orientation call