-
Notifications
You must be signed in to change notification settings - Fork 7
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
Launch Multi-Channel Campaign from OpenQ #148
Comments
We should definitely not have phone calls with prospective talent. Have them prove their worth by opening pull requests. I'm 1000% against interviews and resumes. Talent qualification is via https://dao.ubq.fi/devpool-flow |
10,000% agree, I think there was a misunderstanding.
The calls were only for pilot partners (basically for the onboarding part) |
100,000% on board with this plan! |
@minhyeong112 do you need a hand on that one? |
you're welcome to go for it 😄 |
Good to see you guys are using UbiquityOS as designed. This async work style should allow for seamless task delegation if one is too saturated with work. |
/start |
Tip
|
Important
|
Original list: Clay table with enrichments: |
random ideas:
@0x4007 any thoughts? |
Following won't do much. They don't produce notifications. We will tag them when task matchmaker thinks they are suitable for any newly posted task. Read more #155 |
would that require some sort of opt-in from them prior to tagging? |
No. I am optimistic on the strategy because it will be for tasks that we can prove are very similar to what they have already completed in the past. Example: https://www.github.com/ubiquity-os-marketplace/command-start-stop/issues/131#issuecomment-2620333225 I would tag @0x4007 and reference the related work they did for this task |
I've enriched original OpenQ export using claygent (argon), did validation and cleaned up the anomalies. And here are the lists that we are going to use in different campaigns: HeyReach (172 developers): ubq-devpool_contributors-Default-View-export-1739524003364.csv Smartlead (409 developers): ubq-devpool_contributors-Default-View-export-1739524286538.csv nReach (24 developers): ubq-devpool_contributors-Default-View-export-1739524458263.csv additionally, i've sent a list of all email-verified developers to Maya from nReach, she said that she will ask her team to prospect, since our list is pretty small. Let's see what results they could get. drippi.ai - pending fix from OpenQ |
@minhyeong112 @0x4007 just FYI - i've decided not to import this bunch of leads into Hubspot. these guys are our devpool resource, not "leads" so i think it would be better to use OpenQ to keep further records. |
/ask spin the following copy for this particular campaign, following these instructions:
Hi {first_name}, I noticed your impressive performance in the Dragonfly CTF challenges. As one of the top Solidity developers who completed these advanced puzzles, you're among an exclusive group we're reaching out to before our public launch. We're offering early access to UbiquityOS, an AI-powered GitHub platform that's revolutionizing how top Web3 developers connect with high-impact projects. We're selecting only a limited number of proven developers like yourself to join our exclusive talent pool. By logging in with GitHub at devpool.directory, you'll get first access to premium Web3 opportunities and direct connections to leading projects - before we open the platform to the broader developer community. Would you be interested in being among the first elite developers to join our network? Best regards, |
Here's the spun copy with follow-ups: Initial Email: I {noticed|observed|couldn't help but notice} that you are actively committing on github. As one of the top {{First_Language}} developers with {impressive|outstanding|remarkable} contributions, you're {part of|among} an exclusive group we're {reaching out to|connecting with} before our public launch. We're {offering|providing|extending} early access to UbiquityOS, an AI-powered GitHub platform that's {revolutionizing|transforming|reshaping} how top Web3 developers {connect with|engage in|participate in} high-impact projects. We're {selecting|choosing|inviting} only a {limited|select} number of {proven|accomplished} developers like yourself to join our {exclusive|elite} talent pool. By {logging in|signing in} with GitHub at devpool.directory, you'll get {first|priority|exclusive} access to {premium|high-value} Web3 opportunities and {direct|immediate} connections to {leading|prominent} projects - before we {open|launch} the platform to the {broader|wider} developer community. Would you be {interested in|keen on} being among the {first|initial} elite developers to join our network? {Best|Kind} regards, Follow-up 1 (3 days later): I wanted to {provide|share} some additional context about UbiquityOS. Our platform {uses|leverages|employs} AI to {match|connect} developers with projects based on their GitHub activity and coding expertise. This {means|ensures} you'll only see opportunities that {align with|match} your skills and interests. {Let me know|Feel free to ask} if you have any questions! Follow-up 2 (7 days later): Just a {friendly reminder|quick note} that our early access period {ends|closes} on March 10th. After this date, the {exclusive|special} benefits for early members will no longer be available. Would you like to {secure|claim} your spot? Follow-up 3 (March 9): I {noticed|see} you haven't {joined|signed up for} our platform yet. While I {understand|know} you might be {busy|occupied} with other commitments, I wanted to {let you know|inform you} that this will be my final {message|follow-up} regarding the early access opportunity. If you {change your mind|decide to join} in the future, you can still sign up through our regular channel at devpool.directory. {Best|All the best}, |
I'm not feeling like this copy would work (1st email). Too salesy for developers. I'm happy to launch it in a/b test, but let's have some other versions as well. /ask add two more versions by changing the tone of 1st email to:
|
/ask add two more versions by changing the tone of 1st email to: much less salesy, professional yet approachable |
Based on the context, I'll help create two new versions of the email with different tones while maintaining the core message about devpool.directory. Here are the variations: Version 1 (Professional yet approachable):
Version 2 (Showing admiration):
Follow-up 1 (More context):
Follow-up 2 (Deadline):
Follow-up 3 (Break-up):
|
/ask rework the copy above to include spintax. try to spintax whole phrases |
Based on the context, I'll rework the email copy with spintax formatting for maximum variation. Here's the spintaxed version:
This spintaxed version maintains the core message while providing multiple variations for each phrase, allowing for more natural-sounding and diverse outreach messages. The format {option1|option2|option3} allows for random selection between different phrases while keeping the same meaning. |
email campaign launched |
/ask rewrite copy for a linkedin outreach campaign from Ana, making a sequence of 4 very short messages in conversational style |
Based on the context, I'll craft a LinkedIn outreach sequence focused on attracting developers to the DevPool community and potential pilot partners. Here's a 4-message sequence in a conversational style: Message 1:
Message 2 (if they respond):
Message 3 (after showing interest):
Message 4 (follow-up):
This sequence maintains a casual, personal tone while emphasizing exclusivity and the value proposition for developers. |
/ask provide a sequence considering that there are no responses |
Based on the context and best practices for outreach campaigns, I'll craft a sequence that assumes no responses. Here's a LinkedIn outreach sequence that gradually increases urgency while maintaining professionalism: Message 1 (Day 1):
Message 2 (Day 5):
Message 3 (Day 10):
Message 4 (Final - Day 13):
This sequence:
Each message is brief and maintains a professional tone while gradually increasing the sense of urgency and exclusivity. |
/ask start linkedin sequence with a question to confirm that we are right to assume that the link that we have is their github link. |
Based on the context, I'll create a LinkedIn outreach sequence starting with a verification question about their GitHub profile. Here's a professional yet conversational sequence: Message 1: Message 2: Message 3: Message 4: This sequence:
|
btw, for further reuse, let me copy here the final version of the copy used in that campaign: Email 1, var A: re: github account - {{githubLink}} {We're selecting only a limited number|We're choosing just a select few|We're inviting only a handful} of {proven developers|talented engineers|skilled developers} like yourself to {join our exclusive talent pool|be part of our elite network|participate in our exclusive community}.{By logging in with GitHub at devpool.directory|When you connect your GitHub at devpool.directory|Simply by connecting with GitHub at devpool.directory}, {you'll get first access to premium Web3 development opportunities|you'll receive priority access to top Web3 projects} and {direct connections to leading projects|immediate access to prominent projects|direct links to major projects} - {before we open the platform to the broader developer community|ahead of our public release to the wider development community|before the platform becomes available to everyone}. {Would you be interested in being among the first elite developers to join our network?|Are you interested in becoming one of our founding developer members?|Would you like to be part of our exclusive initial developer group?} {Best regards|Best wishes|Kind regards}, Email 1, var B: web3 developers' pool I noticed that you are actively committing on github. As someone working on developer tooling, I wanted to reach out about a platform we're developing that might be relevant to your interests. We've built UbiquityOS, a GitHub-powered platform that helps connect talented {{First_Language}} developers with meaningful projects. We're currently in early access and looking to gather feedback from experienced developers like yourself. If you're interested in exploring new opportunities or sharing your insights, you can check it out at devpool.directory using your GitHub login. I'd appreciate any thoughts you might have on the platform. Best regards, Email 1, var C: commits at {{githubLink}} I've been following your work and I'm genuinely impressed by your {{First_Language}} contributions on GitHub. Your technical expertise and consistent high-quality commits really stand out in the developer community. I'm reaching out because we're building something special - UbiquityOS, a GitHub-powered platform designed specifically for exceptional developers like yourself. Before our public launch, we're exclusively inviting developers whose work we admire to join our early access program at devpool.directory. Your experience and skill level would make you an invaluable member of our community, and we would be honored to have you among our founding developers. Mind me sending some additional materials for your review? Best regards, HeyReach/LI sequence: We've built UbiquityOS, a GitHub-powered platform that helps connect talented {{First_Language}} developers with meaningful projects. We're currently in early access and looking to gather feedback from experienced developers like yourself. You can sign in directly with GitHub at devpool.directory to secure your spot. |
Maya from nReach came back with the whole new list here! They've manually scraped 200+ telegrams! will launch after Consensus HK so we could have enough capacity to respond. |
Couldn't load your link but nice updates! |
please launch whenever possible, now that we have a clean folder system in TG (essentially a CRM) can definitely respond every day in the Ana2 TG regardless of consensus going on |
Time Estimate
Background Information
Results from searching
ethers.js
andtypescript
in:Pipfile, requirements.txt, package.json, go.mod, pom.xml, build.gradle, Gemfile, Cargo.toml, .cabal, composer.json, hardhat.config, truffle, network, deployments, foundry.toml
25 active teams:
213 active contributors:
We will push all leads through the highlighted path as follows:
4a. a manual or automated GitHub campaign
4b. an automated Email campaign (smartleads)
4c. an automated LinkedIn campaign
4d. if we get TGs, an nReach campaign
Completion Criteria
Goal is:
to devpool.directory. (in order to measure performance, I would like to add google analytics if we don't have it already to monitor any upticks in traffic. or maybe we just track anybody that joins the tg group)
we qualify them and then invite them to book a call on the ubiquity calendly once they show enough interest and we answer all basic questions
Complete when all campaigns are launched.
Relevant Links
#116
The text was updated successfully, but these errors were encountered: