nReach Adoption

[0x4007]

We have three months for the contract to expire. At $3750 it's quite expensive as we all know so let's make the most of it. We can take 50 accounts per month- unlimited telegram contacts so let's front load loading up the CRM so that we don't waste any credits.

We should also plan to launch the telegram outreach ahead of time so as to not waste the contract.

[0x4007]

@v4d33m i trust that you can take the lead on leveraging this expensive tool in the best way possible!

This task implies experimenting and becoming familiar with the tool, setting up test campaigns, and essentially taking the responsibility of making the most of it.

[v4d33m]

I think @minhyeong112 should start that task because he is already setting up accounts and onboarding session with nReach team

[v4d33m]

we would be there together on the onboarding

[minhyeong112]

/start

[ubiquity-os]

! This task does not reflect a business priority at the moment. You may start tasks with one of the following labels: Priority: 3 (High), Priority: 4 (Urgent), Priority: 5 (Emergency)

[ubiquity-os]

Important

• Be sure to link a pull-request before the first reminder to avoid disqualification.
• Reminders will be sent every 3 days and 12 hours if there is no activity.
• Assignees will be disqualified after 7 days of inactivity.

[gentlementlegen]

@0x4007 Maybe you'd like a different configuration for allowed task priority here?

[minhyeong112]

nreach onboarding appointment made late tomorrow night, invite sent to @v4d33m and @0x4007

[v4d33m]

There are 2 scenarios how we can use nReach:

1. use it to prospect and outreach leads in Telegram:

• Prospecting for Telegram
• Phone number validation for Telegram
• Telegram outreach

2. use to substitute the whole MarTech stack. We need to understand whether nReach is capable for:

• Prospecting emails and phone numbers
• Social selling (integrations with LinkedIN)
• Email warmup and sequencing
• CRM

[0x4007]

Just 1.

We likely will only use for three months. Maybe in the future we can renew and do a separate campaign but I already told them we are done after three months to take time to evaluate results.

@gentlementlegen i think we can disable priority gating on this repository. There's no pulls to review so it's less burdensome to review.

[v4d33m]

Key Points
[📝 9:45 PM - Google Chrome meeting December 18 Notes]
🕞 Started at 09:45 PM on 18 Dec, lasted 1h 45m

• The meeting started with a discussion about Ubiquity OS, a platform that allows developers to understand how much time is spent on each action and optimize processes related to development. Vadim explained that Ubiquity is a rating system integrated with GitHub that allows companies to optimize and gamify processes related to development tasks and issues.
• Maya introduced Nreach's capabilities, including lead generation, campaign management, messaging, and campaign metrics for outreach through Telegram.
• Miguel was allocated a new Telegram account from nReach for outreach purposes.
• They created a sample outreach campaign targeting community managers and partnership marketing roles at various Web3 companies.
• They discussed the messaging and value proposition for the outreach campaign, focusing on personalization and avoiding spammy content.
• The meeting concluded with a discussion about the potential integration of nReach with other tools like HubSpot (that could be custom-built, would cost several thousands $), Zapier (that is going to be there some time soon), and LinkedIn outreach tools (no plans for that).

[v4d33m]

Action Items
[📝 9:45 PM - Google Chrome meeting December 18 Notes]
🕞 Started at 09:45 PM on 18 Dec, lasted 1h 45m

• Miguel to send the list of conferences Ubiquity is planning to attend to Maya so Nreach can try to scrape more information if they don't already have it in their system.
• Vadim to send the CSV export from Clay to Maya so it can be imported into Nreach.
• Miguel to edit and improve the messaging content for the Telegram outreach campaign, especially for the third and subsequent messages, before they are sent out.
• Vadim to explore how to integrate nReach with other tools like HubSpot, Heyreach, and Smartlead.ai to create a cohesive omnichannel outreach strategy. - Vadim
• Vadim to test the CSV import feature in nReach to see how well it works for validating existing contact information. - Vadim
• Miguel to change the bio on the new Telegram account provided by Enrich to something more appropriate for business outreach.

[v4d33m]

People-from-PilotDAOs-(1)-Default-View-export-1734549099910.csv

i've shared this list. trying to import it into nReach now

[v4d33m]

Ok, i've successfully imported the list, however there are some perculiarities, that we need to dig into:
Out of 138 records in our csv, only 67 new contacts were created.
If that's because the others were duplicates and were merged into the existing contacts - than it's fantastic, but there is no way to check in their UI
Out of 67 created contacts - only 5 telegrams were revealed.

[v4d33m]

@minhyeong112 - i've applied group name "Blue chip DAOs Import from clay"

[v4d33m]

