Appearance
Positioning & GTM
How VelaPay is positioned in the market, who the ideal customers are, and how to reach them. This document defines the go-to-market strategy and honest constraints.
ICP (Ideal Customer Profile)
"On-chain businesses" is not an ICP. It's a category. The difference between a product that gets 10 merchants and one that gets 10,000 is whether you can name the person who feels the pain, not describe the segment.
Tier 1 — Now: On-chain data/RPC/analytics SaaS
| Attribute | Detail |
|---|---|
| Who | Helius, Triton, Shyft, Step Finance, Hello Moon |
| What they do | Sell RPC access, analytics APIs, data feeds, on-chain intelligence — all via recurring subscriptions |
| Why they feel the pain | Real MRR. Competitors watch their on-chain metrics. No existing recurring billing option that's both native and private. |
| Why they're first | Developer-friendly (can integrate @vela/sdk in a day). Already charge recurring fees. Already suffer from the privacy problem. Their competitors are already scraping their revenue data on Solana Explorer. |
| How to reach them | Developer communities (Solana Discord, Twitter/X), direct outreach to founders, SDK integration guides. |
The key insight: These businesses feel the privacy pain most acutely. A Helius competitor can literally query their billing program on Solana Explorer and see their exact subscriber count, revenue, and pricing. VelaPay encrypts all of that. The pitch writes itself.
Tier 2 — Next: DePIN networks
| Attribute | Detail |
|---|---|
| Who | Decentralized physical infrastructure networks charging node operators recurring fees |
| What they do | Charge operators for participation, bandwidth, compute, storage — recurring access fees |
| Why they feel the pain | Predictable pull payments needed. Operator budgets need cryptographic scope. Token-gated access maps to Vela's Non-Transferable subscription credentials. |
| When to go after them | After 3 Tier 1 merchants are live and validated. |
| How to reach them | DePIN-focused communities, Solana infrastructure events, partnerships with DePIN frameworks. |
Tier 3 — Later: AI agent frameworks
| Attribute | Detail |
|---|---|
| Who | AI agent frameworks charging developers for runtime access, MCP tool providers, agent orchestration platforms |
| What they do | Charge per-use or per-subscription for AI agent runtime, tool access, compute resources |
| Why they feel the pain | Agent budget mandates are the first protocol where an AI agent's spend ceiling is cryptographically enforced on-chain. No existing solution does this. |
| When to go after them | When Phase 1 (Arcium privacy) is shipped and agent mandate demos are polished. |
| How to reach them | Agent economy events, MCP ecosystem, x402 community, hackathons. |
GTM Approach
SDK-first distribution
The winning solo developer tools in the Colosseum corpus (idl-space, zircon, solforge) all made developers the target user and won because developers are both users and distribution channels. Vela's @vela/sdk should make createMandate() so simple that any Solana program can add mandate-gated billing in under an hour.
Every dApp integrating the SDK exposes their users to the mandate model. Distribution compounds through developer adoption, not through merchant sales.
The rule: If a developer can't go from bun add @vela/sdk to their first subscription in under 10 minutes, the SDK isn't good enough.
3 Tier 1 design partners before scale
The Alliance essay "Do Things That Don't Scale: Crypto Edition" is direct: "the most influential people as your most ardent supporters" — find the one Helius-tier founder who hates that their revenue is public on-chain. That person is your first merchant and your best salesperson.
The design partner criteria:
- Real MRR (not speculative)
- Already charges recurring fees on-chain or wants to
- Feels the privacy pain (competitors watching their metrics)
- Developer-friendly (can integrate SDK without enterprise sales cycle)
- Willing to be named publicly as a reference customer
Do Things That Don't Scale
Manually onboard first merchants. Sit with them. Watch what breaks. The PM strategy document puts it directly:
"Go get 3 Tier 1 merchants before building anything new. Manually onboard them. Sit with them. Watch what breaks."
The pattern from winning infra projects in the Colosseum corpus is consistent: real workflows with real usage close the gap from interesting to fundable. A named design partner — a specific on-chain business already billing subscribers with stablecoins — is non-negotiable before any pitch or fundraise.
Don't optimize for self-serve until 10 merchants who needed hand-holding
Self-serve onboarding is a scalability tool, not a discovery tool. You don't know what the self-serve flow should look like until 10 merchants have told you what they needed help with. Every manual onboarding teaches you what the automated flow should handle.
Positioning Angles
Four distinct positioning angles, each targeting a different audience and narrative:
1. "Stripe for on-chain billing" — Familiar framing
Target audience: Investors, traditional tech, crypto-curious businesses
Why it works: Stripe is the universal reference for billing infrastructure. Everyone knows what Stripe Billing does. The framing immediately communicates the category: billing infrastructure that handles subscriptions, invoicing, and customer management.
The pitch: "Stripe is trusted middleware — they sit between merchant and customer, see every transaction, charge 2.9% + $0.30, and take 2–7 days to settle. VelaPay is trustless enforcement — the mandate is on-chain, the transfer hook enforces it, billing logic is encrypted, and settlement happens in 400ms. No intermediary sees merchant data."
When to use: Investor conversations, elevator pitches, general audience introductions.
2. "The missing Token-2022 primitive" — Technical credibility
Target audience: Solana developers, protocol teams, technical investors
Why it works: Token-2022 is a known primitive in the Solana ecosystem. Positioning Vela as the billing primitive that completes what Token-2022 started resonates with developers who understand transfer hooks.
The pitch: "Token-2022 gave us programmable tokens. Transfer hooks fire on every transfer. But nobody has used them for billing enforcement — until now. Vela's mandate program completes the Token-2022 vision: tokens that enforce billing rules at the protocol level."
When to use: Developer conferences, technical blog posts, SDK documentation marketing, Solana ecosystem events.
3. "Agent budget mandates" — AI narrative
Target audience: AI agent ecosystem, MCP developers, agent framework teams
Why it works: Agent payments won 1st place in two tracks at the last Colosseum hackathon. The agent economy is the dominant narrative for 2026+. VelaPay's agent mandates are the missing primitive: pre-authorized, cryptographically scoped spending contracts that the chain enforces.
The pitch: "AI agents need allowances, not blank checks. Last hackathon's winners enforce agent budgets in middleware — a Nuxt server with a private key, zero spending limits in the code. VelaPay enforces them in transfer hooks. $50/day limit. $500 lifetime cap. Authorized services only. The Solana validator is the budget manager."
When to use: AI/agent-focused events, MCP ecosystem outreach, hackathon submissions in AI tracks.
4. "Private billing" — Commercial confidentiality
Target audience: On-chain SaaS companies, B2B businesses considering on-chain operations
Why it works: Every on-chain business that charges recurring fees has the same problem: their metrics are public. This is the most visceral pain point for the Tier 1 ICP.
The pitch: "Your subscriber list, revenue, churn rate, and pricing tiers are all public on-chain. Your competitors can see your MRR in real-time on Solana Explorer. VelaPay encrypts all of that. You see your analytics. Everyone else sees ciphertext."
When to use: Direct merchant outreach, B2B sales conversations, Tier 1 ICP targeting.
The Narrative Stack
Three narratives for three audiences, layered to reinforce each other:
Infrastructure narrative
"What Squads is to multisig, Vela is to recurring payments."
Squads is a primitive — protocol upgrade authorities, DAO treasuries, team multisigs all use it. Nobody competes with Squads; they build on it. Vela aims for the same position in billing: the primitive that everything else builds on.
Stablecoins narrative
"Every USDC transfer validated against mandate in real-time."
The billing layer above stablecoin rails. Stripe processes $1T+ annually as a trusted intermediary. VelaPay processes zero (today) but removes the need for trust entirely. The $3.2T annualized stablecoin volume has no billing primitive. Vela is that primitive.
AI narrative
"AI agents need allowances, not blank checks."
The agent economy's missing infrastructure layer. Per-request payments (x402, MCPay) serve tourist agents. Standing authorizations with cryptographic enforcement (Vela mandates) serve the agents that consolidate into platforms and need vendor relationships.
Honest Constraints
These are the real risks that affect positioning. Acknowledge them upfront rather than being caught off guard.
Privacy is not live until Arcium ships (Phase 1)
The Arcium MPC layer is Phase 1. Phase 0 ships the mandate enforcement without privacy. The privacy moat cannot be claimed in a Phase 0 demo or pitch. The transfer hook mandate enforcement has to carry the story alone until Phase 1.
Positioning adjustment: Don't claim privacy as a current differentiator. Frame it as a phased delivery: "Phase 0 delivers trustless billing enforcement. Phase 1 adds commercial privacy. Phase 3 unlocks DeFi on billing data."
Need a real merchant for the demo to land
The corpus pattern from winning infra projects is clear: real workflows with real usage close the gap from interesting to fundable. "Here is a mandate PDA enforcing a pull payment on devnet" is table stakes. "Here is [merchant X] using Vela mandates to bill [N] subscribers" is what closes the gap.
Positioning adjustment: A named design partner — a specific on-chain business already billing subscribers with stablecoins — is non-negotiable before any pitch or fundraise. This is the hardest execution challenge Vela faces.
GTM is the hardest problem, not the protocol
The protocol works. Seven prior attempts at subscription billing across four hackathons prove demand exists. But finding named design partners with real MRR who need private recurring billing is the critical path.
Positioning adjustment: Treat GTM as a priority, not a footnote. The protocol is the easy part. Distribution is what separates funded protocols from interesting repos.
Token-2022 adoption constraint
VelaPay requires billing tokens to be Token-2022 mints. Standard USDC is SPL, not Token-2022. This limits the addressable market today.
Positioning adjustment: Lead with PYUSD, USDY, and the trend toward Token-2022 for new stablecoins. Frame it as: "VelaPay is ready for the stablecoins of tomorrow. As new issuers choose Token-2022 for its extension support, VelaPay works with all of them without protocol changes."
Solo founder execution risk
One person building 9 repos is a concentration risk. Mitigation: AI-assisted development provides leverage, the codebase is well-documented, and the modular repo structure means each component can be handed off to a specialized hire when the team grows.
Positioning adjustment: Lead with execution velocity (529+ commits, 8 milestones, ~30 commits/day). The output speaks for itself. Frame team growth as a funding milestone, not a current gap.
The Correct Sequencing
Ship product first. Declare primitive when you have 10 merchants using it.
Phase A: Get 3 Tier 1 design partners manually (Month 1-3)
Phase B: Validate product-market fit with those 3 (Month 2-4)
Phase C: SDK-first distribution to next 10 merchants (Month 3-6)
Phase D: Self-serve onboarding based on learnings (Month 6-9)
Phase E: Agent economy wedge with x402 adapter (Month 6-12)
Phase F: DeFi composability (MRR Oracle, lending) (Month 12+)The a16z essay "Getting ready to launch a token" applies here: "Finding product-market fit is the single most important focus." The protocol architecture is designed as a primitive. The go-to-market is designed as a product. Both are correct.
The One Sentence Each ICP Hears
Tier 1 (on-chain SaaS):
"Your competitors can see your MRR on Solana Explorer right now. We encrypt it."
Tier 2 (DePIN):
"Your node operators need predictable billing with cryptographic enforcement, not monthly invoices."
Tier 3 (AI agents):
"Your agents need allowances, not blank checks. The validator enforces the budget."
Sources: Alliance Essays "Do Things That Don't Scale: Crypto Edition", a16z "Getting ready to launch a token", Colosseum Copilot corpus (winning patterns from idl-space, zircon, solforge), internal PM strategy (05-pm-strategy-and-hackathon-brief.md), competitive research (06-colosseum-competitive-research.md, pitch/competition.md).