Toby on X — Engagement Targets

How to use this list#

26 candidate accounts ranked by ICP fit + immediacy of the surfacing tweet. Each entry has:

• Bucket — which ICP shape they map to in toby/x/strategy.md.
• Why now — the specific public tweet (id + date) that surfaces them.
• Suggested first touch — a draft reply, quote, or "follow + listen" recommendation.
• What NOT to do — calibration so we don't blow the relationship.

Hard rules for every target:

• First touch is always in-character (calm, specific, generous — see toby/x/strategy.md voice).
• No link in the first reply. Drop gettoby.com only when the prospect explicitly asks "where" or "what" — or in a clearly-invited context.
• One reply per target per day, max. No follow-pings.
• No DM cold-pitches. Ever.
• No mass-engagement. If we hit more than 8 targets in one day, we look like a bot and we ARE behaving like one.
• New this run — bot filter: every target below has followers_count ≥ 100 AND account_created < 2025-06. Bot-shaped accounts surfaced by the search are explicitly excluded — see strategy doc for the rationale.

Targets are tiered:

• 🅰️ Tier A — Immediate (act this week). Tweet posted in the last 7 days, ICP fit clear, conversation still warm.
• 🅱️ Tier B — Warm (act this month). Tweet 7–30 days old, ICP fit clear, plausible to surface a fresh hook.
• 🅲️ Tier C — Watch list. Follow + monitor; first touch when they post something fresh in-pillar.

---

Tier A — Immediate#

1. @airplanestar_ 🅰️ NEW#

• Bucket: heavy-organiser, influencer-adjacent
• Followers: 5,493 (verified)
• Bio one-liner: "artist ⚡ technologist ⚡ builder" — broad reach, builder-tier productivity-aware.
• Why now: replied to @avarinjung — "morning alizza here is mine the ai thinks im a chaotic sunshine with way too many tabs open😌" (reply 2053688159356215575, 2026-05-11). Casual, in-character moment, screenshot showing the AI's roast.
• Suggested first touch (reply, light, no link):

  "Chaotic sunshine with too many tabs open" is a job title we'd accept at face value.

• What NOT to do: don't pitch. Don't link. The reply is a hat-tip, not a sales motion. If she follows back or replies, she goes into the "warm-acquaintance" pool for a future, more substantive engagement.

2. @tropicanacailin 🅰️ NEW#

• Bucket: heavy-organiser, founder, designer
• Followers: 3,130 (verified, established 2007)
• Bio one-liner: "Designing systems AI still overlooks · Women's health • care infrastructure • migration · Indie product builder" (Dublin, Brazilian-Irish).
• Why now: "Most of my nights lately look the same: baby asleep nearby, too many tabs open, testing ideas around women's health, care infrastructure and tools for people usually ignored by software… I'd rather ship imperfect things than spend years waiting to feel 'ready'." (tweet 2053631111327027388, 2026-05-11). Strong builder-tab-pain shape from an established design voice.
• Suggested first touch (reply, on-character, no link):

  The "too many tabs open" part of building in public is the part nobody talks about. Each one is a half-finished decision you haven't been allowed to forget. Respect for shipping anyway.

• What NOT to do: don't reduce the tweet to "we have a tool for that". Her tweet is about indie-builder vulnerability; the reply lives in that frame first, product never. If she ever asks "what do you use?" — second touch can mention Toby.

3. @wayne_effect 🅰️ NEW#

• Bucket: heavy-organiser, the "lost-tab grief" canonical voice
• Followers: 1,337 (verified, established 2017, technology contractor / web consultant)
• Bio one-liner: "OMS/NAC Shaman and Pagan Cleric who enjoys various sciences and academia; I am also a Technology Contractor, Web Consultant, and Ethnobotanist."
• Why now: "I had a 'problem' that resolved itself. Chrome crashed, and I lost all my tabs. It completely cleared my history and my research tabs were gone. It could have been somewhat a serious issue. I thought I was screwed." (tweet 2050774386022465549, 2026-05-03) — the exact pain Pillar 1 sub-frame addresses.
• Suggested first touch (reply, generous, no link in first touch):

  "It could have been somewhat a serious issue" might be the most understated description of lost-research-tabs we've read. The fix to that feeling is rarely fewer tabs — it's a place to set them down that survives the crash.

• What NOT to do: don't pitch reliability as Toby's USP — the new tab page is currently 1-starring for the same reason. The reply lives at the level of category framing, not "we solved your crash". If he asks "what do you use?", wait until the rel-gate clears before mentioning Toby.

4. @benrayfield 🅰️ NEW#

• Bucket: influencer (AI/dev, builder voice)
• Followers: 3,248 (verified, established 2009)
• Bio one-liner: "Thought-criminal. Custom web tool ninja. Makin opensource massively multiplayer game ppl/AIs build in game by turingComplete GPU swarms."
• Why now: "Codex might be the use-case that pushes Lamgl into K_factor>1. I could tell GPT to write a GPU optimized ed25519 from scratch and it would do it… i still gotta close them when too many tabs get open. Browsers are the GPU number crunching workhorse in my system." (tweet 2053536526034694164, 2026-05-10) — esoteric AI-builder tab pain.
• Suggested first touch (reply, peer-to-peer, no link):

  "Browsers are the GPU number-crunching workhorse" is the most-honest description of a 200-tab dev workflow we've seen. Closing them isn't the move; saving the window is.

• What NOT to do: don't talk down. He'll engage on substance or not at all. No emoji.

5. @Galaxy42_ 🅰️ (carried over)#

• Bucket: heavy-organiser (AuDHD-identifying)
• Followers: 477
• Why now: described his exact tab-organising workflow — "I have a habit of creating folders to save my tabs in… ADHD brain won't allow me to close them but my Autistic brain needs to organise them" (reply 2048389981626937556, 2026-04-26).
• Suggested first touch (reply):

  That two-system thing is real, and it's the workflow people miss when they treat tabs as clutter. The "needs to be organised" brain and the "won't let you close" brain aren't fighting — they're collaborating.

• What NOT to do: do NOT name "ADHD" or "Autism" yourself in the reply. He named them; we don't echo. Don't pitch Toby in this reply at all — just sit in it. Window is closing (tweet now 14 days old); priority if we engage this week, drop next.

6. @Nerdsauce1 🅰️ (carried over)#

• Bucket: heavy-organiser
• Followers: 388
• Why now: "I'm a genuine Tab hoarder, so I thought it might be a good one for wanting to do so much but not having the energy for it all… My poor computer and RAM are always SO stressed out" (reply 2052818277248737347, 2026-05-08).
• Suggested first touch (reply):

  "Wanting to do so much but not having the energy for it all" is the most exact description of a 100-tab afternoon we've ever read. Hope the RAM survives the week.

• What NOT to do: don't pitch. Don't link. The reply is a wave, not a sell.

---

Tier B — Warm (act this month)#

7. @nibzard 🅱️#

• Bucket: influencer (builder/dev)
• Followers: 1,104
• Why now: "are you a tab hoarder, how are you dealing with this?" with screenshot (tweet 2050495728452034863, 2026-05-02) — explicit conversation invitation. Thread is now 8 days old — engage by Mon 2026-05-12 or drop.
• Suggested first touch (reply — see Post 4 in toby/x/content-pipeline.md):

  Honest answer: not closing them is the right instinct. They're context, not clutter. The fix isn't fewer tabs — it's somewhere safe to set them down so the browser stops pretending they need to live as windows.

• What NOT to do: don't paste gettoby.com in the first reply. If he asks "where", that's the cue to drop the link.

8. @TheDevDesign / Alexander 🅱️ NEW#

• Bucket: switcher (Arc → Dia), founder
• Followers: 43 (verified, Copenhagen, young founder building in public)
• Why now: "I don't know. Dia browser has me hooked. So far one of the best browser experiences I've ever had. Still missing a few features from Arc but they will come eventually." (reply 2050329431395237912, 2026-05-01).
• Suggested first touch (reply, on a fresh tweet from him — NOT this one):

  The "Dia hasn't shipped X yet" pain is real. Some of the Arc instincts live cleanly in a separate surface — Toby keeps the visual-collection part in the new tab page if you want it back without waiting.

• What NOT to do: don't bait the Arc-vs-Dia fight. Frame Toby as additive, not a switch.

9. @DazzioDG / Daniel González 🅱️ NEW#

• Bucket: switcher (Arc-ambivalent)
• Followers: 53
• Why now: "It's sad to say, but Arc Browser is still the best. And don't get me wrong, I hate it. I just don't get why Zen's team didn't go with Chrome 😭" (reply 2049999535309570136, 2026-04-30).
• Suggested first touch: follow + watch. Tiny account but exact switcher voice. Engage on next fresh tab tweet, not this one (10 days old + replying-to context).
• What NOT to do: don't pretend Toby resolves the Zen-vs-Chrome philosophical thing. It doesn't; that's not our fight.

10. @SmartFoxDev / Valerii Kuznietsov 🅱️ NEW#

• Bucket: switcher (Arc spaces), builder
• Followers: 522 (verified, Portugal, "Building SaaS in public")
• Why now: "I use conductor daily and miss something like Spaces similar to Arc Browser / Zen. Many active chats gets very confusing and hard to navigate anyway." (reply 2052519456581001238, 2026-05-07). Context: replying to a shadcn/conductor thread — productivity-AI builder audience.
• Suggested first touch (reply, peer):

  The "I want Arc-style Spaces but everywhere" instinct is real. Toby's collections are basically that for the new-tab surface — one screen, many named groups, no horizontal-tab strip.

• What NOT to do: don't paste gettoby.com. The mention itself is the seed.

11. @constantout 🅱️ (carried over)#

• Bucket: switcher (Arc), founder
• Followers: 4,597
• Why now: "This was one of the features I hated the most from Arc actually, I'm a tab hoarder" (reply 2046254370434560465, 2026-04-20) — now 20 days old.
• Suggested first touch (reply, on a fresh tweet of his — NOT the 3-week-old one):

  The "save the tab, don't kill it" instinct lines up with how Toby works — collections persist, nothing auto-vanishes. Worth a look if Arc's autoclose still bothers you.

• What NOT to do: don't reply 3 weeks late on the original tweet (looks like a bot trawl). Wait for him to post a fresh tab/Arc thought.

12. @AgentNaeem 🅱️ (carried over)#

• Bucket: switcher (Brave/Edge → Chrome, wants workspaces)
• Followers: 3,459
• Why now: "Might have to return to chrome / Bringing workspaces like what Microsoft edge have would seal the deal" (reply 2016652405971013723, 2026-01-28).
• Suggested first touch: wait for fresh tab tweet. Original is too old now (102 days). When fresh:

  Chrome workspaces aren't shipping any time soon, but if it's the "save tabs, sync across devices" job that pulls you back, Toby does that — visual collections, cross-device. Worth a 60-second look.

• What NOT to do: don't bait the Chrome-vs-Brave fight. Frame Toby as the bridge, not the team.

13. @display___flex 🅱️ (carried over)#

• Bucket: switcher (despised Arc/Dia, came back), builder
• Followers: 491
• Why now: "i remember years ago despising arc and dia and here i am using them cause i hate horizontal tabls and i manage my tabs like this" (tweet 2029313864886857879, 2026-03-04).
• Suggested first touch: follow + watch for a fresh tab post. When it comes:

  If horizontal tabs are the problem, the new-tab page Toby builds is genuinely a different surface — collections instead of a strip. Worth a 30s look if Dia ever frustrates you again.