@0x4007 FYI - I like their data - it's pretty exclusive and it's all about Web3. We definitely can leverage it.
@minhyeong112 launched his first campaign on community managers, so let's see where those gonna land and let's discuss CxO campaigns and whether we are going to do that in multi-channel manner (i strongly recommend that), or should we just run telegram campaigns (in case we will see 40%+ response rate, why would we need anything else).
We need to do more tests to see how good it is in terms of revealing TGs for VCs and other organizations.
Overall, this tool definitely could be a solution for telegram outreach.

[0x4007]

why would we need anything else).

It's hard to ignore somebody who appears to have reached out across several channels. It seems more legit and less automated.

[0x4007]

Key Points

[📝 9:45 PM - Google Chrome meeting December 18 Notes]

🕞 Started at 09:45 PM on 18 Dec, lasted 1h 45m

• The meeting started with a discussion about Ubiquity OS, ...

I think it makes more sense for you to simply include a link to the meeting notes. My read.ai create links automatically.

It's quite a bit of noise in our conversation thread here

[ubiquity-os]

Passed the disqualification threshold and no activity is detected, removing assignees: @minhyeong112.

[gentlementlegen]

@0x4007 So the configuration is correct and does not require a pull-request as you can see here. However during the run that value was true as you can see here. This is probably due to the fact that the run was triggered from another repo where that value is true. Not sure how we should handle this scenario.

[0x4007]

I suppose it needs to read the local repo config before processing its issues?

When the run starts and it begins collecting issues, it should create a mapping of the correct configs and associate them with each issue.

That's the most direct solution I can think of.

[0x4007]

I think we should target the consensus HK conference people for meetings as well. @minhyeong112 how is everything looking here, can you provide an update?

[minhyeong112]

Test campaign on nReach is complete. nReach's telegram automation works as expected.

Pending:
-edits/approval for copy (see #108)
-lead list cleaning (see #106)

Once #106 and #108 are closed, we can build and launch campaigns on nReach.

[minhyeong112]

Campaign launched on nreach with the leads from #106 and the copy from #108.
Copy can still be continuously improved here https://docs.google.com/document/d/1NZzqT5e0EX6ugxJfl5IquNZikpSyvSmU/edit
I will monitor nreach and respond to leads. Will continue to work with nreach for continuous feedback.
I would say this task is complete.

[minhyeong112]

/start

[minhyeong112]

Campaign launched on nreach with the leads from #106 and the copy from #108. Copy can still be continuously improved here https://docs.google.com/document/d/1NZzqT5e0EX6ugxJfl5IquNZikpSyvSmU/edit I will monitor nreach and respond to leads. Will continue to work with nreach for continuous feedback. I would say this task is complete.

Requesting approval based on this comment.

experimenting and becoming familiar with the tool, setting up test campaigns, and essentially taking the responsibility of making the most of it

I believe we have met the criteria, but open to any and all feedback! Will continue to be responsible for this tool of course.

[0x4007]

@minhyeong112 something I've been thinking about for a while, but I think that we have much greater success if we put together
educational materials highlighting the system features, and its benefits, together.
Then when you send out all this messaging, you can also link the materials so they can peruse and get a better understanding of what exactly were trying to get them to use

[minhyeong112]

agree! I see you've made #109. I'll comment on that task there.

[0x4007]

I have mixed feelings about continuing with the campaign.

On one hand the default behavior is to never wait for other dependencies.

On the other hand I'm not sure how long it will take for us to produce the materials but at least I can pop in a draft as a reference/starting point of what I wrote on the airplane.

Perhaps you can take this information and adjust what you communicate during this campaign.

Will post under #109

[minhyeong112]

https://github.localhost/#:~:text=never%20wait%20for%20other%20dependencies

Agree with this. Definitely more of a "fix the plane while it's flying" kinda guy. I paused the telegram campaign this morning. Will switch to Ana's picture/bio, make edits based on #108 and #109 in about an hour, and unpause the campaign.

[minhyeong112]

-I just switched the nReach-provided tg account to use Ana's pic and bio

-I'm actually talking with people already that are willing to set up appointments already (in Hong Kong for example)

-I think we should set up a calendly for Ana where she sets appointment times to chat with people based on her/your availability at the conferences

-if she/someone keeps it up to date with conference attendance, we can use that to manage in-person meeting times/locations

-I will add these comments to #104

[0x4007]

https://github.localhost/#:~:text=never%20wait%20for%20other%20dependencies

Thats the craziest link that your browser just invented.

-I think we should set up a calendly for Ana where she sets appointment times to chat with people based on her/your availability at the conferences

We have https://calendly.com/ubiquitydao/ in case thats useful I can share access with you.