ProgrammableMarketing/useautumn.com (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 · 13
  • Big bets · 3
  • Wildcards · 1
  • How we can help
Generated Nov 10, 2026 1 view
  1. Programmable
  2. Playbooks
  3. Autumn
Autumn logo

growth playbook · Nov 10, 2026

useautumn.com (opens in a new tab)

Autumn growth playbook

Diagnosis

Autumn is a five-person YC company with real proof: Firecrawl bills billions of credits through it, Runable serves 1.7M+ users on it, Mintlify runs sales-led contracts on it, and the open-source repo has about 2.7K stars. Its strongest acquisition channels are developer ones (the Convex component alone drives more than half of npm downloads) and a candid founder-written blog.

The website leaks that demand: the header "Start for free" button sends visitors back to the homepage, case studies and comparison pages end with no next step, the title says "AI startups" while the H1 says "B2B companies", and the pricing page jumps from $0 to $375 with an empty FAQ.

This playbook fixes the funnel first, then builds the channels Autumn already wins in (Convex, Better Auth, agents, open source), sharper comparison and pricing-model pages, and a sales-led path for Scale deals, before bigger bets on platforms, a pricing data report and more billing sources.

Growth Score

7/10

Biggest Opportunity

Turn the attention Autumn already earns (developer integrations, agent onboarding and customer stories with hard numbers) into sign-ups, by giving every page and channel one clear next step.

Biggest Risk

Well-funded and open-source rivals (Orb, Metronome, Stripe itself, Flexprice, Lago, Schematic, Stigg) chase the same AI companies, and some lead on compliance claims; a five-person team has to choose channels carefully.

01

Start here

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

  1. 1

    Point the header "Start for free" button at sign-up, and end every customer story and comparison page with a next step

    Change the header "Start for free" link to the sign-in URL and deploy.

    High impact First result in 1 week
  2. 2

    Publish a customers page with all four stories and their numbers

    Pull the headline number and quote from each of the four stories.

    High impact First result in 2 weeks
  3. 3

    Make the page title and description say the same thing as the new H1

    Decide the one-line positioning and rewrite the homepage title and description.

    Medium impact First result in 2 weeks

02

Your idea portfolio

23 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.

  • 7 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 · 7Fill-ins · 6Reconsider · 7
Effort →

Showing 23 of 23 ideas

This week 6

Quick wins with a clear first action.

  • 01

    The header "Start for free" button on useautumn.com links to https://useautumn.com, the homepage, on every page we checked (homepage, pricing, /alog and a customer story, checked twice on November 9, 2026). Only the hero button on the homepage goes to sign-in. So a developer who reads the Firecrawl story (billions of credits, 16 pricing changes in five months) or the "Autumn vs Stripe Billing" page and clicks the one sign-up button they can see lands back on the homepage. Those pages also end with no call to action at all, although they are the most persuasive content Autumn has.

    High impactLow effort First result in 1 week Co founder & CEO

    First action

    Change the header "Start for free" link to the sign-in URL and deploy.

    How to measure it

    Sign-ups from non-homepage pages

    Now
    –
    Target
    +30%
    By
    60 days

    Steps

    1. 1

      Fix the header link

      Point "Start for free" in the desktop and mobile header at app.useautumn.com/sign-in.

      Co-founder & CTO 1 hour

    2. 2

      Check every template

      Homepage, pricing, blog index, blog posts, /alog index and comparison pages.

      Co-founder & CTO 1 hour

    3. 3

      Write closing lines

      One sentence per story and comparison, tied to its result.

      Co-founder & CEO half a day

    4. 4

      Build the closing block

      Start for free, Get a demo, and the one-line agent setup.

      Founding Engineer 1 day

    5. 5

      Tag the buttons

      Pass the source page into PostHog and the sign-up record.

      Founding Engineer 2 hours

    6. 6

      Review the numbers

      Sign-ups by source page after four weeks.

      Co-founder & CEO monthly

    First result
    1 week
    Cost
    $0, a day of engineering
    Owner
    Co founder & CEO

    Smallest test

    Fix the header link today and compare sign-ups from blog and /alog visits over the next two weeks.

    Why it works

    Change the header "Start for free" href to https://app.useautumn.com/sign-in (the same target as the hero) on all pages, including the mobile menu. Then add a closing block to every customer story and /alog comparison: one line tied to the page ("Run pricing experiments like Firecrawl"), a "Start for free" button, "Get a demo" for Scale-sized teams, and the one-line agent setup for developers who prefer it. Tag each button with the page it came from so sign-ups can be traced to the story or comparison that produced them.

    The header button is the one CTA visible on every page. Pointing it at the homepage adds a click and a moment of confusion at peak intent. Customer stories and comparison pages are read by people already evaluating billing tools, so a clear next step at the end turns readers into sign-ups.

    Ready to use

    ChecklistNext-step checklist for every page

    [ ] Header "Start for free" goes to app.useautumn.com/sign-in (desktop and mobile)
    [ ] Hero and header buttons share one target
    [ ] Firecrawl, Runable, Mintlify and T3 Chat stories end with a closing block
    [ ] All four /alog comparisons end with a closing block
    [ ] Closing block: one result-based line, Start for free, Get a demo, one-line agent setup
    [ ] Each button carries its source page
    [ ] Sign-ups reported by source page

    Risks and how to handle them

    • The homepage link was deliberate, to show the pitch first

      Keep a "See how it works" link to the homepage next to the sign-up button.

    • Too many CTAs in technical posts

      Use the closing block only on customer stories and comparisons.

    Evidence

    • Your websiteSite header (checked twice on November 9, 2026, on the homepage, /pricing, /alog and a customer story): the "Start for free" button in the header links to https://useautumn.com, the homepage, not to sign-up; the customer stories (Firecrawl, Runable) and the /alog comparison pages end with no call to action; the blog has no newsletter signup.Source
    • Your websiteHomepage (checked November 9, 2026): page title "Billing Infrastructure for AI Startups | Autumn" and meta description "Drop-in billing for AI startups. Stop rebuilding usage limits, credits, and subscription logic."; H1 "Usage-based billing for B2B companies", subhead "complex contract terms, any usage model, and end-to-end automation from contract to invoice"; site footer "Autumn is drop-in billing for AI companies"; logos for Resend, Mintlify, Firecrawl, Mastra, Browser Use, T3.chat, Mobbin and poke.com, three with "Read story" links; the hero "Start for free" goes to sign-in and "Get a demo" to a Cal.com booking page.Source
    • Your websiteFirecrawl story: Firecrawl bills "billions of credits" a month and sends more than 5,000 requests per second at peak; it replaced an 800-line SQL balance function; Autumn assigned an engineer to help migrate; it changed pricing 16 times from April to August, with experiment effort cut "by 10x"; quote from its Head of Support Engineering: "There's no way we'd be able to iterate as fast as we are without Autumn."Source
    • Your website/alog: "Autumn content for your agent. Append .md to any page for raw markdown, or read the llms.txt and llms-full.txt indexes."; not in the main navigation; the Stripe page says "Autumn is the product-facing billing state layer built on top of Stripe" and uses bullet lists rather than a comparison table; there are no pages for Lago, Flexprice, Schematic or Stigg.Source
  • 02

    Autumn reworked its positioning in July, and the homepage H1 now reads "Usage-based billing for B2B companies". But the page title (what search results and browser tabs show) still says "Billing Infrastructure for AI Startups", the meta description says "Drop-in billing for AI startups", and the footer says "drop-in billing for AI companies". Searchers, link previews and AI assistants see three different pitches.

    Medium impactLow effort First result in 2 weeks Co founder & CEO

    First action

    Decide the one-line positioning and rewrite the homepage title and description.

    How to measure it

    Search click-through

    Now
    –
    Target
    +10%
    By
    60 days

    Steps

    1. 1

      Choose the line

      B2B, AI or both, in under 60 characters.

      Co-founder & CEO 1 hour

    2. 2

      Rewrite title and description

      Homepage and pricing.

      Co-founder & CEO 1 hour

    3. 3

      Update the footer

      Same line on every page.

      Founding Engineer 30 minutes

    4. 4

      Update profiles

      YC, Product Hunt, GitHub, LinkedIn, X and llms.txt.

      Co-founder & CEO 2 hours

    5. 5

      Check previews

      Link previews in Slack and X.

      Founding Engineer 30 minutes

    6. 6

      Measure

      Search Console click-through.

      Co-founder & CEO monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Co founder & CEO

    Smallest test

    Change the homepage title and description today.

    Why it works

    Pick one line and use it everywhere. If the B2B and contract-to-invoice story is the new direction, rewrite the title and description around it while keeping "AI" as the proof ("Usage-based billing for B2B and AI companies: credits, limits and contracts on Stripe"). Update the footer, the YC profile, Product Hunt, GitHub and the llms.txt summary to match.

    Consistent wording between the search result and the page raises click-through and stops AI summaries from describing an older Autumn.

    Risks and how to handle them

    • Losing searches for "billing for AI startups"

      Keep AI in the description and on pricing-model pages.

    Evidence

    • Your websiteHomepage (checked November 9, 2026): page title "Billing Infrastructure for AI Startups | Autumn" and meta description "Drop-in billing for AI startups. Stop rebuilding usage limits, credits, and subscription logic."; H1 "Usage-based billing for B2B companies", subhead "complex contract terms, any usage model, and end-to-end automation from contract to invoice"; site footer "Autumn is drop-in billing for AI companies"; logos for Resend, Mintlify, Firecrawl, Mastra, Browser Use, T3.chat, Mobbin and poke.com, three with "Read story" links; the hero "Start for free" goes to sign-in and "Get a demo" to a Cal.com booking page.Source
    • Your website"Reworking our positioning" (July 29, 2026): React hooks and shadcn components deprecated for new work; new projects pointed at the backend SDK; "The harder problem is the ongoing management experience": changing pricing models, provisioning custom deals and debugging billing history; "Our value prop and positioning has changed with the times."Source
  • 03

    Autumn has four strong customer stories (Firecrawl, Runable, Mintlify, T3 Chat) with hard numbers, but they sit in the blog among engineering posts with no categories, and the homepage links only three of them. Runable's story (1.7M+ users, 15 plans cut to 3, a 5% conversion lift) is not linked from the homepage at all, and the sitemap has no customers page.

    High impactLow effort First result in 2 weeks Co founder & CEO

    First action

    Pull the headline number and quote from each of the four stories.

    How to measure it

    Customers page conversion

    Now
    –
    Target
    5% to sign-up or demo
    By
    60 days

    Steps

    1. 1

      Pick the numbers

      One headline figure and quote per story.

      Co-founder & CEO 2 hours

    2. 2

      Design the cards

      Company, model, number, quote, link.

      Founding Engineer 1 day

    3. 3

      Tag by model

      Credits, sales-led contracts, consumer AI.

      Co-founder & CEO 1 hour

    4. 4

      Add to the navigation

      Customers link next to Pricing.

      Founding Engineer 1 hour

    5. 5

      Add Runable to the homepage

      A fourth "Read story" card.

      Founding Engineer 1 hour

    6. 6

      Ask for the next stories

      Two logo customers per quarter.

      Co-founder & CEO quarterly

    First result
    2 weeks
    Cost
    Staff time only
    Owner
    Co founder & CEO

    Smallest test

    Add the Runable story to the homepage row this week.

    Why it works

    Create /customers with one card per story: the company, its pricing model, the headline number and a quote, linking to the full story. Add the eight homepage logos, the Runable story to the homepage row, and a "Customers" link in the navigation. Tag stories by pricing model (credits, sales-led, consumer AI) so a visitor can find the one like theirs.

    Billing is a high-trust decision. Buyers want proof from a company like theirs, and numbers like "16 pricing changes in five months" are more persuasive than logos alone.

    Risks and how to handle them

    • Customers object to numbers shown out of context

      Use only figures already published in the approved stories.

    Evidence

    • Your websiteRunable story: 1.7M+ users; "Going from 15 plans to 3 was the best pricing decision we made"; Autumn handles about 1.3M balance checks and 500K usage events a day; a $1 first month beat every other discount; about a 5% relative conversion lift from easy experiments; building it in-house was estimated at five engineers; one customer record across Stripe and RevenueCat; Runable's agent uses Autumn's CLI and Platform API to set up billing for each app its users build, each with its own Autumn org and Stripe Connect account.Source
    • Your websiteSitemap (39 URLs, checked November 9, 2026): homepage, pricing, blog, /alog, terms and privacy; 29 blog posts (latest October 10, 2026); four /alog comparison pages (vs building in-house, Metronome, Orb and Stripe Billing, all dated June 22, 2026). No customers hub, no integration, use-case or pricing-model pages, no changelog, no security page and no careers page.Source
    • Your websiteHomepage (checked November 9, 2026): page title "Billing Infrastructure for AI Startups | Autumn" and meta description "Drop-in billing for AI startups. Stop rebuilding usage limits, credits, and subscription logic."; H1 "Usage-based billing for B2B companies", subhead "complex contract terms, any usage model, and end-to-end automation from contract to invoice"; site footer "Autumn is drop-in billing for AI companies"; logos for Resend, Mintlify, Firecrawl, Mastra, Browser Use, T3.chat, Mobbin and poke.com, three with "Read story" links; the hero "Start for free" goes to sign-in and "Get a demo" to a Cal.com booking page.Source
    • Your websiteBlog index: 29 posts, all by the two co-founders, with no categories; includes "Talking about billing with 30 YC founders", "How we made our first sale as a startup", "Marketing is hard", "People really don't like metered billing", "The psychology behind T3 Chat's pricing", "Post mortem: database outage" and engineering posts such as "How to build a credit ledger that scales".Source
  • 04

    The pricing page has an FAQ heading, but no questions appeared in the page text we read. If they render only in the browser, search engines and AI agents that read the page do not see them either. Meanwhile the page raises real questions: what "billing volume" means, what happens past 8K on Free, how Stripe's 0.7% fee stacks with Autumn, and whether there is an annual price or a startup offer.

    Medium impactLow effort First result in 2 weeks Co founder & CEO

    First action

    List the ten most common pricing questions from Discord and sales calls.

    How to measure it

    Pricing-to-sign-up conversion

    Now
    –
    Target
    +10%
    By
    60 days

    Steps

    1. 1

      Collect questions

      Discord, demo calls and support.

      Co-founder & CEO 1 day

    2. 2

      Write answers

      Short, factual, with numbers.

      Co-founder & CEO 1 day

    3. 3

      Render on the server

      Answers in the HTML, not only after a click.

      Founding Engineer 2 hours

    4. 4

      Add structured data

      FAQPage markup.

      Founding Engineer 1 hour

    5. 5

      Mirror in llms.txt

      Pricing answers in the agent index.

      Co-founder & CTO 1 hour

    6. 6

      Review quarterly

      Update with new questions.

      Co-founder & CEO quarterly

    First result
    2 weeks
    Cost
    $0
    Owner
    Co founder & CEO

    Smallest test

    Publish the three Stripe-fee and billing-volume answers this week.

    Why it works

    Write eight to ten answers in server-rendered HTML with FAQ structured data: what counts as billing volume, what happens when you pass a limit, how Stripe fees work alongside Autumn, self-hosting the open-source version, migration time (the docs say under an hour for first payments and 1-2 weeks for migrations), data ownership if you leave, uptime and the edge cache, and when Scale makes sense.

    Pricing-page questions left unanswered become support tickets or lost sign-ups. Answers in the HTML also let agents and AI assistants quote Autumn's terms correctly.

    Risks and how to handle them

    • Answers promise terms that change

      Date the FAQ and review it with each pricing change.

    Evidence

    • Your websitePricing page: Free at $0 ("Perfect while finding PMF": 8K monthly billing volume, up to 10,000 customers, 10M API requests, CLI and MCP access, community support); Pro at $375 a month (50K billing volume, 20M API requests, data warehouse integration, dedicated Slack support, Stripe, RevenueCat and Vercel as billing sources, $5 per extra 1M requests); Scale at custom pricing ("Contact us" to a booking link); a billing-volume slider from 8K to 500K+; "Stripe fees (0.7% and 2.9% + 30¢) still apply"; an FAQ heading with no questions in the page text; no annual price or startup offer.Source
    • Your docsWelcome page: Autumn is the "source of truth for billing and entitlements between your application and Stripe"; first payment setup "typically goes live in under an hour" and migrations take 1-2 weeks; an edge cache runs in the customer's own AWS account; SDKs default to fail-open.Source
  • 05

    Autumn publishes several posts a month (29 so far, roughly weekly since July) and changes the product fast: an API change, deprecated React hooks, six onboarding revamps in one month. But the blog has no email signup and the sitemap has no changelog, so readers and users have no way to follow along except Discord.

    Medium impactLow effort First result in 1 month Co founder & CTO

    First action

    Add a signup form to the blog index.

    How to measure it

    Subscribers

    Now
    –
    Target
    1,000
    By
    90 days

    Steps

    1. 1

      Pick a tool

      One that sends from your own domain.

      Co-founder & CTO 1 hour

    2. 2

      Add the forms

      Blog index and end of posts.

      Founding Engineer half a day

    3. 3

      Build /changelog

      Dated entries from release notes.

      Co-founder & CTO 1 day

    4. 4

      Backfill

      Last six months of changes.

      Co-founder & CTO half a day

    5. 5

      Send monthly

      Changelog plus one customer story.

      Co-founder & CEO monthly

    6. 6

      Track

      Subscribers who later sign up.

      Co-founder & CEO monthly

    First result
    1 month
    Cost
    Under $50 a month
    Owner
    Co founder & CTO

    Smallest test

    Add the signup to the blog index and count sign-ups for two weeks.

    Why it works

    Add an email signup to the blog index and the end of each post, with two tracks (product updates, and pricing stories). Publish a /changelog page with dated entries, migration notes and links to docs, and send a short monthly email that bundles the changelog with the month's customer story.

    Developers who are not ready to switch billing today will be later; a monthly email keeps Autumn in mind until then. A changelog also reassures existing users that changes like the hook deprecation are planned.

    Risks and how to handle them

    • No time to write each month

      Generate the draft from the changelog and posts already written.

    Evidence

    • Your websiteSite header (checked twice on November 9, 2026, on the homepage, /pricing, /alog and a customer story): the "Start for free" button in the header links to https://useautumn.com, the homepage, not to sign-up; the customer stories (Firecrawl, Runable) and the /alog comparison pages end with no call to action; the blog has no newsletter signup.Source
    • Your websiteSitemap (39 URLs, checked November 9, 2026): homepage, pricing, blog, /alog, terms and privacy; 29 blog posts (latest October 10, 2026); four /alog comparison pages (vs building in-house, Metronome, Orb and Stripe Billing, all dated June 22, 2026). No customers hub, no integration, use-case or pricing-model pages, no changelog, no security page and no careers page.Source
    • Your website"Rebuilding our onboarding for agents" (September 20, 2026): the sixth onboarding revamp that month; agents write a config and run `atmn push`; skills and evals with simulated users; keyless onboarding where the agent provisions an org and API key and the user claims it later via a link; users start by pasting one line into their agent; no activation numbers are reported.Source
  • 06

    Real visitors pass Core Web Vitals, so this is not urgent. But Google's lab test scores the homepage 98 on mobile and 56 on desktop, with a 4.6-second desktop LCP caused by the hero background image, 1.94 MB of images and 451 KB of unused JavaScript. Developers often evaluate tools at a desktop, and field LCP is trending 41% slower.

    Low impactLow effort First result in 1 week Founding Engineer

    First action

    Compress and resize the hero background image.

    How to measure it

    Desktop performance score

    Now
    –
    Target
    85+
    By
    30 days

    Steps

    1. 1

      Fix the hero image

      AVIF or WebP, sized, high fetch priority.

      Founding Engineer 2 hours

    2. 2

      Trim JavaScript

      Lazy-load below-the-fold sections.

      Founding Engineer 1 day

    3. 3

      Set cache headers

      Long lifetimes for static files.

      Founding Engineer 1 hour

    4. 4

      Fix accessibility

      Contrast, touch targets, main landmark, hidden focus.

      Founding Engineer half a day

    5. 5

      Retest

      PageSpeed desktop and mobile.

      Founding Engineer 1 hour

    6. 6

      Watch the field trend

      LCP in Search Console monthly.

      Co-founder & CTO monthly

    First result
    1 week
    Cost
    $0
    Owner
    Founding Engineer

    Smallest test

    Swap the hero image and rerun PageSpeed on desktop.

    Why it works

    Serve the hero background as a compressed, correctly sized AVIF or WebP with priority loading, cut unused JavaScript from the homepage bundle, and set long cache lifetimes for static assets. Fix the four accessibility issues PageSpeed flags (contrast, touch targets, a missing main landmark and focusable items inside hidden elements) in the same pass.

    A faster, cleaner first screen for a developer audience that notices, and a halt to the slowing field trend before it fails.

    Risks and how to handle them

    • Lower-quality hero visual

      Compare sizes side by side before shipping.

    Evidence

    • Google PageSpeedHomepage test (November 9, 2026): mobile 98, desktop 56; desktop LCP 4.6 s, with the hero background image as the LCP element; the homepage weighs 2.97 MB (1.94 MB images, 888 KB JavaScript, 451 KB unused); 750 ms render-blocking; real visitors pass Core Web Vitals (LCP 1.6 s, INP 117 ms, CLS 0.03), though field LCP is trending 41% slower; four accessibility issues (contrast, touch targets, no main landmark, focusable items inside aria-hidden).Source

This quarter 13

The core plays for the next three months.

  • 07

    Autumn already has four comparison pages, but they live under /alog, a section described as "content for your agent" and not in the main navigation. They use bullet lists instead of tables and end with no next step. And the rivals Autumn meets in open-source and AI-billing searches (Lago, Flexprice, Schematic, Stigg) have no pages at all, while Flexprice publishes "alternatives" pages about its competitors.

    High impactMedium effort First result in 6 weeks Co founder & CEO

    First action

    Turn "Autumn vs Stripe Billing" into a table-led page with a closing CTA.

    How to measure it

    Comparison-page sign-ups

    Now
    –
    Target
    40 a month
    By
    90 days

    Steps

    1. 1

      Pick the rivals

      The four existing plus four new.

      Co-founder & CEO 1 day

    2. 2

      Check facts

      Each rival's current pricing and features from their own site.

      Co-founder & CEO 3 days

    3. 3

      Write the tables

      Same rows on every page.

      Co-founder & CEO 1 week

    4. 4

      Build /compare

      Index plus pages, linked in the nav.

      Founding Engineer 2 days

    5. 5

      Keep agent copies

      /alog .md versions stay in sync.

      Co-founder & CTO 1 day

    6. 6

      Refresh

      Every quarter, with a dated note.

      Co-founder & CEO quarterly

    First result
    6 weeks
    Cost
    Staff time only
    Owner
    Co founder & CEO

    Smallest test

    Publish a table-led Autumn vs Lago page and track sign-ups for a month.

    Why it works

    Keep /alog and its .md versions for agents, and publish human versions under /compare: a fair table (pricing model fit, runtime checks, credits, contracts, open source, self-hosting, Stripe relationship, price to start), when the rival is the better choice, and a migration path. Add four new pages for Lago, Flexprice, Schematic and Stigg, link /compare from the navigation and footer, and date every page.

    Comparison searches come from buyers close to a decision. Honest tables that admit when a rival fits better earn trust with developers and get quoted by AI assistants.

    Risks and how to handle them

    • Outdated or unfair claims about rivals

      Cite each rival's own pages and date every table.

    Builds on

    Evidence

    • Your website/alog: "Autumn content for your agent. Append .md to any page for raw markdown, or read the llms.txt and llms-full.txt indexes."; not in the main navigation; the Stripe page says "Autumn is the product-facing billing state layer built on top of Stripe" and uses bullet lists rather than a comparison table; there are no pages for Lago, Flexprice, Schematic or Stigg.Source
    • Competitor researchRivals' own homepages: Flexprice, "Monetization Infrastructure for AI Native Companies", open source with on-prem deployment, claiming SOC 2 Type II and "under 60ms P99 latency", and publishing "alternatives" pages about rivals such as Schematic; Schematic, "Credits, metering, and usage governance on one realtime ledger", claiming SOC 2, an MCP interface for agents and Stripe Verified Partner status. Orb, Metronome, Lago and Stigg sell to the same AI companies.Source
    • Developer channelsOpen source: useautumn/autumn on GitHub has about 2.7K stars, 250 forks and an Apache-2.0 license (listing verified September 30, 2026); openalternative.co compares Autumn with Lago, Flexprice, UniBee, BillaBear and Meteroid.Source
  • 08

    Developers search for how to build a specific model ("credits with daily reset", "seats plus usage", "rollover credits", "auto top-up"), and Autumn's customer stories show exactly these patterns: Runable's 1,500 daily credits, Firecrawl's search-only promo credits and auto top-ups, Mintlify's pooled credits across deployments. But the sitemap has no pricing-model or use-case pages; the patterns are buried in long stories and docs.

    High impactMedium effort First result in 2 months Co founder & CTO

    First action

    Write the credits-with-daily-reset page using the Runable example.

    How to measure it

    Pricing-model page sign-ups

    Now
    –
    Target
    50 a month
    By
    1 quarter

    Steps

    1. 1

      List the models

      Eight patterns from stories and support.

      Co-founder & CTO 1 day

    2. 2

      Write configs

      Working `atmn` config per model.

      Founding Engineer 1 week

    3. 3

      Write the pages

      When to use, example, config.

      Co-founder & CEO 2 weeks

    4. 4

      Add agent prompts

      One-line prompt per model.

      Co-founder & CTO 2 days

    5. 5

      Link from the homepage

      The Pricing Models section points to each page.

      Founding Engineer 1 day

    6. 6

      Track

      Config copies and sign-ups per page.

      Co-founder & CEO monthly

    First result
    2 months
    Cost
    Staff time only
    Owner
    Co founder & CTO

    Smallest test

    Publish the credits page and track copies of its config.

    Why it works

    Publish /pricing-models with eight pages: credits, daily and monthly resets, rollovers, auto top-ups, seats plus usage, promo credits, pooled team credits, and enterprise contracts. Each page explains when to use the model, shows a real example from a customer story, and includes the `atmn` config to push it in one command (or a one-line prompt for an agent).

    It captures searches from developers designing pricing before they pick a tool, and the copy-paste config makes trying Autumn the easiest next step.

    Risks and how to handle them

    • Configs break with API changes

      Test configs in CI against the live API.

    Evidence

    • Your websiteSitemap (39 URLs, checked November 9, 2026): homepage, pricing, blog, /alog, terms and privacy; 29 blog posts (latest October 10, 2026); four /alog comparison pages (vs building in-house, Metronome, Orb and Stripe Billing, all dated June 22, 2026). No customers hub, no integration, use-case or pricing-model pages, no changelog, no security page and no careers page.Source
    • Your websiteRunable story: 1.7M+ users; "Going from 15 plans to 3 was the best pricing decision we made"; Autumn handles about 1.3M balance checks and 500K usage events a day; a $1 first month beat every other discount; about a 5% relative conversion lift from easy experiments; building it in-house was estimated at five engineers; one customer record across Stripe and RevenueCat; Runable's agent uses Autumn's CLI and Platform API to set up billing for each app its users build, each with its own Autumn org and Stripe Connect account.Source
    • Your website"Rebuilding our onboarding for agents" (September 20, 2026): the sixth onboarding revamp that month; agents write a config and run `atmn push`; skills and evals with simulated users; keyless onboarding where the agent provisions an org and API key and the user claims it later via a link; users start by pasting one line into their agent; no activation numbers are reported.Source
  • 09

    Autumn's strongest argument is engineering time: Runable estimated five engineers to build its billing in-house, and Mintlify had 2-4 engineers on billing before switching. The pricing page instead asks visitors to think in "billing volume" and mentions Stripe's 0.7% fee, without ever showing the cost of the alternative.

    Medium impactMedium effort First result in 1 month Co founder & CEO

    First action

    Agree the formula and default values.

    How to measure it

    Pricing-page conversion to Pro or demo

    Now
    –
    Target
    +15%
    By
    2 months

    Steps

    1. 1

      Set the formula

      Engineer cost and changes per year vs plan price.

      Co-founder & CEO 1 day

    2. 2

      Design

      Three inputs, one answer.

      Founding Engineer 2 days

    3. 3

      Build

      Under the plan cards.

      Founding Engineer 3 days

    4. 4

      Cite sources

      Link the Runable and Mintlify stories.

      Co-founder & CEO 1 hour

    5. 5

      Pass to demo

      Prefill the booking for Scale answers.

      Founding Engineer 1 day

    6. 6

      Test

      Compare conversion before and after.

      Co-founder & CEO 4 weeks

    First result
    1 month
    Cost
    Engineering time
    Owner
    Co founder & CEO

    Smallest test

    Add a static three-row table first: 1, 2 and 5 engineers vs Pro.

    Why it works

    Add a small calculator under the plans: engineers on billing today, their loaded cost, and expected pricing changes per year, against Autumn's plan price at the visitor's billing volume. Show the yearly difference and link the Runable and Mintlify stories as the source of the engineer numbers. Pass the result into the demo booking for Scale-sized answers.

    It reframes $375 a month against a salary, which is the comparison founders actually make, and uses customer numbers rather than claims.

    Risks and how to handle them

    • Inflated savings look like marketing

      Use conservative defaults and show the math.

    Builds on

    Evidence

    • Your websiteRunable story: 1.7M+ users; "Going from 15 plans to 3 was the best pricing decision we made"; Autumn handles about 1.3M balance checks and 500K usage events a day; a $1 first month beat every other discount; about a 5% relative conversion lift from easy experiments; building it in-house was estimated at five engineers; one customer record across Stripe and RevenueCat; Runable's agent uses Autumn's CLI and Platform API to set up billing for each app its users build, each with its own Autumn org and Stripe Connect account.Source
    • Your websiteMintlify story: sales is close to half the company; before Autumn, customers waited about a week for features, some overage prices were missing so usage went uncharged, and 2-4 engineers worked on billing; now a closed-won deal triggers an agent that reads the contract and provisions the plan in one API call; quote: "Since the migration, I have a lot more confidence that customers are actually getting what they're paying for."Source
    • Your websitePricing page: Free at $0 ("Perfect while finding PMF": 8K monthly billing volume, up to 10,000 customers, 10M API requests, CLI and MCP access, community support); Pro at $375 a month (50K billing volume, 20M API requests, data warehouse integration, dedicated Slack support, Stripe, RevenueCat and Vercel as billing sources, $5 per extra 1M requests); Scale at custom pricing ("Contact us" to a booking link); a billing-volume slider from 8K to 500K+; "Stripe fees (0.7% and 2.9% + 30¢) still apply"; an FAQ heading with no questions in the page text; no annual price or startup offer.Source
  • 10

    Autumn's plans jump from Free (8K monthly billing volume) straight to Pro at $375 a month, with no annual option and no startup offer. Many of Autumn's users are indie developers and early AI products that pass 8K in billing volume long before $375 a month feels small. Autumn's own customer Runable found that a $1 first month beat every other discount, and that a bigger yearly discount raised yearly uptake about fivefold.

    High impactMedium effort First result in 6 weeks Co founder & CEO

    First action

    Count how many Free accounts are within 50% of the 8K limit.

    How to measure it

    Free-to-paid conversion

    Now
    –
    Target
    +25%
    By
    1 quarter

    Steps

    1. 1

      Size the gap

      Free accounts near or over 8K.

      Co-founder & CTO 1 day

    2. 2

      Design the tier

      Volume, price and support level.

      Co-founder & CEO 2 days

    3. 3

      Add annual Pro

      With a clear yearly discount.

      Co-founder & CEO 1 day

    4. 4

      Configure in Autumn

      Run the test on your own product.

      Founding Engineer 2 days

    5. 5

      Email graduates

      Free accounts near the limit get the offer.

      Co-founder & CEO 1 day

    6. 6

      Publish the result

      A blog post on your own pricing experiment.

      Co-founder & CEO after 8 weeks

    First result
    6 weeks
    Cost
    Possible lower revenue per account
    Owner
    Co founder & CEO

    Smallest test

    Offer annual Pro to the next ten Pro sign-ups.

    Why it works

    Test a launch tier (for example 20K billing volume at a price a seed-stage team accepts, with community support), an annual price for Pro, and a first-month offer for teams graduating from Free. Use Autumn itself to run the test, and write it up as a public pricing experiment.

    A middle step captures teams that would otherwise stay on Free, build their own, or pick an open-source rival, and an annual option improves cash flow for a seed-stage company.

    Risks and how to handle them

    • Pro customers downgrade

      Keep Slack support, data warehouse and multiple billing sources on Pro only.

    Evidence

    • Your websitePricing page: Free at $0 ("Perfect while finding PMF": 8K monthly billing volume, up to 10,000 customers, 10M API requests, CLI and MCP access, community support); Pro at $375 a month (50K billing volume, 20M API requests, data warehouse integration, dedicated Slack support, Stripe, RevenueCat and Vercel as billing sources, $5 per extra 1M requests); Scale at custom pricing ("Contact us" to a booking link); a billing-volume slider from 8K to 500K+; "Stripe fees (0.7% and 2.9% + 30¢) still apply"; an FAQ heading with no questions in the page text; no annual price or startup offer.Source
    • Your websiteRunable story: 1.7M+ users; "Going from 15 plans to 3 was the best pricing decision we made"; Autumn handles about 1.3M balance checks and 500K usage events a day; a $1 first month beat every other discount; about a 5% relative conversion lift from easy experiments; building it in-house was estimated at five engineers; one customer record across Stripe and RevenueCat; Runable's agent uses Autumn's CLI and Platform API to set up billing for each app its users build, each with its own Autumn org and Stripe Connect account.Source
    • HiringFounding Engineer (Y Combinator job board, listed as open on November 9, 2026): London, in person, £80K-£120K and 0.50%-1.00% equity; a "backend Founding Engineer who loves to build, loves developers and has excellent product taste" who would be the fifth team member; the post says Autumn works with fast-growing AI startups and an active community of indie developers. YC profile: Summer 2025 batch, team of 5, London; raised "millions" from YC, Paul Graham, PeakXV and devtool founders.Source
  • 11

    Of Autumn's roughly 13,500 weekly npm downloads, 7,364 (more than half) come from @useautumn/convex, while the React package gets 16. Convex's components directory lists Autumn and links to the docs without tracking, and useautumn.com has no Convex page. Autumn's largest developer channel is invisible on its own site and unmeasured.

    High impactMedium effort First result in 1 month Co founder & CTO

    First action

    Add a tracking parameter to the docs links on the Convex component page.

    How to measure it

    Convex-sourced activations

    Now
    –
    Target
    +50%
    By
    1 quarter

    Steps

    1. 1

      Measure today

      Accounts whose first SDK is the Convex one.

      Co-founder & CTO 1 day

    2. 2

      Track links

      Tagged links from the Convex directory.

      Co-founder & CTO 1 day

    3. 3

      Build the starter

      Convex app with a credits plan.

      Founding Engineer 1 week

    4. 4

      Publish /convex

      Starter, patterns and a story.

      Founding Engineer 1 week

    5. 5

      Co-market

      A tutorial with the Convex team.

      Co-founder & CEO 1 month

    6. 6

      Report

      Installs to activations monthly.

      Co-founder & CTO monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Co founder & CTO

    Smallest test

    Publish the Convex starter on GitHub and link it from the component page.

    Why it works

    Build /convex on the main site: a working Convex starter (auth, a credits plan, check and track) deployable in one step, the pricing patterns Convex apps use most, and a Convex customer story. Ask Convex to add tracked links from the component page, co-write a tutorial for their blog, and measure sign-ups from Convex as their own funnel.

    Developers who install the Convex component already chose Autumn in code; a dedicated path turns installs into activated accounts, and a co-written tutorial reaches Convex's whole audience.

    Risks and how to handle them

    • Downloads include CI installs, not people

      Measure activations, not downloads.

    Evidence

    • Developer channelsnpm: 6 packages with about 13,500 weekly downloads; @useautumn/convex has 7,364 a week, more than half the total; @useautumn/gateway 6,047; @useautumn/react 16. Convex's components directory lists Autumn ("abstracts Stripe billing in Convex with three functions") and links to the docs with no tracking parameters.Source
    • Your websiteSitemap (39 URLs, checked November 9, 2026): homepage, pricing, blog, /alog, terms and privacy; 29 blog posts (latest October 10, 2026); four /alog comparison pages (vs building in-house, Metronome, Orb and Stripe Billing, all dated June 22, 2026). No customers hub, no integration, use-case or pricing-model pages, no changelog, no security page and no careers page.Source
  • 12

    Autumn already has the integrations developers look for: a Better Auth plugin in Better Auth's own docs, RevenueCat and Vercel as billing sources on Pro, and Stripe plus RevenueCat combined for Runable's web and iOS users. None of them has a page on useautumn.com; the sitemap has no integration pages.

    Medium impactMedium effort First result in 6 weeks Founding Engineer

    First action

    Write the Better Auth integration page from the existing plugin docs.

    How to measure it

    Integration-page sign-ups

    Now
    –
    Target
    30 a month
    By
    1 quarter

    Steps

    1. 1

      List integrations

      Better Auth, RevenueCat, Vercel, Stripe, Convex.

      Founding Engineer 1 day

    2. 2

      Build starters

      One repo per integration.

      Founding Engineer 2 weeks

    3. 3

      Write pages

      Setup, starter, example.

      Founding Engineer 1 week

    4. 4

      Ask partners to link

      Better Auth docs and partner directories.

      Co-founder & CEO 2 weeks

    5. 5

      Add to navigation

      Footer and docs.

      Founding Engineer 1 hour

    6. 6

      Track

      Sign-ups per page.

      Co-founder & CEO monthly

    First result
    6 weeks
    Cost
    Staff time only
    Owner
    Founding Engineer

    Smallest test

    Publish the Better Auth page and ask for one link from the plugin docs.

    Why it works

    Publish /integrations with one page per integration: what it does, a five-minute setup, a starter repo, and a customer example (Runable for RevenueCat). Ask Better Auth to link the page from the plugin docs, and list Autumn in the Vercel and RevenueCat partner directories where available.

    Integration pages rank for "<tool> billing" and "<tool> credits" searches and meet developers at the stack decision they have already made.

    Risks and how to handle them

    • Starters go stale

      Run them in CI on every release.

    Builds on

    Evidence

    • Developer channelsBetter Auth: Better Auth's docs list an Autumn plugin maintained by the Autumn team, with five setup steps, customers created at sign-up with a default plan, and links to useautumn.com, the dashboard, GitHub and Discord.Source
    • Your websitePricing page: Free at $0 ("Perfect while finding PMF": 8K monthly billing volume, up to 10,000 customers, 10M API requests, CLI and MCP access, community support); Pro at $375 a month (50K billing volume, 20M API requests, data warehouse integration, dedicated Slack support, Stripe, RevenueCat and Vercel as billing sources, $5 per extra 1M requests); Scale at custom pricing ("Contact us" to a booking link); a billing-volume slider from 8K to 500K+; "Stripe fees (0.7% and 2.9% + 30¢) still apply"; an FAQ heading with no questions in the page text; no annual price or startup offer.Source
    • Your websiteSitemap (39 URLs, checked November 9, 2026): homepage, pricing, blog, /alog, terms and privacy; 29 blog posts (latest October 10, 2026); four /alog comparison pages (vs building in-house, Metronome, Orb and Stripe Billing, all dated June 22, 2026). No customers hub, no integration, use-case or pricing-model pages, no changelog, no security page and no careers page.Source
  • 13

    Autumn rebuilt onboarding so a developer can paste one line into their coding agent and have billing set up end to end, with evals that run real sessions. That is a sharp differentiator, but it lives in a September blog post. The homepage hero still offers only "Start for free" and "Get a demo", and the post reports no numbers on how fast or how often agent setup succeeds.

    High impactLow effort First result in 3 weeks Co founder & CTO

    First action

    Add the copy-prompt button to the hero.

    How to measure it

    Agent-setup activations

    Now
    –
    Target
    30% of new accounts
    By
    1 quarter

    Steps

    1. 1

      Finalise the prompt

      One line that works across common agents.

      Co-founder & CTO 1 day

    2. 2

      Add copy buttons

      Hero, pricing models, story endings.

      Founding Engineer 1 day

    3. 3

      Instrument

      Paste to first successful check.

      Co-founder & CTO 3 days

    4. 4

      Publish the benchmark

      Median time and success rate from evals.

      Co-founder & CTO 1 week

    5. 5

      Show it on the homepage

      One line with the number.

      Founding Engineer 1 hour

    6. 6

      Refresh

      With each onboarding release.

      Co-founder & CTO monthly

    First result
    3 weeks
    Cost
    Staff time only
    Owner
    Co founder & CTO

    Smallest test

    Add the copy-prompt button and compare clicks with "Start for free" for two weeks.

    Why it works

    Add a copyable one-line agent prompt next to "Start for free" in the hero, on pricing-model pages and at the end of stories. Use the existing evals to publish a simple benchmark (median time from paste to first successful `check()`, and success rate) and refresh it with each onboarding release.

    Developers increasingly start tools from their agent, not a browser form. A visible, measured one-line setup turns a blog post into the main reason to try Autumn today.

    Risks and how to handle them

    • The benchmark disappoints

      Publish it after fixing the top failure, and show the trend.

    Builds on

    Evidence

    • Your website"Rebuilding our onboarding for agents" (September 20, 2026): the sixth onboarding revamp that month; agents write a config and run `atmn push`; skills and evals with simulated users; keyless onboarding where the agent provisions an org and API key and the user claims it later via a link; users start by pasting one line into their agent; no activation numbers are reported.Source
    • Your websiteHomepage (checked November 9, 2026): page title "Billing Infrastructure for AI Startups | Autumn" and meta description "Drop-in billing for AI startups. Stop rebuilding usage limits, credits, and subscription logic."; H1 "Usage-based billing for B2B companies", subhead "complex contract terms, any usage model, and end-to-end automation from contract to invoice"; site footer "Autumn is drop-in billing for AI companies"; logos for Resend, Mintlify, Firecrawl, Mastra, Browser Use, T3.chat, Mobbin and poke.com, three with "Read story" links; the hero "Start for free" goes to sign-in and "Get a demo" to a Cal.com booking page.Source
    • CommunityProduct Hunt: tagline "Stripe made easy for AI startups", about 96 upvotes; commenters said setup went from days or weeks to hours; the maker said only Stripe was supported, with more providers planned, and a commenter asked for alternatives.Source
  • 14

    With keyless onboarding, a coding agent creates an Autumn org and API key, and the developer claims it later through a link. That removes friction, but it also creates a new kind of lead: working billing setups with no human account attached. If the claim link is lost in an agent's terminal output, Autumn has no way to reach the developer.

    Medium impactMedium effort First result in 1 month Co founder & CTO

    First action

    Count orgs created through keyless onboarding and how many were claimed.

    How to measure it

    Claimed agent orgs

    Now
    –
    Target
    60%
    By
    1 quarter

    Steps

    1. 1

      Measure

      Created vs claimed orgs and time to claim.

      Co-founder & CTO 1 day

    2. 2

      Improve the hand-off

      Agent shows the claim link and asks for an email.

      Co-founder & CTO 3 days

    3. 3

      Add reminders

      Claim notices in CLI and test-mode responses.

      Founding Engineer 3 days

    4. 4

      Write the sequence

      Tour of the agent's config, next pattern.

      Co-founder & CEO 2 days

    5. 5

      Add to evals

      Claim step in the simulated-user tests.

      Co-founder & CTO 2 days

    6. 6

      Report

      Claim rate weekly.

      Co-founder & CTO weekly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Co founder & CTO

    Smallest test

    Add an email prompt to the last step of agent setup for two weeks.

    Why it works

    Track unclaimed orgs as a funnel stage. Make the agent show the claim link prominently and ask for an email at the end of setup, show a claim banner in test-mode responses or the CLI, and send a short sequence after claiming: a dashboard tour of the config the agent wrote, and the next pricing pattern to try. Report claim rate and time-to-claim weekly.

    Developers who let an agent set up billing have already done the hardest step; reaching them at that moment turns a test org into a customer.

    Risks and how to handle them

    • Nagging inside developer tools

      One reminder in the CLI and none in production responses.

    Builds on

    Evidence

    • Your website"Rebuilding our onboarding for agents" (September 20, 2026): the sixth onboarding revamp that month; agents write a config and run `atmn push`; skills and evals with simulated users; keyless onboarding where the agent provisions an org and API key and the user claims it later via a link; users start by pasting one line into their agent; no activation numbers are reported.Source
  • 15

    The new homepage promises "complex contract terms" and "end-to-end automation from contract to invoice", and the Mintlify story proves it: customers used to wait a week for features, overage went uncharged, and 2-4 engineers maintained billing, until an agent started provisioning each closed deal in one API call. Yet there is no page for this buyer, who comes to Autumn via Scale and a demo link, not a free sign-up.

    High impactMedium effort First result in 6 weeks Co founder & CEO

    First action

    Draft the page from the Mintlify story.

    How to measure it

    Scale demos

    Now
    –
    Target
    10 a month
    By
    1 quarter

    Steps

    1. 1

      Draft the page

      Problem, how it works, proof.

      Co-founder & CEO 3 days

    2. 2

      Show the flow

      Closed-won to provisioned plan diagram.

      Founding Engineer 2 days

    3. 3

      Add a demo form

      CRM, contract count, billing source.

      Founding Engineer 1 day

    4. 4

      Find a second story

      Another sales-led customer.

      Co-founder & CEO 1 month

    5. 5

      Build a target list

      AI companies hiring their first salespeople.

      Co-founder & CEO 1 week

    6. 6

      Run outbound

      Short emails linking the page.

      Co-founder & CEO ongoing

    First result
    6 weeks
    Cost
    Staff time only
    Owner
    Co founder & CEO

    Smallest test

    Send the page to five AI companies that recently announced sales hires.

    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

    Publish /sales-led: the problem (CRM and billing out of sync, unbilled usage, slow provisioning), how Autumn handles pilots, ramps, pooled credits and parent-child accounts, the Mintlify numbers, and a demo booking that asks for CRM and contract volume. Use it in outbound to AI companies that have just hired their first sales team.

    Scale contracts are where revenue concentrates, and these buyers need a page they can forward to finance and sales leadership, not a developer quickstart.

    Risks and how to handle them

    • Founder time spread across sales and product

      Limit outbound to ten accounts a week.

    Builds on

    Evidence

    • Your websiteMintlify story: sales is close to half the company; before Autumn, customers waited about a week for features, some overage prices were missing so usage went uncharged, and 2-4 engineers worked on billing; now a closed-won deal triggers an agent that reads the contract and provisions the plan in one API call; quote: "Since the migration, I have a lot more confidence that customers are actually getting what they're paying for."Source
    • Your websiteHomepage (checked November 9, 2026): page title "Billing Infrastructure for AI Startups | Autumn" and meta description "Drop-in billing for AI startups. Stop rebuilding usage limits, credits, and subscription logic."; H1 "Usage-based billing for B2B companies", subhead "complex contract terms, any usage model, and end-to-end automation from contract to invoice"; site footer "Autumn is drop-in billing for AI companies"; logos for Resend, Mintlify, Firecrawl, Mastra, Browser Use, T3.chat, Mobbin and poke.com, three with "Read story" links; the hero "Start for free" goes to sign-in and "Get a demo" to a Cal.com booking page.Source
    • Your website"Reworking our positioning" (July 29, 2026): React hooks and shadcn components deprecated for new work; new projects pointed at the backend SDK; "The harder problem is the ongoing management experience": changing pricing models, provisioning custom deals and debugging billing history; "Our value prop and positioning has changed with the times."Source
  • 16

    The Scale plan is "for high throughput, compliance, or custom requirements", and rivals lead with compliance and speed: Flexprice claims SOC 2 Type II and under 60 ms P99, Schematic claims SOC 2. Autumn has strong material of its own (an edge cache in the customer's AWS account, fail-open SDKs, Firecrawl's 5,000+ requests per second, a 3x throughput post and an open post-mortem), but the sitemap has no security or reliability page to bring it together.

    Medium impactMedium effort First result in 2 months Co founder & CTO

    First action

    List the security questions asked in the last ten Scale calls.

    How to measure it

    Scale close rate

    Now
    –
    Target
    +20%
    By
    2 quarters

    Steps

    1. 1

      Collect questions

      From Scale calls and questionnaires.

      Co-founder & CEO 1 day

    2. 2

      Write the page

      Data, Stripe, fail-open, edge cache.

      Co-founder & CTO 1 week

    3. 3

      Add scale numbers

      Customer throughput and checks per day.

      Co-founder & CTO 1 day

    4. 4

      State compliance accurately

      Current status and dates only.

      Co-founder & CEO 1 day

    5. 5

      Link it

      Scale card, demo booking, footer.

      Founding Engineer 1 hour

    6. 6

      Keep current

      Update after each audit or incident.

      Co-founder & CTO quarterly

    First result
    2 months
    Cost
    Staff time; audit costs if pursued
    Owner
    Co founder & CTO

    Smallest test

    Send a one-page security summary to the next three Scale prospects.

    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 /security with a plain account of data handling, sub-processors, Stripe's role, fail-open behaviour, the edge cache, status page history and post-mortems, plus the current state of any compliance audit (stated accurately, with a date if one is in progress). Add a "production scale" block with real numbers from customers. Link it from Scale and the demo booking.

    Billing sits on the revenue path; the buyer's engineering lead and finance team need one page that answers "what if Autumn goes down?" before they sign.

    Risks and how to handle them

    • Overstating compliance

      Publish only what is complete, with dates.

    Evidence

    • Competitor researchRivals' own homepages: Flexprice, "Monetization Infrastructure for AI Native Companies", open source with on-prem deployment, claiming SOC 2 Type II and "under 60ms P99 latency", and publishing "alternatives" pages about rivals such as Schematic; Schematic, "Credits, metering, and usage governance on one realtime ledger", claiming SOC 2, an MCP interface for agents and Stripe Verified Partner status. Orb, Metronome, Lago and Stigg sell to the same AI companies.Source
    • Your docsWelcome page: Autumn is the "source of truth for billing and entitlements between your application and Stripe"; first payment setup "typically goes live in under an hour" and migrations take 1-2 weeks; an edge cache runs in the customer's own AWS account; SDKs default to fail-open.Source
    • Your websiteFirecrawl story: Firecrawl bills "billions of credits" a month and sends more than 5,000 requests per second at peak; it replaced an 800-line SQL balance function; Autumn assigned an engineer to help migrate; it changed pricing 16 times from April to August, with experiment effort cut "by 10x"; quote from its Head of Support Engineering: "There's no way we'd be able to iterate as fast as we are without Autumn."Source
    • Your websiteSitemap (39 URLs, checked November 9, 2026): homepage, pricing, blog, /alog, terms and privacy; 29 blog posts (latest October 10, 2026); four /alog comparison pages (vs building in-house, Metronome, Orb and Stripe Billing, all dated June 22, 2026). No customers hub, no integration, use-case or pricing-model pages, no changelog, no security page and no careers page.Source
  • 17

    Autumn's biggest prospects already have billing, usually home-grown: Firecrawl had an 800-line SQL balance function, and Autumn assigned an engineer to move it. The docs say migrations take 1-2 weeks. That hands-on help is a strong closer, but it appears only inside a story, not as an offer a prospect can ask for.

    Medium impactMedium effort First result in 6 weeks Founding Engineer

    First action

    Write the four-step migration scope from the Firecrawl migration.

    How to measure it

    Migrations booked

    Now
    –
    Target
    4 a month
    By
    1 quarter

    Steps

    1. 1

      Define the scope

      Audit, map, parallel run, cut-over.

      Co-founder & CTO 2 days

    2. 2

      Build the importer

      Stripe products and prices into an Autumn config.

      Founding Engineer 2 weeks

    3. 3

      Write the page

      Scope, timeline, who qualifies.

      Co-founder & CEO 2 days

    4. 4

      Add a booking path

      From comparisons and the in-house page.

      Founding Engineer 1 day

    5. 5

      Run the first five

      Track days to cut-over.

      Founding Engineer 1 quarter

    6. 6

      Publish the results

      Median migration time on the page.

      Co-founder & CEO after 5 migrations

    First result
    6 weeks
    Cost
    Engineering time per migration
    Owner
    Founding Engineer

    Smallest test

    Add a "Book a migration" link to the Autumn vs Building In-House page.

    Why it works

    Publish a migration page with a fixed scope: an audit of the current billing, a mapped Autumn config, parallel running against live usage, and cut-over, with a named engineer and a two-week target. Offer it free on Pro annual and Scale. Build a small import tool for existing Stripe products and prices to shorten the first step.

    The fear of migrating live billing stops more deals than price does; a scoped, staffed offer removes it.

    Risks and how to handle them

    • Migrations eat the small team's time

      Limit to qualified accounts and automate the import first.

    Builds on

    Evidence

    • Your websiteFirecrawl story: Firecrawl bills "billions of credits" a month and sends more than 5,000 requests per second at peak; it replaced an 800-line SQL balance function; Autumn assigned an engineer to help migrate; it changed pricing 16 times from April to August, with experiment effort cut "by 10x"; quote from its Head of Support Engineering: "There's no way we'd be able to iterate as fast as we are without Autumn."Source
    • Your docsWelcome page: Autumn is the "source of truth for billing and entitlements between your application and Stripe"; first payment setup "typically goes live in under an hour" and migrations take 1-2 weeks; an edge cache runs in the customer's own AWS account; SDKs default to fail-open.Source
    • HiringFounding Engineer (Y Combinator job board, listed as open on November 9, 2026): London, in person, £80K-£120K and 0.50%-1.00% equity; a "backend Founding Engineer who loves to build, loves developers and has excellent product taste" who would be the fifth team member; the post says Autumn works with fast-growing AI startups and an active community of indie developers. YC profile: Summer 2025 batch, team of 5, London; raised "millions" from YC, Paul Graham, PeakXV and devtool founders.Source
  • 18

    Autumn's most-quoted content is about pricing decisions, not plumbing: "People really don't like metered billing", the psychology of T3 Chat's pricing, Runable's cut from 15 plans to 3 and its $1 first month. These posts teach founders how to price, which is the moment before they choose billing software. They appear irregularly, mixed in with engineering posts.

    Medium impactMedium effort First result in 1 month Co founder & CEO

    First action

    Pick the first three products to tear down and ask one customer for an experiment story.

    How to measure it

    Series-sourced sign-ups

    Now
    –
    Target
    40 a month
    By
    2 quarters

    Steps

    1. 1

      Plan the calendar

      One teardown and one customer story a month.

      Co-founder & CEO 1 day

    2. 2

      Write the first teardown

      Public pricing only.

      Co-founder & CEO 3 days

    3. 3

      Interview a customer

      One experiment with numbers.

      Co-founder & CEO 1 week

    4. 4

      Create an index

      A pricing series page in the blog.

      Founding Engineer 1 day

    5. 5

      Distribute

      Newsletter, X, LinkedIn, Discord.

      Co-founder & CEO monthly

    6. 6

      Measure

      Sign-ups per post.

      Co-founder & CEO monthly

    First result
    1 month
    Cost
    Founder time
    Owner
    Co founder & CEO

    Smallest test

    Publish one teardown and compare sign-ups with an engineering post.

    Why it works

    Run a monthly series: one teardown of a public AI product's pricing (what it charges, how credits work, what Autumn would change) and one co-written story with a customer about a pricing experiment, with real before-and-after numbers. Give the series its own index, send it in the newsletter, and cut each into a short thread for X and LinkedIn.

    Founders search and share pricing advice; owning that conversation puts Autumn in front of buyers before they look for a billing tool.

    Risks and how to handle them

    • Teardowns read as attacks

      Keep them constructive and stick to public facts.

    Builds on

    Evidence

    • Your websiteBlog index: 29 posts, all by the two co-founders, with no categories; includes "Talking about billing with 30 YC founders", "How we made our first sale as a startup", "Marketing is hard", "People really don't like metered billing", "The psychology behind T3 Chat's pricing", "Post mortem: database outage" and engineering posts such as "How to build a credit ledger that scales".Source
    • Your websiteRunable story: 1.7M+ users; "Going from 15 plans to 3 was the best pricing decision we made"; Autumn handles about 1.3M balance checks and 500K usage events a day; a $1 first month beat every other discount; about a 5% relative conversion lift from easy experiments; building it in-house was estimated at five engineers; one customer record across Stripe and RevenueCat; Runable's agent uses Autumn's CLI and Platform API to set up billing for each app its users build, each with its own Autumn org and Stripe Connect account.Source
  • 19

    Autumn grew out of founder conversations ("Talking about billing with 30 YC founders", "How we made our first sale as a startup") and is backed by YC, Paul Graham, PeakXV and devtool founders. AI founders ask each other what they use for billing, but Autumn gives its users nothing to pass on: there is no referral page or offer on the site.

    Medium impactLow effort First result in 1 month Co founder & CEO

    First action

    Set up referral codes in Autumn for the current paying customers.

    How to measure it

    Referred sign-ups

    Now
    –
    Target
    15% of new paid accounts
    By
    2 quarters

    Steps

    1. 1

      Define the reward

      Both sides, simple to explain.

      Co-founder & CEO 1 day

    2. 2

      Configure in Autumn

      Referral codes and credits.

      Founding Engineer 2 days

    3. 3

      Add to the dashboard

      A "Refer a founder" link.

      Founding Engineer 2 days

    4. 4

      Seed the network

      YC and investor portfolio channels.

      Co-founder & CEO 1 week

    5. 5

      Thank referrers

      Public shout-outs with permission.

      Co-founder & CEO ongoing

    6. 6

      Measure

      Referred sign-ups and paid conversions.

      Co-founder & CEO monthly

    First result
    1 month
    Cost
    Discounted months
    Owner
    Co founder & CEO

    Smallest test

    Ask ten happy customers for one introduction each.

    Why it works

    Give every paying customer a referral link: the new team gets a first month of Pro free or a launch-tier credit, and the referrer gets a month off. Seed it through the YC founder network and investor portfolios with a short "how YC companies price AI products" note, and run the program on Autumn's own credits feature.

    Billing tools spread by word of mouth between founders, and a referral that uses Autumn's own product is also a demo.

    Risks and how to handle them

    • Low uptake from busy founders

      Ask personally at moments of success, such as a pricing launch.

    Builds on

    Evidence

    • Your websiteBlog index: 29 posts, all by the two co-founders, with no categories; includes "Talking about billing with 30 YC founders", "How we made our first sale as a startup", "Marketing is hard", "People really don't like metered billing", "The psychology behind T3 Chat's pricing", "Post mortem: database outage" and engineering posts such as "How to build a credit ledger that scales".Source
    • HiringFounding Engineer (Y Combinator job board, listed as open on November 9, 2026): London, in person, £80K-£120K and 0.50%-1.00% equity; a "backend Founding Engineer who loves to build, loves developers and has excellent product taste" who would be the fifth team member; the post says Autumn works with fast-growing AI startups and an active community of indie developers. YC profile: Summer 2025 batch, team of 5, London; raised "millions" from YC, Paul Graham, PeakXV and devtool founders.Source
    • Your websiteSitemap (39 URLs, checked November 9, 2026): homepage, pricing, blog, /alog, terms and privacy; 29 blog posts (latest October 10, 2026); four /alog comparison pages (vs building in-house, Metronome, Orb and Stripe Billing, all dated June 22, 2026). No customers hub, no integration, use-case or pricing-model pages, no changelog, no security page and no careers page.Source

Big bets 3

Larger plays that can change the trajectory.

  • 20

    Runable's agent uses Autumn's CLI and Platform API to set up billing for each app its users build, with a separate Autumn org and Stripe Connect account per app. That turns one customer into many billing accounts. Every AI app builder whose users want to charge for what they build faces the same problem, and Autumn has a working reference already.

    High impactHigh effort First result in 1 quarter Co founder & CEO

    First action

    Write up the Runable platform architecture as an internal reference with Runable's approval.

    How to measure it

    Platform-provisioned orgs

    Now
    –
    Target
    1,000
    By
    2 quarters

    Steps

    1. 1

      Document the reference

      How Runable provisions orgs and Stripe Connect.

      Co-founder & CTO 1 week

    2. 2

      Harden the Platform API

      Provisioning, limits and reporting.

      Founding Engineer 1 month

    3. 3

      Set platform pricing

      Volume or revenue share.

      Co-founder & CEO 2 weeks

    4. 4

      Recruit design partners

      Two or three app builders.

      Co-founder & CEO 1 quarter

    5. 5

      Publish the program

      A /platforms page with the reference.

      Co-founder & CEO 2 weeks

    6. 6

      Review

      Orgs, revenue and support load per partner.

      Co-founder & CEO monthly

    First result
    1 quarter
    Cost
    Engineering quarter
    Owner
    Co founder & CEO

    Smallest test

    Pitch the platform model to two app builders using the Runable numbers.

    Why it works

    Package what Runable does into a platform offer: a Platform API guide, per-app org provisioning, Stripe Connect onboarding, platform-level reporting, and revenue-share or volume pricing for the platform. Recruit two or three more app builders and agent platforms as design partners, and publish the Runable architecture as the reference.

    Each platform partner brings a steady stream of new paying apps without separate acquisition cost, and agent-built apps are a fast-growing source of new software.

    Risks and how to handle them

    • Thousands of tiny orgs drive support load

      Support goes through the platform, not the end user.

    Builds on

    Evidence

    • Your websiteRunable story: 1.7M+ users; "Going from 15 plans to 3 was the best pricing decision we made"; Autumn handles about 1.3M balance checks and 500K usage events a day; a $1 first month beat every other discount; about a 5% relative conversion lift from easy experiments; building it in-house was estimated at five engineers; one customer record across Stripe and RevenueCat; Runable's agent uses Autumn's CLI and Platform API to set up billing for each app its users build, each with its own Autumn org and Stripe Connect account.Source
    • Your website"Rebuilding our onboarding for agents" (September 20, 2026): the sixth onboarding revamp that month; agents write a config and run `atmn push`; skills and evals with simulated users; keyless onboarding where the agent provisions an org and API key and the user claims it later via a link; users start by pasting one line into their agent; no activation numbers are reported.Source
  • 21

    Autumn sees pricing behaviour few others can: billions of credits a month at Firecrawl, 1.3M balance checks a day at Runable, and dozens of plan changes across customers. Its customer stories already show which experiments work (a $1 first month, yearly discounts, cutting 15 plans to 3). Aggregated, that is the data every AI founder wants when setting prices.

    High impactHigh effort First result in 2 quarters Co founder & CEO

    First action

    Ask the top 20 customers to opt in to anonymised aggregate reporting.

    How to measure it

    Report-sourced sign-ups

    Now
    –
    Target
    300 in 60 days after launch
    By
    2 quarters

    Steps

    1. 1

      Get consent

      Opt-in for aggregate use.

      Co-founder & CEO 1 month

    2. 2

      Define metrics

      Pricing model, change frequency, allowances.

      Co-founder & CTO 1 week

    3. 3

      Build queries

      Anonymised, with minimum group sizes.

      Founding Engineer 2 weeks

    4. 4

      Write the report

      Findings and charts.

      Co-founder & CEO 3 weeks

    5. 5

      Launch

      Webinar, social charts, newsletter.

      Co-founder & CEO 1 week

    6. 6

      Repeat yearly

      Same metrics for trends.

      Co-founder & CEO yearly

    First result
    2 quarters
    Cost
    A month of founder and engineer time
    Owner
    Co founder & CEO

    Smallest test

    Publish one chart, share of customers using credits vs usage, on X.

    Why it works

    With customer opt-in and strict anonymisation, publish a yearly report: share of companies on credits, seats, usage or hybrid; how often they change pricing; typical free allowances; top-up and rollover patterns; and which changes lifted conversion. Release it with a webinar, a set of charts for social, and a short version for agents in llms.txt.

    Original data earns links, press and AI-assistant citations that blog posts cannot, and it positions Autumn as the authority on AI pricing.

    Risks and how to handle them

    • Customers fear exposure

      Opt-in only, minimum group sizes, no company-level figures.

    Builds on

    Evidence

    • Your websiteFirecrawl story: Firecrawl bills "billions of credits" a month and sends more than 5,000 requests per second at peak; it replaced an 800-line SQL balance function; Autumn assigned an engineer to help migrate; it changed pricing 16 times from April to August, with experiment effort cut "by 10x"; quote from its Head of Support Engineering: "There's no way we'd be able to iterate as fast as we are without Autumn."Source
    • Your websiteRunable story: 1.7M+ users; "Going from 15 plans to 3 was the best pricing decision we made"; Autumn handles about 1.3M balance checks and 500K usage events a day; a $1 first month beat every other discount; about a 5% relative conversion lift from easy experiments; building it in-house was estimated at five engineers; one customer record across Stripe and RevenueCat; Runable's agent uses Autumn's CLI and Platform API to set up billing for each app its users build, each with its own Autumn org and Stripe Connect account.Source
    • Your websiteBlog index: 29 posts, all by the two co-founders, with no categories; includes "Talking about billing with 30 YC founders", "How we made our first sale as a startup", "Marketing is hard", "People really don't like metered billing", "The psychology behind T3 Chat's pricing", "Post mortem: database outage" and engineering posts such as "How to build a credit ledger that scales".Source
  • 22

    Autumn is built on Stripe, and Pro already adds RevenueCat and Vercel as billing sources, which let Runable unify web and iOS customers. On Product Hunt, the maker said more providers were planned and a commenter asked for alternatives. Teams in markets or business models Stripe serves poorly cannot adopt Autumn at all today.

    Medium impactHigh effort First result in 2 quarters Co founder & CTO

    First action

    Tag every lost deal and Discord request by the provider asked for.

    How to measure it

    Non-Stripe accounts

    Now
    –
    Target
    50
    By
    2 quarters after launch

    Steps

    1. 1

      Rank demand

      Lost deals and community requests.

      Co-founder & CEO 2 weeks

    2. 2

      Pick one provider

      Highest demand and feasible API.

      Co-founder & CTO 1 week

    3. 3

      Build the adapter

      Same check, track and attach behaviour.

      Founding Engineer 2 months

    4. 4

      Beta with requesters

      Teams who asked for it.

      Co-founder & CTO 1 month

    5. 5

      Launch

      Guide, story and pricing page update.

      Co-founder & CEO 2 weeks

    6. 6

      Review

      Adoption vs maintenance cost.

      Co-founder & CTO quarterly

    First result
    2 quarters
    Cost
    An engineering quarter
    Owner
    Co founder & CTO

    Smallest test

    Add a "request a billing source" form and count requests for a month.

    Why it works

    Use Pro sign-up data, lost deals and Discord requests to rank the next provider by demand, then build one more billing source with the same check and track API. Launch it with a migration guide and a customer story, and present Autumn as the layer that keeps pricing logic stable whichever processor is underneath.

    It opens deals Autumn cannot win today and supports the "source of truth" position against processor-native tools.

    Risks and how to handle them

    • A small team spread thin

      Build one adapter only after the demand count justifies it.

    Evidence

    • Your websitePricing page: Free at $0 ("Perfect while finding PMF": 8K monthly billing volume, up to 10,000 customers, 10M API requests, CLI and MCP access, community support); Pro at $375 a month (50K billing volume, 20M API requests, data warehouse integration, dedicated Slack support, Stripe, RevenueCat and Vercel as billing sources, $5 per extra 1M requests); Scale at custom pricing ("Contact us" to a booking link); a billing-volume slider from 8K to 500K+; "Stripe fees (0.7% and 2.9% + 30¢) still apply"; an FAQ heading with no questions in the page text; no annual price or startup offer.Source
    • CommunityProduct Hunt: tagline "Stripe made easy for AI startups", about 96 upvotes; commenters said setup went from days or weeks to hours; the maker said only Stripe was supported, with more providers planned, and a commenter asked for alternatives.Source
    • Your websiteRunable story: 1.7M+ users; "Going from 15 plans to 3 was the best pricing decision we made"; Autumn handles about 1.3M balance checks and 500K usage events a day; a $1 first month beat every other discount; about a 5% relative conversion lift from easy experiments; building it in-house was estimated at five engineers; one customer record across Stripe and RevenueCat; Runable's agent uses Autumn's CLI and Platform API to set up billing for each app its users build, each with its own Autumn org and Stripe Connect account.Source

Wildcards 1

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

  • 23

    Autumn's best-known Hacker News moment was a roasting: "We tried to make billing backendless" drew 41 comments, mostly about trusting the client. The team answered openly, changed course, wrote "A roasting from HN makes better devtools", and has since moved new projects to the backend SDK. That arc, plus agent onboarding and a 2.7K-star open-source repo, is a story HN rewards.

    Medium impactLow effort First result in 1 week Co founder & CEO

    First action

    Draft the Show HN post and the first comment.

    How to measure it

    Launch-week sign-ups

    Now
    –
    Target
    200
    By
    1 week after posting

    Steps

    1. 1

      Draft the post

      What changed since the last thread.

      Co-founder & CEO 1 day

    2. 2

      Prepare the repo

      README with self-host and agent setup.

      Co-founder & CTO 2 days

    3. 3

      Check the setup path

      Fresh run of one-line onboarding.

      Founding Engineer 1 day

    4. 4

      Post

      A weekday morning US time.

      Co-founder & CEO 1 hour

    5. 5

      Answer everything

      Both founders for six hours.

      Co-founder & CTO 1 day

    6. 6

      Write it up

      What HN said and what you will change.

      Co-founder & CEO 1 week later

    First result
    1 week
    Cost
    $0
    Owner
    Co founder & CEO

    Smallest test

    Share the draft with five developer friends and fix what they question first.

    Why it works

    Post a Show HN for the open-source repo framed around what changed: backend-first by default, agents that set up billing from one line, and the evals behind it. Credit the earlier thread, invite the commenters' scrutiny, and have both founders answer for the first six hours. Link to the docs and the repo, with a self-hosting path for skeptics.

    Showing that criticism led to a better product builds the trust developers need before they put billing on someone else's infrastructure, and HN traffic is the exact audience.

    Risks and how to handle them

    • Another roasting

      Expect it, answer openly, and fix what is fair, as last time.

    Builds on

    Evidence

    • CommunityHacker News: "We tried to make billing backendless" (May 2025): 43 points and 41 comments; commenters questioned trusting the client and the "backendless" label; the team answered openly and changed approach, then wrote "A roasting from HN makes better devtools"; 11 Hacker News mentions, latest July 2026.Source
    • Your website"Reworking our positioning" (July 29, 2026): React hooks and shadcn components deprecated for new work; new projects pointed at the backend SDK; "The harder problem is the ongoing management experience": changing pricing models, provisioning custom deals and debugging billing history; "Our value prop and positioning has changed with the times."Source
    • Developer channelsOpen source: useautumn/autumn on GitHub has about 2.7K stars, 250 forks and an Apache-2.0 license (listing verified September 30, 2026); openalternative.co compares Autumn with Lago, Flexprice, UniBee, BillaBear and Meteroid.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 23 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.

More example playbooks and reviews
ProgrammableDigital

Show Autumn’s product working

Turn screenshots or the website into an animated product demo in its own brand, for the homepage, launch posts and outreach in this playbook.

Make a demo (opens programmable.digital in a new tab)

More growth playbooks

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

  • F2 growth strategyAn AI platform for credit investing ("the agentic operating system for global credit"). It screens deals, spreads financials, works inside…22 growth ideas
  • Kitab growth strategyA wisdom app with Kavi, an AI companion that turns what is on your mind into key ideas from books, 3-minute Wisdom Bites and guided…21 growth ideas
  • AutoScout24 Austria growth strategyRuns autoscout24.at (and gebrauchtwagen.at), the Austrian sites of Europe's largest online car marketplace: new and used cars, motorbikes…22 growth ideas
  • Markforged growth strategyAn additive manufacturing company: the Digital Forge platform of industrial 3D printers (continuous carbon fiber composites, metal)…21 growth ideas
  • FitFeast growth strategyAn Indian protein snack brand: flavoured peanut butters, protein chips, protein shake sachets, protein bars and cookies, third-party…21 growth ideas
  • Bizllionaire growth strategyA small digital marketing agency selling SEO with AI-search visibility (AEO/GEO), social media marketing, paid ads, marketplace ads and…22 growth ideas
  • Cape Diamond Exchange growth strategyA family-run jewellery shop on St. George's Mall in Cape Town since 1991, selling certified diamonds, Tanzanite, gemstones and gold…21 growth ideas
  • OptimumARC growth strategyA Toronto consulting firm and Geomagic Authorized software and training partner that turns 3D scan data into usable CAD and inspection…22 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 10, 2026, and cites them throughout. Autumn did not commission, review or endorse it, and Programmable is not affiliated with Autumn. 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 Autumn runs its business.

Something wrong, or do you represent Autumn? 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 306 ideas

    Fix the header button and add next steps to stories and comparisons, align the title with the H1, publish a customers hub, fill the pricing FAQ, add a newsletter and changelog, and trim the desktop homepage.

  2. Days 31 to 6013 ideas

    Comparison and pricing-model pages, the build-vs-buy calculator, a starter tier, the Convex and Better Auth channels, agent onboarding as the hero, claim-link follow-up, the sales-led page, trust page, migration offer, teardown series and referrals.

  3. Days 61 to 904 ideas

    Commit to the bets: a platform program for app builders, an annual AI pricing report, more billing sources, and a Show HN relaunch.

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 changing pricing weekly without rewriting billing code. The most cited problem: in-house billing logic that grows into hundreds of lines of SQL.

  • A team that helps with migration and answers fast
  • Customers paying but waiting for features, or usage going uncharged
  • In their words: “credits”

Market

Competitive landscape

6 competitors compared: Stripe Billing, Orb, Metronome, Flexprice and 2 more.

  • Gap to exploit: Billing that agents can set up and change end to end
  • Stripe Billing: Credits, limits and in-product entitlements left to the developer
  • Orb: Priced for later-stage companies

Hiring signals

Autumn is a five-person team hiring its fifth engineer-level member: a backend Founding Engineer in London who "loves developers and has excellent product taste".

  • Founding Engineer (London): Backend engineer with product taste who loves developers; fifth team member. Ideas 12, 17, 20.

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 first (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)
  • 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