A marketing strategy isn't what Radix needs first. A sequenced wedge is. The case for what to do, in what order, and why broadcast awareness is the wrong move.
§ 01 — The honest constraint
The Radix growth problem is not primarily a marketing problem. It is a distribution and incentive structure problem. Throwing awareness at it before the underlying conditions exist is money burning — and the ecosystem has seen that cycle before.
Marketing amplifies what exists. If what exists is technically excellent but sparsely used, marketing produces a spike and a crash. People arrive, find nothing to do, and leave. The conditions that don't yet exist at scale: a major DeFi protocol with significant TVL to anchor new users; deep native stablecoin liquidity; a Binance or Coinbase listing that brings passive retail exposure; developer tooling with a support community large enough to self-sustain.
The community paradox
The community is strong precisely because many of its members have looked at other L1s from a technical perspective and found them lacking. That is a resilience asset — they don't panic-sell, they staff the RAC, they contribute through drawdowns.
It is also a growth ceiling risk. Communities self-selected on technical rigour do not naturally expand into the mainstream developer population, which makes decisions on ecosystem size, grant availability, and job security — not architectural elegance.
The strategy that follows is sequenced, not broadcast. Each phase creates the conditions the next phase requires. Getting the sequence wrong wastes capital on awareness that cannot convert.
§ 02 — Phase one · Now → 12 months
Stop trying to be a general-purpose L1 in messaging. Pick the vertical where Radix's architecture is decisively better and where the operator making the platform decision can actually see it. That vertical is regulated RWA lending and tokenisation.
The reasons are structural. Radix's badge-based identity model solves the compliance problem that makes every EVM RWA project bolt on an awkward KYC layer as an afterthought. The asset-oriented engine means loan tokens, compliance badges, and investor credentials are native primitives, not smart contract workarounds. No other L1 can say this honestly.
Commission a serious comparison of Radix's compliance architecture against EVM-based RWA infrastructure. Not a blog post — a document written for legal and compliance officers, not developers. Circulated to NZ, Singapore, and UAE financial regulators and the law firms that advise them. The audience who needs convincing is not on crypto Twitter.
The first Ploughshare dairy loan proved concept. The next three prove product. Work with the SRWA team to build an investor-facing dashboard showing live loan positions on mainnet. The whole point of putting loans on-chain is that they're verifiable — that verifiability needs to be visible to the people it's meant to convince.
Trade finance, invoice discounting, agricultural lending in other jurisdictions. Not grants. Partnerships with named operators who bring their own capital. The pitch is white-glove technical onboarding against a compliance architecture that EVM cannot match. Operators who are being failed by EVM's limitations are the target — not operators who haven't looked at blockchain yet.
Target NZ, Australian, and Singapore fintech regulatory sandboxes explicitly. Radix's architecture is better suited to sandbox participation than EVM precisely because compliance controls are native. A formal sandbox participation produces a press release that reaches the right audience — the one that moves institutional capital, not retail.
§ 03 — Phase two · Months 6 → 18
The developer rotation argument — that EVM frustrations will eventually push developers toward Radix — is weak as a passive bet. It has to be actively engineered. The insight is that you don't need to convert EVM developers. You need to find the developers already frustrated with EVM and give them a concrete reason to try something different.
EVM limitations have been "eventually fatal" for five years. The ecosystem keeps patching around them — Layer 2s, rollups, account abstraction, parallel execution VMs. The market repeatedly reveals a preference for compatibility and tooling over architectural elegance. This is not a reason for despair; it is a targeting constraint.
§ 04 — Phase three · Months 12 → 24
No amount of messaging fixes thin liquidity. But liquidity acquisition is partly a marketing and partnerships function. The specific goal: get one asset that non-crypto people already hold onto Radix with deep liquidity. The most viable candidate is tokenised NZ or Australian government bonds — precisely because Radix's regulatory architecture makes it the structurally natural home.
§ 05 — Exclusions
A strategy is only as useful as its exclusions. A list of priorities without a list of things to abandon is a wish list. These are not tasks to defer — they are misdirections to abandon now.
The community strength is real — but it is currently an internal support network, not an acquisition engine. The job is to turn the technical credibility that already exists inside the community into external credibility with the operators and developers who haven't looked yet.
— The one-line answer