Public-source review · Web3 / AI
From protocol story to measurable demand
PR, Influence and Growth — one connected audit.
One evidence trail.
- Review date
- 2026-09-12
- Audit type
- Pre-sales demonstration
- Revision
- demo-2026-09-12-v1
Evidence, not assumptions
NEAR presents a connected agent-infrastructure story. This preliminary review maps that public narrative into three testable marketing workstreams: evidence-led media, audience-specific creator education, and measurable developer journeys. It does not establish earned coverage, campaign effectiveness or conversion performance.
Requires a dated, deduplicated PR source set.
Requires verified creator posts, views and campaign scope.
Requires consented analytics and an agreed activation event.
No performance score is assigned. Missing evidence is a collection task—not a negative assessment of NEAR.
E01 · E03
Make the story independently verifiable
The homepage connects the protocol, Intents and NEAR AI under an agent-economy narrative. The blog provides an owned editorial destination.
What this suggests
There is a coherent first-party story to test against independent media. Owned announcements alone cannot demonstrate earned authority.
What to do next
Build a claim-to-proof matrix, then classify independent reporting separately from owned posts and syndicated copies.
Independent coverage, outlet quality, message pull-through and matched-window competitor share of voice.
E01
Match the explanation to the audience
The public product story spans cross-chain execution, private inference and the underlying protocol; the homepage links to social and community destinations.
What this suggests
A single creator brief may be too broad. Developer educators, product demonstrators and ecosystem explainers are candidate segments to validate, not a measured audience breakdown.
What to do next
Test separate briefs for those segments. Verify audience relevance, recent post evidence and commercial disclosure before shortlisting named creators.
Verified creator inventory, historical collaboration evidence, current rates, audience quality and attributable campaign outcomes.
E01 · E02
Connect attention to an activation event
The homepage offers distinct product and developer paths. The docs expose contract and application quickstarts, plus llms.txt and MCP entry points.
What this suggests
The journeys can be evaluated separately. Discoverability and available documentation are observable; activation and retention require first-party measurement.
What to do next
Define one activation event per audience, instrument the journey with consent, then establish a baseline before attributing improvements.
Traffic sources, funnel events, conversion, retention, acquisition cost and revenue attribution.
How the measurement layer will look
Illustrative sample data only — no chart below represents NEAR, named competitors, measured results or forecasts.
Sample · coverage trend
Illustrative weekly article counts. The gap is unmeasured, not zero.
Sample · content mix
Example composition of a fictional content set; not an audience estimate.
Sample · independent articles
A measured zero in W2 is different from missing W3.
Sample · journey events
Illustrative counts only; not NEAR funnel analytics.
Sample · content engagement density
Magnitude only. Dashed = never measured; zero remains visible.
Sample · compact trend
A server-rendered SVG for tables, summaries and static deliverables.
12 · 16 · — · 23 · 28 · 31Same missing-value contract as the full-size chart.
View sample trend values as a table
| Week | Example subject | Example peer A | Example peer B |
|---|---|---|---|
| W1 | 12 | 18 | 9 |
| W2 | 16 | 17 | 12 |
| W3 | Never measured | 21 | 14 |
| W4 | 23 | 20 | 16 |
| W5 | 28 | 25 | 19 |
| W6 | 31 | 26 | 21 |
Source register
First-party pages show what NEAR communicates. They do not independently verify performance or campaign outcomes.
First-party positioning and product navigation; not independent validation of product claims.
www.near.org · observed 2026-09-12Developer onboarding paths and agent-readable documentation entry points.
docs.near.org · observed 2026-09-12Owned editorial destination. Dynamic article listings were not enumerated; no publication-frequency claim is made.
www.near.org · observed 2026-09-12Method & limitations
This is a point-in-time desk review of three public first-party pages, not an exhaustive media, social or analytics audit. Recommendations are hypotheses to validate. No overall performance score is assigned. Illustrative figures are excluded from benchmarks and production metrics.
A practical path forward
A proposed test plan, not a delivery commitment or a forecast of results.
Establish the evidence baseline
Agree subject identity, goals, peers, source permissions and measurement windows. Collect a bounded public sample; request only the analytics scopes needed.
Versioned evidence register and measurement plan
PR + Influence + GrowthRun audience-specific tests
Test evidence-backed narratives and creator briefs against the agreed audiences. Keep placement, reach and conversion as separate measures.
Reviewed experiment briefs and comparable observations
PR + InfluenceCompare, learn and compound
Compare equivalent periods. Record limitations and costs, retain useful findings, and admit only permissioned, comparable observations into benchmarks.
Before/after report and approved reusable insights
Growth + delivery lead