• What NOT to do: pile in on a 10-week-old screenshot tweet.

14. @iBladesi 🅱️ (carried over)#

• Bucket: heavy-organiser, finance Twitter
• Followers: 3,148
• Why now: "self proclaimed tab hoarder here." + screenshot (reply 2051831997006241823, 2026-05-06).
• Suggested first touch (reply, light):

  Tab-hoarding is a research instinct, and finance Twitter is an extreme case. Toby was built for the "I need this tab next earnings season" energy.

• What NOT to do: don't claim Toby is a finance-research tool specifically. It's general; we just see the use case.

15. @AngledLuminary / Rohini Del Ray 🅱️ NEW#

• Bucket: heavy-organiser, lost-tab-grief
• Followers: 268 (EM resident, manga/webtoons)
• Why now: "I lost all my tabs including the fanfics I had saved to read later 😭😭" (tweet 2052412672159916349, 2026-05-07).
• Suggested first touch: Skip first touch — too much grief, too in-conversation. Watch list. If she posts a less-loaded tab tweet later, that's the moment.
• What NOT to do: capitalize on the "lost the fanfics" pain by pitching the product. Reads as crass; the moment belongs to her.

16. @humba1icious 🅱️ (carried over)#

• Bucket: adjacent (productivity newsletter)
• Followers: ~15
• Why now: "professional tab hoarder with a calendar full of fake urgency" (tweet 2045396913185595760, 2026-04-18).
• Suggested first touch (reply, light):

  "Professional tab hoarder" is a job title. Embrace it.

• What NOT to do: pitch. Tiny following, but the framing is gold for our P1 voice — this is a user we want as a friend of the brand, not a conversion target.

17. @jacobrask 🅱️ (carried over)#

• Bucket: influencer (KM, builder, Claude-skill-author)
• Followers: 616
• Why now: "Safari Tabs Skill" built on Claude + AppleScript (quote-tweet 2005283790139040150, 2025-12-28) — 133 days old now.
• Suggested first touch: follow + watch. He is intellectually adjacent but currently building his own thing. If he ever shares his skill more widely or asks for tools, that's the moment.
• What NOT to do: try to pitch him on Toby as a replacement for his Claude skill. He doesn't want a replacement; he built one.

---

Tier C — Watch list#

18. @LacrimosaVT 🅲️ (carried over)#

• Bucket: adjacent (vtuber community, "professional tab hoarder" bio)
• Followers: 110
• Why: bio explicitly says "professional tab hoarder" (profile, 2026-05-10); intro tweet 2052925722193183149 (2026-05-09).
• Suggested: follow + listen. Vtuber audience is not core ICP, but the "tab hoarder" identity is on-brand.
• What NOT to do: reply to her intro tweet as a brand — feels like an impersonal RP-thread invader.

19. @paper2gether 🅲️ (carried over)#

• Bucket: heavy-organiser (Opera GX)
• Followers: ~184
• Why: "fellow operagx tab hoarder #KEEPTHEM" (reply 2046228217669861882, 2026-04-20).
• Suggested: follow + listen. Reply only when they post a fresh tab tweet. Opera GX has a strong tab-pinning culture; pitching them out of the browser is hard.
• What NOT to do: pitch a switch from Opera GX to Chrome. Lose-lose.

20. @oceansnavi 🅲️ (carried over)#

• Bucket: heavy-organiser (Safari Tab Groups, mobile pain)
• Followers: ~136
• Why: "100+ tab groups left… no aggregate tab saving" on iPhone Safari (tweet 1988229387276480809, 2025-11-11).
• Suggested: Skip — Safari/iOS-only pain. Watch for a desktop tweet.

21. @Vishavnath_772 🅲️ (carried over)#

