ProgrammableMarketing/stigg.io (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 6
  • This quarter · 10
  • Big bets · 3
  • Wildcards · 3
  • How we can help
Generated Oct 26, 2026 1 view
  1. Programmable
  2. Playbooks
  3. Stigg
Stigg logo

growth playbook · Oct 26, 2026

stigg.io (opens in a new tab)

Stigg growth playbook

Diagnosis

Stigg relaunched as the usage runtime for AI products in June 2026, and self-serve signups from AI startups have roughly doubled without a team behind them. The first Head of Growth will own that number and make Stigg the default choice for coding agents.

The groundwork is uneven: the MCP server is not in the official MCP Registry, the docs llms.txt still describes a SaaS subscription tool, the marketing site has no llms.txt, the pricing page still says "early preview", and every customer story is an established SaaS company.

This playbook fixes agent discovery and the pricing page first, then measures signups by path, shortens time to a first entitlement check, defines PQLs for inside sales, and adds AI-startup proof, comparisons and an AEO program, with bigger bets on agent payments, a pricing data report and BYOC.

Growth Score

7/10

Biggest Opportunity

Become the tool coding agents pick when a developer asks for credits, limits or metering: listed where agents look, described correctly, and installable without leaving the terminal.

Biggest Risk

Schematic, Flexprice, Orb and billing platforms now part of larger payment companies all pitch credits and metering for AI; if agents and buyers see them first, the self-serve lead built by Stigg 2.0 can fade.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Get the MCP server into the MCP Registry and rewrite the docs llms.txt for the agent era

    Submit the MCP server to the official MCP Registry today.

    High impact First result in 2 weeks
  2. 2

    Publish an llms.txt on www.stigg.io so agents can answer "what does Stigg cost and is there a free plan"

    Draft the file from the current pricing page.

    High impact First result in 1 month
  3. 3

    Take "EARLY PREVIEW GA on Sep 2026" off the pricing page

    Edit the label in Webflow.

    Medium impact First result in 1 week

02

Your idea portfolio

22 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 6 ideas are marked Unexpected: plays you are unlikely to have tried.

    2 of these are things Programmable can build and run for you.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 3Big bets · 9Fill-ins · 7Reconsider · 3
Effort →

Showing 22 of 22 ideas

This week 6

Quick wins with a clear first action.

  • 01

    Stigg says its fastest-growing evaluator is now a coding agent that reads the docs and calls the MCP server, and the new Head of Growth owns "the MCP Registry" and "agent-readable docs and llms.txt". Today a search of the official MCP Registry for "stigg" returns nothing (Stripe has 29 entries), and the llms.txt that every docs page tells agents to read first still introduces Stigg as "a subscription and entitlement management platform for SaaS companies", without naming the MCP server, the CLI or npx @stigg/terminal. An agent asked to "add AI credits to my app" gets an older, narrower picture of Stigg than the homepage gives.

    High impactLow effort First result in 2 weeks Head of Growth

    First action

    Submit the MCP server to the official MCP Registry today.

    How to measure it

    Agent-sourced signups (terminal, MCP, Stripe Projects)

    Now
    –
    Target
    2x
    By
    90 days

    Steps

    1. 1

      List the server

      Submit mcp.stigg.io with name, description, auth method and docs link to the official MCP Registry.

      Head of Growth, Self-Serve & Agents 1 day

    2. 2

      Rewrite the summary

      New first paragraph of docs llms.txt: usage runtime for AI products, credits, entitlements, metering, governance.

      Senior Product Manager 2 hours

    3. 3

      Add an agent start block

      npx @stigg/terminal, MCP URL, CLI, Build plan limits and where to get an API key, at the top of llms.txt.

      Senior Product Manager 2 hours

    4. 4

      Promote key pages

      Link MCP Server, Agent Skills and the four AI-agent guides directly from the top-level index.

      Senior Product Manager 1 hour

    5. 5

      Run the agent test

      Ask three coding assistants to add credits to a sample app; record the tool picked and the install path.

      Growth Engineer (to be hired) 2 days

    6. 6

      Fix what agents miss

      Edit docs pages the agents misread or skipped.

      Senior Product Manager 1 week

    7. 7

      Repeat monthly

      Rerun the same prompts and track the pick rate.

      Head of Growth, Self-Serve & Agents monthly

    First result
    2 weeks
    Cost
    Staff time only
    Owner
    Head of Growth, Self Serve & Agents

    Smallest test

    Rewrite the llms.txt first paragraph and submit the registry entry this week.

    Why it works

    Publish mcp.stigg.io to the official MCP Registry (and the client directories that read from it) with a clear description: credits, entitlements, metering and budgets for AI products. Rewrite the first lines of docs llms.txt to match "the usage runtime for AI products", add a short "Start here for agents" block (npx @stigg/terminal, the MCP server, CLI, the free Build plan and its limits), and link the MCP Server, Agent Skills and AI-agent guides at the top level. Then test the result: ask three popular coding assistants to add credits to a sample app and record whether they pick Stigg and how they install it.

    Agents choose tools from what registries and llms.txt files tell them. Getting listed and describing the current product costs a day and puts Stigg in front of the evaluator it says is growing fastest.

    Ready to use

    ChecklistAgent discovery launch list

    [ ] mcp.stigg.io listed in the official MCP Registry
    [ ] docs llms.txt first line: "the usage runtime for AI products"
    [ ] "Start here for agents" block: npx @stigg/terminal, MCP URL, CLI
    [ ] Build plan limits stated (10,000 entities, 5M events)
    [ ] MCP Server and Agent Skills linked at top level
    [ ] Monthly three-assistant test with results logged

    Risks and how to handle them

    • Registry listing alone changes little

      Pair it with the llms.txt rewrite and measure installs from each.

    • Beta server confuses agents

      State "public beta" and the supported clients in the listing.

    Evidence

    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
    • Your docsdocs.stigg.io/llms.txt (checked October 23, 2026), the index coding agents are pointed to from every docs page, opens: "Stigg is a subscription and entitlement management platform for SaaS companies." Its guides list covers credits, AI-agent metering and paywalls, but it names no MCP server, CLI or the npx @stigg/terminal installer; the MCP Server and Agent Skills pages appear only one level down, in the 278-page documentation.txt.Source
    • MCP Registry checkThe official MCP Registry (registry.modelcontextprotocol.io) returned 0 servers for a search on "stigg" on October 23, 2026; the same search for "stripe" returned 29. Stigg's MCP server is in public beta at https://mcp.stigg.io (with an @stigg/typescript-mcp local bridge) and authenticates with an environment API key copied from the Stigg app; scoped keys are available on the Scale plan.Source
    • Your websiteHomepage: title "Stigg - The Usage Runtime for AI Products"; H1 "Every AI request is a spend decision. Make it in milliseconds."; two calls to action, "Install with AI" (npx @stigg/terminal) and "Talk to a Human"; claims "p99 < 10ms" entitlement checks and "1M+ events/sec". www.stigg.io/llms.txt returns 404, so the site's product, pricing and comparison pages have no agent-readable summary.Source
    • HiringHead of Growth, Self-Serve & Agents (Tel Aviv, posted October 6, 2026): "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." The hire builds "Stigg's first product-led channel as a self-sufficient squad, with your own engineer, your own inside sales and your own budget" and owns "the number from first visit to activation, paid conversion and expansion".Source
  • 02

    www.stigg.io/llms.txt returns 404, so the pricing page, product pages and comparisons have no agent-readable summary. The pricing model is new and unusual (managed entities rather than seats, a free Build plan, BYOC from $40K a year), exactly the kind of detail an agent gets wrong when it has to guess.

    High impactLow effort First result in 1 month Head of Growth

    First action

    Draft the file from the current pricing page.

    How to measure it

    Assistant answers that state the free Build plan correctly

    Now
    –
    Target
    9 of 10 test prompts
    By
    60 days

    Steps

    1. 1

      Draft

      Plans, limits, entity definition, links.

      Head of Growth, Self-Serve & Agents 1 day

    2. 2

      Publish

      Serve /llms.txt from the Webflow site.

      Full Stack Engineer 2 hours

    3. 3

      Link both files

      Cross-link the site and docs llms.txt files.

      Senior Product Manager 1 hour

    4. 4

      Test prompts

      Ten pricing and comparison questions in three assistants.

      Growth Engineer (to be hired) 1 day

    5. 5

      Correct gaps

      Edit pages that assistants misquote.

      Marketing lead 1 week

    6. 6

      Keep current

      Update with every pricing change.

      Head of Growth, Self-Serve & Agents ongoing

    First result
    1 month
    Cost
    $0
    Owner
    Head of Growth, Self Serve & Agents

    Smallest test

    Publish a ten-line version today.

    Why it works

    Write a short llms.txt for the marketing site: one paragraph on what Stigg is, the four plans with limits and prices, the definition of a managed entity, links to the product pages, the customer stories and the comparison posts. Keep it in the Webflow build so it updates with pricing.

    Agents increasingly answer pricing and "which tool should I use" questions before a developer ever visits; a plain-text page makes the free tier and pricing model hard to misquote.

    Risks and how to handle them

    • Prices change and the file goes stale

      Add it to the pricing-change checklist.

    Evidence

    • Your websiteHomepage: title "Stigg - The Usage Runtime for AI Products"; H1 "Every AI request is a spend decision. Make it in milliseconds."; two calls to action, "Install with AI" (npx @stigg/terminal) and "Talk to a Human"; claims "p99 < 10ms" entitlement checks and "1M+ events/sec". www.stigg.io/llms.txt returns 404, so the site's product, pricing and comparison pages have no agent-readable summary.Source
    • Your websitePricing page: Build "Free forever" (10,000 managed entities, 5M usage events a month, 1K events/sec, full credits and entitlements engine); Pro $499 a month or $399 billed annually; Scale custom from 50K entities; BYOC "Starting from $40K/yr". The page still carries the label "EARLY PREVIEW GA on Sep 2026". On Build, at the entity cap "New entity creation paused. Existing enforcement continues. Prompt to upgrade." Build support is "Community" via "Docs + Intercom". A managed entity is any customer, user, agent or team Stigg enforces for.Source
    • Your websiteSitemap (242 URLs, checked October 23, 2026): 221 blog posts, 5 product pages and one customer-story page (/customers/miro). Other case studies (Webflow, PagerDuty, Guidde, Talkbase, Swimm, Reclaim) are blog posts. Comparisons are also blog posts: stigg-vs-schematic-hq, stigg-vs-flexprice, stigg-vs-credyt-ai, metronome-alternatives, orb-alternative, amberflo-alternatives and chargebee-vs-metronome. Recent launches posted: Stigg 2.0, MCP and CLI public beta (May 25, 2026), agent skills, enum entitlements, HTTP 402.Source
    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
  • 03

    It is late October 2026 and the pricing page still says the new plans are an early preview going GA in September. A buyer about to start on the free plan or pay $399-$499 a month reads that as "not finished yet".

    Medium impactLow effort First result in 1 week Head of Growth

    First action

    Edit the label in Webflow.

    How to measure it

    Pricing-to-signup conversion

    Now
    –
    Target
    +5%
    By
    30 days

    Steps

    1. 1

      Find every instance

      Label, table, FAQs.

      Head of Growth, Self-Serve & Agents 1 hour

    2. 2

      Write the new line

      GA wording.

      Head of Growth, Self-Serve & Agents 30 minutes

    3. 3

      Publish

      Webflow update.

      Full Stack Engineer 30 minutes

    4. 4

      Check the docs

      Pricing references in docs and llms.txt.

      Senior Product Manager 1 hour

    5. 5

      Add to checklist

      Date-bound labels reviewed monthly.

      Head of Growth, Self-Serve & Agents 15 minutes

    6. 6

      Measure

      Pricing-to-signup before and after.

      Growth Engineer (to be hired) 30 days

    First result
    1 week
    Cost
    $0
    Owner
    Head of Growth, Self Serve & Agents

    Smallest test

    Remove the label today.

    Why it works

    Replace the label with a launch line (for example "Usage-based pricing for AI products, generally available") or remove it, and check the plan cards, comparison table and estimator for other preview wording.

    Pricing pages are read by the most serious buyers; a stale date undermines trust at the moment of decision.

    Risks and how to handle them

    • Plans still change

      Say "pricing reviewed quarterly" instead of a preview label.

    Evidence

    • Your websitePricing page: Build "Free forever" (10,000 managed entities, 5M usage events a month, 1K events/sec, full credits and entitlements engine); Pro $499 a month or $399 billed annually; Scale custom from 50K entities; BYOC "Starting from $40K/yr". The page still carries the label "EARLY PREVIEW GA on Sep 2026". On Build, at the entity cap "New entity creation paused. Existing enforcement continues. Prompt to upgrade." Build support is "Community" via "Docs + Intercom". A managed entity is any customer, user, agent or team Stigg enforces for.Source
  • 04

    The Head of Growth must "Measure how much of our growth comes from agents, then grow it". Stigg already has four non-browser ways in (the terminal installer, the MCP server, the CLI and Stripe Projects provisioning), but a signup from a coding agent looks like any other new account unless the path is recorded.

    High impactMedium effort First result in 1 month Growth Engineer

    First action

    List every way an account can be created today.

    How to measure it

    Signups with a known path

    Now
    –
    Target
    95%
    By
    45 days

    Steps

    1. 1

      Map paths

      Every account-creation route.

      Growth Engineer (to be hired) 1 day

    2. 2

      Add the field

      Source set at creation.

      Backend Engineer 1 week

    3. 3

      Pass to CRM

      HubSpot property and report.

      Growth Engineer (to be hired) 2 days

    4. 4

      Activation by path

      First live entitlement check rate.

      Growth Engineer (to be hired) 1 week

    5. 5

      Weekly review

      In the self-serve number review.

      Head of Growth, Self-Serve & Agents weekly

    6. 6

      Shift budget

      Toward the best path.

      Head of Growth, Self-Serve & Agents quarterly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Growth Engineer (to be hired)

    Smallest test

    Add a source flag to the terminal installer first.

    Why it works

    Add a source field set by each path (installer, MCP first call, CLI login, Stripe Projects, web form), carry it into the CRM and the weekly self-serve report, and break activation and paid conversion out by path.

    You cannot grow the agent channel without counting it; the split also shows which path activates best and deserves budget.

    Risks and how to handle them

    • Paths overlap

      Record first and last path.

    Evidence

    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
    • Developer footprintnpm: 25 @stigg packages with about 81,000 weekly downloads (node-server-sdk about 17,500); @stigg/terminal ("interactive setup TUI for AI coding assistants") first published June 25, 2026, now at 0.4.0. YouTube @trystigg: 28 videos, 222 subscribers. Public changelog on AnnounceKit and a status page on incident.io.Source
    • News coverageStigg launched Stigg 2.0 in June 2026 at the AI Engineer World's Fair (per its job posts), acquired Received.ai in August 2026 "to Bring Contract Management and Invoicing Into Its Runtime AI Usage Platform" (PR Newswire), and raised a $17.5 million Series A in December 2024. Its docs add Stripe Projects (provision a Stigg account and API keys from the Stripe CLI), Airwallex invoicing and an AWS Marketplace listing.Source
    • HiringHead of Growth, Self-Serve & Agents (Tel Aviv, posted October 6, 2026): "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." The hire builds "Stigg's first product-led channel as a self-sufficient squad, with your own engineer, your own inside sales and your own budget" and owns "the number from first visit to activation, paid conversion and expansion".Source
  • 05

    Stigg already writes "Stigg vs Schematic", "Stigg vs Flexprice", "Stigg vs Credyt", Metronome, Orb and Amberflo alternatives, but they sit among 221 blog posts. Schematic now leads with "credits, metering, and usage governance on one realtime ledger", close to Stigg's own pitch.

    Medium impactLow effort First result in 1 month Marketing lead

    First action

    Pick the three rivals that come up most in deals.

    How to measure it

    Compare-page conversions

    Now
    –
    Target
    40 a month
    By
    90 days

    Steps

    1. 1

      Pick rivals

      From deal notes and search data.

      Head of Growth, Self-Serve & Agents 1 day

    2. 2

      Check facts

      Each rival's current site and pricing.

      Marketing lead 2 days

    3. 3

      Build template

      Table plus migration path.

      Full Stack Engineer 3 days

    4. 4

      Write pages

      Three first, then the rest.

      Marketing lead 1 week

    5. 5

      Link

      Pricing page, nav, llms.txt.

      Marketing lead 1 day

    6. 6

      Refresh

      Quarterly fact check.

      Marketing lead quarterly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Marketing lead

    Smallest test

    Move one comparison post into the new template.

    Why it works

    Create /compare with a page per rival: one table (real-time enforcement, credits ledger, BYOC, works with your billing provider, free tier, pricing model), a fair summary and a migration path. Link it from the pricing page and both llms.txt files.

    Buyers and agents both look for side-by-side answers; a dedicated hub ranks and gets cited better than scattered posts.

    Risks and how to handle them

    • Out-of-date claims

      Date each page and cite rivals' own pages.

    Evidence

    • Your websiteSitemap (242 URLs, checked October 23, 2026): 221 blog posts, 5 product pages and one customer-story page (/customers/miro). Other case studies (Webflow, PagerDuty, Guidde, Talkbase, Swimm, Reclaim) are blog posts. Comparisons are also blog posts: stigg-vs-schematic-hq, stigg-vs-flexprice, stigg-vs-credyt-ai, metronome-alternatives, orb-alternative, amberflo-alternatives and chargebee-vs-metronome. Recent launches posted: Stigg 2.0, MCP and CLI public beta (May 25, 2026), agent skills, enum entitlements, HTTP 402.Source
    • Competitor researchRivals' own homepages (October 23, 2026): Schematic, "Credits, metering, and usage governance on one realtime ledger"; Metronome, "Usage-Based Billing Platform", with a banner "Metronome is now part of Stripe"; Orb, "The revenue design company"; Flexprice, "Monetization Infrastructure for AI Native Companies".Source
    • Your websitePricing page: Build "Free forever" (10,000 managed entities, 5M usage events a month, 1K events/sec, full credits and entitlements engine); Pro $499 a month or $399 billed annually; Scale custom from 50K entities; BYOC "Starting from $40K/yr". The page still carries the label "EARLY PREVIEW GA on Sep 2026". On Build, at the entity cap "New entity creation paused. Existing enforcement continues. Prompt to upgrade." Build support is "Community" via "Docs + Intercom". A managed entity is any customer, user, agent or team Stigg enforces for.Source
  • 06

    On Build, when a customer reaches 10,000 managed entities "New entity creation paused... Prompt to upgrade". For a growing AI startup that pause lands on its own users. It is the highest-intent upgrade moment Stigg has.

    High impactLow effort First result in 1 month Senior Product Manager

    First action

    Count Build accounts above 70% of the cap.

    How to measure it

    Build-to-Pro upgrades

    Now
    –
    Target
    +30%
    By
    90 days

    Steps

    1. 1

      Find accounts

      Usage against cap.

      Growth Engineer (to be hired) 1 day

    2. 2

      Design warnings

      70% and 90%, all channels.

      Senior Product Manager 1 week

    3. 3

      Agent-readable message

      Clear upgrade text in MCP and CLI responses.

      Full Stack Engineer 1 week

    4. 4

      Grace buffer

      Short buffer above cap.

      Backend Engineer 1 week

    5. 5

      Sales routing

      Fast-growing accounts to inside sales.

      Inside Sales Rep (to be hired) 1 week

    6. 6

      Measure

      Upgrade rate by warning.

      Growth Engineer (to be hired) monthly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Senior Product Manager

    Smallest test

    Email the accounts above 70% this week.

    Why it works

    Warn at 70% and 90% of the cap by email, in the app and through the MCP and CLI responses; show the Pro cost at their volume; offer one-click upgrade and a short grace buffer so no end user is blocked. Route accounts that hit the cap fast to inside sales.

    Upgrades timed to real usage convert far better than generic nudges, and a smooth cap protects the trust that enforcement software depends on.

    Risks and how to handle them

    • Grace buffer abused

      Time-limit it.

    Evidence

    • Your websitePricing page: Build "Free forever" (10,000 managed entities, 5M usage events a month, 1K events/sec, full credits and entitlements engine); Pro $499 a month or $399 billed annually; Scale custom from 50K entities; BYOC "Starting from $40K/yr". The page still carries the label "EARLY PREVIEW GA on Sep 2026". On Build, at the entity cap "New entity creation paused. Existing enforcement continues. Prompt to upgrade." Build support is "Community" via "Docs + Intercom". A managed entity is any customer, user, agent or team Stigg enforces for.Source
    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
    • HiringHead of Growth, Self-Serve & Agents (Tel Aviv, posted October 6, 2026): "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." The hire builds "Stigg's first product-led channel as a self-sufficient squad, with your own engineer, your own inside sales and your own budget" and owns "the number from first visit to activation, paid conversion and expansion".Source

This quarter 10

The core plays for the next three months.

  • 07

    The MCP server needs an environment API key copied from the Stigg app, so an agent working for a developer has to stop and send them to a browser. The Head of Growth post names "CLI and API-first signup" as a goal, and Stripe Projects already shows that provisioning from a CLI works.

    High impactHigh effort First result in 1 quarter Growth Engineer

    First action

    Map today's steps from npx @stigg/terminal to a first entitlement check.

    How to measure it

    Median time to first check

    Now
    –
    Target
    under 5 minutes
    By
    1 quarter

    Steps

    1. 1

      Map the path

      Steps and drop-offs today.

      Growth Engineer (to be hired) 1 week

    2. 2

      Design the flow

      Email confirmation, sandbox, scoped key.

      Senior Product Manager 2 weeks

    3. 3

      Security review

      Abuse limits and key scopes.

      Head of Engineering 1 week

    4. 4

      Build

      CLI and installer changes.

      Full Stack Engineer 1 month

    5. 5

      Sample check

      Auto-run a demo entitlement.

      Full Stack Engineer 1 week

    6. 6

      Measure

      Time and completion by path.

      Growth Engineer (to be hired) weekly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Growth Engineer (to be hired)

    Smallest test

    Let the installer open a prefilled signup page as a first step.

    Why it works

    Let npx @stigg/terminal and the CLI create a Build account, a sandbox environment and a scoped key after an email confirmation, then run a sample entitlement check. Measure minutes from first command to first live check.

    Every hand-off to a browser loses agent-driven evaluations; removing it is the clearest way to be "the easiest infrastructure in the world for an agent to find, integrate and pay for".

    Risks and how to handle them

    • Fake signups

      Email confirmation and rate limits.

    • Full-access keys in agent hands

      Issue scoped sandbox keys by default.

    Evidence

    • MCP Registry checkThe official MCP Registry (registry.modelcontextprotocol.io) returned 0 servers for a search on "stigg" on October 23, 2026; the same search for "stripe" returned 29. Stigg's MCP server is in public beta at https://mcp.stigg.io (with an @stigg/typescript-mcp local bridge) and authenticates with an environment API key copied from the Stigg app; scoped keys are available on the Scale plan.Source
    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
    • News coverageStigg launched Stigg 2.0 in June 2026 at the AI Engineer World's Fair (per its job posts), acquired Received.ai in August 2026 "to Bring Contract Management and Invoicing Into Its Runtime AI Usage Platform" (PR Newswire), and raised a $17.5 million Series A in December 2024. Its docs add Stripe Projects (provision a Stigg account and API keys from the Stripe CLI), Airwallex invoicing and an AWS Marketplace listing.Source
    • Developer footprintnpm: 25 @stigg packages with about 81,000 weekly downloads (node-server-sdk about 17,500); @stigg/terminal ("interactive setup TUI for AI coding assistants") first published June 25, 2026, now at 0.4.0. YouTube @trystigg: 28 videos, 222 subscribers. Public changelog on AnnounceKit and a status page on incident.io.Source
  • 08

    The time-to-value goal is a first live entitlement check "in minutes". The docs have strong AI-agent guides (meter token usage, gateway spend, agent budgets), but they read as reference pages, not runnable starters.

    High impactMedium effort First result in 1 quarter Senior Product Manager

    First action

    List the top stacks among last quarter's signups.

    How to measure it

    Signups reaching a live check in 7 days

    Now
    –
    Target
    +25%
    By
    1 quarter

    Steps

    1. 1

      Find stacks

      From signup data and SDK downloads.

      Growth Engineer (to be hired) 1 week

    2. 2

      Write starters

      Five repos.

      Full Stack Engineer 1 month

    3. 3

      Test with agents

      Can an assistant run each one?

      Growth Engineer (to be hired) 2 weeks

    4. 4

      Publish

      Docs, GitHub, llms.txt.

      Senior Product Manager 1 week

    5. 5

      Link from signup

      Pick your stack screen.

      Full Stack Engineer 1 week

    6. 6

      Track

      Activation by starter.

      Growth Engineer (to be hired) monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Senior Product Manager

    Smallest test

    Publish one starter for the top stack.

    Why it works

    Ship runnable starter repos for the five most common stacks among new signups (for example a Next.js app with an LLM gateway, a Python API, an agent framework), each wiring credits and one entitlement in under five minutes, with matching agent skills so assistants use them.

    Starters cut setup time for people and give agents a known-good pattern to copy.

    Risks and how to handle them

    • Starters go stale

      Run them in CI weekly.

    Evidence

    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
    • Your docsdocs.stigg.io/llms.txt (checked October 23, 2026), the index coding agents are pointed to from every docs page, opens: "Stigg is a subscription and entitlement management platform for SaaS companies." Its guides list covers credits, AI-agent metering and paywalls, but it names no MCP server, CLI or the npx @stigg/terminal installer; the MCP Server and Agent Skills pages appear only one level down, in the 278-page documentation.txt.Source
    • Developer footprintnpm: 25 @stigg packages with about 81,000 weekly downloads (node-server-sdk about 17,500); @stigg/terminal ("interactive setup TUI for AI coding assistants") first published June 25, 2026, now at 0.4.0. YouTube @trystigg: 28 videos, 222 subscribers. Public changelog on AnnounceKit and a status page on incident.io.Source
  • 09

    The customers page is all established SaaS (Webflow, Miro, PagerDuty and peers), while the most important number is now net-new AI logos arriving self-serve. A founder of a ten-person AI company does not see themselves in a Miro case study.

    High impactMedium effort First result in 1 quarter Marketing lead

    First action

    List the ten most active self-serve AI accounts.

    How to measure it

    AI startup stories published

    Now
    –
    Target
    5
    By
    1 quarter

    Steps

    1. 1

      Shortlist

      Active self-serve AI accounts.

      Growth Engineer (to be hired) 1 week

    2. 2

      Ask

      Offer co-marketing.

      Head of Growth, Self-Serve & Agents 2 weeks

    3. 3

      Interview

      Numbers and quotes.

      Marketing lead 1 month

    4. 4

      Publish

      Stories under /customers.

      Marketing lead 1 month

    5. 5

      Logo strip

      Homepage and pricing.

      Full Stack Engineer 1 week

    6. 6

      Distribute

      Social and newsletter.

      Marketing lead ongoing

    First result
    1 quarter
    Cost
    Staff time only
    Owner
    Marketing lead

    Smallest test

    Publish one story this month.

    Why it works

    Interview five self-serve AI startups: why they picked Stigg, time to launch credits, what it replaced. Publish short stories with numbers, a "built by AI startups" logo strip on the homepage and pricing page, and clips for social.

    Peer proof sells to the segment that is growing; it also gives agents and search engines examples of Stigg in AI products.

    Risks and how to handle them

    • Startups decline publicity

      Offer anonymized stories.

    Evidence

    • Your websiteCustomers page, "Real teams. Real scale.": quotes from Webflow, Miro, PagerDuty, a business-intelligence company, a product-management company and a work marketplace. Every story is an established SaaS company; none is an AI startup that signed up on its own.Source
    • HiringHead of Growth, Self-Serve & Agents (Tel Aviv, posted October 6, 2026): "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." The hire builds "Stigg's first product-led channel as a self-sufficient squad, with your own engineer, your own inside sales and your own budget" and owns "the number from first visit to activation, paid conversion and expansion".Source
    • Your websiteSitemap (242 URLs, checked October 23, 2026): 221 blog posts, 5 product pages and one customer-story page (/customers/miro). Other case studies (Webflow, PagerDuty, Guidde, Talkbase, Swimm, Reclaim) are blog posts. Comparisons are also blog posts: stigg-vs-schematic-hq, stigg-vs-flexprice, stigg-vs-credyt-ai, metronome-alternatives, orb-alternative, amberflo-alternatives and chargebee-vs-metronome. Recent launches posted: Stigg 2.0, MCP and CLI public beta (May 25, 2026), agent skills, enum entitlements, HTTP 402.Source
  • 10

    The growth role must "Define product-qualified leads, run an inside sales motion that grows self-serve logos into bigger contracts". Usage data already shows who is growing: entities, event volume, environments, approaching caps.

    High impactMedium effort First result in 1 quarter Inside Sales Rep

    First action

    Pull the usage profile of the last ten Pro and Scale upgrades.

    How to measure it

    PQL-to-paid rate

    Now
    –
    Target
    25%
    By
    2 quarters

    Steps

    1. 1

      Study upgrades

      Usage before upgrade.

      Growth Engineer (to be hired) 1 week

    2. 2

      Set the score

      Signals and weights.

      Head of Growth, Self-Serve & Agents 1 week

    3. 3

      Daily list

      In the CRM.

      Growth Engineer (to be hired) 2 weeks

    4. 4

      Outreach scripts

      Usage-based openers.

      Inside Sales Rep (to be hired) 1 week

    5. 5

      Handoff rules

      Scale-sized accounts to sales.

      Head of Growth, Self-Serve & Agents 1 week

    6. 6

      Review

      Score accuracy monthly.

      Growth Engineer (to be hired) monthly

    First result
    1 quarter
    Cost
    Inside sales salary
    Owner
    Inside Sales Rep (to be hired)

    Smallest test

    Hand-pick ten PQLs and call them this month.

    Why it works

    Score self-serve accounts daily on usage growth, cap proximity, company size and funding, send the top 20 to the inside sales rep with context, and hand Scale-sized accounts to the sales team with a clean summary.

    Usage-based signals find buyers at the right moment, and a clear handoff stops enterprise-sized self-serve accounts from stalling.

    Risks and how to handle them

    • Developers dislike sales contact

      Lead with help, not pricing.

    Evidence

    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
    • Your websitePricing page: Build "Free forever" (10,000 managed entities, 5M usage events a month, 1K events/sec, full credits and entitlements engine); Pro $499 a month or $399 billed annually; Scale custom from 50K entities; BYOC "Starting from $40K/yr". The page still carries the label "EARLY PREVIEW GA on Sep 2026". On Build, at the entity cap "New entity creation paused. Existing enforcement continues. Prompt to upgrade." Build support is "Community" via "Docs + Intercom". A managed entity is any customer, user, agent or team Stigg enforces for.Source
    • HiringHead of Growth, Self-Serve & Agents (Tel Aviv, posted October 6, 2026): "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." The hire builds "Stigg's first product-led channel as a self-sufficient squad, with your own engineer, your own inside sales and your own budget" and owns "the number from first visit to activation, paid conversion and expansion".Source
  • 11

    The role owns AI search (AEO/GEO) with agency support. Stigg has 221 blog posts on billing and pricing topics, but the questions AI builders ask assistants are practical: "how do I add credits", "how do I cap spend per agent".

    High impactMedium effort First result in 1 quarter Head of Growth

    First action

    Write the 30 prompts with the inside sales rep and support.

    How to measure it

    Prompt share

    Now
    –
    Target
    40%
    By
    2 quarters

    Steps

    1. 1

      Write prompts

      30 builder questions.

      Head of Growth, Self-Serve & Agents 1 week

    2. 2

      Baseline

      Three assistants, weekly.

      Growth Engineer (to be hired) 1 week

    3. 3

      Map pages

      One answer page per prompt.

      Marketing lead 2 weeks

    4. 4

      Write

      Direct answers with code.

      Marketing lead 1 month

    5. 5

      Agency brief

      Targets and reporting.

      Head of Growth, Self-Serve & Agents 1 week

    6. 6

      Track

      Weekly share.

      Growth Engineer (to be hired) weekly

    First result
    1 quarter
    Cost
    Agency retainer
    Owner
    Head of Growth, Self Serve & Agents

    Smallest test

    Run the baseline for ten prompts this week.

    Why it works

    Pick 30 such prompts, record weekly which tools assistants recommend, and write or rewrite pages to answer each directly with code, linking to starters. Brief the SEO/AEO agency against the list.

    Assistant answers now shape shortlists; measured prompts turn AEO from guesswork into a weekly number.

    Risks and how to handle them

    • Answers fluctuate

      Track a rolling four-week average.

    Evidence

    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
    • Your websiteSitemap (242 URLs, checked October 23, 2026): 221 blog posts, 5 product pages and one customer-story page (/customers/miro). Other case studies (Webflow, PagerDuty, Guidde, Talkbase, Swimm, Reclaim) are blog posts. Comparisons are also blog posts: stigg-vs-schematic-hq, stigg-vs-flexprice, stigg-vs-credyt-ai, metronome-alternatives, orb-alternative, amberflo-alternatives and chargebee-vs-metronome. Recent launches posted: Stigg 2.0, MCP and CLI public beta (May 25, 2026), agent skills, enum entitlements, HTTP 402.Source
    • Your docsdocs.stigg.io/llms.txt (checked October 23, 2026), the index coding agents are pointed to from every docs page, opens: "Stigg is a subscription and entitlement management platform for SaaS companies." Its guides list covers credits, AI-agent metering and paywalls, but it names no MCP server, CLI or the npx @stigg/terminal installer; the MCP Server and Agent Skills pages appear only one level down, in the 278-page documentation.txt.Source
  • 12

    Metronome's homepage now says it "is now part of Stripe", and Stigg already writes about Metronome alternatives and "Metronome vs Stripe". Stigg's pitch is that it "layers on top of your current billing provider", so a change in the billing market is a reason to look at the enforcement layer.

    Medium impactMedium effort First result in 1 quarter Marketing lead

    First action

    Outline the guide from existing Metronome posts.

    How to measure it

    Guide-sourced demos

    Now
    –
    Target
    15 a quarter
    By
    2 quarters

    Steps

    1. 1

      Outline

      From existing posts.

      Marketing lead 1 week

    2. 2

      Write

      Neutral, factual guide.

      Marketing lead 2 weeks

    3. 3

      Review

      Claims about other vendors.

      Legal 1 week

    4. 4

      Publish

      With a review offer.

      Full Stack Engineer 1 day

    5. 5

      Promote

      Paid search and newsletter.

      Marketing lead 1 month

    6. 6

      Measure

      Demos booked.

      Growth Engineer (to be hired) monthly

    First result
    1 quarter
    Cost
    Staff time and small ad budget
    Owner
    Marketing lead

    Smallest test

    Publish the outline as a short post.

    Why it works

    Publish a neutral guide: what changes when your billing vendor changes, how to keep entitlements and credits independent of it, and a step-by-step path to add Stigg without migrating billing. Offer a migration review call.

    Teams reviewing vendors are in buying mode; a useful guide meets them with the "augment, don't replace" message.

    Risks and how to handle them

    • Seen as attacking a rival

      Keep it neutral and practical.

    Evidence

    • Competitor researchRivals' own homepages (October 23, 2026): Schematic, "Credits, metering, and usage governance on one realtime ledger"; Metronome, "Usage-Based Billing Platform", with a banner "Metronome is now part of Stripe"; Orb, "The revenue design company"; Flexprice, "Monetization Infrastructure for AI Native Companies".Source
    • Your websiteSitemap (242 URLs, checked October 23, 2026): 221 blog posts, 5 product pages and one customer-story page (/customers/miro). Other case studies (Webflow, PagerDuty, Guidde, Talkbase, Swimm, Reclaim) are blog posts. Comparisons are also blog posts: stigg-vs-schematic-hq, stigg-vs-flexprice, stigg-vs-credyt-ai, metronome-alternatives, orb-alternative, amberflo-alternatives and chargebee-vs-metronome. Recent launches posted: Stigg 2.0, MCP and CLI public beta (May 25, 2026), agent skills, enum entitlements, HTTP 402.Source
    • Your websiteHomepage: title "Stigg - The Usage Runtime for AI Products"; H1 "Every AI request is a spend decision. Make it in milliseconds."; two calls to action, "Install with AI" (npx @stigg/terminal) and "Talk to a Human"; claims "p99 < 10ms" entitlement checks and "1M+ events/sec". www.stigg.io/llms.txt returns 404, so the site's product, pricing and comparison pages have no agent-readable summary.Source
  • 13

    Net-new AI logos are the key number, and Pro costs $399-$499 a month. Early AI startups pick infrastructure in their first months and rarely switch later.

    Medium impactLow effort First result in 1 quarter Head of Growth

    First action

    List five accelerators and their perk portals.

    How to measure it

    Program accounts

    Now
    –
    Target
    100
    By
    2 quarters

    Steps

    1. 1

      Pick partners

      Accelerators and funds.

      Head of Growth, Self-Serve & Agents 2 weeks

    2. 2

      Set terms

      Six months Pro.

      Head of Growth, Self-Serve & Agents 1 week

    3. 3

      Landing page

      Program signup.

      Full Stack Engineer 1 week

    4. 4

      Launch

      Perk listings.

      Marketing lead 1 month

    5. 5

      Office hours

      Monthly.

      Senior Product Manager monthly

    6. 6

      Measure

      Conversion at month 6.

      Growth Engineer (to be hired) quarterly

    First result
    1 quarter
    Cost
    Discounted revenue
    Owner
    Head of Growth, Self Serve & Agents

    Smallest test

    Sign one accelerator.

    Why it works

    Partner with three accelerators and two AI-focused funds: six months of Pro free, office hours, and a starter repo. Track program accounts against regular signups.

    Programs put Stigg into companies at the moment pricing is designed, and graduates become the AI-startup case studies.

    Risks and how to handle them

    • Free users never pay

      Require a usage milestone to extend.

    Evidence

    • HiringHead of Growth, Self-Serve & Agents (Tel Aviv, posted October 6, 2026): "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." The hire builds "Stigg's first product-led channel as a self-sufficient squad, with your own engineer, your own inside sales and your own budget" and owns "the number from first visit to activation, paid conversion and expansion".Source
    • Your websitePricing page: Build "Free forever" (10,000 managed entities, 5M usage events a month, 1K events/sec, full credits and entitlements engine); Pro $499 a month or $399 billed annually; Scale custom from 50K entities; BYOC "Starting from $40K/yr". The page still carries the label "EARLY PREVIEW GA on Sep 2026". On Build, at the entity cap "New entity creation paused. Existing enforcement continues. Prompt to upgrade." Build support is "Community" via "Docs + Intercom". A managed entity is any customer, user, agent or team Stigg enforces for.Source
    • HiringSenior Product Manager, Full Stack Engineer and Backend Engineer posts (October 19-21, 2026): "A lean global team of around 40 people", headquartered in Tel Aviv; backed by Red Dot Capital Partners, Unusual Ventures and Emerge; customers "such as Miro, Webflow, PagerDuty, Upwork, Productboard, Qlik, and HackerOne"; metering "built to handle 1M events per second, including remote deployments running in our customers' cloud environments" (BYOC); engineers build "APIs, SDKs, CLI tools".Source
  • 14

    The YouTube channel has 28 videos and 222 subscribers, while the product is now installed by a single command and driven by agents. Seeing an agent wire up credits is the most convincing demo Stigg has.

    Medium impactLow effort First result in 1 quarter Marketing lead

    First action

    Record the first video with the starter repo.

    How to measure it

    Video-sourced signups

    Now
    –
    Target
    50 a month
    By
    2 quarters

    Steps

    1. 1

      Plan topics

      Ten features.

      Marketing lead 1 week

    2. 2

      Record

      Weekly.

      Senior Product Manager weekly

    3. 3

      Edit

      Under four minutes.

      Marketing lead weekly

    4. 4

      Post

      YouTube, X, LinkedIn.

      Marketing lead weekly

    5. 5

      Embed

      In docs pages.

      Senior Product Manager monthly

    6. 6

      Track

      Tracked links.

      Growth Engineer (to be hired) monthly

    First result
    1 quarter
    Cost
    Staff time only
    Owner
    Marketing lead

    Smallest test

    Post one video this week.

    Why it works

    Record a weekly two-to-four-minute screen video: one prompt, one agent, one working pricing feature (credits, budgets per agent, a paywall). Post on YouTube, X and LinkedIn, and embed in docs.

    Short, real demos travel in developer communities and show time to value without a sales call.

    Risks and how to handle them

    • Demos break with product changes

      Rerecord quarterly.

    Evidence

    • Developer footprintnpm: 25 @stigg packages with about 81,000 weekly downloads (node-server-sdk about 17,500); @stigg/terminal ("interactive setup TUI for AI coding assistants") first published June 25, 2026, now at 0.4.0. YouTube @trystigg: 28 videos, 222 subscribers. Public changelog on AnnounceKit and a status page on incident.io.Source
    • Your websiteHomepage: title "Stigg - The Usage Runtime for AI Products"; H1 "Every AI request is a spend decision. Make it in milliseconds."; two calls to action, "Install with AI" (npx @stigg/terminal) and "Talk to a Human"; claims "p99 < 10ms" entitlement checks and "1M+ events/sec". www.stigg.io/llms.txt returns 404, so the site's product, pricing and comparison pages have no agent-readable summary.Source
    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
  • 15

    Real visitors pass Core Web Vitals, but in the phone lab test the homepage takes 4.1s to show its main content, with 674 KB from the tag manager, 21 third-party services and 531 KB of unused JavaScript. Stigg's headline is a decision "in milliseconds".

    Medium impactLow effort First result in 1 month Full Stack Engineer

    First action

    List every tag in the container with its owner.

    How to measure it

    Mobile PageSpeed score

    Now
    –
    Target
    80+
    By
    1 month

    Steps

    1. 1

      List tags

      Owner and purpose.

      Full Stack Engineer 1 day

    2. 2

      Remove duplicates

      Overlapping tools.

      Full Stack Engineer 2 days

    3. 3

      Delay non-essential

      After interaction.

      Full Stack Engineer 2 days

    4. 4

      Retest

      PageSpeed lab.

      Full Stack Engineer 1 day

    5. 5

      Check tracking

      Conversion data intact.

      Growth Engineer (to be hired) 1 week

    6. 6

      Review quarterly

      New tags need an owner.

      Head of Growth, Self-Serve & Agents quarterly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Full Stack Engineer

    Smallest test

    Delay the chat widget first.

    Why it works

    Audit the tags: remove duplicate analytics and ad pixels, load chat and intent tools after interaction, and keep a named owner for each. Retest and aim for a lab score above 80.

    Developers notice slow pages, and a fast site supports a speed claim.

    Risks and how to handle them

    • Lost attribution

      Test each removal.

    Evidence

    • Google PageSpeedHomepage: real visitors pass Core Web Vitals (LCP 2.2s, INP 99 ms at the 75th percentile). In the phone lab test the score is 57: main content at 4.1s, 884 ms of blocking time, 1.8 MB over 103 requests, 21 third-party services (Google Tag Manager alone 674 KB), 531 KB of unused JavaScript and 1.1s of render-blocking requests.Source
    • Your websiteHomepage: title "Stigg - The Usage Runtime for AI Products"; H1 "Every AI request is a spend decision. Make it in milliseconds."; two calls to action, "Install with AI" (npx @stigg/terminal) and "Talk to a Human"; claims "p99 < 10ms" entitlement checks and "1M+ events/sec". www.stigg.io/llms.txt returns 404, so the site's product, pricing and comparison pages have no agent-readable summary.Source
  • 16

    Stigg bought Received.ai to bring contract management and invoicing into the runtime. The growth role must hand enterprise-scale accounts to sales "cleanly". The point where a startup signs its first annual contract is where both meet.

    Medium impactMedium effort First result in 1 quarter Senior Product Manager

    First action

    Draft the contract template for Pro accounts.

    How to measure it

    Self-serve to contract upgrades

    Now
    –
    Target
    10 a quarter
    By
    2 quarters

    Steps

    1. 1

      Template

      Usage-based contract.

      Senior Product Manager 2 weeks

    2. 2

      In-app offer

      For qualifying accounts.

      Full Stack Engineer 1 month

    3. 3

      Sales review

      Inside sales step.

      Inside Sales Rep (to be hired) ongoing

    4. 4

      Sign and invoice

      In Stigg.

      Backend Engineer 1 month

    5. 5

      Handoff

      To account management.

      Head of Growth, Self-Serve & Agents ongoing

    6. 6

      Measure

      Upgrades and cycle time.

      Growth Engineer (to be hired) monthly

    First result
    1 quarter
    Cost
    Product time
    Owner
    Senior Product Manager

    Smallest test

    Offer contracts by hand to five Pro accounts.

    Why it works

    Offer growing Pro accounts an in-app path to a committed contract (entity block, events, SLA) generated from their usage, reviewed by inside sales and signed in Stigg's own contract module.

    It shortens the step from self-serve to contract and shows the new product in use.

    Risks and how to handle them

    • Customers want negotiation

      Keep a talk-to-sales option.

    Evidence

    • News coverageStigg launched Stigg 2.0 in June 2026 at the AI Engineer World's Fair (per its job posts), acquired Received.ai in August 2026 "to Bring Contract Management and Invoicing Into Its Runtime AI Usage Platform" (PR Newswire), and raised a $17.5 million Series A in December 2024. Its docs add Stripe Projects (provision a Stigg account and API keys from the Stripe CLI), Airwallex invoicing and an AWS Marketplace listing.Source
    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
    • Your websitePricing page: Build "Free forever" (10,000 managed entities, 5M usage events a month, 1K events/sec, full credits and entitlements engine); Pro $499 a month or $399 billed annually; Scale custom from 50K entities; BYOC "Starting from $40K/yr". The page still carries the label "EARLY PREVIEW GA on Sep 2026". On Build, at the entity cap "New entity creation paused. Existing enforcement continues. Prompt to upgrade." Build support is "Community" via "Docs + Intercom". A managed entity is any customer, user, agent or team Stigg enforces for.Source

Big bets 3

Larger plays that can change the trajectory.

  • 17

    The growth post expects that agents will next be "paying for usage on their own" and lists x402 and machine payment protocols. Stigg has written about HTTP 402 and sells the credits that would meter such payments.

    High impactHigh effort First result in 3 quarters Head of Growth

    First action

    Pick one agent payment protocol and scope a pilot.

    How to measure it

    Agent-paid upgrades

    Now
    –
    Target
    100
    By
    3 quarters

    Steps

    1. 1

      Choose protocol

      One to start.

      Head of Growth, Self-Serve & Agents 1 month

    2. 2

      Design guardrails

      Owner budgets and receipts.

      Senior Product Manager 1 month

    3. 3

      Build

      Payment and credit grant.

      Backend Engineer 1 quarter

    4. 4

      Security review

      Fraud and limits.

      Head of Engineering 1 month

    5. 5

      Launch pilot

      Opt-in accounts.

      Head of Growth, Self-Serve & Agents 1 month

    6. 6

      Publish

      Case study and docs.

      Marketing lead 1 month

    First result
    3 quarters
    Cost
    Engineering time
    Owner
    Head of Growth, Self Serve & Agents

    Smallest test

    Accept one agent-paid credit pack in a sandbox.

    Why it works

    Pilot an agent-paid Pro upgrade: an agent hitting the Build cap can buy a credit pack within a budget the developer set, paid through an agent payment protocol, with a receipt to the human owner. Use it as a public reference for Stigg's own customers.

    Being first to accept agent payments for its own product makes Stigg the reference for the use case it wants to sell.

    Risks and how to handle them

    • Protocols still changing

      Keep the pilot small and swappable.

    Evidence

    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
    • Your websiteSitemap (242 URLs, checked October 23, 2026): 221 blog posts, 5 product pages and one customer-story page (/customers/miro). Other case studies (Webflow, PagerDuty, Guidde, Talkbase, Swimm, Reclaim) are blog posts. Comparisons are also blog posts: stigg-vs-schematic-hq, stigg-vs-flexprice, stigg-vs-credyt-ai, metronome-alternatives, orb-alternative, amberflo-alternatives and chargebee-vs-metronome. Recent launches posted: Stigg 2.0, MCP and CLI public beta (May 25, 2026), agent skills, enum entitlements, HTTP 402.Source
    • Your websitePricing page: Build "Free forever" (10,000 managed entities, 5M usage events a month, 1K events/sec, full credits and entitlements engine); Pro $499 a month or $399 billed annually; Scale custom from 50K entities; BYOC "Starting from $40K/yr". The page still carries the label "EARLY PREVIEW GA on Sep 2026". On Build, at the entity cap "New entity creation paused. Existing enforcement continues. Prompt to upgrade." Build support is "Community" via "Docs + Intercom". A managed entity is any customer, user, agent or team Stigg enforces for.Source
  • 18

    Stigg manages over 100 million customers and subscriptions and runs credits and limits for AI products. No one else sees how AI companies actually package credits, overages and budgets.

    High impactHigh effort First result in 3 quarters CEO

    First action

    Pick ten questions AI founders ask about pricing.

    How to measure it

    Report downloads

    Now
    –
    Target
    5,000
    By
    1 year

    Steps

    1. 1

      Pick questions

      Ten.

      Marketing lead 2 weeks

    2. 2

      Privacy review

      Aggregation rules.

      Legal 1 month

    3. 3

      Analyze

      Anonymized data.

      Growth Engineer (to be hired) 2 months

    4. 4

      Write

      Report and charts.

      Marketing lead 1 month

    5. 5

      Launch

      Event and press.

      CEO 1 month

    6. 6

      Use in sales

      Benchmarks in calls.

      Inside Sales Rep (to be hired) ongoing

    First result
    3 quarters
    Cost
    Analyst time
    Owner
    CEO

    Smallest test

    Publish one chart from aggregated data.

    Why it works

    Publish a yearly report: share of AI products using credits vs seats, typical credit burn, overage rules, per-agent budgets, how often pricing changes. Anonymize and aggregate, launch it at an event and in press.

    Original data earns links, press and assistant citations, and makes Stigg the authority on AI pricing.

    Risks and how to handle them

    • Customer data concerns

      Aggregate and suppress small groups; let customers opt out.

    Evidence

    • HiringHead of Engineering (posted October 13, 2026): "Today, Stigg manages over 100 million customers and subscriptions", self-serve signups from AI startups have roughly doubled since Stigg 2.0, customers "run their pricing, credits and usage limits on Stigg", and the role owns "the 99.99% uptime bar".Source
    • Your websiteSitemap (242 URLs, checked October 23, 2026): 221 blog posts, 5 product pages and one customer-story page (/customers/miro). Other case studies (Webflow, PagerDuty, Guidde, Talkbase, Swimm, Reclaim) are blog posts. Comparisons are also blog posts: stigg-vs-schematic-hq, stigg-vs-flexprice, stigg-vs-credyt-ai, metronome-alternatives, orb-alternative, amberflo-alternatives and chargebee-vs-metronome. Recent launches posted: Stigg 2.0, MCP and CLI public beta (May 25, 2026), agent skills, enum entitlements, HTTP 402.Source
    • Your websiteHomepage banner: "After Tokens", an event on November 10 in San Francisco; a "Stigg x Airwallex" announcement bar; product menu of Entitlements, Metering/BYOC, Contract Management & Invoicing, AI Credits and AI Usage Control.Source
  • 19

    BYOC starts at $40K a year with no event billing and unlimited throughput, and the backend team builds deployments inside customers' clouds. The largest AI companies are the ones "tired of paying for usage-based events ingestion".

    High impactHigh effort First result in 4 quarters CEO

    First action

    Build the calculator from the pricing page tiers.

    How to measure it

    BYOC opportunities

    Now
    –
    Target
    10
    By
    4 quarters

    Steps

    1. 1

      Calculator

      Metered vs BYOC cost.

      Full Stack Engineer 2 weeks

    2. 2

      Reference architecture

      Docs page.

      Backend Engineer 1 month

    3. 3

      Security pack

      Trust center bundle.

      Head of Engineering 1 month

    4. 4

      Target list

      Top AI companies.

      CEO 2 weeks

    5. 5

      Outreach

      Founder-led.

      CEO 1 quarter

    6. 6

      Review

      Win and loss.

      CEO quarterly

    First result
    4 quarters
    Cost
    Sales time
    Owner
    CEO

    Smallest test

    Publish the calculator.

    Build the prospect list. The list compiled from public sources, verified, deduplicated and delivered to your CRM. Usually live within days.

    Book a working session

    Why it works

    Build a BYOC value calculator (events per month vs metered cost), a reference architecture and a security pack, and run a named-account program for the top AI companies by usage.

    A few BYOC deals can match hundreds of self-serve accounts and bring credibility to the AI segment.

    Risks and how to handle them

    • Long cycles

      Keep self-serve the core metric.

    Evidence

    • Your websitePricing page: Build "Free forever" (10,000 managed entities, 5M usage events a month, 1K events/sec, full credits and entitlements engine); Pro $499 a month or $399 billed annually; Scale custom from 50K entities; BYOC "Starting from $40K/yr". The page still carries the label "EARLY PREVIEW GA on Sep 2026". On Build, at the entity cap "New entity creation paused. Existing enforcement continues. Prompt to upgrade." Build support is "Community" via "Docs + Intercom". A managed entity is any customer, user, agent or team Stigg enforces for.Source
    • HiringSenior Product Manager, Full Stack Engineer and Backend Engineer posts (October 19-21, 2026): "A lean global team of around 40 people", headquartered in Tel Aviv; backed by Red Dot Capital Partners, Unusual Ventures and Emerge; customers "such as Miro, Webflow, PagerDuty, Upwork, Productboard, Qlik, and HackerOne"; metering "built to handle 1M events per second, including remote deployments running in our customers' cloud environments" (BYOC); engineers build "APIs, SDKs, CLI tools".Source
    • HiringHead of Engineering (posted October 13, 2026): "Today, Stigg manages over 100 million customers and subscriptions", self-serve signups from AI startups have roughly doubled since Stigg 2.0, customers "run their pricing, credits and usage limits on Stigg", and the role owns "the 99.99% uptime bar".Source

Wildcards 3

Unexpected experiments, each with a cheap way to test it.

  • 20

    The homepage promises "p99 < 10ms" and the engineering team owns a 99.99% uptime bar. Buyers who put Stigg in their request path need proof, and Stigg already runs a public status page.

    Medium impactMedium effort First result in 1 quarter Backend Engineer

    First action

    Agree which metrics to publish.

    How to measure it

    Latency page views

    Now
    –
    Target
    2,000 a month
    By
    2 quarters

    Steps

    1. 1

      Choose metrics

      p50, p99, uptime.

      Head of Engineering 1 week

    2. 2

      Build feed

      From monitoring.

      Backend Engineer 2 weeks

    3. 3

      Publish page

      With methodology.

      Full Stack Engineer 1 week

    4. 4

      Link

      Homepage and docs.

      Marketing lead 1 day

    5. 5

      Review

      Bad days explained.

      Head of Engineering ongoing

    6. 6

      Measure

      Views and signups.

      Growth Engineer (to be hired) monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Backend Engineer

    Smallest test

    Post last month's p99 in a blog post.

    Build the monitor. A live page fed by the public registries and re-checked every day. Usually live within days.

    Book a working session

    Why it works

    Publish live p50/p99 latency and uptime per region on the status page or a /performance page, with methodology. Link it from the homepage claim and the docs.

    Visible numbers turn a marketing claim into evidence and reassure engineers evaluating a request-path dependency.

    Risks and how to handle them

    • Bad days are public

      Publish incident notes with them.

    Evidence

    • Your websiteHomepage: title "Stigg - The Usage Runtime for AI Products"; H1 "Every AI request is a spend decision. Make it in milliseconds."; two calls to action, "Install with AI" (npx @stigg/terminal) and "Talk to a Human"; claims "p99 < 10ms" entitlement checks and "1M+ events/sec". www.stigg.io/llms.txt returns 404, so the site's product, pricing and comparison pages have no agent-readable summary.Source
    • HiringHead of Engineering (posted October 13, 2026): "Today, Stigg manages over 100 million customers and subscriptions", self-serve signups from AI startups have roughly doubled since Stigg 2.0, customers "run their pricing, credits and usage limits on Stigg", and the role owns "the 99.99% uptime bar".Source
    • Developer footprintnpm: 25 @stigg packages with about 81,000 weekly downloads (node-server-sdk about 17,500); @stigg/terminal ("interactive setup TUI for AI coding assistants") first published June 25, 2026, now at 0.4.0. YouTube @trystigg: 28 videos, 222 subscribers. Public changelog on AnnounceKit and a status page on incident.io.Source
  • 21

    Build users get "Community" support through docs and Intercom chat. Private chats help one developer once; public answers can help everyone and be read by assistants.

    Medium impactLow effort First result in 1 quarter Senior Product Manager

    First action

    Export the top 50 Build support questions.

    How to measure it

    Public threads

    Now
    –
    Target
    200
    By
    2 quarters

    Steps

    1. 1

      Pick platform

      Forum or GitHub Discussions.

      Senior Product Manager 1 week

    2. 2

      Seed

      Top 50 questions.

      Senior Product Manager 2 weeks

    3. 3

      Answer rota

      One-day response.

      Growth Engineer (to be hired) ongoing

    4. 4

      Link

      From docs.

      Senior Product Manager 1 week

    5. 5

      Promote

      In onboarding emails.

      Marketing lead 1 week

    6. 6

      Measure

      Deflection and activation.

      Growth Engineer (to be hired) monthly

    First result
    1 quarter
    Cost
    Staff time only
    Owner
    Senior Product Manager

    Smallest test

    Post the top ten questions and answers.

    Why it works

    Open a public forum or GitHub Discussions for Build users, seed it with the top 50 support questions, and have the growth engineer and product team answer within a day. Link threads from the docs.

    Public Q&A lowers support load, raises activation and adds indexed, practical content.

    Risks and how to handle them

    • Unanswered threads

      Daily rota.

    Evidence

    • Your websitePricing page: Build "Free forever" (10,000 managed entities, 5M usage events a month, 1K events/sec, full credits and entitlements engine); Pro $499 a month or $399 billed annually; Scale custom from 50K entities; BYOC "Starting from $40K/yr". The page still carries the label "EARLY PREVIEW GA on Sep 2026". On Build, at the entity cap "New entity creation paused. Existing enforcement continues. Prompt to upgrade." Build support is "Community" via "Docs + Intercom". A managed entity is any customer, user, agent or team Stigg enforces for.Source
    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
    • Your docsdocs.stigg.io/llms.txt (checked October 23, 2026), the index coding agents are pointed to from every docs page, opens: "Stigg is a subscription and entitlement management platform for SaaS companies." Its guides list covers credits, AI-agent metering and paywalls, but it names no MCP server, CLI or the npx @stigg/terminal installer; the MCP Server and Agent Skills pages appear only one level down, in the 278-page documentation.txt.Source
  • 22

    Stigg is hosting After Tokens in San Francisco on November 10. Events produce talks, conversations and attendee lists that usually fade after the day.

    Medium impactLow effort First result in 1 month Marketing lead

    First action

    Book recording for every session.

    How to measure it

    Attendee opportunities

    Now
    –
    Target
    15
    By
    60 days

    Steps

    1. 1

      Record

      All sessions.

      Marketing lead 1 day

    2. 2

      Cut clips

      One per talk.

      Marketing lead 1 week

    3. 3

      Write recap

      Key lessons.

      Marketing lead 1 week

    4. 4

      Score attendees

      PQL model.

      Growth Engineer (to be hired) 2 days

    5. 5

      Follow up

      Within a week.

      Inside Sales Rep (to be hired) 1 week

    6. 6

      Publish series

      Weekly posts.

      Marketing lead 1 month

    First result
    1 month
    Cost
    Production costs
    Owner
    Marketing lead

    Smallest test

    Publish the recap within three days.

    Why it works

    Record every talk, cut each into a short video and a blog post, publish a recap on AI pricing, and score attendees' companies against the PQL model for inside sales follow-up within a week.

    One event becomes weeks of content and a warm pipeline.

    Risks and how to handle them

    • Speakers decline recording

      Ask in advance.

    Evidence

    • Your websiteHomepage banner: "After Tokens", an event on November 10 in San Francisco; a "Stigg x Airwallex" announcement bar; product menu of Entitlements, Metering/BYOC, Contract Management & Invoicing, AI Credits and AI Usage Control.Source
    • HiringSame post: "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". The role owns "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)" and must "Measure how much of our growth comes from agents, then grow it"; get a developer "from signup to a first live entitlement check in minutes"; "Define product-qualified leads, run an inside sales motion"; direct agencies for SEO/AEO, paid and content.Source
    • Developer footprintnpm: 25 @stigg packages with about 81,000 weekly downloads (node-server-sdk about 17,500); @stigg/terminal ("interactive setup TUI for AI coding assistants") first published June 25, 2026, now at 0.4.0. YouTube @trystigg: 28 videos, 222 subscribers. Public changelog on AnnounceKit and a status page on incident.io.Source

03

How Programmable can help

Where an idea in this playbook is something Programmable builds or runs, it's listed here with what we'd do. Everything else is yours to run.

Have it built

ProgrammableAgency

2 of the 22 ideas are things Programmable builds and runs for its customers: pages, outreach, prospect lists, booking flows and monitors. Pick one, or send the whole list.

Prospect lists1The list compiled from public sources, verified, deduplicated and delivered to your CRM.

Monitors1A live page fed by the public registries and re-checked every day.

A 30-minute session with the engineer who would build it, not a sales call. You leave with a plan whether or not you hire us.

Book a working session

Usually live within days.

Tools for the rest

ProgrammableInfo

Turn the research into a list you can act on

These ideas start with finding the right companies. Info finds them and the right person at each, researches every one and drafts the outreach, then asks before it sends.

  • Build this list in Info for idea #9 (opens programmable.info in a new tab)

New accounts: 100,000 free credits with code BETA100K

Find the companies (opens programmable.info in a new tab)
ProgrammableDigital

Show it, don't just describe it

These ideas need something to show: a demo, a video, an animation, graphics or a deck. Digital turns screenshots or the site into all of them, in the company's own brand.

Make a demo (opens programmable.digital in a new tab)
More example playbooks and reviews

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • Liquid Compute growth strategyA financial layer for GPU compute: the Liquid Compute Index (daily reference prices for A100, H100, H200, B200 and B300), an OTC desk for…24 growth ideas
  • Oglesby Media growth strategyAn Irish, fully remote Shopify SEO agency that fixes technical SEO, catalogue architecture, collection and product pages and structured…21 growth ideas
  • Routin growth strategyAn AI life tracker that connects tasks, routines, mood, sleep, fitness, health, finance, focus and journaling into one daily Life Score…21 growth ideas
  • PERGOLUX growth strategyDesigns and sells Scandinavian-inspired aluminium pergolas with louvred roofs, awnings, Wintergarten enclosures and accessories direct to…24 growth ideas
  • DeepReach growth strategyA global network that collects real-world human work data for physical AI. DeepReach designs wearable stereo capture devices (dr.ego)…23 growth ideas
  • Pendulum growth strategyA microbiome company that researches, makes and sells probiotics and prebiotics, including Metabolic Daily, Akkermansia, Glucose Control…21 growth ideas
  • AplyNow growth strategyAn AI job-search copilot that finds matched roles, identifies the hiring manager, recruiter or referral at each, and drafts outreach sent…21 growth ideas
  • WisdomAI growth strategyAn agentic analytics platform that builds and governs a company's business context (metrics, definitions, access rules) and uses it to…22 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on October 26, 2026, and cites them throughout. Stigg did not commission, review or endorse it, and Programmable is not affiliated with Stigg. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Stigg runs its business.

Something wrong, or do you represent Stigg? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 307 ideas

    MCP Registry listing and docs llms.txt, a site llms.txt, the pricing label, signup path tracking, the compare hub and the Build cap upgrade; After Tokens content.

  2. Days 31 to 6012 ideas

    Terminal signup, starters, AI-startup stories, PQLs, AEO tracking, the migration guide, the startup program, build videos, tag trimming and contracts for growing accounts; public latency and community support.

  3. Days 61 to 903 ideas

    Commit to agent payments, the AI pricing report and BYOC named accounts.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value launching credits and new pricing in weeks instead of months. The most cited problem: building ledgers and usage limits in-house.

  • Pricing changes without engineering bottlenecks
  • Usage costs incurred before billing sees them
  • In their words: “AI credits”

Market

Competitive landscape

4 competitors compared: Schematic, Metronome, Orb and Flexprice.

  • Gap to exploit: Tools that coding agents can find, install and pay for unaided
  • Schematic: Overlaps directly, harder to differentiate on features alone
  • Metronome: Billing-first rather than request-path enforcement

Hiring signals

Stigg is hiring its first Head of Growth for self-serve and agents, with a growth engineer, inside sales and a budget, because AI-startup signups have roughly doubled since Stigg 2.0 and net-new AI logos are now its…

  • Head of Growth, Self-Serve & Agents: Self-serve AI logos, agent discovery, PQLs and inside sales. Ideas 1-6, 9-14, 17.
  • Head of Engineering: 100 million customers and subscriptions, 99.99% uptime. Ideas 7, 20.
  • Senior Product Manager: Product strategy and launches for developers. Ideas 6, 8, 16, 21.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks firstNew accounts get 100,000 free enrichment credits with code BETA100K (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammableMediaAn AI note taker, interpreter and webinar host for your calls (opens programmable.media in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence