How I Built Omnipost (And Why It Made $24K in 6 Months)

# Omnipost: A $24K/Month Automation Service

Started as a side project in March 2026. First paying customer: May 2026. By August: $24K ARR from 50 customers.

The Original Problem

I was manually onboarding 20 new domain investors every month onto my domain management system. Each took 15 minutes.

Monthly cost: 5 hours × $100/hour = $500.

The First Build

Built a form + MCP agent flow:

1. Customer fills form with domain registrar credentials
2. Agent logs in, verifies domains
3. Agent configures monitoring alerts
4. Agent sends daily email digest

Total build time: 8 hours. Price point: $49/month.

50 customers × $49 = $2,450/month.

Scaling Challenges

Multiple Registrars

• GoDaddy: REST API with OAuth
• Namecheap: XML API via wrapper
• Porkbun: Custom MCP server
• Cloudflare: API with rate limits

Each adapter: ~3 days to build, ~2 hours/month to maintain.

Authentication

• All passwords AES-256 encrypted in Supabase
• Read-only credentials where possible
• 90-day rotation policy
• SOC 2 Type II compliance

Failure Recovery

• Every failure triggers Slack alert within 5 minutes
• Retry queue with exponential backoff
• Manual escalation for repeated failures
• Customer auto-notified after 3 attempts

Pricing Evolution

Current mix: 60% v2, 15% v3, 25% v4. ARPU: $93.

Architecture

Customer Portal (Next.js)

↓

Edge Functions (Vercel)

↓

PostgreSQL (Supabase) ↔ Redis Queue

↓

MCP Agent Orchestrator

↓

Registrar Adapters

Growth Tactics

Free migration — Offer free setup. Cost: 1 hour. Removes friction.

Referral program — $100 credit per referral. 23% of customers came via referral.

Content marketing — 12 articles ranked #1 for domain automation keywords.

Community — Private Discord reduces churn to 2.3%.

Metrics

Lessons

1. Start with your own pain
2. MCP servers are the new integration layer
3. Price anchoring works ($199 makes $99 look cheap)
4. Automation is a feature, not the product

---

*Related: Automate Everything