• Bucket: switcher-from-Brave (cross-device sync)
• Followers: ~1,614
• Why: "@brave Brave is not my primary browser coz it doesn't save my tabs if i delete or shift to new phn" (reply 1994078798216581294, 2025-11-27).
• Suggested: watch. Brave-switch shape, but the pain is cross-device — Toby cloud sync solves it. Reply when he posts something fresher.

22. @ciprian__b / Uncluttr 🅲️ NEW — COMPETITOR#

• Bucket: COMPETITOR — AI-organize tab manager
• Why: ranked #18 on CWS for "vertical tab manager", just earned Blue Checkmark badge (tweet 2052286463866241370, 2026-05-07), building in public.
• Suggested: DO NOT engage as a target. Competitor founder explicitly building the AI-tab-organize lane Toby is sitting on until Q4. Monitor cordially.
• What NOT to do: subtweet, "compare", or engage from @TobyForTabs. We share a category; we don't share an audience yet.

23. @godesign_art / TabVault Pro 🅲️ NEW — COMPETITOR#

• Bucket: COMPETITOR — free OneTab/Session-Buddy alternative
• Why: launch post (tweet 2045981145439871127, 2026-04-19) — "Tired of losing your browser tabs?".
• Suggested: monitor. Don't engage.

24. ThoughtFold (via @PersonAI_talks share) 🅲️ NEW — COMPETITOR#

• Bucket: COMPETITOR — "Zero-cloud Chrome tab manager for neurodivergent brains"
• Why: Producthunt launch surfaced 2026-04-25 (tweet 2047951471501509016). Directly targets the AuDHD ICP we identified.
• Suggested: monitor; cordial silence. Their explicit ND positioning gives them a sharper claim on the audience that uses health-language; we should keep our framing implicit and let them have the explicit lane.
• What NOT to do: engage. Compare publicly. Or — under any circumstances — reframe Toby as "for neurodivergent users". It isn't a positioning we earn, and it's not a fight we should pick.

25. tab-out / @Yieioo 🅲️ NEW — COMPETITOR#

• Bucket: COMPETITOR-adjacent — open-source visual tab manager with "Page Snapshot"
• Why: "added a new 'Page Snapshot' feature to the open-source Chrome extension tab-out" (tweet 2050929512658121143, 2026-05-03).
• Suggested: monitor. Open-source play with adjacent visual-pillar feature.

26. @RomanGweb3 / leap-tabs 🅲️ (carried over) — COMPETITOR#

• Bucket: COMPETITOR — sidebar tab manager + spaces for Chrome
• Why: build-in-public, multi-device sync conflict work (reply 2048801246182576312, 2026-04-27); previous "professional tab hoarder" reply 2045918213376975212.
• Suggested: DO NOT engage as a target. Competitor founder. Cordial silence.

---

Recap by bucket#

Bucket	Tier A	Tier B	Tier C	Total
heavy-organiser	4	3	2	9
switcher	0	5	1	6
influencer	1	2	0	3
team-buyer	0	0	0	0
adjacent	1	1	1	3
competitor (don't engage)	0	0	5	5 (informational only)
TOTAL	6	11	9	26

The team-buyer column is still zero. Operator: confirm we drop the team-buyer pillar from X entirely by 2026-05-17 if no operator input arrives.

Operator one-pager — what to do this week#

If the operator wants the absolute-minimum first move out of all this, the single highest-leverage action is:

1. Verify @TobyForTabs creds are in our hands (the 🔒 acct gate).
2. Reply to @nibzard (Tier B #7) within 48h using the reply draft above — thread closes ~2026-05-12. After that, replace with engagement on @airplanestar_ or @wayne_effect as the lead Tier-A move.
3. Pin Post 13 from toby/x/content-pipeline.md as the new pinned tweet.
4. Post Post 1 on Tue 2026-05-12, Post 2 on Wed 2026-05-13, Post 3 on Thu 2026-05-14. That's the relaunch week. Everything else is sequencing.