
In our previous article, we explained who Business Developers are and why this role matters in Web3. Now it’s time to go one level deeper.
If you’ve joined the Nomis Community Hub or are thinking about it, you should read this.
This is the exact process our team uses — adapted for Hub contributors so you can learn, practice, and earn confidently.
Let’s break the whole BD workflow into three stages:
1. Research (finding the right projects) 2. Outreach (starting conversations) 3. Closing (bringing integrations to life)
And now — the full guide.
Research is the foundation of good BD. You’re not messaging random teams. You’re choosing projects that Nomis can actually help — and where collaboration makes sense for both sides.
When looking at a project, check these simple markers:
Fit with Nomis: Where can our scoring or data make the project better?
Your goal at this stage is simple: Is this project relevant? And can Nomis add value?
If yes — continue.
DMs are usually:
Collect their profiles (Telegram, X, LinkedIn) and keep them organized.
Before you message anyone, answer one question:
“What exactly can Nomis help this project with?”
Some examples:
Once you know the angle, your outreach becomes easier — and 10× more effective.
This is where BD becomes active. Your job is to make the first move — politely, clearly, and with value.
The best BD channels are:
For important leads, always try more than one channel.
Your tone should be confident but polite, short and clear, personalized (never generic). And, most importantly, not “salesy” or spammy.
Good BD messages feel human, not robotic.
A clean first message includes:
Example:
“Hi! I’m part of the Nomis BD team. We help ecosystems and products filter for real users and run clean campaigns through on-chain reputation. Saw your recent update about expanding to new chains — we can support that with verified user segmentation and co-marketing. Would you be open to a quick chat?” Simple. Personal. Relevant.
People are busy. Most deals happen because of good follow-up.
Your pipeline:
Professional. Respectful. Effective.
Once a project starts replying, your role shifts from “initiating” to “structuring.”
A good offer answers three questions:
Include:
Before confirming anything, sync with:
**Tech team: **requirements, feasibility
Marketing: announcements, campaigns, content
**Product: **features, Score support
**Legal: **if needed
This ensures everything is realistic.
Fix all agreements:
This is the final stretch:
Once everything is complete — the integration is live.
This is the exact BD flow our internal team uses. And as a member of the Nomis Community Hub, you’re learning the same system — the real one, not a simplified “intern version.”
By following this process, you:
With Nomis Hub you’re building your future. And you’re getting paid for it.