Why this team looks for signals
Lead gen agencies are judged on meetings and blamed for black boxes. The fix is a system the client can inspect: which signal, which fit rule, which sentence, which approval.
TWL is that system. The tools share one system, so the repetitive capture and drafting can run without a new researcher per client, and it is still constrained. TWL Reach is the email and LinkedIn delivery. The client sees the evidence on the record.
Signals that matter here
The client’s buyers, not the agency’s
Watching: Sources the client’s market actually reads: competitors, jobs, keywords, launches.
A lead gen offer that reuses one LinkedIn search across clients is a static list with extra steps.
Competitor engagement in the client’s category
Watching: Comments that name a pain the client’s product addresses.
Keep the comment. The client should be able to open it. Read the signal page.
Roles that reveal the buying group
Watching: Job posts that name the tool, the pain or the team.
A hiring post is often a better brief than the client’s persona slide. Read the signal page.
Companies asking for help in public
Watching: Posts that ask for outbound, research or intros.
Respond to the ask. Do not bolt on a second pitch.
Sample TWL Reach sequence an agency can show a client
Example TWL Reach sequence. Placeholder copy for planning. Not a customer result, and not a message you should send unchanged.
- Qualify. The row shows the signal, the fit score inputs and the reason it was rejected or kept. Rejected rows stay visible.
- Day 0 · Email. Written from the signal. The client approves the pattern on a sample before the agent continues.
- Day 3 · LinkedIn. Same person, different channel, suppressed if they replied or opted out.
- Weekly. A review of sources that produced nothing. Kill those sources. That is the agency’s craft.
How the stack holds the work
Productise the workflow, not the paragraph. A new client clones the system and replaces sources, fit rules and the voice. Permissions keep client data apart.
Browser sessions let research happen on sites without an API. They are not a excuse to ignore a site’s terms. Put that in the operating rule.
Keep reading
Questions people ask
Can the client approve sends?
Yes. Put the client on the approval step for the first weeks, then move to exception review if they want that and the plan allows the access.
Is this “done for you” outreach?
It can be operated by the agency. The page does not promise meetings. It describes a system the agency can run and show.
How do you stop client niches collapsing into one list?
Separate sources and rules per client. Dedupe inside the client, not across clients, unless they have agreed to share suppression.
Which comparisons should we read?
lemlist, HeyReach and Expandi if the client is asking for a sending tool. Pancake, Clay and Common Room if they are asking for the signal layer. TWL is the stack that holds both.
Put the next workflow on the stack.
Start with the tool you need. Connect signals, TWL Reach and the rest of the system when the job is real.
Get TWL