Platform 5: Hacker News (Show HN)

Priority: #5 — Developer credibility and explosive single-day reach
URL: https://news.ycombinator.com
Primary Persona: Developers (Persona 3)
Time to Impact: 1 day (prepare 2–3 weeks ahead)
Effort Level: Medium (one-time post + 4–6 hours of intense engagement)

---

Why Hacker News Matters for Agent Builder

A single front-page Hacker News post can bring 10,000–80,000 visitors in 24 hours. It’s one of the most powerful free launch platforms on the internet for anything with genuine technical merit. Multiple WordPress AI plugins have already launched successfully via “Show HN” — there’s proven demand and precedent.

But HN is brutally meritocratic. Marketing language will be ignored or mocked. Feature lists will be ignored. What works: genuine technical depth, honest presentation, and a product that solves a real problem in an interesting way. Agent Builder has strong HN angles: the WordPress Abilities API integration, MCP support, the 5-tier safety system, local AI via Ollama, and the open developer framework.

HN will humble you. They’ll question your architecture, poke holes in your security model, and ask why WordPress needs AI. But that brutal honesty converts — posts that get criticized often still drive hundreds of paying customers.

---

Pre-Submission Preparation

Know the Culture

• HN values technical substance over marketing polish
• Show HN posts must include a working demo — don’t just talk about what you’re building
• Be candid about limitations, trade-offs, and what’s not finished
• Never use marketing buzzwords: “revolutionary,” “game-changing,” “disruptive”
• Admit what you don’t know and what competitors do better in specific areas
• Respond to every comment, especially critical ones

Prepare Your Post

Title format:

Show HN: Agent Builder – AI assistants that manage your WordPress site (write posts, fix SEO, monitor security)

Rules for HN titles:
– No ALL CAPS
– No exclamation marks
– No superlatives (“best,” “first,” “only”)
– State what it does factually
– Keep under 80 characters if possible

Post body:
Show HN allows a text body. Use it to explain:

I've been building WordPress sites for [X] years and got frustrated that every plugin 
is passive — you configure it, it waits, you still do all the work.

Agent Builder puts AI assistants inside the WordPress admin that take real actions:
- Content Writer: writes blog posts, puts them in your review queue
- SEO Assistant: audits pages and fixes issues (works alongside Yoast/Rank Math)
- Security Assistant: monitors failed logins, flags outdated plugins, audits files
- Site Doctor: grades your site A-F, finds database bloat, broken links, PHP errors

Technical details that might interest this community:

- Built on PHP 8.1+ with PSR-4 autoloading, 432 tests, 1,646 assertions
- 5-tier risk system: each tool has a safety rating. Low-risk (read operations) 
  runs automatically. High-risk (publish, modify) pauses for approval.
- Supports 9 AI providers including Ollama for 100% local inference
- Implements the WordPress Abilities API (6.9+) — agent tools are published as 
  native WordPress abilities, discoverable via REST API and MCP
- MCP integration: each agent gets its own scoped MCP server. Connect Claude 
  Desktop, VS Code, or Cursor directly to your WordPress agents
- API keys encrypted at rest with AES-256-CBC using WordPress auth salts
- Free tier includes everything. No API key needed to start (built-in provider).

GitHub: [link]
Live demo: [link]
Docs: [link]

Happy to answer questions about the architecture, the safety model, or anything else.

Prepare for Questions

HN users will ask hard questions. Draft answers for these in advance:

“Why does WordPress need AI?”
Response: Most WordPress sites are maintained by non-technical owners who don’t know what meta descriptions are, can’t diagnose PHP errors, and don’t check for security vulnerabilities. AI assistants that do this automatically — with human approval for anything risky — make these sites safer and better maintained.

“What about security? You’re giving AI write access to a CMS?”
Response: Every tool has a risk level. Read-only operations run automatically. Anything that writes, publishes, or modifies settings requires explicit user approval. Extreme-risk tools (like WP-CLI access) are disabled by default. Full audit log of every action.

“Why not just use ChatGPT?”
Response: ChatGPT doesn’t know your site’s actual state. It can’t read your database, check your installed plugins, measure your Core Web Vitals, or publish a post. Agent Builder has real WordPress context and real tools that take action inside the CMS.

“What AI provider does the free tier use?”
Response: We run a hosted Gemini endpoint (chat.agentic-plugin.com). Users can also bring their own API key for any of 9 providers, or run Ollama locally for zero external calls.

“How is this different from [competitor]?”
Response: Be honest. Acknowledge what competitors do well. Focus on the specific differentiator: Agent Builder’s assistants take action, not just give advice.

---

Submission Timing

• Best days: Tuesday, Wednesday (Monday and Thursday work too)
• Best time: 8:00–9:00 AM ET (catches US morning + European afternoon)
• Avoid: Fridays, weekends, and any day a major tech event is dominating the news cycle
• Don’t coordinate votes. HN detects and penalizes vote manipulation. Just share the link naturally and let it stand on its own merit.

---

Launch Day Execution

Hour 1–2 (Critical)

• Submit the post
• Share the link on X: “Just posted Agent Builder on Hacker News — would love the community’s feedback [link]” (do NOT ask for upvotes)
• Monitor the post constantly
• Respond to every comment within 15–30 minutes
• Be technical, honest, and gracious

Hour 3–6

• If it hits the front page, expect 1,000+ visitors per hour
• Continue responding to all comments
• If people find bugs or issues, acknowledge immediately and fix if possible
• Share interesting technical discussions from the thread on X

Hour 6–24

• The post will naturally cycle off the front page
• Continue responding to new comments for 24 hours
• Write up results for your Indie Hackers journal and X

---

What to Have Ready

• [ ] Website that can handle 10,000+ concurrent visitors (CDN, caching)
• [ ] Analytics with UTM tracking for HN-specific traffic
• [ ] A way to convert visitors (clear download link, email signup, or free trial)
• [ ] GitHub repo (HN users will look at your code — make sure it’s clean)
• [ ] Documentation (HN users will check your docs — make sure they’re thorough)
• [ ] Pre-drafted responses to the most likely questions
• [ ] Someone monitoring the post for the full day (ideally the technical founder)

---

KPIs

Metric	Good	Great	Exceptional
Points	50+	200+	500+
Comments	30+	100+	250+
Front page	Top 30	Top 10	Top 3
Website visits (24hr)	5,000+	20,000+	50,000+
GitHub stars (if applicable)	100+	500+	1,000+

---

Common Mistakes to Avoid

1. Using marketing language. HN readers will literally stop reading at the first buzzword. Write like an engineer, not a marketer.
2. Asking for upvotes. HN detects coordinated voting and will penalize or kill your post. Share the link once and let it stand.
3. Getting defensive. HN criticism can be harsh. “This is just a wrapper around an API call” — respond with the technical details that show it isn’t, but stay gracious. Getting defensive always backfires.
4. Not having a working demo. “Show HN” means show. If people can’t try it or see it working, the post will die.
5. Ignoring comments. HN’s algorithm weights comment activity. If you stop responding, the post drops faster.
6. Submitting during a major news day. If Apple just announced something or a major security breach happened, your post will be buried. Check the front page before submitting.
7. Resubmitting too quickly. If your first post doesn’t take off, wait at least a week before trying again. Multiple rapid submissions look desperate and may be flagged.