II. Recommended segments to push to LGM / Best practices for Reo.Dev data in LGM

This playbook builds on our previous guide: Data transfer guide - Reo to La Growth machine.

If you haven’t gone through that one yet, give it a quick read first. Otherwise this’ll feel like jumping into the sequel without watching part one.

Now that you've set up the Zap and data is flowing from Reo.Dev into LGM, the question becomes:

What kind of segments should you actually send to LaGrowthMachine?

And more importantly:

How should you structure the data and campaigns to get the most out of it?

This guide gives you both:

• A deep dive example of a powerful Reo.Dev segment you can use right away
• A list of high-signal segment ideas other GTM teams are using
• Best practices for working with Reo data inside LGM

Deep Dive Example: Developers Active on Competitor or Complementary GitHub Repositories

Why this works:

If your product offers an alternative to a popular OSS project or builds on top of one, you can identify engineers who are:

• Already using those tools
• Likely feeling the pain your product solves
• More open to hearing about better/faster solutions

Segment Setup in Reo.Dev:

• Source Type: GitHub
• Activity Type: Starred, Forked, PR Opened, Issues Commented
• Repos: Pick 3–5 competitor or complementary OSS repos
• Time Window: Last 90–180 days
• Enrichment: Add only if LinkedIn + Email available

Example segment name: Kubernetes Upgrade Relevance — Last 180d

What it captures: Developers who’ve recently engaged with:

• kube-no-trouble
• pluto
• kubepug

You now have a high-relevance segment of in-market developers. Push them into a multi-channel LGM campaign.

Message Strategy:

• Don’t try to pitch immediately.
• Lead with context: “Saw you’ve been active on X...”
• Ask for feedback, share something useful, offer value.

This is exactly what Tim from Kubegrade did — and booked 5 demos with a 22% reply rate. (See full story →)

Other High-Intent Segment Ideas to Push to LGM

An optional step can be that you can start with firmographic + ICP filters (e.g. Dev-first companies in NA/EU, 11–500 employees, active developers). Then layer it with developer activity signals:

1. CRM Owner = You + Has Activity Surge = Yes + Dev Funnel = Building or Deployed

Use case:
📈 Mid–late stage deal acceleration or POC support.

Why this works:
This segment pinpoints developers from accounts you're already working who are now showing a surge in product engagement. Great for personalized nudges, support check-ins, or moving stuck deals forward.

Reo.Dev Filters:

• Has Activity Surge = Yes
• Dev Funnel = Building or Deployed

2. In-Product Devs Seeking Support Touchpoint

Use case:
🧩 Devs who are inside your product and actively looking at install guides or troubleshooting docs, deal for timely, helpful outreach to nudge them forward.

Why this works:
These users are hands-on. They've logged in, triggered install commands, and browsed through troubleshooting docs. This usually means they’re either setting things up, debugging something, or evaluating deeper integrations. A quick message offering help can turn them into champions.

Reo.Dev Filters:

• Activity Type = Product Login
• Key Commands = Includes install or setup triggers (e.g. npm, helm, pip installs, etc.)
• Key Pages: Docs = Includes Troubleshooting or Integration docs unique to your product

Use in LGM:

• Outreach angle: “Saw you were digging into setup guides — need a hand getting things running smoothly?”
• Keep it short, helpful, and low-pressure. Offer assistance, not a pitch.

3. Signed Up Recently + Viewed Pricing Page + Customer Fit = Strong

Use case:
💰 High-fit inbound leads showing buying intent.

Why this works:
This segment captures individual buyers who are explored pricing, belong to accounts that are in the building/deployed stage in your Dev Funnel. Timely outreach here often leads to fast demos or conversions.

Reo.Dev Filters:

• Developer Tag = Buyer
• Activity Group = Key Website Pages - Including Pricing
• Customer Fit Score = Strong
• Dev Funnel = Building or Deployed

💡 Best Practices for Using Reo.Dev Data Inside LGM

1. Slice the Name Field

Use Zapier's Formatter to split the full name field from Reo and extract the first name. This improves personalization and tone:

Hi {{firstName}},

2. Don’t Just Send Email. Use Multi-Channel Sequences

LGM performs best when you mix:

• LinkedIn connect → follow-ups → value message
• Email fallback if no reply

This improves visibility and gives your campaign more touchpoints.

3. Use Reo Tags to Personalize Messaging

Reo tags (e.g. Viewed Docs, Starred GitHub Repo, Product Login) let you:

• Mention the exact activity in your outreach
• Keep messaging short, useful, and context-rich

{{lgm-callout-2}}

4. Keep the Message Short and Human

• Lead with value or curiosity
• Avoid generic cold outreach copy
• Don’t try to “sell”.t Try to start a real conversation and offer help based on where they are at in their evaulation journey.

Your Next Step

You’ve now got the first principles on how to think about Reo.Dev segments and how they plug into your outbound motion. From here, you’re smart enough to figure out which segment filters and custom tags make the most sense for your GTM strategy.

That said, there’s a lot more you can do with a tool like LaGrowthMachine — things like AI voice messages on LinkedIn, AI personalized videos, and smarter workflows to boost reply rates and drive more booked meetings.

We’re not going to cram all of that into this one doc (and honestly, we’d just be repeating the great stuff the LGM team already covers). If you want to go deeper, start here.

And if you ever need help figuring out how to get the most out of Reo.Dev, reach out at support@reo.dev or message your account manager on Slack. We got you :)