Ecosystem Success

Onboarding projects into the ecosystem

The Ecosystem Success (ES) team works with projects to help them find early success in the NEAR ecosystem. This is accomplished via a consultative relationship that leverages a growing list of service providers that can assist projects in a variety of domains. The ES role can be broken down into the following primary components:

• Onboard new projects into the program to learn about their plans, needs, and experience

• Host regular check-ins with projects to support them and learn about their experience

• Maintain community resources including the ecosystem map and service menu

• Coordinate with service providers to help projects remove project blockers

• Monitor ecosystem trends, developments and metrics.

• Share insights with the NEAR community

Onboarding - First Contact

The checklist below helps the ES team understand a project and its needs. After we have this information we can design a follow-up plan.

Onboarding Tip: As much as we want to help, do not over-promise (and under deliver!). ES provides the most value by matchmaking projects with service providers. The service providers need to be bought in too, so check with them first!

The type of interaction and level of engagement will be guided by the project's forecasted impact. We want to use resources strategically and fairly. If a project doesn’t meet our current requirements then we look to the community for support.

Onboarding Questionnaire:

Project Basics

• Major milestones

  • Do you have a roadmap to share?

  • Do you have a launch planned?

  • What are your key success metrics? (eg. Users? TVL? Exposure?)

• Fundraising

  • Do you plan on fundraising?

  • Target dates and amounts?

Additional Questions

• How did you start building on NEAR?

• How has the experience been?

• Can you describe the team?

• Will your project have a token? *

• Tech stack?

• Are you getting support from any other groups (NEAR collective or otherwise)

• Are there technical blockers or issues? *

• Have you performed security reviews on your smart contracts? Do you need a review? *

• Are you on the ecosystem map? * Can you add yourself?

• Do you nee support? technical?* marketing?* FLO?* product?* design/usertesting?*

ES Response Goals (Q4 2021)

The ecosystem is starting to expand faster than we can track it! This is a good problem that requires us to be strategic with our limited resources. We’ll review these recommendations every quarter while also integrating more community resources. Remember these are recommendations! A project nearing launch will require more support than a project just starting out.

On-boarding Guide - Grant Recipients (Q4 2021):

• $10K+

  • Email intro. Use template announcing Ecosystem team, high level support options, request call with calendly link.

  • Ongoing: Followup with standard ongoing guidelines below.

• <$10K

  • Email intro. Use template announcing what we do. Request async communication channel (tg, discord)

On-boarding Guide - Organic Growth (no grant):

• Large:

  • Intro. Use template announcing Ecosystem team with high level support options. Request 1 hour on-boarding call via calendly.

  • Ongoing: Bi-weekly cadence calls. Success plan. Dedicated point of contact and NEAR Core availability. TG or Discord channel.

• Medium:

  • Intro. Use template announcing Ecosystem team with high level support options. Request 1 hour on-boarding call via calendly.

  • Ongoing: Bi-weekly cadence calls. Success plan. Dedicated point of contact and NEAR Core availability. TG or Discord channel.

• Small growth projects:

  • Intro. Use template announcing Ecosystem team with high level support options. Request 30 min on-boarding call.

  • Ongoing. Monthly check-ins over email or chat DM.

• Micro growth projects:

  • Intro. Email template announcing Ecosystem team. Include onboarding questionaire/typeform. Link to Service Catalog. Direct them to community and discord for ongoing support.

  • Ongoing support. Community supported. Discord.