-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mindmap and strategy deck for outreach in 2025 #105
Comments
@v4d33m looks great. I think the last two (tools and messages) would be the most valuable to map out in detail. |
@gentlementlegen no price tag here. Can you fix that? |
/start |
Here is the first draft of the strategy doc: Disclaimer: this is a preliminary document for our async discussion, don't close the issue before we get to the final one. Here is also an xls file with ICP description: https://docs.google.com/spreadsheets/d/1OIGxZ-foDL9ddzxKe2Ji-Ct38AtU3j0k/edit?usp=drive_link&ouid=102054621059928486501&rtpof=true&sd=true @0x4007 @minhyeong112 - looking forward to hearing your thoughts on ICP/personas |
Thanks for putting this together. I left comments on the Google Sheet. I wonder if it makes sense to produce the doc in the form of a GitHub issue. In exchange for more primitive collaboration tools (we can directly edit your spec, but only leave comments in the thread below) we can currently receive financial incentives (our spec and comment scoring system) it also forces us to focus on the content and less on the visuals which can yield time savings. Lastly it does technically train our system since we capture all the text on here now. The data can be used with the /ask command (which is a bit unstable at the moment but we are working on a fix within the next couple weeks) One day in the near future, I think that we can post Google doc links in the issue specification, and then capture all the web hook events that occur on the doc and once the issue is closed as complete, we can associate any of the linked docs and all of the work done on them to offer financial rewards for everybody's contributions. |
Ironically the bot is overworked and dropping requests (api rate limiting) so we have been working to optimize api usage these days to minimize the dropped requests. Each GitHub organization has their own limits and it seems that we use it quite a bit within this org. |
@0x4007 thank you for your input. Please have another look at it - I'd love to finish it today. |
Then let's leave tables and graphs (those are mostly informational anyway) where they are and I will copy&paste here the rest of the content to discuss. I'll post each slide/topic here so it could be referred separately. Let me know if you want it to be present differently. |
Prospecting DAOs:
VCs:
Enrichment tools – Clay (LI, emails, phone numbers), nReach (telegram) |
Channels
Email campaign
Telegram campaigns via nReach |
Campaigns Static DAO/VC campaign:
Event campaign:
I've edited campaign description:
|
Messaging for events campaigns here: |
Maybe we can make another dedicated account that represents me? I could even use a real picture of myself for conferences and such. I'm a little bit unsure about attaching my real account because it's very valuable to me. I've been using it since like 2015 and I use it daily. If anything were to happen to it, it would be a big problem for me. |
that would be obvious that this is a new acc that has been just created. also, LinkedIn tend to ban duplicate accounts. Anyway, we can still use Miguel and Ana for campaigns, and then you'd communicating "manually" with cherry picked leads. How does that sound? |
I want to clarify that I was referring to telegram I don't care anything about my LinkedIn account |
I'd like to prepare a mindmap and the slide deck to cover the following:
@minhyeong112 since you were the first to bring it up, is there anything else that you would like me to potentially cover in that doc?
The text was updated successfully, but these errors were encountered: