Head of Growth, Self-Serve & Agents

About Stigg

Every AI company is accidentally building a bank. Every prompt, agent run and API call spends real money, and something has to decide, in real time, who is allowed to do what and how much it costs.

Stigg is the usage runtime for AI products. We sit in the request path and give engineering teams real-time entitlement enforcement, AI credits, usage metering and spend governance, so they can launch any pricing model without building a ledger into their codebase. AI Credits, Under Control.

Teams at Miro, Webflow, PagerDuty, Upwork, Qlik and AI21 Labs run on Stigg. In June 2026 we launched Stigg 2.0 at the AI Engineer World's Fair, and AI startups started showing up on their own.

The role

Since Stigg 2.0, self-serve signups from AI startups have roughly doubled, with no dedicated team behind them. Winning net-new AI logos is now the most important number in the company.

We are hiring our first Head of Growth to turn that pull into a compounding engine. You will build and run Stigg's first product-led channel as a self-sufficient squad, with your own engineer, your own inside sales and your own budget. You own the number from first visit to activation, paid conversion and expansion.

Here is the twist: more and more, the "user" evaluating Stigg is not a person. It is a coding agent reading our docs, calling our MCP server and wiring up entitlements on a developer's behalf. Next, it will be agents paying for usage on their own. You will make Stigg the default answer when an agent needs credits, metering or entitlements, and the easiest infrastructure in the world for an agent to find, integrate and pay for.

What you'll own

• The self-serve number, end to end. Signups, activation, free-to-paid conversion and AI logo acquisition, reviewed weekly. You decide which levers to pull and which channels to kill.
• Time to value. Get a developer, or their agent, from signup to a first live entitlement check in minutes. Onboarding, quickstarts, templates, docs, the pricing page and the in-product upgrade path are yours to change.
• Agents as users and as customers. Make Stigg discoverable and usable by agents: AI search (AEO / GEO), the MCP Registry and agent marketplaces, agent-readable docs and llms.txt, CLI and API-first signup, and agent-native payments (x402, Stripe's Machine Payments Protocol and whatever comes next). Measure how much of our growth comes from agents, then grow it.
• Expansion revenue. Define product-qualified leads, run an inside sales motion that grows self-serve logos into bigger contracts, and hand enterprise-scale accounts to our sales team cleanly.
• Your squad. Hire and lead a growth engineer and an inside sales rep, direct agencies (SEO / AEO, paid, content), and partner closely with product, engineering and marketing. You have a dedicated budget. Spend it like it is yours.
  
  

• An operator, not an advisor. You have owned a self-serve number at a developer, API or AI infrastructure company, and you can tell us what it was when you started and when you left.
• Technical enough to be dangerous. You read API docs, write SQL and ship your own experiments with AI tools. You pair with engineers instead of filing tickets for them.
• Fast, with taste. You run lots of experiments, kill the losers without sentiment, and still know the difference between a growth hack and a product developers love.
• Already building for agents. You have opinions on how coding agents discover, choose and integrate tools, because you have tested it yourself.
• A player-coach. High agency, low ego, comfortable working directly with founders, with no committee between you and the decision.
  
  

• 6+ years in growth, product or marketing, including 2+ years leading self-serve or product-led growth for a developer-facing product
• Measurable wins in activation and free-to-paid conversion, with numbers you can walk us through
• Experience building a PLG-to-sales motion: PQLs, inside sales and expansion
• Experience hiring and managing a small team and agencies against a budget
  
  

• You have grown a usage-based, credits or payments infrastructure product
• You have shipped an MCP server, a CLI signup flow or agent-facing docs, or experimented with x402, MPP or ACP
• You have a public voice in the developer or AI community