Skip to content

Processes/growth — marketing, subscriptions, and retentiongrowth

Launch on Product Hunt & directories — growth processLaunch on Product Hunt & directories

moderatepartially automatable🔁 once

The launch-day play: prep assets and copy, submit to Product Hunt and startup directories, rally your network, and track the signup spike.

Asset prep and analytics are agent work. The submission portals have no launch APIs, and rallying your network on the day is human.

Current agent ceiling

An agent can run 2 of 5 steps

⚡ Closable with today’s market (2 — via Browser Automation for Agents): Submit to Product Hunt (computer-use candidate — a browser agent can drive this deterministic web flow); Submit to startup directories (computer-use candidate — a browser agent can drive this deterministic web flow)

No workaround yet (1): Rally your network on launch day (needs a human)

How it runs

Route-coded block flow: emerald = agent, amber = manual form/portal, red = needs a human. ⏸ approval gate · ⏳ async wait.

01Prepare launch assets and copy

agent

02Submit to Product Hunt

manual form
via:Product Hunt

⚡ agentic workaround: computer-use candidate — a browser agent can drive this deterministic web flow Steel, top of Browser Automation for Agents · assisted, not autonomous — a human supervises; verify the portal’s terms allow automation

03Submit to startup directories

manual form
via:BetaListHacker News

⚡ agentic workaround: computer-use candidate — a browser agent can drive this deterministic web flow Steel, top of Browser Automation for Agents · assisted, not autonomous — a human supervises; verify the portal’s terms allow automation

04Rally your network on launch day

human

05Track the signup spike

agent
1 API call
  • POST /api/projects/{id}/query

Context the agent needs first: launch date and positioning (from the founder)

The market options

Each role resolves against its arena’s live leaderboard — the default is the process’s canonical vendor, alternatives ranked by agent-readiness.

Simulate this process

simulated dry run from the mapped process — no real calls are made
For agents Process manifest (JSON)·/llms.txt