mirror of
https://github.com/boxpositron/absolute-dotfiles.git
synced 2026-10-24 16:33:19 +00:00
David Ibia
ea570af409
- Move the vendored skills from .config/opencode/skills to .config/omo/skills, with provenance and local changes in its README - Rewrite Impeccable's script paths to ~/.omo/agent/skills/impeccable so its detector and live-server verbs resolve under omo - frontend-workflow hands screenshots to a visual-engineering task instead of opencode run - Move the notes commands and /impeccable to .config/omo/prompts as omo prompt templates; setup-mcp stays behind because it writes opencode.json - Archive DEVELOPMENT-WORKFLOW.md and UI-WORKFLOW.md under .config/omo/archive; nothing loads them - link-ai-configs.sh links the skills into omo and Claude Code only and stops linking OpenCode's config, TUI, plugins and workflow docs - setup-mac.sh and Brewfile.apps stop installing OpenCode; README and .withcontextconfig.jsonc follow the new layout ~/.config/opencode/AGENTS.md stays linked: omo's rules engine reads it before ~/.claude/CLAUDE.md and stops at the first hit, so it carries the shared preferences and keeps OMC's instructions out of omo.
91 lines
5.1 KiB
Markdown
91 lines
5.1 KiB
Markdown
# Personalization at Scale
|
||
|
||
Personalization drives **50–250% more replies** (Lavender). The key insight: **if your personalization has nothing to do with the problem you solve, it's just an attention hack** (Clay).
|
||
|
||
## Four Levels of Personalization
|
||
|
||
### Level 1 — Basic (merge tags)
|
||
|
||
First name, company name, job title. Table stakes, no longer differentiating. ~5% lift.
|
||
|
||
### Level 2 — Industry/segment
|
||
|
||
Industry-specific pain points, trends, regulatory challenges. Scalable via micro-segmentation.
|
||
|
||
> Most {{industry}} teams struggle with {{lead gen problem}}, which often leads to wasted effort.
|
||
|
||
### Level 3 — Role-level
|
||
|
||
Challenges specific to their role and seniority.
|
||
|
||
> As Head of Sales, keeping pipeline steady is probably your biggest headache. Your RevOps team is small, so you're likely wearing multiple hats during scaling.
|
||
|
||
### Level 4 — Individual (gold standard)
|
||
|
||
Specific, timely observations about that person connected to the problem you solve.
|
||
|
||
> Noticed you're hiring 3 SDRs. Sounds like you're scaling outbound fast. Most teams hit follow-up fatigue during onboarding.
|
||
|
||
## Research Signal Stack
|
||
|
||
| Signal | Where to find it | How to use it |
|
||
| ----------------- | ---------------------------------- | ---------------------------------------------------------------------------- |
|
||
| Recent funding | Crunchbase, LinkedIn, press | "Congrats on Series B. Scaling teams fast usually creates X challenge" |
|
||
| Job postings | LinkedIn Jobs, careers page | "Noticed you're hiring 3 SDRs. Sounds like you're scaling outbound" |
|
||
| Tech stack | BuiltWith, Wappalyzer, HG Insights | "I see you're using HubSpot. Most teams at your stage hit a ceiling with X" |
|
||
| LinkedIn activity | Posts, comments, job changes | "Really enjoyed your post about X" |
|
||
| Company news | Google News, press releases | "Congrats on acquiring X. Integrating teams usually creates Y challenge" |
|
||
| Podcast/talks | Google, YouTube, podcasts | "Caught your talk at SaaStr on X. Really insightful" |
|
||
| Website changes | Manual review | "Your new pricing page caught my eye. Curious how it's converting" |
|
||
|
||
## The 3-Minute Personalization System
|
||
|
||
From "30 Minutes to President's Club":
|
||
|
||
**Step 1:** Build a research stack of top 10 buying signals — 5 company triggers, 5 person triggers. Stack-rank by relevance.
|
||
|
||
**Step 2:** Build a 3x3 template: (1) personalization attached to a problem, (2) problem you solve, (3) one-sentence solution + low-friction CTA.
|
||
|
||
**Step 3:** Create 5 "trigger templates" — pre-written personalization paragraphs for each trigger, with a smooth segue into the problem.
|
||
|
||
The personalization must logically connect to the problem. This creates 5 reusable triggers with the rest of the email constant. A top SDR writes a personalized email in **under 3 minutes**.
|
||
|
||
## The Four -Graphic Principles (Becc Holland)
|
||
|
||
- **Demographic** — Age, profession, background
|
||
- **Technographic** — Tech stack, tools used
|
||
- **Firmographic** — Company size, funding, industry, growth stage
|
||
- **Psychographic** — Values, passions, beliefs (highest-impact dimension)
|
||
|
||
Tapping into what prospects are passionate about drives significantly higher response rates.
|
||
|
||
## Observation-Based Openers (highest performing)
|
||
|
||
**Trigger-event:** "Congrats on the recent funding round. Scaling the team from here is exciting, and I imagine [challenge] is top of mind."
|
||
|
||
**Observation:** "Your recent post about [topic] resonated. Especially the part about [detail]. Got me thinking about how that applies to [challenge]."
|
||
|
||
**Industry insight:** "Most [role titles] I talk to spend [X hours/week] on [problem]. Curious if that matches your experience at [Company]."
|
||
|
||
## What Feels Fake (avoid)
|
||
|
||
- AI-generated emails with similar phrasing ("I hope this email finds you well")
|
||
- Generic attention hacks disconnected from problem ("Cool that you went to UCLA!" → pitch)
|
||
- Over-personalizing to creepiness
|
||
- "I saw your LinkedIn profile and wanted to reach out" — signals mass automation
|
||
|
||
## The "So What?" Test
|
||
|
||
After writing any opening line, read from prospect's perspective: "So what? Why would I care?" If the answer is nothing, rewrite.
|
||
|
||
## Personalizing With AI
|
||
|
||
Agents make Level 4 research affordable at scale, and they make invented personalization just as cheap. Buyers in 2026 spot it fast: praise for the company mission, congratulations on a year-old funding round, "I noticed you're in SaaS."
|
||
|
||
- **Relevance beats personalization.** A specific trigger, the pain it implies, and a concrete offer outperform a clever personal line attached to a generic pitch.
|
||
- **Facts first, then the angle,** in two separate steps, with a source URL for every fact.
|
||
- **Allow "no hook found."** When research turns up nothing specific, use the segment-level message instead of a manufactured one.
|
||
- **Review before sending** for Tier 1 and a sample of Tier 2.
|
||
|
||
The full research rules and the account brief template are in the prospecting skill's account research reference.
|