Updated 12-month strategy after competitor analysis: own the reliability control plane for production RPC
This version takes the base 12-month strategy and overlays the competitor evidence already published on rpc.run: QuickNode, Alchemy, Infura, Chainstack, Ankr, Moralis, daily monitoring, and the attack-surface synthesis.
What the competitor analysis changes
The base strategy says: escape commodity perception through reliability proof, CS, and ABM. The competitor layer sharpens the conclusion: GetBlock should not merely claim reliability; it should productize a Reliability Control Plane around workload cost, failure containment, and method-level proof.
| Competitor | What they already own | Implication for GetBlock |
|---|---|---|
| QuickNode | Premium broad developer platform: RPC, streams, webhooks, validators, marketplace, enterprise SLAs. | Threat: breadth + enterprise confidence. Opening: package focused private RPC, simpler workload economics, and proof-by-method for production teams. |
| Alchemy | Developer velocity and education platform with strong free tier, CUs, dashboards, APIs, and enterprise trust. | Threat: brand + education moat. Opening: teams graduating from free/PAYG need predictable dedicated infrastructure and CU-to-real-cost clarity. |
| Infura | Consensys-backed Ethereum default with long-term trust, high-availability APIs, and enterprise support. | Threat: default trust. Opening: multichain expansion, backup infrastructure, and chain-specific dedicated endpoints beyond Ethereum. |
| Chainstack | Closest direct competitor: transparent RU pricing, calculators, managed dedicated nodes, performance/cost positioning. | Threat: comparison/calculator SEO and cost transparency. Opening: GetBlock must answer with public benchmarks, calculators, and workload-specific proof. |
| Ankr | Massive free/public RPC and broad Web3 infrastructure surface across 80+ networks. | Threat: free/public top-of-funnel capture. Opening: own the “free RPC is not production infrastructure” migration path. |
| Moralis | Web3 data API layer for wallet, token, NFT, price, streams, datasets, indexing. | Threat: data layer can own app-builder workflow before raw RPC is chosen. Opening: position GetBlock as raw reliability foundation under data/indexing workloads, not a generic API clone. |
Competitive synthesis by criterion
Positioning
QuickNode and Alchemy sell platform breadth; Infura sells Ethereum trust; Chainstack sells cost/performance transparency; Ankr sells free/public access; Moralis sells app-facing data APIs. GetBlock’s cleanest gap is production RPC reliability control: dedicated/private infrastructure, method-level proof, workload economics, incident accountability, and human engineering support.
Pricing / usage units
Alchemy CUs, QuickNode credits, Chainstack RUs, and Infura credits/day all force buyers to translate abstract units into production cost. GetBlock should publish calculators that convert competitor usage models into concrete GetBlock plan/dedicated-node choices.
Enterprise proof
Competitors use SLAs, status, security, support, logos, and dashboards to sell trust. GetBlock should make proof the product: benchmark hub, incident/RCA process, private health API, security/procurement pack, and migration proof pilots.
SEO / content
Alchemy owns education, Ankr owns free RPC, Chainstack owns calculators/comparisons, QuickNode owns docs/use-case breadth, Moralis owns data API use cases. GetBlock should avoid generic education and own commercial decision pages: production RPC, public-to-private migration, toxic workloads, chain/method benchmarks, and competitor calculators.
Updated strategic thesis
GetBlock should become the reliability control plane for production multichain RPC: the vendor that helps enterprise/web2 and analytics/indexing teams understand cost, isolate toxic workloads, detect failures by method/chain, migrate from public/shared providers, and prove performance before committing traffic.
Updated package architecture
1. Enterprise Web3 Launch Reliability
- For enterprise/web2 teams entering web3.
- SLA, onboarding architect, security/procurement pack, launch checklist, monthly reliability review.
- Competitor counter: beats “big platform” ambiguity by giving a concrete launch path and accountable support.
2. Analytics & Indexing Reliability
- For analytics/indexing/data-heavy teams.
- Archive/log/backfill capacity, method-level monitoring, rate-limit transparency, ingestion support, p95/p99 proof.
- Competitor counter: addresses Moralis/data-layer and Alchemy/QuickNode/Chainstack heavy-workload economics.
3. Toxic Workload Suite
- RPC Cost Profiler, Logs/Archive/Backfill SLO, websocket stability, stream/webhook alternative.
- Why: toxic workloads are the strongest attack surface in the site’s existing report.
4. Failure Containment Layer
- Private Health API, method-level status, incident RCA, customer-specific diagnostics, synthetic monitoring, optional failover recommendations.
- Why: buyers want fewer production unknowns, not just another endpoint.
Concrete competitive moves to add
Against Chainstack calculators
Ship transparent workload calculators: archive reads, logs, websocket, backfill, and dedicated endpoint break-even. Every calculator should end with a sales-ready diagnostic report.
Against Alchemy/QuickNode platform breadth
Do not try to out-platform them. Win production workloads with private capacity, direct engineer support, failure containment, and method-level proof.
Against Infura trust
Sell multichain resilience and backup/failover posture: “keep your default, but do not make it your only production dependency.”
Against Ankr/free RPC
Create the public-to-production migration funnel: free RPC risk checklist, production readiness score, and migration pilot offer.
X/social signal overlay
Public benchmarks and endpoint hygiene
X-visible CompareNodes-style rankings and endpoint failure callouts make benchmark proof, TLS/cert hygiene, stale-height checks and incident transparency more urgent. Add these to the benchmark hub and sales diagnostics.
AI/MCP/x402 competitive pressure
QuickNode’s agent/MCP/x402 motion means GetBlock needs visible AI-ready RPC assets: MCP-lite setup, LLM-readable docs, function-calling examples, scoped keys and budget guardrails.
New-chain launch demand
Robinhood Chain, World Chain, Stable, Sonic, HyperEVM and Base are ABM/event triggers. Build chain-specific pages with status/benchmark proof and migration offers.
Institutional/RWA language
For RWA and enterprise/web2 buyers, sell controlled onchain operations: transaction visibility, historical/debug data, operational records, SLA and support accountability.
Sales assets to build immediately
- Enterprise Web3 Launch one-pager.
- Analytics/Indexing Reliability one-pager.
- RPC reliability checklist.
- Provider migration guide: public RPC / Alchemy / QuickNode / Infura / Chainstack → GetBlock.
- Security/procurement FAQ.
- Benchmark methodology page.
- Proof pilot template with success criteria.
- Battlecards for QuickNode, Alchemy, Infura, Chainstack, Ankr, Moralis.
Updated 12-month roadmap
Q1 — proof foundation and calculator wedge
- Build churn command center and segment churn by revenue.
- Publish first three proof assets: RPC Reliability Checklist, Public RPC → Production RPC migration guide, and one benchmark methodology page.
- Create calculators: Alchemy CU → GetBlock, QuickNode credits → dedicated RPC, Chainstack RU comparison.
- Research 200 ABM accounts with competitor/provider hypothesis per account.
Q2 — ABM with proof, not cold claims
- Launch 50–100 Tier 1/2 accounts using proof-led outbound.
- Run migration proof pilots: parallel GetBlock vs current provider for two weeks.
- Publish first monthly RPC Reliability Report.
- Turn CS into expansion: usage/risk health score, incident RCA, upgrade triggers.
Q3 — toxic workload productization
- Ship beta Toxic Workload Suite for heavy logs/archive/websocket/indexing accounts.
- Create chain/method benchmark pages for top commercial chains/workloads.
- Segment P&L: decide what revenue to keep, price up, or stop serving.
- Publish two case studies: enterprise launch and analytics/indexing workload.
Q4 — enterprise revenue organization
- Hire/assign AE + SDR + CS ownership around reliability packages.
- Standardize procurement pack: MSA, SLA, security FAQ, architecture diagram, incident policy.
- Make reliability tiers official: Standard, Pro, Enterprise Reliability, Analytics/Indexing Enterprise.
- Drive toward the $350k new MRR/month run-rate with pipeline coverage, higher ACV, and fewer churn-prone deals.
12-month roadmap by month with owners/KPIs
This is the operating cadence version of the strategy: every month has one primary owner, one cross-functional owner group, and KPIs that tell the CEO whether the strategy is moving from memo to revenue system.
| Month | Theme | Primary owner | Core deliverables | KPIs / exit criteria |
|---|---|---|---|---|
| M1 | Churn truth + ICP baseline | CEO + RevOps | Revenue-weighted churn taxonomy; top 20 churn/lost reviews; CRM required fields; first 25 Tier-1 ABM accounts. | 90%+ churned MRR classified; 20 interviews/reviews; 25 researched accounts; CRM hygiene baseline live. |
| M2 | Package the reliability offers | Product Marketing + Infra Lead | Enterprise Web3 Launch package; Analytics/Indexing Reliability package; first proof asset; enterprise discovery script. | 2 package one-pagers; 1 reliability checklist live; 10 discovery calls; first 3 qualified opportunities. |
| M3 | Proof-led ABM pilot | CEO + Sales/BD | First 50 ABM accounts contacted; sales deck v1; objection doc; status/benchmark methodology page. | 50 accounts contacted; 20 replies/conversations; 8 qualified opps; 2–4 pilots or enterprise deals in motion. |
| M4 | CS health score v1 | Head of Support/CS | Customer health model; risk triggers; first monthly reliability reviews for top accounts; save/expansion playbooks. | Top 30 accounts scored; usage-drop/error-spike triggers live; 10 QBR/reliability reviews; first expansion pipeline identified. |
| M5 | Migration proof pilots | Solutions Engineer + Sales | Parallel-provider pilot process; migration guide from Alchemy/QuickNode/Infura/public RPC; first customer proof reports. | 5 pilot accounts; 3 completed proof reports; p95/p99/error comparison template; 1 case-study candidate. |
| M6 | Repeatable pipeline machine | Sales/BD + RevOps | 100–120 ABM accounts touched cumulatively; forecasting dashboard; first monthly RPC Reliability Report. | 30–40 discovery calls cumulative; 15–20 tech evals; 8–12 proposals; forecast coverage visible by stage. |
| M7 | Toxic Workload Suite beta | Product + Infra | RPC Cost Profiler beta; logs/archive/backfill SLO draft; heavy-workload customer list. | 20 heavy-workload accounts identified; 5 beta reports delivered; 429/support-ticket reduction hypothesis measured. |
| M8 | Benchmark + calculator moat | Product Marketing + Data/Infra | Alchemy CU calculator; QuickNode credits calculator; Chainstack RU comparison; chain/method benchmark pages. | 3 calculators live; 5 benchmark pages; benchmark methodology cited in outbound; calculator-assisted opps tracked. |
| M9 | Segment P&L + focus cut | CEO + Finance/RevOps | Segment P&L by ICP; bad-margin/churny segment decision; pricing/packaging revision. | Revenue/margin/churn/support load by segment; clear double-down/maintain/kill decisions; updated pricing guardrails. |
| M10 | Enterprise sales capacity | CEO | Hire or assign senior AE/BDR/CS capacity; deal desk docs; procurement/security pack. | AE/SDR/CS ownership assigned; MSA/SLA/security FAQ/procurement checklist ready; sales cycle blockers reduced. |
| M11 | Reliability tiers launch | Product + Sales | Standard/Pro/Enterprise Reliability/Analytics Enterprise tiers; upgrade paths; annual contract motion. | Reliability tiers public/internal-ready; top 20 expansion accounts pitched; NRR/churn-risk movement visible. |
| M12 | $350k new MRR/month operating rhythm | CEO + Revenue Leadership | Weekly revenue operating meeting; Q4 close plan; annual renewal/expansion plan; next-year strategy refresh. | 3–4x pipeline coverage for monthly target; new MRR run-rate trending toward $350k/month; churn down in ICP accounts; board-ready metrics pack. |
Owner model
CEO: ICP focus, big accounts, churn truth, hiring, weekly revenue rhythm. Infra/Product: reliability proof, benchmarks, Toxic Workload Suite, status/health APIs. Support/CS: health score, onboarding, saves, expansion triggers. Sales/BD: ABM execution, discovery, pilots, pipeline. RevOps: CRM hygiene, forecasting, segment P&L, KPI reporting.
Updated ABM messaging
Against QuickNode / Alchemy
“Great platforms to start. GetBlock is where you go when production workloads need predictable private infrastructure, method-level proof, and direct engineering accountability.”
Against Infura
“Keep Ethereum default trust if you want, but add GetBlock as your multichain/dedicated reliability layer before the next launch.”
Against Chainstack
“Do not compare adjectives. Compare your actual methods, p95/p99, archive/log behavior, support path, and monthly cost.”
Against Ankr / public RPC
“Free/public RPC is a good prototype path. It is not a production reliability plan.”
Final recommendation
The updated strategy is more specific than the original: do not position GetBlock only as reliable RPC. Position it as the control plane for production RPC reliability — where buyers can see cost, workload risk, failure signals, migration path, and human support before churn happens.