How BD Works Inside Nomis: A Complete, Simple Guide From the Nomis Team

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.

1. Research: Finding the Right Projects

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.

1.1. Define the “ideal lead”

When looking at a project, check these simple markers:

• Ecosystem traction: TVL, trading volume, active users, growth pace.
• Token status: Do they have a token? Are they preparing for TGE? Already listed?
• Social activity: X, Telegram, Discord, LinkedIn — size, engagement, tone.
• Partners & investors: Known funds, ecosystem grants, strategic partners.
• Vertical: L1/L2, DeFi, SocialFi, GameFi, tools, infra, NFT, etc.

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.

1.2. Find the right people (Decision Makers)

DMs are usually:

• CEO / Founder
• COO
• BD Director / Head of Growth
• Partnerships Lead
• Sometimes Marketing Lead

Collect their profiles (Telegram, X, LinkedIn) and keep them organized.

1.3. Define “touchpoints”

Before you message anyone, answer one question:

“What exactly can Nomis help this project with?”

Some examples:

• Boosting the community
• Better user segmentation
• Airdrop protection
• Partner activations
• Integrations
• Co-marketing
• Access to the Nomis ecosystem and ScoreFront

Once you know the angle, your outreach becomes easier — and 10× more effective.

2. Outreach: Starting the Conversation

This is where BD becomes active. Your job is to make the first move — politely, clearly, and with value.

2.1. Choose the right channels

The best BD channels are:

• Telegram
• X (DMs)
• LinkedIn
• Discord
• Email (if needed)

For important leads, always try more than one channel.

2.2. Use the right TOV

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.

2.3. The first message

A clean first message includes:

• who you are
• why you’re writing
• something personal about their project
• a clear, short value proposition
• a call to action (suggest a chat or quick sync)

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.

2.4. Follow-ups

People are busy. Most deals happen because of good follow-up.

Your pipeline:

• First message
• Follow-up after 2–3 days
• Follow-up after 3–5 more days (add value: news, idea, reference)
• Break-up message (“I’ll let you go for now. If timing changes, I’m here.”)

Professional. Respectful. Effective.

3. Closing: Turning Interest Into Integration

Once a project starts replying, your role shifts from “initiating” to “structuring.”

3.1. Build a personalized offer

A good offer answers three questions:

1. What Nomis can do for the project
2. What results we expect
3. What the integration or campaign looks like

Include:

• key benefits
• format of collaboration
• timelines
• example cases (if relevant)

3.2. Align internally

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.

3.3. Planning

Fix all agreements:

• deadlines
• responsible team members
• communication channels
• next steps

3.4. Implementation

This is the final stretch:

• technical integration
• joint announcements
• ScoreFront listing if applicable
• marketing activities
• tracking results

Once everything is complete — the integration is live.

How This Helps You Inside Nomis Hub

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:

• build real BD skills
• learn how to research ecosystems
• talk to teams confidently
• build your personal network
• earn for every successful connection
• grow your career in Web3 from the ground up

With Nomis Hub you’re building your future. And you’re getting paid for it.

Start working in Hub