The Minimum Viable Growth Ecosystem: How to Design a Connected Public Surface

A product can be present on six public channels and still leave a prospective user with nowhere useful to go. The X account announces features but never reaches documentation. The developer repository is active but disconnected from the product site. A community link is impossible to verify. Each surface exists, yet the system between them does not.

Do not optimize for presence everywhere. Build a connected path in which every maintained surface has a defined audience, job, owner, next handoff, and success signal. The practical decision is not “Which accounts do we have?” It is “Which surfaces help someone discover, trust, evaluate, adopt, or advocate for the product—and which should we keep, repair, consolidate, or deliberately close?”

Violet’s research supplies the evidence problem underneath that decision. We selected 16 consumer-crypto products and reconciled 224 product-by-surface cells across 14 public surfaces. Visibility was uneven and source-dependent, and unresolved evidence could not honestly become zero. The operating framework in this article is Violet’s strategic recommendation; the cohort did not measure traffic, handoff completion, conversion, or the growth effect of any surface mix.

This is original Violet analysis of public data followed by a separately labeled operating framework. Violet designed the cohort, reconciled the public identities, and built the evidence-state model. The underlying records remain attributable to their publishers and platforms.

At a glance

Growth-leader question	Decision
Must we operate every plausible channel?	No. Maintain a surface only when it has a named audience and job in the growth system.
What makes a surface operationally complete?	A canonical entry, next handoff, owner, job-specific signal, and review decision.
What should happen to an unresolved surface?	Investigate it only if the surface has a strategic job; never convert it to zero.
What did Violet’s research establish?	Public identities and coverage states across 16 selected products—not traffic, conversion, adoption, or causal growth.
What should the audit produce?	A keep, repair, consolidate, or close decision for every maintained surface.

The minimum viable growth ecosystem is not the smallest number of accounts. It is the smallest connected set that can move a named audience through the jobs the strategy actually requires.

Surface jobs

A maintained public surface needs one primary job, a next handoff, an owner, and a success signal. Otherwise it is presence without a growth function.

Use six jobs to make the decision concrete:

Surface job	Reader or user need	Example surface types	A signal appropriate to the job
Discovery	Learn that the product or use case exists	Search result, social account, event, aggregator	Qualified discovery visits or relevant reach
Trust	Verify identity, legitimacy, and claims	Official site, support page, verified account	Successful verification or reduced identity confusion
Evaluation	Understand fit and compare the product	Documentation, demo, repository, use-case page	Meaningful evaluation actions
Participation	Ask, contribute, govern, or join	Forum, Discord, governance, developer community	Qualified participation and resolved questions
Adoption	Complete the next product action	Product, onboarding, integration, download	Activation against the declared product action
Advocacy	Carry useful proof or knowledge outward	Community, creator, partner, referral surface	Attributable recommendations or useful redistribution

These are operating categories, not findings from the 16-product cohort. One surface may support several jobs, but assigning one primary job forces the team to say why it exists and how it should be judged. A social account assigned to discovery should not be defended with community-support activity; a forum assigned to participation should not be graded by raw follower count.

Surface evidence

Violet selected a purposive, maximum-variation cohort of 16 consumer-crypto products; it is not a probability sample of the market. The products span self-custody and onboarding, swapping and trading, collecting and marketplaces, and social or attention products, from MetaMask to Pump.

Violet reconciled 224 product-by-surface cells while keeping observed, explicit-negative, source-not-covered, unavailable, and unresolved states separate. All 16 selected products had an exact official website and accepted official X identity; 15 had a verified qualifying public repository identity and one remained unresolved.

Figure 1. Violet’s evidence matrix. It shows which identities or qualifying records could be established. It does not show which surfaces produced attention, movement between surfaces, activation, or revenue.

The matrix explains why a simple presence count is a weak planning tool. Official websites and X identities were complete for the selected cohort, while Instagram, YouTube, TikTok, community, and event evidence remained partial. DappRadar and DefiLlama covered different entities and exposed different units.

Evidence family	Accepted state	What a growth leader may use it for
Official website	16 observed	Verify the canonical product identity
Public repository	15 observed; 1 unresolved	Locate the accepted public technical surface
X	16 observed; 8,258 tweets	Describe the selected-account publishing corpus
Instagram	8 observed; 8 unresolved; 669 posts	Plan additional identity verification, not a cohort benchmark
YouTube	9 observed; 7 unresolved; 195 videos	Plan additional identity verification, not a cohort benchmark
TikTok	2 observed; 4 unavailable; 10 unresolved; 17 posts	Use only as narrow retained evidence
Community	30 observed; 2 explicit negatives; 48 unresolved across 80 cells	Verify specific public participation paths
Events	10 qualifying events across 6 products; 10 product states unresolved	Use as a partial event pilot
DappRadar	7 exact cohort joins; 9 source-not-covered	Understand exact accepted source coverage
DefiLlama	15 matched; 1 source-not-covered	Understand accepted catalog coverage

