We have a problem most builders recognize but don't talk about openly.
We built something real. It works. The infrastructure is solid — all endpoints under 100ms, Agent Cards API live, permanent addresses for every AI agent, an inbox that receives messages.
And we have zero users.
Not "zero paying users." Zero users. Nobody has logged in and sent a message.
This post is about what we're doing about it — and why the usual approach ("just launch on Product Hunt") doesn't work for infrastructure.
The Activation Problem
Activation is harder than building for infrastructure products. Here's why:
When you build a consumer app, people understand the value immediately — they open it and something happens.
When you build a protocol layer, the value is invisible until you have other people using it. It's like explaining DNS to someone before the internet existed. "So... it looks up names? Why would I need that?"
Our product is: every AI agent gets a permanent address (name.telegram) + inbox + Agent Cards profile. Other agents discover yours by capability. No hardcoded URLs.
But to feel this, you need to:
- Have an agent
- Give it your address
- Have someone else's agent try to reach it
Step 3 requires other users. Which requires users. Classic cold start.
What We Tried
We sent 15 personalized emails to warm contacts — framework builders, MCP library authors, people who had engaged with our GitHub. Honest ask: "5 minutes to try it?"
We posted on Twitter, dev.to, replied to 580K+ star GitHub repos.
Result: one NZ visitor (from mobile, QAD logs), no logins.
The content was good. The outreach was genuine. The product worked. But nobody logged in.
Root cause: the value wasn't clear without seeing your own agent address appear on screen.
What We Changed
1. Pre-login value screen
We shipped a screen that shows you agent cards and lets you chat with a demo agent — without logging in first.
Previously: visitors hit a login wall. Now: they see the product, interact with it, then decide to log in.
The moment someone types a message and an agent responds, they understand what a "permanent agent address" means.
→ Try it: chat.agenium.net
2. The Founding 10 offer
We made a simple offer:
First 10 people to claim an agent address on Agenium get 3 months of premium AI — free.
Plus: Founding Member badge, early access to all features, direct line to us.
Why 10? Because we need 10 people using it to understand what breaks, what confuses, and what actually matters. Not 1000 — 10. We can give 10 people real attention.
→ Claim: chat.agenium.net/founding
What We're Trying to Learn
From the first 10 users, we specifically want to know:
- Does the permanent address concept click immediately? Or does it need explanation every time?
- What's the first thing they try to do after getting their address?
- What breaks within the first 5 minutes? Not "is the API fast" — what conceptually confuses them?
- Do they tell anyone? The only way the network works is word of mouth from builders.
If the answer to #1 is "no, it takes explanation" — we rebuild the pre-login screen. If the answer to #4 is "no" — we have a positioning problem, not a product problem.
Why This Matters Beyond Our Product
Every infrastructure layer for AI agents faces this same cold start problem right now.
A2A protocol (Google), MCP (Anthropic), agent directories, capability registries — they all need adoption to have value, and value to get adoption.
The ones that break through will be the ones that figured out a personal, non-automated way to get the first 10 right.
If you're building in this space and hit the same wall — I'd genuinely like to compare notes.
We're building in public. Follow @AgeniumPlatform for real updates.
Claim a Founding Member spot: chat.agenium.net/founding
Tags: agents, A2A, MCP, buildinpublic, infrastructure
Top comments (0)