You’re getting traffic. Someone found your site, read your services page, then clicked over to pricing and spent three minutes there. Then they left. You have no idea who they were, and you sent them nothing.
That’s a closed deal that slipped through a hole you didn’t know existed.
Inbound signals, pricing page visits, proposal downloads, content downloads, repeat visits, are the highest-quality leads you’ll ever see. These aren’t cold prospects you interrupted. They came to you. They already decided you were worth investigating. The only question is whether you respond fast enough and smart enough to capture them.
The inbound-to-outbound loop is a system: signals come in, get classified by heat, trigger a specific template, and get sent within 48 hours. It takes about 4 hours to build and runs in the background forever after. Here’s exactly how to set it up.
The Signal Stack: What to Track and What It Means
Not all signals are equal. Treating a blog reader the same as a pricing-page visitor wastes your best shot at a warm lead. Classify every trackable behavior into three tiers:
Hot signals (pitch-ready):
- Pricing page visit (any duration)
- Proposal or case study download
- Repeat visit within 7 days
- Multiple pages in a single session (services → pricing → about)
Warm signals (value-add approach):
- Blog post or article read (single visit)
- Newsletter open with click-through to site
- LinkedIn profile view from a company in your ICP
Cold signals (nurture only):
- Newsletter open without click
- Social post engagement
- Single blog visit, bounced
Hot signals mean someone is in active buying mode. Warm signals mean someone is aware of you. Cold signals mean they’re in your ecosystem but not ready. Treat them accordingly, hot gets a direct message, warm gets a resource, cold gets a nurture sequence.
Setting Up Your Notification System
Before you can respond to signals, you need to know they happened. Here’s the minimum-viable notification stack:
Step 1: Google Analytics 4, create custom events
Set up GA4 events for pricing page visits and any downloadable assets. In GA4, go to Events → Create Event. Name it pricing_page_visit and set the condition to page_path equals /pricing. Repeat for any download pages.
Step 2: Connect GA4 to Slack or email via Zapier
Create a Zap: Trigger = GA4 custom event fires. Action = Slack message to yourself or email to your inbox. Message format: [HOT SIGNAL] Pricing page visit, [timestamp], [traffic source], [city if available]. This pings you within minutes of a visit.
Step 3: For named visitor identification, add RB2B RB2B’s free tier identifies anonymous US website visitors and pushes a name + LinkedIn profile to Slack. Install the script tag on your site, connect to Slack. When a pricing page visitor is identified, you now have a name, company, and LinkedIn URL. This is the difference between knowing “someone visited” and knowing “Marcus from Belk Industries visited.”
Budget: GA4 is free. Zapier Starter is $20/month. RB2B free tier handles 150 identified visitors/month.
The 48-Hour Outreach Templates
Signal fires. You have 48 hours. Here’s what to send based on signal type.
Template A: Hot signal (pricing page), no name identified Use your email list, LinkedIn connections, or recent conversations to cross-reference traffic source. If the signal came from your email newsletter, check who opened and clicked in that window. Then send:
Subject: Quick question about [your service]
Hi [Name],
Working on a [specific thing relevant to them] lately and thought of you. I’ve had a few spots open up this month for [service type] work, curious if the timing is interesting.
Do you have 20 minutes this week?
Template B: Hot signal, name identified via RB2B
Subject: Saw you work at [Company]
Hi [Name],
I do [specific service] for [their industry]. Noticed you might be exploring options.
I recently helped [comparable company] [specific outcome, e.g., “cut their content production time by 40%”]. Worth a quick call to see if it’s relevant?
20 minutes this week?
Template C: Warm signal (blog read, LinkedIn view)
Subject: Thought this might be useful
Hi [Name],
You came across my radar, [one sentence connecting the dots, e.g., “saw your LinkedIn comment on the Figma partnership news”].
I wrote something recently that’s directly relevant to [their challenge]: [link to specific resource].
No pitch, just thought it was worth sharing. Happy to discuss if it raises questions.
Never lead with “I noticed you visited my site.” Find the lateral reason to reach out. The signal tells you to act. Your message should feel like a well-timed coincidence.
The point of a warm outreach isn’t to close a deal, it’s to create a reason for the prospect to think of you when they’re ready. A useful resource sent at the right moment does more work than ten cold pitches sent at the wrong moment.
Building the 48-Hour Response Protocol
The system breaks down in the gap between “signal fires” and “message sent.” Close that gap with a decision tree, not willpower.
When a HOT signal fires:
- Signal hits your Slack/inbox
- Check RB2B for identity (30 seconds)
- If identified: send Template B within 2 hours
- If not identified: cross-reference email opens in the same time window
- If matched to a known contact: send Template B
- If unknown: add to your “revisit in 7 days” list, if they return, the second visit is your outreach trigger
When a WARM signal fires:
- Signal hits your inbox
- Look up the person on LinkedIn (60 seconds)
- Identify one specific thing about their work, company, or recent post
- Customize Template C with that specific detail
- Send within 24-48 hours
When a COLD signal fires:
- No action except tagging in your CRM or newsletter tool
- They go into your standard nurture sequence
- Next outreach trigger is either a hot signal or 90 days of silence
Calibrating Your Signal Thresholds
Most freelancers set up notifications and then get overwhelmed or desensitized. Avoid this by setting volume caps on yourself.
Daily action limit: 5 outreach messages max. If you get 12 hot signals in one day, prioritize by: (1) identified visitors from your ICP, (2) pricing page + multi-page sessions, (3) single pricing page visits. The rest go into a next-day queue.
Weekly review: Every Friday, check your signal log. How many hot signals fired? How many triggered an outreach? What was the response rate this week? Track this in a simple spreadsheet: date, signal type, outreach sent (Y/N), response (Y/N), outcome. After 60 days you’ll see which signals convert and which are noise.
Adjust thresholds quarterly. If your blog traffic explodes, warm signals become noise, raise the threshold to only act on repeat blog visits or specific high-intent posts like “how to hire a [your service].”
Connecting Signals to Your CRM Loop
The loop isn’t complete until signal data feeds back into your pipeline management.
Add a “Signal Origin” field to your CRM (or Notion pipeline, or whatever you use). When a prospect comes from an inbound signal, tag them. After 6 months, check: do signal-originated leads close faster? At higher rates? At better prices?
For most freelancers, the answer is yes, because the prospect was already warmed by your content before the outreach. Signal-originated deals often close in 2-3 conversations instead of 5-7.
That data justifies investing more in the content and SEO that generates the signals in the first place. The loop becomes a flywheel: content generates signals, signals generate conversations, conversations generate case studies, case studies generate more content, content generates more signals.
Most freelancers treat their website analytics as a scorecard, they look at numbers, feel good or bad, and move on. The inbound-to-outbound loop treats analytics as a trigger, something that tells you exactly when and who to contact. That shift alone is worth more than doubling your content output.
The 4-Hour Setup Checklist
Run this once and the system operates continuously:
- Install GA4 on your site (if not already done), 30 min
- Create pricing page visit + download events in GA4, 30 min
- Set up Zapier: GA4 event → Slack notification, 45 min
- Install RB2B script tag on site, connect Slack channel, 30 min
- Write and save your three templates (A, B, C) in a notes app or email draft, 45 min
- Create a signal log spreadsheet (Date / Signal Type / Person / Outreach Sent / Response), 15 min
- Set a recurring Friday calendar block: “Signal log review”, 5 min
Total: approximately 4 hours. After that, the system runs. Your only job is to respond to notifications and log the outcomes.
What to Expect in the First 90 Days
Month 1: You’ll miss some signals, forget to use templates, and send a few messages too late. That’s fine. You’re building the habit.
Month 2: You’ll get your first response from a signal-triggered outreach. Someone who visited your pricing page, got a timely message, and said “actually, yes.” That will recalibrate your entire view of your website traffic.
Month 3: You’ll have enough signal log data to know which signals convert for your specific audience. You’ll also have 2-4 live conversations that originated from signals, leads you wouldn’t have had if you’d kept treating your analytics as a scorecard.
The math works like this: if you get 200 monthly visitors, 10% visit the pricing page, and you reach 30% of those with a timely message, and 15% of those respond, you’re generating one new conversation per month from traffic you already had. That’s not nothing. For most freelancers, one extra qualified conversation per month is an extra $15,000-$50,000 annually, compounded by the deals that close from it.
Build the loop once. Let it run.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