These denominators cannot be added into one ecosystem score. They can identify where evidence is complete, where a first-party answer exists, and where a strategically important surface needs investigation.

Surface states

Violet reconciled 224 product-by-surface cells while keeping observed, explicit-negative, source-not-covered, unavailable, and unresolved states separate.

An unresolved surface is a research task, not a performance penalty. A source-not-covered surface requires a different source, not a zero.

Evidence state	What it establishes	Operating response
Observed	The exact identity or qualifying record passed its source gate	Evaluate whether the surface has a strategic job, owner, handoff, and useful signal
Explicit negative	A first-party source says the surface does not exist	Keep the negative clear unless the channel strategy changes
Source not covered	The accepted source does not represent the exact product identity	Use another qualified source if the question matters
Source unavailable	The collection route failed or was stopped	Decide whether the surface is important enough to recollect
Unresolved	Available evidence did not establish an exact identity	Seek first-party confirmation only when the surface has a defined job

For example, MetaMask’s support guidance explicitly says it has no official Telegram group. That is not missing research. It is a useful trust decision: users should not be sent searching for an official group that the company says does not exist. The observed MetaMask Community forum is a separate participation surface.

The five states prevent a growth team from solving the wrong problem. An identity problem needs verification. A source-model problem needs another source. A deliberately absent channel may need a clear warning or redirect. None of those situations is improved by reporting “zero.”

Catalogs such as DappRadar and DefiLlama make the source-model boundary visible: they organize different entities, so an exact non-match remains a coverage state rather than evidence of product absence.

Growth surface canvas

Complete one row for every surface the team currently maintains or is considering:

Surface	Audience	Primary job	Canonical entry	Next handoff	Owner	Success signal	State	Action
Example: official website	Prospective users	Trust	First-party domain	Product evaluation path	Named growth owner	Qualified evaluation action	Observed	Keep or repair after path review
Example: community forum	Existing and evaluating users	Participation	First-party community URL	Resolved answer or product action	Named community owner	Qualified questions resolved	Observed	Keep if the operating job is staffed
Example: claimed official Telegram	Users seeking support	Trust	No official group	Official support guidance	Named safety/support owner	Users reach the verified support path	Explicit negative	Keep closed and maintain the warning

The examples use bounded MetaMask identity evidence. Traffic, handoff completion, ownership, and conversion were not established by Violet’s cohort research; those fields must be completed from the team’s own systems.

Use these completion rules:

1. Audience: name the person and situation, not “everyone.”
2. Primary job: choose one of the six jobs.
3. Canonical entry: record the exact first-party path that establishes identity.
4. Next handoff: name the next useful action, not another generic homepage.
5. Owner: name the role responsible for operating and repairing the surface.
6. Success signal: choose a behavior that matches the job.
7. State: preserve observed, explicit-negative, source-not-covered, unavailable, or unresolved.
8. Action: decide to keep, repair, consolidate, or close.

The output of the audit is not a score. It is a keep, repair, consolidate, or close decision for every surface the team is paying to maintain.

Run the audit in one session

Bring growth, product, developer relations, and community owners into one 60-minute working session.

1. List every public surface the company claims or operates.
2. Assign the intended audience and one primary job.
3. Open the canonical entry and follow the next handoff as a user would.
4. Mark the evidence state without guessing.
5. Name the owner and job-specific success signal.
6. Decide keep, repair, consolidate, or close.
7. Assign only the strategically necessary repairs to the next operating cycle.

Review the canvas when the audience, product motion, or channel strategy changes. A surface that once served discovery may become a support burden; a community that once needed a standalone channel may be better consolidated into a forum with clearer identity and ownership.

What this does not show

The 16-product research does not show that more surfaces cause more growth, that an unresolved surface is absent, or that any product has a stronger ecosystem. It does not measure movement between surfaces, audience attention, conversion, adoption, customer value, or private activity.

The framework prioritizes operating work; it does not claim that any particular surface mix caused growth in the researched cohort. Its value is forcing every maintained surface to justify its audience, job, handoff, owner, and signal before the team invests further.

Method and source disclosure

Violet froze a purposive 16-product cohort and reconciled exact identities across official websites, qualifying public repositories, official X accounts, partial Instagram, YouTube, and TikTok evidence, five community types, qualifying events, DappRadar, and DefiLlama. Social objects use the frozen 90-day window ending September 10, 2026; repository signals use the frozen 180-day window ending the same day.

The evidence matrix and source counts are original Violet analysis of public data. The surface jobs, Growth Surface Canvas, completion rules, and audit sequence are Violet’s operating framework. No unresolved or unavailable state was imputed as zero, and no traffic, conversion, or causal growth claim was added.