by
COZ / Tyler Adams (Facilitator)
12 September 2026
How to Pitch Market Opportunities, Lobby the Council, and Shape Neo's 5-Year Strategy
Meteor is Neo's open, structured initiative to evaluate global market opportunities, assign strategic priority, and establish unified focus for Neo's growth over the next 5 years (2026–2031).
Meteor assigns market priority and unified focus. Depending on Council voting, there may be one or multiple target opportunities prioritized for development.
A living, repeatable process supporting new opportunity injection, periodic reweighting, and strategic focus shifts as markets mature.
Built on open research, objective scoring against 16 standardized criteria, and active ecosystem-wide participation rather than closed-door mandates.
A blockchain ecosystem benefits greatly from its builders, token holders, and active observers. In Meteor, the community is an important source of market signals, user perspectives, and priority discussions.
Share candidate market spaces, developer friction points, and architecture pitches directly with the nominated Research Team.
Lobby Council members on the 16 voting categories to ensure ecosystem priorities reflect true community conviction.
Submit problem statements & architecture fits to Dylan, Malcolm, John, and the Research Group.
Communicate category weighting priorities and strategic tradeoffs to voting Councilors.
The Research Team is tasked with packaging 5 to 10 high-potential Market Opportunity Dossiers. They need your field intelligence, developer pain points, and commercial ideas.
Council members will vote on the relative importance of 16 evaluation categories during the 2-week voting window (Monday, September 14 – Friday, September 25, 2026).
Reach out on Discord, X, and governance forums. Voice your perspective directly to Council representatives before ballots close.
When discussing priorities with Council Members and framing your candidate pitches, reference these 16 standardized evaluation criteria:
| # | Category | Description (What It Tests) | Scoring Examples (Weak vs. Strong) |
|---|---|---|---|
| 1 | Right market timing (next 5 years) | Is this a good opportunity for Neo to pursue now, with a realistic chance to matter during the next five years (2026–2031)? |
Weak (1)
Market is fading, too early to support, or Neo arrives after the window has closed.
Strong (10)
Clear market opening now, with high relevance and growth sustained over the next 5 years. |
| 2 | Long-term staying power (10 years) | If the first version works, is the underlying need likely to stay useful, relevant, and adaptable for a decade? |
Weak (1)
Depends mainly on a short-lived trend, temporary incentive, or fleeting market cycle.
Strong (10)
Addresses a durable, foundational need that can evolve and expand for many years. |
| 3 | Strength of the problem | Does this solve a real problem that users or organizations care enough about to change behavior or spend budget? |
Weak (1)
Vague, minor, or mostly an internal ecosystem hope rather than a felt customer pain.
Strong (10)
Clear, painful, frequent, and important enough that customers actively seek an alternative. |
| 4 | Clear customer, buyer, and route to reach them | Do we know who uses it, who approves/pays for it, why they act now, and how Neo can practically reach them? |
Weak (1)
Users, buyers, and GTM routes are vague; relies on passive hope that someone will adopt it.
Strong (10)
Target user group, decision maker/payer, trigger to act, and distribution path are crisp. |
| 5 | Why Neo should do this | Does this direction leverage Neo's distinctive strengths (dBFT, NeoFS, Oracles, Neo X, SpoonOS) and reinforce Neo's position? |
Weak (1)
Any generic chain could do it identically; gives Neo no distinctive advantage or brand lift.
Strong (10)
Directly harnesses Neo's technical, governance, and brand strengths to create a clear home. |
| 6 | Ability to stand out and stay ahead | Can this become meaningfully differentiated and defensible rather than easy to commoditize or copy by L1s/L2s? |
Weak (1)
Looks like existing crowded offers with no moat; easily replicated or outspent.
Strong (10)
Clear structural reason to choose Neo; built-in stickiness and sustainable differentiation. |
| 7 | Believable way to make money | Is there an early, credible path to revenue, sustainable fee capture, or direct economic value creation? |
Weak (1)
No identifiable payer; relies on wishful future monetization or indefinite subsidies.
Strong (10)
Clear paying customer, high-value outcome, and believable ongoing value capture. |
| 8 | Ability to bring useful activity to Neo | Will this bring real recurring builders, users, partners, applications, and liquidity into the Neo ecosystem? |
Weak (1)
Isolated one-off project or announcement with little lasting ecosystem spillover.
Strong (10)
Creates repeatable incentives for outside developers, capital, and users to engage with Neo. |
| 9 | Speed to a useful first proof | Can a focused, lean team deliver something credible to test, show, or sell quickly without a multi-year program? |
Weak (1)
First proof takes years, requires a massive team, or depends on heavy unresolved dependencies.
Strong (10)
Small team can deliver a functional prototype, pilot, or initial validation within months. |
| 10 | Practical path to a real first product (MVP) | How realistic is it to obtain required non-code assets, licenses, capital, counterparties, liquidity, or audits for a real MVP? |
Weak (1)
Needs heavy external licenses, massive liquidity, or complex regulatory assets before a real MVP can exist.
Strong (10)
Required assets and conditions are accessible; normal product execution delivers a truthful MVP. |
| 11 | Can Neo build and operate it well? | Can the ecosystem realistically build, secure, operate, and maintain this with available or obtainable technical talent? |
Weak (1)
Relies on unproven tech, fragile architecture, unmanageable security, or implausible operations.
Strong (10)
Practical architecture, manageable security/ops, and credible engineering capability in place. |
| 12 | Manageable legal, trust, and reputation risk | Can Neo pursue this direction safely without severe compliance hazards or unmanageable reputational exposure? |
Weak (1)
Severe regulatory/legal hazards or forces promises the ecosystem cannot safely keep.
Strong (10)
Risks are well-understood, proportionate, and safely manageable through clean operating design. |
| 13 | Ability to learn quickly | Can Phase 1/2 rapidly test critical assumptions through user conversations, sales feedback, or small staged pilots? |
Weak (1)
Critical assumptions cannot be validated until after massive capital expenditure or long delays.
Strong (10)
Key hypotheses can be pressure-tested rapidly with real users, partners, and lightweight tests. |
| 14 | Useful future options | Does this direction open valuable strategic options and adjacent expansion paths even if the initial wedge pivots? |
Weak (1)
Narrow dead-end bet; if the initial concept misses, little reusable capability or learning remains.
Strong (10)
Builds reusable infrastructure, relationships, and market footholds that support multiple future paths. |
| 15 | A clear Neo story | Can the direction be explained simply, crisply, and convincingly as a logical Neo foothold to builders, investors, and users? |
Weak (1)
Feels random, confusing, or disconnected from what Neo stands for and is building toward.
Strong (10)
Inspiring, cohesive narrative that clearly articulates Neo's strategic rationale and role. |
| 16 | Market attention, hype, and token demand | Can this credibly generate organic attention, narrative pull, and structural demand for NEO and GAS? |
Weak (1)
Low narrative pull; depends on artificial promotion with no real connection to token utility.
Strong (10)
High-interest narrative with clear mechanics driving genuine ecosystem excitement and token demand. |
Public release of the Operation Meteor framework across the ecosystem. The 16 evaluation categories, research methodology, and governance rules are opened for ecosystem review.
Review the 16 evaluation criteria, join ecosystem discussions, and prepare candidate market problem statements.
The 21-seat Neo Council engages in a 2-week voting window to assign relative strategic weights across the 16 decision categories, establishing the mathematical lens used for scoring candidate markets.
Directly lobby Council members across Discord, X, and governance forums on category tradeoffs (e.g. Near-term Speed vs. Long-term Moats, Token Utility vs. Technical Prestige).
Parallel 2-week Council voting session ranking technical backlog items, core infrastructure enhancements, and developer tooling priorities to ensure engine readiness for prioritized workloads.
Share feedback on developer tool bottlenecks (SDKs, indexing, compiler features, NeoFS tooling) in community developer channels.
The nominated Research Team investigates global macro trends, interviews builders, aggregates community submissions, and clusters market opportunities into rigorous standardized templates.
Submit concrete market problems, developer friction points, and customer pain points to Research Team members on GitHub Discussions, Discord, and X.
Formal public release of 5 to 10 standardized Market Opportunity Dossiers detailing problem severity, target buyers, Neo technical leverage, commercial defensibility, unit economics, and required MVP assets.
Read, debate, and pressure-test published dossiers in public AMAs, Reddit threads, and Discord stages before Council scoring begins.
2-week voting window where all 21 Council members independently score each published Market Opportunity Dossier across the 16 weighted evaluation categories (1–10 scale per criterion).
Highlight dossier strengths, hidden operational risks, or technical synergies to Council representatives during their initial scoring window.
1-week structured Delphi review cycle. Anonymized scoring distributions, standard deviations, and polarized outlier ratings are shared among Council members to deliberate differing perspectives.
Observe public governance summaries detailing major points of debate and strategic alignment.
1-week final adjustment window where Council members may update ballots based on Delphi insights. Scores are finalized, weighted, and the consensus opportunity rankings are published openly with full rationale.
Review finalized rankings, score breakdowns, and approved opportunity priorities across official ecosystem channels.
Prioritized market opportunities enter Phase 1 Product Definition Workshops. Technical architects, product designers, and ecosystem leads author execution roadmaps, resource allocations, and grant programs.
Apply for targeted builder grants, join working group hackathons, and begin building applications on the prioritized product roadmaps.
Operation Meteor is a recurring, living governance mechanism. Market shifts trigger periodic category re-weighting, new dossier research sprints, and iterative priority updates over the 2026–2031 horizon.
Continuously submit emerging market trends, new DePIN/AI/RWA hardware protocols, and competitive landscape feedback.
Join the conversation across community channels today. Pitch your market concepts to the nominated Research Team and lobby Council Members on category priorities.
Head to GitHub Discussions, the Neo Discord governance channels, or the Neo Subreddit to engage directly.
Frame your proposal around a clear market pain, buyer profile, and why Neo's stack (dBFT, NeoFS, Neo X, Oracles) provides a distinct edge.
Express which of the 16 voting categories matter most to you before the Category Weighting ballot closes on September 25, 2026.