Inbound → LinkedIn

The silent signup problem

Signup volume looks healthy. Pipeline from those signups does not. Sales says marketing’s leads are soft. Marketing says sales never follows up fast enough. Both can be true.

1. Someone signs up.
2. They get a product email and a nurture drip.
3. Nobody talks to them as a person for days.
4. If someone does follow up, it’s another email into an inbox trained to ignore vendors.

Warm intent dies of slow process, not bad ICP.

Action this week

Pick one product status that means “worth a human conversation” (activated, invited a teammate, hit feature X). Write it down. That is your trigger.

Why LinkedIn for inbound follow-up

You already have their email. So why leave the inbox?

Because the same person who signed up for your product will often ignore vendor email and still reply to a short, relevant LinkedIn note. Especially founders and operators. Their email is a war zone. LinkedIn is where peers still talk.

Keep onboarding email. Add a human (or human-approved) LinkedIn thread tied to the same moment: they raised their hand in your product.

Keep product email for activation. Use LinkedIn for the conversation.

Metric·Meetings booked before vs after LinkedIn follow-up (IncrediBuild) — filling in.

Action

Audit your last 20 activated signups. How many got a personal LinkedIn touch within 48 hours?

The Inbound → LinkedIn loop

Four steps. Change one variable at a time.

1. Trigger — product event (signup / activated / status you choose)
2. Resolve — email (+ name/company) → LinkedIn profile
3. Qualify — is this person worth a sequence right now?
4. Reach — LinkedIn sequence with intent (feedback or convert)

This playbook assumes a custom webhook: your product (or middleware) POSTs the person into your LinkedIn outbound system when the trigger fires.

Trigger → resolve → qualify → reach. Everything else is tooling.

{
  "linkedin_url": "…/in/james-park",
  "context": "activated · pro plan",
  "source_label": "product.signup"
}

In Obert: create a Custom webhook signal. Your backend POSTs a LinkedIn profile URL plus optional context. A qualification agent gates every lead. Qualified people land in Copilot with a generated sequence. You Send sequence from Pending action, or turn on Auto-approve qualified leads when you trust the gate.

Step 1 — Pick the trigger

If you LinkedIn-message every email that creates an account, you burn trust and sender limits on tire-kickers.

Pick the earliest status that still means intent:

1. Activated (preferred) — used the core action once
2. Qualified signup — passed a form or firmographic filter
3. Raw signup — only if volume is low and you qualify hard

In Obert, pass that moment in context and source_label so Copilot writes for the event, not a generic “saw you signed up.”

Step 2 — Resolve email → LinkedIn

Your product has an email. LinkedIn outreach needs a profile. Without a resolve step, the loop dies in a spreadsheet.

1. Take work email from signup (skip personal emails if that is policy).
2. Reverse-lookup to a LinkedIn URL.
3. Attach name + company when you have them.
4. If no match, park the lead. Do not guess a profile.

No LinkedIn URL, no send. Park unmatched emails.

Obert’s custom webhook expects a linkedin_url on the POST. Resolve in your product or middleware before the webhook fires.

{
  "linkedin_url": "https://www.linkedin.com/in/…",
  "context": "activated · team plan",
  "source_label": "product.signup"
}

Step 3 — Qualify before you reach

Reverse lookup gets you a person. It does not mean they are ICP. Messaging every matched profile is how inbound turns into spam with better data.

• Fit — title, seniority, company vs ICP
• Moment — does this trigger deserve outreach?
• Path — feedback vs sales (different sequence)

Resolve finds the person. Qualify decides if they deserve a message.

Insight·Share of resolved signups that fail qualification — measuring with customers.

In Obert every webhook lead passes a qualification agent before Copilot. Gated leads never get a sequence.

Step 4 — Reach with intent

“Hey, saw you signed up!” is how you get ignored on LinkedIn too.

One sequence, one intent. Feedback or convert, not both.

In Obert an outreach agent defines structure and voice. Copilot generates the concrete steps. Review under Pending action, then Send sequence.

Human review vs autopilot

Start on Pending review while the trigger, ICP, and copy are new. Flip Auto-approve qualified leads per signal only after you trust the gate.

Obert’s Copilot feed splits Pending action and On autopilot. Autopilot is a per-signal switch, not a global “trust AI” button.

Action

Run the first 30 qualified leads on manual approve. Log every edit. Those edits become agent fixes before you flip autopilot.

First 14 days

• Day 1–2: Pick trigger + write Feedback and Convert intents.
• Day 3–4: Wire event → resolve → webhook POST with context.
• Day 5–6: Qualification rules live. Test with 10 events.
• Day 7–8: Sequences in place. Manual Copilot review only.
• Day 9–11: Send to real activated ICP. Track replies and meetings.
• Day 12–14: Fix qualifier false positives. Only then consider auto-approve.

Metric·Replies and meetings in the first 14 days of a live run — fill after launch.

What goes wrong

1. Trigger too early — messaging email-confirmers who never activated.
2. No qualify step — reverse lookup becomes a spray cannon.
3. Generic copy — no product context in the first note.
4. Email-only follow-up — LinkedIn never gets the lead.
5. Autopilot on day one — bad first impressions at scale.
6. One sequence for every path — feedback prospects get a hard pitch.

How Obert runs this loop

Obert is the LinkedIn outbound system for lean GTM teams: find high-intent leads, qualify them, and reach out. Inbound → LinkedIn is the same system, fed by your product instead of a static list.

1. Create a Custom webhook signal (description + source label).
2. Point your product/middleware at the webhook URL with the signing secret.
3. On activation, resolve email → LinkedIn, then POST linkedin_url + context.
4. Qualification agent gates. Survivors hit Copilot.
5. Review and Send sequence, or enable Auto-approve qualified leads.

Native CRM connectors are fine when you have them. This playbook stays on the custom webhook path on purpose: the craft is the loop, not the logo on the middleware.