lattice-target-accounts
Curated accounts to engage with for building Lattice project visibility.
Table of Contents
- Priority Tier 1: Knowledge Graph & MCP Ecosystem
- Priority Tier 2: PKM Tool Creators & Community
- Priority Tier 3: AI/LLM Developer Tools
- Priority Tier 4: Build in Public & Indie Devs
- Engagement Strategy
- Hashtags & Keywords
Priority Tier 1: Knowledge Graph & MCP Ecosystem
Why Priority: Direct overlap with Lattice’s core functionality - these accounts discuss knowledge graphs, semantic search, and AI memory systems daily.
MCP Community
| Handle | Description | Engagement Opportunity |
|---|---|---|
| @MCP_Community | Official Model Context Protocol community | Share Lattice as MCP-compatible tool, engage in protocol discussions |
| @svpino | Santiago - shared knowledge graph + Cursor MCP integration | Direct competitor/collaborator in KG+MCP space |
| @cline | Cline AI - built Knowledge Graph Memory MCP Plugin | Very similar problem space to Lattice |
| @deepgraphMCP | Deep Graph MCP - interactive knowledge graph tool | Direct knowledge graph + MCP overlap |
| @AIC_Hugo | Hugo - explains MCP architecture clearly | Good for technical discussions |
| @dharmesh | HubSpot founder, MCP thought leader | High reach, discusses MCP future |
Knowledge Graph Tools
| Handle | Description | Engagement Opportunity |
|---|---|---|
| @zep_ai | Zep AI - temporal knowledge graphs for AI agents | Graphiti is similar to Lattice’s approach |
| @neo4j | Neo4j - leading graph database | GraphRAG discussions, knowledge graph patterns |
| @emileifrem | Emil Eifrem - Neo4j Co-Founder & CEO | High-level knowledge graph thought leadership |
| @KGConference | Knowledge Graph Conference | Academic/enterprise KG community |
| @Connected_Data | Connected Data - KG book authors | Knowledge graph education content |
Priority Tier 2: PKM Tool Creators & Community
Why Priority: PKM users understand the value proposition of connected notes and semantic search. Natural early adopters.
Tool Creators
| Handle | Description | Engagement Opportunity |
|---|---|---|
| @obsdmd | Obsidian official account | Engage on PKM discussions, graph view topics |
| @kepano | Steph Ango - Obsidian CEO | Plugin ecosystem, local-first philosophy |
| @logseq | Logseq official account | Outliner + graph community |
| @tiensonqin | Tienson Qin - Logseq founder | Knowledge graph philosophy discussions |
| @silver | Erica Xu - Obsidian Co-founder & COO | Product decisions, PKM future |
| @licat | Shida - Obsidian Co-founder & CTO | Technical PKM discussions |
PKM Influencers
| Handle | Description | Engagement Opportunity |
|---|---|---|
| @nicolevanderhoeven | Obsidian content creator | Tested tooling, reviews |
| @TfTHacker | Obsidian Observer, plugin creator | Deep PKM technical content |
Priority Tier 3: AI/LLM Developer Tools
Why Priority: Lattice works with Claude Code and AI workflows. This audience understands the value of context and memory.
Official AI Accounts
| Handle | Description | Engagement Opportunity |
|---|---|---|
| @AnthropicAI | Anthropic official | Claude ecosystem discussions |
| @claudeai | Claude AI official | Claude Code workflows |
| @OpenAIDevs | OpenAI Developers | MCP adoption announcements |
AI Developer Influencers
| Handle | Description | Engagement Opportunity |
|---|---|---|
| @gaborcselle | AI developer tools thought leader | Developer experience discussions |
| @ChiefScientist | Alexy - Graph + AI intersection | Neo4j Graph Gathering, technical depth |
| @SergioRocks | CTO sharing AI tools for dev workflow | AI productivity tools |
Priority Tier 4: Build in Public & Indie Devs
Why Priority: Supportive community, amplify each other’s work. Algorithm rewards engaging with smaller creators.
High-Reach Accounts
| Handle | Description | Engagement Opportunity |
|---|---|---|
| @arvidkahl | Arvid Kahl - 120K followers, indie SaaS expert | Bootstrapped tool building |
| @levelsio | Pieter Levels - Nomad List founder | Solo dev, AI tools |
| @courtikipling | Courtland Allen - Indie Hackers founder | Bootstrapped business authority |
Active Builders
| Handle | Description | Engagement Opportunity |
|---|---|---|
| @tdinh_me | Tony Dinh - DevUtils, solo dev | CLI tools, build in public |
| @marc_louvion | Marie - Tally Forms co-founder | Bootstrapped SaaS |
| @jonbuda | Jon - Bannerbear founder | Solo dev journey |
| @ollybot | Olly - Senja co-founder | Marketing + indie dev |
Developer Productivity Accounts
| Handle | Description | Engagement Opportunity |
|---|---|---|
| @sindresorhus | Open source CLI tools, npm packages | CLI tool patterns |
| @wesbos | Web dev educator | Developer tooling content |
| @ThePracticalDev | DEV Community | Developer tips aggregator |
Engagement Strategy
Daily Actions (15-30 min)
-
Search and engage with posts containing:
- “knowledge graph”
- “MCP server”
- “AI memory”
- “semantic search”
- “Claude Code”
-
Reply with value to 3-5 posts from Tier 1-2 accounts
- Add technical insights, not just “great post”
- Share relevant experience from building Lattice
- Ask thoughtful follow-up questions
-
Retweet/quote tweet 1-2 posts from smaller builders (<10K followers)
Weekly Actions
-
Post original content about Lattice development:
- Use Commit-to-Tweet Framework
- Tag relevant accounts when genuinely applicable
-
Create one thread about:
- Knowledge graph patterns
- MCP integration techniques
- CLI tool development
- Semantic search approaches
-
Engage with trending discussions in #buildinpublic, knowledge graph topics
Engagement Templates
Replying to KG/MCP posts:
Interesting approach! I've been building something similar with [Lattice] -using DuckDB + embeddings for local-first semantic search.
Question: How do you handle [specific technical aspect they mentioned]?Quote tweeting with value:
This is exactly why I built @lattice_cli - [specific problem they describe].
The key insight: [your solution approach].
[Optional: link to relevant code/docs]Introducing Lattice in relevant threads:
Been solving a similar problem with Lattice - a CLI for buildingknowledge graphs from markdown docs.
Key features:- Local-first (DuckDB)- Semantic search via embeddings- Entity extraction from frontmatter
Happy to share more if useful!Hashtags & Keywords
Primary (use 1-2 per post)
Secondary (context-dependent)
Keywords to Monitor
- “knowledge graph”
- “MCP server”
- “semantic search”
- “AI memory”
- “graph database”
- “PKM tool”
- “Claude Code”
- “document search”
- “entity extraction”
Tracking Progress
Metrics to Watch
| Metric | Target | Frequency |
|---|---|---|
| Profile views | +20% monthly | Weekly |
| Follower growth | +10% monthly | Weekly |
| Engagement rate | >5% | Per post |
| Replies received | 2+ per post | Per post |
Account-Level Tracking
Track which accounts engage back:
- Tier 1: Direct replies, retweets, follows
- Tier 2: Mutual follows, thread participation
- Tier 3-4: Community building, collaboration opportunities