ProgrammableMarketing/sim.ai (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 · 11
  • Big bets · 3
  • Wildcards · 2
Generated Nov 10, 2026
  1. Programmable
  2. Playbooks
  3. Sim
Sim logo

growth playbook · Nov 10, 2026

sim.ai (opens in a new tab)

Sim growth playbook

Diagnosis

Sim has a large, fast-growing open-source base (30.1k GitHub stars, up from 18k at its $7M Series A) and a huge search footprint: 919 URLs, including 407 model pages, 280 integration pages and 164 library articles. Its first marketing and sales hires are both judged on activation and qualified pipeline.

The gap is that this traffic seldom becomes a Sim answer. The pricing calculator stops at dollars, model pages send people to the homepage, solution buttons open a blank sign-up, library articles have no template link, and customer stories have no numbers.

This playbook first connects the high-intent free tools to Sim's credits, templates and spend limits. It then adds proof, a migration path from n8n, and a self-host-to-Enterprise route. The big bets are an importer, a public report built from run data, and a cost-governance wedge.

Growth Score

7/10

Biggest Opportunity

Turn the 800+ model, integration and library pages that already attract builders into one-click starts with the right template, model and spend limit set, so the founding marketer can measure activation from day one.

Biggest Risk

n8n (250k+ developers, 209.9k stars), Dust and Gumloop sell to the same teams with far more visible proof, and Sim's per-user pricing invites the "unlimited users" comparison its own n8n page concedes.

01

Start here

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

  1. 1

    Make the LLM pricing calculator end in a Sim answer: the same workload in credits, the plan that covers it and a spend limit to set

    Write the formula for runs, base credits, model credits and plan fit, and test it on three example workloads.

    High impact First result in 3 weeks
  2. 2

    Make "Build with these models" open an agent with that model already chosen, not the homepage

    Change the button target to /signup with a model parameter on one comparison page.

    High impact First result in 2 weeks
  3. 3

    Point "See sales agents" and the other solution buttons at installable templates, not a blank sign-up

    Map the six sales use cases to existing integration templates.

    High impact First result in 2 weeks

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.

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

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 · 6
Effort →

Showing 22 of 22 ideas

This week 6

Quick wins with a clear first action.

  • 01

    Sim's free LLM API pricing calculator prices 125 models in dollars, and its own FAQ asks "How do I control LLM costs in an AI agent?". Yet the answer never mentions Sim. There are no credits, no plan, no spend limit and no BYOK, only the site-wide "Start building" button. Someone who has just modelled 1,000 requests a day is a qualified buyer with a budget question, and the page leaves the Sim half of the sum to them. Sim's answer is unusually concrete: 1 credit ($0.005) per run as the base charge, model usage from recorded tokens, BYOK to pay the provider directly, and spend caps per member.

    High impactMedium effort First result in 3 weeks Founding Marketing

    First action

    Write the formula for runs, base credits, model credits and plan fit, and test it on three example workloads.

    How to measure it

    Calculator-to-sign-up rate

    Now
    –
    Target
    2x
    By
    60 days

    Steps

    1. 1

      Agree the math

      Runs × 1 credit, model tokens at the Sim rate, BYOK mode, overage at $0.005, as in the costs doc.

      Founding Marketing 1 day

    2. 2

      Map plans

      Thresholds for Free, Pro, Max and an Enterprise prompt above Max.

      Founding Sales 1 day

    3. 3

      Design the panel

      One line in credits, one plan badge, a BYOK toggle and a batching tip under the dollar result.

      Founding Design Engineer 2 days

    4. 4

      Carry the budget

      Pass model and monthly budget as sign-up parameters and pre-fill the usage cap.

      Founding Design Engineer 3 days

    5. 5

      Reuse it

      A compact panel on the token counter and the model pages.

      Founding Design Engineer 3 days

    6. 6

      Instrument

      Events for panel views, BYOK toggles, button clicks, sign-ups and first run.

      Founding Marketing 1 day

    7. 7

      Route big budgets

      Estimates above the Max allowance offer a call with sales.

      Founding Sales 1 day

    8. 8

      Review

      Compare sign-up and first-run rates with the month before.

      Founding Marketing monthly

    First result
    3 weeks
    Cost
    About two weeks of design-engineering time
    Owner
    Founding Marketing

    Smallest test

    Add a static line under the result, "On Sim: about N credits a month, fits Pro/Max", plus a sign-up link with the model preselected, and compare clicks for two weeks.

    Why it works

    Under the dollar result, add a "Run this on Sim" panel. (1) Monthly runs × 1 credit base charge, plus hosted model usage converted at $0.005 a credit, with a BYOK toggle that shows the base charge only. (2) The plan that covers it: Free (1,000 one-time credits), Pro ($25 per user, 6,000 credits a month plus 2,000 a week) or Max ($100 per user, 25,000 plus 4,000 a week), and any overage. (3) A note that several model calls inside one run share one base charge, so batching lowers cost. (4) A "Start with this budget" button that carries the model and monthly figure into sign-up and pre-fills the workspace usage cap. Be honest at volume: at the default 1,000 requests a day, if each request is its own run, the base charge alone is about 30,000 credits ($150) a month, which is more than Pro's allowance. Showing that up front, with BYOK and batching as the levers, builds more trust than a surprise bill. Add a compact version of the panel to the token counter and the 400+ model pages.

    Cost is the first objection to agents, and this page attracts people actively working on it. Answering in Sim's own units turns a research tool into a sales tool, and it shows spend limits (a headline feature) at the moment they matter. It gives the founding marketer a clean activation metric: calculator, then sign-up with a budget set, then first run.

    Ready to use

    Copy"Run this on Sim" panel

    Inputs (already on the page): input tokens, output tokens, % cached, requests/day, model
    runs_month = requests_day × 30 (editable: calls per run)
    base_credits = runs_month × 1
    model_credits = model_cost_usd ÷ 0.005 (0 when BYOK is on)
    total_credits = base_credits + model_credits
    Plan: ≤ 1,000 one-time → Free; within Pro allowance → Pro $25/user; within Max allowance → Max $100/user; above → Enterprise call
    Overage = credits above allowance × $0.005
    Button: "Start with this budget" → /signup?model=<id>&budget=<usd>
    Tip: "Several model calls inside one run share one base charge."

    Risks and how to handle them

    • The honest base-charge figure scares away high-volume users

      Show the BYOK and batching levers next to it and offer a sales call above Max.

    • The estimate drifts from real bills

      Use the same rate table as billing and date it, as the calculator already does.

    Evidence

    • Your websiteLLM API pricing calculator ("Free tool", 125 models, prices updated November 5, 2026): estimates cost per request, day and month in US dollars from tokens and requests per day (default 2,000 input and 500 output tokens at 1,000 requests a day). It never mentions Sim credits, plans, spend limits or BYOK; its FAQ asks "How do I control LLM costs in an AI agent?"; the only Sim calls to action are the site-wide "Start building" and "Request a demo".Source
    • Your docsCredits, billing and limits: each billable run costs 1 credit ($0.005), and child executions share the parent's base charge; hosted model calls are billed from recorded token usage; with your own provider keys (BYOK) you pay the provider directly and the base run charge still applies; paid usage is capped at the included allowance by default, and "Manage credits" sets a member's cap; a Pro account with 1,000 credits of overage is billed $5 on top of $25.Source
    • Your websitePricing page: Free $0 with 1,000 one-time credits, 1 workspace, 2 concurrent executions and 30-day logs; Pro $25 per user a month with 6,000 credits a month plus 2,000 a week; Max $100 per user a month with 25,000 credits plus 4,000 a week; Enterprise custom. "On Sim Cloud, one credit is worth $0.005." An "Annual -15%" toggle, and no FAQ section.Source
    • HiringFounding Marketing (San Francisco, posted September 24, 2026): "You'll own how people discover, understand, and adopt Sim" through positioning, technical content and demos, launches and channel tests, measured on activation and qualified pipeline rather than attention.Source
  • 02

    407 of Sim's 919 URLs are model pages, and the directory says every model is available in the Agent block. But the comparison pages' "Build with these models" button goes to the homepage, so the visitor loses the model they were comparing and must find it again after sign-up.

    High impactLow effort First result in 2 weeks Founding Design Engineer

    First action

    Change the button target to /signup with a model parameter on one comparison page.

    How to measure it

    Model-page sign-up to first run

    Now
    –
    Target
    +40%
    By
    45 days

    Steps

    1. 1

      Add a parameter

      Accept model IDs on sign-up.

      Founding Design Engineer 1 day

    2. 2

      Build the starters

      One-agent and two-agent comparison workflows.

      Founding Design Engineer 2 days

    3. 3

      Rewire buttons

      All comparison and single model pages.

      Founding Design Engineer 1 day

    4. 4

      Label clearly

      "Try both in one workflow" as the button text.

      Founding Marketing 1 hour

    5. 5

      Track

      Sign-up, first run and model chosen.

      Founding Marketing 1 day

    6. 6

      Review

      Which model pages bring the most active users.

      Founding Marketing monthly

    First result
    2 weeks
    Cost
    A few days of engineering
    Owner
    Founding Design Engineer

    Smallest test

    Rewire the ten most-visited comparison pages first.

    Why it works

    Point the button to sign-up with the model (or both models) as a parameter. After sign-up, open a starter workflow with an Agent block already set to that model, or two Agent blocks side by side for a comparison page, with an evaluator block to compare their answers. Use the same deep link on single model pages.

    The visitor arrives with a specific intent, and fulfilling it in the first minute is the shortest route to a first run, the activation event the marketing role is measured on.

    Risks and how to handle them

    • Models are removed or renamed

      Fall back to the newest model from the same provider.

    Evidence

    • Your websiteModels directory: 173 models across 29 providers; "Every model listed in this directory is available in the Agent block." Model-versus-model comparison pages have a "Build with these models" button that links to the homepage, with no model preselected and no mention of credits; the token counter shows each model's input cost but not Sim's plans.Source
    • Your websiteSitemap (919 URLs, read November 9, 2026): /models 407, /integrations 280, /library 164, /comparisons 21, /blog 14 (last post September 19, 2026), /changelog 12, /solutions 6; English only.Source
    • HiringFounding Marketing (San Francisco, posted September 24, 2026): "You'll own how people discover, understand, and adopt Sim" through positioning, technical content and demos, launches and channel tests, measured on activation and qualified pipeline rather than attention.Source
  • 03

    The sales solution page lists six concrete agents (lead routing, lead research, outreach, CRM updates, meeting prep, pipeline reports). But "See sales agents" and "Explore CRM automation" both go to a plain sign-up, and the workflows in the mock-up can't be installed. The integration pages already offer templates that "build it instantly".

    High impactLow effort First result in 2 weeks Founding Marketing

    First action

    Map the six sales use cases to existing integration templates.

    How to measure it

    Template run within 24 hours of sign-up

    Now
    –
    Target
    50% of solution-page sign-ups
    By
    60 days

    Steps

    1. 1

      Map use cases

      Six solution pages × six cards to templates.

      Founding Marketing 2 days

    2. 2

      Fill gaps

      Build the missing templates.

      Forward Deployed Engineer 1 week

    3. 3

      Deep links

      Each card's button opens its template after sign-up.

      Founding Design Engineer 2 days

    4. 4

      Rename buttons

      "Open the lead-routing agent" rather than "See sales agents".

      Founding Marketing 1 hour

    5. 5

      Track

      Template opened, connected and run.

      Founding Marketing 1 day

    6. 6

      Iterate

      Replace templates that are rarely run.

      Founding Marketing monthly

    First result
    2 weeks
    Cost
    About a week of staff time
    Owner
    Founding Marketing

    Smallest test

    Rewire the sales page only and compare it with finance.

    Why it works

    For each of the six solution pages, publish the agents named on the page as templates and link each use-case card to its own template through sign-up. Reuse the Salesforce, HubSpot and Slack templates that already exist on integration pages.

    A visitor who clicks "See sales agents" expects to see one. Landing in a working template instead of an empty canvas shortens time to value for non-developer buyers.

    Risks and how to handle them

    • Templates need credentials before they run

      Ship each with sample data, so the first run works before OAuth.

    Evidence

    • Your websiteSales solution page: six use cases (route inbound leads, research every lead, draft outreach, update the CRM, prep meetings, report the pipeline); the buttons "See sales agents" and "Explore CRM automation" both go to the plain /signup page, and the workflows named in the product mock-up are not installable templates; customer logos but no customer quotes.Source
    • Your websiteIntegrations: 279 integrations, "5,776 tools", 67 with triggers and 65 with one-click OAuth, in 16 categories; no request-an-integration option shown. The Salesforce page lists 40 tools, 6 triggers and about a dozen agent templates: "Click any to build it instantly."Source
  • 04

    The library has 164 pages, updated almost daily. A typical article runs 9,000-10,000 words and puts Sim first in its table, but has no try-it or template link inside the text. A reader convinced halfway down has to scroll to the header to act.

    Medium impactLow effort First result in 3 weeks Founding Marketing

    First action

    Pick the 20 most-visited articles and assign a template to each.

    How to measure it

    Library-sourced sign-ups

    Now
    –
    Target
    3x
    By
    90 days

    Steps

    1. 1

      Rank articles

      Top 20 by visits.

      Founding Marketing 1 day

    2. 2

      Assign templates

      One per article.

      Founding Marketing 2 days

    3. 3

      Build the card

      A reusable component with source tagging.

      Founding Design Engineer 2 days

    4. 4

      Place it

      After the main table and at the end.

      Founding Marketing 2 days

    5. 5

      Roll out

      To the rest of the library.

      Founding Marketing 2 weeks

    6. 6

      Measure

      Sign-ups and first runs by article.

      Founding Marketing monthly

    First result
    3 weeks
    Cost
    Staff time only
    Owner
    Founding Marketing

    Smallest test

    Add cards to five articles and compare them with five without.

    Why it works

    Add one template card per article, matched to its topic (for example a CRM-update agent on the sales-call article, or an MCP connection on the MCP how-to), after the comparison table and again at the end. Each card opens the template through sign-up and tags the article as the source.

    Readers of "best agents for X" are evaluating, and a ready agent for X is the most useful next step. It also tells marketing which articles produce users rather than visits.

    Risks and how to handle them

    • Cards make neutral-looking articles feel salesy

      Pair them with the disclosure in idea 22.

    Evidence

    • Your websiteLibrary (164 pages): for example "Best Enterprise AI Agent Platforms in 2026" (published August 9, updated November 7, 2026) runs to roughly 9,000-10,000 words, puts Sim first in its comparison table, carries no "published by Sim" note and has no try-it or template link inside the article.Source
    • Your websiteIntegrations: 279 integrations, "5,776 tools", 67 with triggers and 65 with one-click OAuth, in 16 categories; no request-an-integration option shown. The Salesforce page lists 40 tools, 6 triggers and about a dozen agent templates: "Click any to build it instantly."Source
    • HiringFounding Marketing (San Francisco, posted September 24, 2026): "You'll own how people discover, understand, and adopt Sim" through positioning, technical content and demos, launches and channel tests, measured on activation and qualified pipeline rather than attention.Source
  • 05

    The pricing page says a credit is worth $0.005 and lists allowances, but it has no FAQ. The rules that decide a bill (1 credit per run, model usage on top, BYOK still pays the base charge, usage capped by default, overage settled at a $100 threshold) live only in the docs.

    Medium impactLow effort First result in 2 weeks Founding Sales

    First action

    Turn the costs doc's overage example into the first FAQ answer.

    How to measure it

    Pricing-page visitors who start a paid plan

    Now
    –
    Target
    +15%
    By
    60 days

    Steps

    1. 1

      Collect questions

      From sales calls and support.

      Founding Sales 1 day

    2. 2

      Work examples

      Three real workloads.

      Founding Sales 1 day

    3. 3

      Write answers

      From the costs doc, in plain words.

      Founding Marketing 1 day

    4. 4

      Publish

      With FAQ structured data.

      Founding Design Engineer half a day

    5. 5

      Link

      From the calculator panel in idea 1.

      Founding Marketing 1 hour

    6. 6

      Review

      Upgrade and support-ticket trends.

      Founding Sales monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founding Sales

    Smallest test

    Publish three FAQ answers this week.

    Why it works

    Add an FAQ and three worked examples to the pricing page: a daily Slack digest agent, a lead-routing agent at 200 leads a day, and a support agent at 1,000 tickets a month. For each, show runs, credits, plan and monthly cost, with and without BYOK. Answer "What happens when I run out?" and "Can I cap each member?"

    Credits are abstract, and buyers who can't predict a bill stall or pick the free plan. Worked examples also equip the founding seller for procurement questions.

    Risks and how to handle them

    • Examples go stale as model prices change

      Date them and refresh with the model price table.

    Evidence

    • Your websitePricing page: Free $0 with 1,000 one-time credits, 1 workspace, 2 concurrent executions and 30-day logs; Pro $25 per user a month with 6,000 credits a month plus 2,000 a week; Max $100 per user a month with 25,000 credits plus 4,000 a week; Enterprise custom. "On Sim Cloud, one credit is worth $0.005." An "Annual -15%" toggle, and no FAQ section.Source
    • Your docsCredits, billing and limits: each billable run costs 1 credit ($0.005), and child executions share the parent's base charge; hosted model calls are billed from recorded token usage; with your own provider keys (BYOK) you pay the provider directly and the base run charge still applies; paid usage is capped at the included allowance by default, and "Manage credits" sets a member's cap; a Pro account with 1,000 credits of overage is billed $5 on top of $25.Source
  • 06

    The Sim vs n8n page says plainly: "There is no automated one-click migration tool between n8n and Sim", so workflows must be rebuilt, and it suggests starting with one high-value automation. That is the moment to offer help, and Sim is hiring a Forward Deployed Engineer to do exactly that kind of work.

    High impactLow effort First result in 2 weeks Forward Deployed Engineer

    First action

    Add the offer and form to the n8n comparison page.

    How to measure it

    Workflows rebuilt from comparison pages

    Now
    –
    Target
    30 a month
    By
    60 days

    Steps

    1. 1

      Write the offer

      One workflow, 48 hours, free.

      Founding Marketing 1 day

    2. 2

      Add the form

      JSON upload and team size.

      Founding Design Engineer 1 day

    3. 3

      Set a playbook

      Node-to-block mapping notes.

      Forward Deployed Engineer 2 days

    4. 4

      Rebuild

      In a shared workspace with a handover video.

      Forward Deployed Engineer ongoing

    5. 5

      Qualify

      Teams over 20 people go to sales.

      Founding Sales ongoing

    6. 6

      Log patterns

      The most common nodes, for idea 7.

      Forward Deployed Engineer weekly

    First result
    2 weeks
    Cost
    Engineering time, capped per week
    Owner
    Forward Deployed Engineer

    Smallest test

    Offer five rebuild slots on the n8n page this week.

    Why it works

    Add a "Send us one n8n workflow and we'll rebuild it in Sim" form to the n8n, Zapier and Make comparison pages. Accept the exported JSON, rebuild it in a shared workspace within 48 hours, and hand it over with a short video. Qualify larger teams for a sales conversation.

    Switching cost is the main reason people stay. A free rebuild removes it for the first workflow, and each rebuild teaches the team what an importer (idea 7) must handle.

    Risks and how to handle them

    • Demand swamps a small team

      Cap weekly slots and prioritise by team size.

    Evidence

    • Your websiteSim vs n8n ("last verified November 2, 2026"): "There is no automated one-click migration tool between n8n and Sim", so workflows must be rebuilt; the page advises choosing n8n for "execution-based pricing with unlimited users on every plan". There are 21 comparison pages in all, including Zapier, Make, Gumloop and Dust.Source
    • HiringForward Deployed Engineer (posted September 24, 2026): works directly with customers to turn their workflows into production agents, owns deployments end to end (integrations, agents, evals) and feeds recurring problems back into the product.Source

This quarter 11

The core plays for the next three months.

  • 08

    Sim shows five customer logos, but only two have stories, and neither the Rivian nor the eXp Realty story has a single number or customer quote. Competitors lead with scale (Dust: 3,000+ organisations, 300,000+ agents). Enterprise buyers need measured outcomes.

    High impactMedium effort First result in 6 weeks Founding Sales

    First action

    Ask the two existing story customers for one metric and one quote each.

    How to measure it

    Win rate on qualified opportunities

    Now
    –
    Target
    +20%
    By
    2 quarters

    Steps

    1. 1

      Pick metrics

      Hours saved, runs and time to production.

      Founding Sales 2 days

    2. 2

      Pull data

      From deployment logs, with customer consent.

      Forward Deployed Engineer 1 week

    3. 3

      Interview

      One sponsor per customer.

      Founding Marketing 2 weeks

    4. 4

      Write

      Three new stories and two updated ones.

      Founding Marketing 2 weeks

    5. 5

      Approve

      Customer sign-off.

      Founding Sales 2 weeks

    6. 6

      Distribute

      Solution, demo and pricing pages.

      Founding Marketing 1 week

    First result
    6 weeks
    Cost
    Staff time only
    Owner
    Founding Sales

    Smallest test

    Add one approved metric to the Rivian story.

    Why it works

    Have the Forward Deployed Engineer pull before-and-after measures from each deployment (hours saved, runs a month, systems connected, time to production) and get one approved quote per story. Write stories for Artie, thinkproject and Mobile Health Consumer, and use the numbers on solution and demo pages.

    Proof from named companies in production is what moves a governance-led enterprise sale, and the founding seller needs it for every evaluation.

    Risks and how to handle them

    • Enterprises won't approve numbers

      Accept ranges or anonymised metrics alongside the logo.

    Evidence

    • Your websiteCustomers page: two stories (Rivian with Volkswagen Group Technologies, and eXp Realty), neither with quantified results or customer quotes; five logos, three of them (Artie, thinkproject, Mobile Health Consumer) without a story.Source
    • HiringFounding Sales (posted August 26, 2026): owns the full cycle from use cases through technical discovery, demos, evaluations and closing; Sim is "already working with eXp Realty, Rivian, and Volkswagen Group Technologies" and wants to turn existing demand into a repeatable sales process. The team is 10 people, in person in San Francisco.Source
    • Competitor researchRivals' own homepages: n8n, "250k+ developers", "209.9k stars", "500+ native integrations", "Trusted by Fortune 500 companies"; Dust, "3,000+" organisations, "300,000+ agents deployed" and 12 customer logos; Gumloop, "Anyone at a company can build agents with any AI model and any integration, while IT controls access."Source
  • 09

    The last public traction figures (60,000+ developers, 100+ companies in production, 10M+ workflows) come from the November 2025 Series A post, when the repo had 18k stars. It now has 30.1k. Rivals publish current scale: n8n "250k+ developers", Dust "300,000+ agents deployed".

    Medium impactLow effort First result in 2 weeks Founding Marketing

    First action

    Pull current counts of builders, runs and production companies.

    How to measure it

    Demo form completion

    Now
    –
    Target
    +10%
    By
    60 days

    Steps

    1. 1

      Pull counts

      Builders, runs, companies and stars.

      Founding Marketing 1 day

    2. 2

      Define rules

      What counts and when it updates.

      Founding Marketing 1 day

    3. 3

      Build the strip

      A reusable component.

      Founding Design Engineer 2 days

    4. 4

      Place it

      Demo, pricing and solution pages.

      Founding Marketing 1 day

    5. 5

      Update llms.txt

      The same figures.

      Founding Marketing 1 hour

    6. 6

      Refresh

      Monthly.

      Founding Marketing monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founding Marketing

    Smallest test

    Update the demo page with three current numbers.

    Why it works

    Add a small live (or monthly-updated) proof strip to the demo, pricing and solution pages: builders, workflow runs, companies in production and GitHub stars. Use the same figures in llms.txt, so AI assistants describe Sim at its current scale.

    Growth from 18k to 30.1k stars implies much higher usage than the old figures show. Current numbers raise trust at no cost.

    Risks and how to handle them

    • Counts are disputed

      Footnote each definition.

    Evidence

    • Your blogSeries A post (November 12, 2025): $7M led by Standard Capital, with Y Combinator among investors; at the time "60,000+ developers", "100+ companies" in production, "10M+ workflows" processed and 18k GitHub stars.Source
    • GitHubsimstudioai/sim: 30.1k stars, 3.9k forks, Apache-2.0; self-hosting through "npx sim-setup"; the README's "Cloud-hosted: sim.ai" section links to the homepage rather than to sign-up.Source
    • Competitor researchRivals' own homepages: n8n, "250k+ developers", "209.9k stars", "500+ native integrations", "Trusted by Fortune 500 companies"; Dust, "3,000+" organisations, "300,000+ agents deployed" and 12 customer logos; Gumloop, "Anyone at a company can build agents with any AI model and any integration, while IT controls access."Source
  • 10

    Self-hosting is one command ("npx sim-setup"), and Enterprise sells "Self-Hosted Enterprise Features", SSO, access control and dedicated support. Yet the README's cloud section links only to the homepage, and nothing in the setup wizard tells a self-hoster what the licence adds or how to try it.

    High impactMedium effort First result in 1 quarter Founding Sales

    First action

    Add an Enterprise section with a trial-licence link to the README.

    How to measure it

    Self-host trial licences issued

    Now
    –
    Target
    20 a quarter
    By
    2 quarters

    Steps

    1. 1

      README section

      What Enterprise adds, and a trial link.

      Founding Marketing 1 day

    2. 2

      Wizard step

      An optional, opt-in deployment profile.

      Software Engineer, Agent Harness 1 week

    3. 3

      In-app page

      Locked features with a trial button.

      Founding Design Engineer 1 week

    4. 4

      Trial licence

      A 30-day key flow.

      Software Engineer, Agent Harness 1 week

    5. 5

      Route

      Larger companies go to sales.

      Founding Sales ongoing

    6. 6

      Onboard

      Help with SSO and access control.

      Forward Deployed Engineer ongoing

    First result
    1 quarter
    Cost
    About three engineering weeks
    Owner
    Founding Sales

    Smallest test

    Add the README section and count trial requests for a month.

    Why it works

    Add an optional "Tell us about your deployment" step to the setup wizard (company and size, opt-in only), a README section on Enterprise features with a trial-licence request, and an in-app settings page that lists locked enterprise features with a "Try for 30 days" button. Route larger companies to sales.

    Companies self-hosting an open-source tool are the most qualified enterprise leads, because they have already chosen Sim for control and compliance.

    Risks and how to handle them

    • The open-source community dislikes upsell prompts

      Keep everything opt-in and out of the core run path.

    Evidence

    • GitHubsimstudioai/sim: 30.1k stars, 3.9k forks, Apache-2.0; self-hosting through "npx sim-setup"; the README's "Cloud-hosted: sim.ai" section links to the homepage rather than to sign-up.Source
    • Your websitePricing page: Free $0 with 1,000 one-time credits, 1 workspace, 2 concurrent executions and 30-day logs; Pro $25 per user a month with 6,000 credits a month plus 2,000 a week; Max $100 per user a month with 25,000 credits plus 4,000 a week; Enterprise custom. "On Sim Cloud, one credit is worth $0.005." An "Annual -15%" toggle, and no FAQ section.Source
    • HiringFounding Sales (posted August 26, 2026): owns the full cycle from use cases through technical discovery, demos, evaluations and closing; Sim is "already working with eXp Realty, Rivian, and Volkswagen Group Technologies" and wants to turn existing demand into a repeatable sales process. The team is 10 people, in person in San Francisco.Source
  • 11

    Product Hunt reviewers praise the canvas but say failed runs mean digging through dense logs and nested outputs, and one asks for side-by-side comparisons of runs. Sim already ships "Compare workflow versions before you deploy", and logs record inputs, outputs, timing and cost per block.

    Medium impactMedium effort First result in 6 weeks Founding Design Engineer

    First action

    Prototype the diff on two runs of one template.

    How to measure it

    Builders active in week 4

    Now
    –
    Target
    +10%
    By
    1 quarter

    Steps

    1. 1

      Interview

      Five builders on how they debug.

      Founding Design Engineer 1 week

    2. 2

      Design

      A block-aligned two-run view.

      Founding Design Engineer 1 week

    3. 3

      Build

      On top of the version-compare code.

      Founding Design Engineer 2 weeks

    4. 4

      Alert link

      "Compare with the last good run".

      Software Engineer, Agent Harness 2 days

    5. 5

      Launch

      Changelog post and a short demo.

      Founding Marketing 1 day

    6. 6

      Measure

      Use and time to fix.

      Founding Design Engineer monthly

    First result
    6 weeks
    Cost
    About a month of design-engineering time
    Owner
    Founding Design Engineer

    Smallest test

    Show differing block outputs for two runs as plain text.

    Why it works

    Let a user pick two runs and see them block by block: inputs, outputs, model, tokens, cost and time, with the first difference highlighted. Link it from failed-run alerts as "Compare with the last good run".

    Debugging pain is a churn risk for builders, and fixing it in the product is also good launch content.

    Risks and how to handle them

    • Large outputs are slow to render

      Collapse unchanged blocks.

    Evidence

    • ReviewsProduct Hunt: 4.7 from 6 reviews. Praise: the visual canvas, open source and self-hosting, integration coverage, built-in tables and mailer. Criticism: young docs and edge cases, debugging through dense logs, and wishes for side-by-side run comparisons, evaluation and tracing on the canvas, and starting workflows from the UI.Source
    • Your websiteChangelog: ten entries between October 2 and 26, 2026 (new models, Power BI, Intune, Fivetran, "Compare workflow versions before you deploy"); the blog's last post was September 19, 2026; no newsletter sign-up was found on the site.Source
  • 12

    Sim has three big entry points (407 model pages, 280 integration pages and 164 library pages), but almost every button leads to the same /signup. The founding marketer is measured on activation, which needs to know where each user came from and what they wanted to build.

    High impactMedium effort First result in 1 month Founding Marketing

    First action

    Define the intent parameters and the first-run event.

    How to measure it

    First run within 24 hours

    Now
    –
    Target
    +25%
    By
    1 quarter

    Steps

    1. 1

      Define intent

      Source, integration, model and template.

      Founding Marketing 1 day

    2. 2

      Persist it

      Through sign-up, including OAuth sign-ups.

      Founding Design Engineer 1 week

    3. 3

      Route in app

      Open the matching starter.

      Founding Design Engineer 1 week

    4. 4

      Event

      First successful run.

      Software Engineer, Agent Harness 2 days

    5. 5

      Dashboard

      Activation by entry page.

      Founding Marketing 3 days

    6. 6

      Act

      Invest in the best-converting sections.

      Founding Marketing monthly

    First result
    1 month
    Cost
    About three engineering weeks
    Owner
    Founding Marketing

    Smallest test

    Persist the integration parameter only.

    Why it works

    Pass the entry page, integration, model or template through sign-up as one intent object. Open the matching starter in the workspace, and report first run within 24 hours by entry type. Ideas 1-4 are the first users of this plumbing.

    Continuity of intent is the cheapest activation lift there is, and per-page activation data shows which content to make more of.

    Risks and how to handle them

    • Intent is lost across OAuth redirects

      Store it server-side, keyed to the session.

    Builds on

    Evidence

    • Your websiteSitemap (919 URLs, read November 9, 2026): /models 407, /integrations 280, /library 164, /comparisons 21, /blog 14 (last post September 19, 2026), /changelog 12, /solutions 6; English only.Source
    • HiringFounding Marketing (San Francisco, posted September 24, 2026): "You'll own how people discover, understand, and adopt Sim" through positioning, technical content and demos, launches and channel tests, measured on activation and qualified pipeline rather than attention.Source
    • Your websiteSales solution page: six use cases (route inbound leads, research every lead, draft outreach, update the CRM, prep meetings, report the pipeline); the buttons "See sales agents" and "Explore CRM automation" both go to the plain /signup page, and the workflows named in the product mock-up are not installable templates; customer logos but no customer quotes.Source
  • 13

    The homepage scores 89 on mobile in the lab, but real visitors fail Core Web Vitals: LCP is 3.9 s and INP 505 ms at the 75th percentile. The page ships 1,316 KB of JavaScript, 524 KB of it unused, plus about 0.9 s of render-blocking requests.

    Medium impactMedium effort First result in 1 month Founding Design Engineer

    First action

    Run a bundle analysis on the homepage.

    How to measure it

    Core Web Vitals pass

    Now
    –
    Target
    LCP under 2.5 s and INP under 200 ms
    By
    60 days

    Steps

    1. 1

      Analyse bundles

      Find the 524 KB of unused code.

      Founding Design Engineer 1 day

    2. 2

      Split

      Lazy-load the canvas and lower sections.

      Founding Design Engineer 1 week

    3. 3

      Hero first

      Server-render the H1 and CTA.

      Founding Design Engineer 2 days

    4. 4

      Defer tags

      Load the tag manager after interaction.

      Founding Marketing 1 day

    5. 5

      Fix blocking CSS

      Inline critical CSS.

      Founding Design Engineer 2 days

    6. 6

      Verify

      PageSpeed field data after 28 days.

      Founding Design Engineer 1 month

    First result
    1 month
    Cost
    About two weeks of engineering
    Owner
    Founding Design Engineer

    Smallest test

    Lazy-load the canvas demo and re-test.

    Why it works

    Split the interactive canvas demo and below-the-fold components into lazily loaded chunks, server-render the hero, defer the tag manager until after first interaction, and remove render-blocking CSS. Check field data in the Chrome UX Report after 28 days.

    A slow first screen loses developers who click through from search and GitHub, and the page's lead promise is a fast, modern workspace.

    Risks and how to handle them

    • Deferred tags lose attribution

      Check conversion events before and after.

    Evidence

    • PageSpeedHomepage, tested November 9, 2026: lab score 89 on mobile and 91 on desktop, but real visitors fail Core Web Vitals, with field LCP of 3.9 s and INP of 505 ms at the 75th percentile; 1,316 KB of JavaScript, 524 KB of it unused; render-blocking requests cost about 0.9 s.Source
  • 14

    Sim has 30.1k GitHub stars and 3.9k forks, and reviewers praise how quickly they build. But templates come only from Sim, on integration pages. Builders have no public place to publish an agent with their name on it.

    Medium impactMedium effort First result in 2 months Founding Marketing

    First action

    Invite 20 active community builders to publish one template each.

    How to measure it

    Template-sourced sign-ups

    Now
    –
    Target
    1,000 a month
    By
    2 quarters

    Steps

    1. 1

      Publish flow

      Strip credentials and add a description.

      Founding Design Engineer 2 weeks

    2. 2

      Template pages

      Author, runs and one-click use.

      Founding Design Engineer 2 weeks

    3. 3

      Seed

      20 builders from the community.

      Founding Marketing 2 weeks

    4. 4

      Moderate

      Review before listing.

      Forward Deployed Engineer weekly

    5. 5

      Reward

      Credits for the most-used templates.

      Founding Marketing monthly

    6. 6

      Cross-link

      Show them on integration pages.

      Founding Marketing 1 week

    First result
    2 months
    Cost
    About a month of engineering, plus credit rewards
    Owner
    Founding Marketing

    Smallest test

    Publish ten community templates as static pages.

    Why it works

    Let users publish a workflow as a public template with an author profile and a link back. Each template gets its own indexable page with run counts, and is shown on matching integration pages. Feature the best each month and reward authors with credits.

    Authors share their own pages, which brings new builders, and long-tail templates rank for problems Sim's team will never write about.

    Risks and how to handle them

    • Templates leak secrets

      Strip credentials automatically and review before listing.

    Evidence

    • GitHubsimstudioai/sim: 30.1k stars, 3.9k forks, Apache-2.0; self-hosting through "npx sim-setup"; the README's "Cloud-hosted: sim.ai" section links to the homepage rather than to sign-up.Source
    • Your websiteIntegrations: 279 integrations, "5,776 tools", 67 with triggers and 65 with one-click OAuth, in 16 categories; no request-an-integration option shown. The Salesforce page lists 40 tools, 6 triggers and about a dozen agent templates: "Click any to build it instantly."Source
    • ReviewsProduct Hunt: 4.7 from 6 reviews. Praise: the visual canvas, open source and self-hosting, integration coverage, built-in tables and mailer. Criticism: young docs and edge cases, debugging through dense logs, and wishes for side-by-side run comparisons, evaluation and tracing on the canvas, and starting workflows from the UI.Source
  • 16

    Sim connects to 279 tools, 65 of them with one-click OAuth and 67 with triggers, but all promotion runs one way, from Sim's pages to the partner. The partners' own app directories reach the teams that already use those tools.

    Medium impactMedium effort First result in 2 months Founding Marketing

    First action

    Rank OAuth integrations by active connections.

    How to measure it

    Marketplace-sourced sign-ups

    Now
    –
    Target
    300 a month
    By
    2 quarters

    Steps

    1. 1

      Rank

      OAuth integrations by usage.

      Founding Marketing 1 day

    2. 2

      Check programmes

      Which partners run app directories.

      Founding Marketing 3 days

    3. 3

      Prepare listings

      Copy, screenshots and templates.

      Founding Marketing 2 weeks

    4. 4

      Pass reviews

      Security reviews where required.

      Forward Deployed Engineer 1 month

    5. 5

      Co-market

      One guide per partner.

      Founding Marketing ongoing

    6. 6

      Track

      Sign-ups by marketplace.

      Founding Marketing monthly

    First result
    2 months
    Cost
    Staff time; some marketplace fees
    Owner
    Founding Marketing

    Smallest test

    Submit two listings this month.

    Why it works

    Rank the 65 OAuth integrations by usage, then submit Sim listings to the marketplaces of the top ten that run app directories. Pair each listing with the matching templates and co-write one "agents for <tool>" guide per partner.

    Marketplace visitors already use the tool and are looking for add-ons, so they are close to activation.

    Risks and how to handle them

    • Long partner reviews

      Start with self-serve directories.

    Evidence

    • Your websiteIntegrations: 279 integrations, "5,776 tools", 67 with triggers and 65 with one-click OAuth, in 16 categories; no request-an-integration option shown. The Salesforce page lists 40 tools, 6 triggers and about a dozen agent templates: "Click any to build it instantly."Source
  • 17

    The demo form asks for company size and "What can we help you with?" but promises no response time and treats every request the same. Sim is hiring a Forward Deployed Engineer to take customer workflows into production.

    Medium impactLow effort First result in 1 month Founding Sales

    First action

    Add a size-based routing rule and a response promise.

    How to measure it

    Large-company demos that start a pilot

    Now
    –
    Target
    40%
    By
    1 quarter

    Steps

    1. 1

      Set bands

      Company-size routing.

      Founding Sales 1 day

    2. 2

      Instant booking

      For small teams.

      Founding Sales 1 day

    3. 3

      Pilot offer

      Scope for a one-week build.

      Forward Deployed Engineer 3 days

    4. 4

      Page copy

      Response time and pilot offer.

      Founding Marketing 1 day

    5. 5

      Run pilots

      One at a time at first.

      Forward Deployed Engineer ongoing

    6. 6

      Review

      Pilot-to-contract rate.

      Founding Sales monthly

    First result
    1 month
    Cost
    FDE time
    Owner
    Founding Sales

    Smallest test

    Offer the pilot to the next five large-company demos.

    Why it works

    Small teams get an instant booking link and a template matching their answer. Larger companies get a reply within one business hour and an offer of a one-week pilot, in which an FDE builds their first production agent. State the response time on the page.

    Enterprise buyers judge a vendor by its first response, and a working pilot is the strongest evaluation step for a small sales team.

    Risks and how to handle them

    • Pilots consume the FDE

      Cap concurrent pilots and qualify on budget.

    Evidence

    • Your websiteDemo page: "Operationalize AI with Sim, the AI agent workspace"; eight fields including company size and "What can we help you with?"; no response time stated; a logo row headed "Trusted by technical teams at".Source
    • HiringForward Deployed Engineer (posted September 24, 2026): works directly with customers to turn their workflows into production agents, owns deployments end to end (integrations, agents, evals) and feeds recurring problems back into the product.Source
    • HiringFounding Sales (posted August 26, 2026): owns the full cycle from use cases through technical discovery, demos, evaluations and closing; Sim is "already working with eXp Realty, Rivian, and Volkswagen Group Technologies" and wants to turn existing demand into a repeatable sales process. The team is 10 people, in person in San Francisco.Source
  • 21

    Sim shipped ten changelog entries in October 2026 alone, but the blog's last post was September 19, and there is no newsletter sign-up anywhere on the site. Free users who signed up months ago never hear about the integrations and features that might bring them back.

    Medium impactLow effort First result in 2 weeks Founding Marketing

    First action

    Write the November digest from the October changelog.

    How to measure it

    Dormant users running a workflow after the digest

    Now
    –
    Target
    5% per issue
    By
    3 months

    Steps

    1. 1

      Format

      Three releases, a template, a community build and a tip.

      Founding Marketing 1 day

    2. 2

      Sign-up form

      On the changelog, library and model pages.

      Founding Design Engineer 1 day

    3. 3

      First issue

      From the October releases.

      Founding Marketing 2 days

    4. 4

      Send

      All users, with opt-out.

      Founding Marketing 1 day

    5. 5

      Repost

      As a blog post and on social.

      Founding Marketing 1 day

    6. 6

      Measure

      Clicks to runs.

      Founding Marketing monthly

    First result
    2 weeks
    Cost
    Email tool and a few hours a month
    Owner
    Founding Marketing

    Smallest test

    Send one issue to users inactive for 60 days.

    Why it works

    Send a monthly digest: the three biggest releases, one template built on them, one community build and one cost tip. Add a sign-up form to the changelog, library and model pages, and send it to all users by default, with an easy opt-out.

    Shipping velocity is a selling point only if people see it, and a digest reactivates dormant free accounts at near-zero cost.

    Risks and how to handle them

    • Unsubscribes

      Keep it short and monthly.

    Evidence

    • Your websiteChangelog: ten entries between October 2 and 26, 2026 (new models, Power BI, Intune, Fivetran, "Compare workflow versions before you deploy"); the blog's last post was September 19, 2026; no newsletter sign-up was found on the site.Source
    • HiringFounding Marketing (San Francisco, posted September 24, 2026): "You'll own how people discover, understand, and adopt Sim" through positioning, technical content and demos, launches and channel tests, measured on activation and qualified pipeline rather than attention.Source
  • 22

    The library's roundups rank competitors and put Sim first in the comparison table, at around 10,000 words, but carry no note that Sim wrote them. Readers, and the AI assistants that summarise these pages, may discount vendor roundups that look neutral but aren't labelled.

    Medium impactLow effort First result in 1 month Founding Marketing

    First action

    Add the disclosure line to the article template.

    How to measure it

    Roundup-to-sign-up rate

    Now
    –
    Target
    +20%
    By
    90 days

    Steps

    1. 1

      Template change

      The disclosure line.

      Founding Design Engineer 1 hour

    2. 2

      Verdict boxes

      Top 20 roundups.

      Founding Marketing 1 week

    3. 3

      Method note

      How products were assessed, dated.

      Founding Marketing 1 day

    4. 4

      Trim

      Cut the longest pieces.

      Founding Marketing 2 weeks

    5. 5

      Fact check

      Rivals' claims against their own pages.

      Founding Marketing ongoing

    6. 6

      Measure

      Scroll depth and sign-ups.

      Founding Marketing monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Founding Marketing

    Smallest test

    Add disclosure and a verdict box to five roundups.

    Why it works

    Add a one-line disclosure under each title ("Written by the Sim team; we make one of the products compared"), a 100-word verdict box at the top that says when each rival fits better (the articles already do this deep in the text), and a dated method note. Trim the longest pieces to make them easier to read.

    Openness makes the recommendation more credible, and a short verdict at the top is what readers and AI summaries actually use.

    Risks and how to handle them

    • Disclosure lowers click-through

      Test on half the roundups first.

    Evidence

    • Your websiteLibrary (164 pages): for example "Best Enterprise AI Agent Platforms in 2026" (published August 9, updated November 7, 2026) runs to roughly 9,000-10,000 words, puts Sim first in its comparison table, carries no "published by Sim" note and has no try-it or template link inside the article.Source
    • Your websiteSitemap (919 URLs, read November 9, 2026): /models 407, /integrations 280, /library 164, /comparisons 21, /blog 14 (last post September 19, 2026), /changelog 12, /solutions 6; English only.Source

Big bets 3

Larger plays that can change the trajectory.

  • 07

    n8n alone claims 250k+ developers, and Sim's own comparison page confirms there is no migration tool. The agent harness that builds and runs agents from company context could also read an exported workflow and rebuild it as a Sim workflow.

    High impactHigh effort First result in 1 quarter Software Engineer

    First action

    List the 50 most common n8n nodes from the rebuilds in idea 6.

    How to measure it

    Successful imports a month

    Now
    –
    Target
    1,000
    By
    2 quarters

    Steps

    1. 1

      Collect samples

      Exports from idea 6 rebuilds.

      Forward Deployed Engineer 1 month

    2. 2

      Map nodes

      To blocks and integrations.

      Software Engineer, Agent Harness 1 month

    3. 3

      Harness fallback

      Rebuild unmapped steps from their description.

      Software Engineer, Agent Harness 1 month

    4. 4

      Diff view

      What moved and what needs credentials.

      Founding Design Engineer 2 weeks

    5. 5

      Evals

      Import accuracy on a fixed test set.

      Software Engineer, Agent Harness ongoing

    6. 6

      Launch

      On the comparison pages and in the changelog.

      Founding Marketing 1 week

    7. 7

      Add sources

      Make, then Zapier.

      Software Engineer, Agent Harness 1 quarter

    First result
    1 quarter
    Cost
    One engineer for about two quarters
    Owner
    Software Engineer, Agent Harness

    Smallest test

    Import the ten most common n8n templates and measure the share that run first time.

    Why it works

    Accept n8n JSON first (then Make and Zapier exports), map nodes to Sim blocks and integrations, rebuild with the harness for anything unmapped, and show a diff of what moved and what needs attention. Promote it on every comparison page.

    It turns comparison traffic into switching, and it shows off the harness on a task every evaluator understands.

    Risks and how to handle them

    • Imports run but behave differently

      Run both side by side on sample inputs before cut-over.

    Builds on

    Evidence

    • Your websiteSim vs n8n ("last verified November 2, 2026"): "There is no automated one-click migration tool between n8n and Sim", so workflows must be rebuilt; the page advises choosing n8n for "execution-based pricing with unlimited users on every plan". There are 21 comparison pages in all, including Zapier, Make, Gumloop and Dust.Source
    • Competitor researchRivals' own homepages: n8n, "250k+ developers", "209.9k stars", "500+ native integrations", "Trusted by Fortune 500 companies"; Dust, "3,000+" organisations, "300,000+ agents deployed" and 12 customer logos; Gumloop, "Anyone at a company can build agents with any AI model and any integration, while IT controls access."Source
    • HiringSoftware Engineer, Agent Harness (posted August 26, 2026): the harness is the agent that reasons over a company knowledge graph to build and run agents, with evals built from production traces. A Founding Design Engineer (posted June 2, 2026) is to make "complex agent workflows feel intuitive".Source
  • 18

    Sim's homepage sells governance (permission groups, spend limits, audit records, usage by member), and its pricing calculator already attracts people asking how to control LLM costs. But the only way to see the governance features is a demo. Companies with scattered AI usage rarely know their total spend.

    High impactHigh effort First result in 1 quarter Founding Sales

    First action

    Run the audit by hand for three design partners.

    How to measure it

    Enterprise opportunities from audits

    Now
    –
    Target
    15 a quarter
    By
    2 quarters

    Steps

    1. 1

      Manual pilots

      Three companies.

      Forward Deployed Engineer 1 month

    2. 2

      Define the report

      Spend, savings and recommended limits.

      Founding Sales 1 week

    3. 3

      Build the agent

      As a Sim template on read-only data.

      Software Engineer, Agent Harness 1 month

    4. 4

      Landing page

      Linked from the pricing calculator.

      Founding Marketing 1 week

    5. 5

      Security review

      Read-only scopes and data retention.

      Forward Deployed Engineer 2 weeks

    6. 6

      Follow up

      Sales call on large results.

      Founding Sales ongoing

    7. 7

      Publish anonymised findings

      Feeds idea 19.

      Founding Marketing quarterly

    First result
    1 quarter
    Cost
    About two months of engineering
    Owner
    Founding Sales

    Smallest test

    Offer three manual audits to current free-plan companies.

    Why it works

    Offer a free audit agent: a team connects read-only billing exports or usage logs from its model providers and tools. The agent returns spend by team and model, likely savings from model routing, caching and batching, and the spend limits it would set in Sim. Larger results trigger a sales follow-up.

    It leads with the buyer's problem (cost and control), shows Sim's governance on their own data, and creates a qualified enterprise conversation.

    Risks and how to handle them

    • Companies won't share billing data

      Accept CSV exports and process them in the user's own workspace.

    Builds on

    Evidence

    • Your websiteHomepage: H1 "Build and govern every AI agent in one place"; description "the open-source AI workspace where companies build, distribute, and govern AI agents. 270+ integrations, every major LLM, permission groups, spend limits, and self-hosting." A year earlier the headline was "Workflows for LLMs".Source
    • Your websiteLLM API pricing calculator ("Free tool", 125 models, prices updated November 5, 2026): estimates cost per request, day and month in US dollars from tokens and requests per day (default 2,000 input and 500 output tokens at 1,000 requests a day). It never mentions Sim credits, plans, spend limits or BYOK; its FAQ asks "How do I control LLM costs in an AI agent?"; the only Sim calls to action are the site-wide "Start building" and "Request a demo".Source
    • Your docsCredits, billing and limits: each billable run costs 1 credit ($0.005), and child executions share the parent's base charge; hosted model calls are billed from recorded token usage; with your own provider keys (BYOK) you pay the provider directly and the base run charge still applies; paid usage is capped at the included allowance by default, and "Manage credits" sets a member's cap; a Pro account with 1,000 credits of overage is billed $5 on top of $25.Source
  • 19

    Sim had already processed 10M+ workflows by its Series A, it tracks 173 models, and its logs record model, tokens, cost and duration per block. No one publishes neutral, aggregate data on how agents actually run in production: which models are used for which steps, cost per run, failure points, and how often humans approve.

    High impactMedium effort First result in 1 quarter Founding Marketing

    First action

    Agree the anonymisation rules and five headline questions.

    How to measure it

    New referring domains

    Now
    –
    Target
    100 per report
    By
    2 quarters

    Steps

    1. 1

      Set privacy rules

      Aggregate thresholds and opt-out.

      Founding Sales 1 week

    2. 2

      Pick questions

      Five that builders ask.

      Founding Marketing 2 days

    3. 3

      Query data

      From run logs.

      Software Engineer, Agent Harness 2 weeks

    4. 4

      Write

      Report and charts.

      Founding Marketing 2 weeks

    5. 5

      Design

      Embeddable charts.

      Founding Design Engineer 1 week

    6. 6

      Launch

      Media, community and model pages.

      Founding Marketing 1 week

    7. 7

      Repeat

      Every six months.

      Founding Marketing 6 months

    First result
    1 quarter
    Cost
    About a month of staff time per edition
    Owner
    Founding Marketing

    Smallest test

    Publish one chart on model mix by task.

    Why it works

    Publish an anonymised, aggregated report every six months: model mix by task, median cost per run, which integrations are most automated, common failure points and the effect of caching. Release the charts as embeddable images, feed the numbers into the model pages, and pitch the findings to developer media.

    Original data earns links and citations, including from AI assistants, at a scale 164 library articles can't match. It also positions Sim as the authority on governing agents.

    Risks and how to handle them

    • Customers worry about data use

      Publish the method, aggregate only, and honour opt-outs.

    Evidence

    • Your blogSeries A post (November 12, 2025): $7M led by Standard Capital, with Y Combinator among investors; at the time "60,000+ developers", "100+ companies" in production, "10M+ workflows" processed and 18k GitHub stars.Source
    • Your websiteModels directory: 173 models across 29 providers; "Every model listed in this directory is available in the Agent block." Model-versus-model comparison pages have a "Build with these models" button that links to the homepage, with no model preselected and no mention of credits; the token counter shows each model's input cost but not Sim's plans.Source
    • Your websiteSitemap (919 URLs, read November 9, 2026): /models 407, /integrations 280, /library 164, /comparisons 21, /blog 14 (last post September 19, 2026), /changelog 12, /solutions 6; English only.Source

Wildcards 2

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

  • 15

    Sim's own n8n page tells readers to choose n8n for "execution-based pricing with unlimited users on every plan", while Sim charges $25 or $100 per user. In most companies a few people build agents and many only run or review them.

    Medium impactMedium effort First result in 2 months Founding Sales

    First action

    Count how many paid seats edited nothing last month.

    How to measure it

    Average seats per paid org

    Now
    –
    Target
    +30%
    By
    2 quarters

    Steps

    1. 1

      Analyse seats

      Editors versus runners today.

      Founding Sales 2 days

    2. 2

      Define the seat

      Permissions and price.

      Founding Sales 1 week

    3. 3

      Build the role

      On permission groups.

      Founding Design Engineer 2 weeks

    4. 4

      Pilot

      Five paying teams.

      Founding Sales 1 month

    5. 5

      Publish

      Pricing and the comparison page.

      Founding Marketing 1 week

    6. 6

      Review

      Revenue per org and seat growth.

      Founding Sales monthly

    First result
    2 months
    Cost
    Engineering time; possible seat revenue dilution
    Owner
    Founding Sales

    Smallest test

    Offer run-only seats to five teams by hand.

    Why it works

    Test a run-only seat (use deployed agents and chat, view logs, no editing) at a small fixed price or free on Max, with usage still paid in credits. Update the comparison page once it exists.

    It removes a price objection that Sim itself publishes, and it spreads agents across a company, which is what governance buyers want.

    Risks and how to handle them

    • Builders downgrade to run-only seats

      Keep editing tied to full seats.

    Evidence

    • Your websiteSim vs n8n ("last verified November 2, 2026"): "There is no automated one-click migration tool between n8n and Sim", so workflows must be rebuilt; the page advises choosing n8n for "execution-based pricing with unlimited users on every plan". There are 21 comparison pages in all, including Zapier, Make, Gumloop and Dust.Source
    • Your websitePricing page: Free $0 with 1,000 one-time credits, 1 workspace, 2 concurrent executions and 30-day logs; Pro $25 per user a month with 6,000 credits a month plus 2,000 a week; Max $100 per user a month with 25,000 credits plus 4,000 a week; Enterprise custom. "On Sim Cloud, one credit is worth $0.005." An "Annual -15%" toggle, and no FAQ section.Source
  • 20

    Sim adds new models within days (three in one October changelog entry) and publishes model and comparison pages. But a new model is a reason for existing users to come back, and nothing tells them which of their agents could use it.

    Medium impactMedium effort First result in 1 month Founding Marketing

    First action

    Write the launch-day checklist and segment for the next model release.

    How to measure it

    Users running a comparison within 7 days of a launch

    Now
    –
    Target
    10% of actives
    By
    2 quarters

    Steps

    1. 1

      Checklist

      Model page, changelog and email on day one.

      Founding Marketing 1 day

    2. 2

      Segment

      Agents using the predecessor model.

      Software Engineer, Agent Harness 3 days

    3. 3

      Replay test

      Last 20 inputs on both models.

      Software Engineer, Agent Harness 2 weeks

    4. 4

      One-click switch

      With version history.

      Founding Design Engineer 1 week

    5. 5

      Launch

      On the next model release.

      Founding Marketing 1 day

    6. 6

      Measure

      Reactivation and switches.

      Founding Marketing per launch

    First result
    1 month
    Cost
    About three engineering weeks, plus replay credits
    Owner
    Founding Marketing

    Smallest test

    Send a plain launch-day email to users of the predecessor model.

    Why it works

    When a model ships, email and notify users whose agents use the previous model from that provider. Offer "Run your last 20 inputs on the new model" as a side-by-side test showing quality, cost and speed, and switch with one click. Publish the model page and changelog the same day.

    It turns industry news into a reason to log in and gives users evidence before they switch. It also shows off multi-model support, which competitors with fewer models can't match.

    Risks and how to handle them

    • Replays cost users credits

      Cover replay credits for the first 20 inputs.

    Builds on

    Evidence

    • Your websiteChangelog: ten entries between October 2 and 26, 2026 (new models, Power BI, Intune, Fivetran, "Compare workflow versions before you deploy"); the blog's last post was September 19, 2026; no newsletter sign-up was found on the site.Source
    • Your websiteModels directory: 173 models across 29 providers; "Every model listed in this directory is available in the Agent block." Model-versus-model comparison pages have a "Build with these models" button that links to the homepage, with no model preselected and no mention of credits; the token counter shows each model's input cost but not Sim's plans.Source
More example playbooks and reviews

More growth playbooks

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

  • One Acre Fund growth strategyA nonprofit social enterprise that supplies smallholder farmers in sub-Saharan Africa with quality seed and farm supplies on credit…20 growth ideas
  • Stream growth strategyAPIs and SDKs for in-app chat, video and audio, activity feeds and AI moderation, plus Vision Agents for real-time voice and video AI.21 growth ideas
  • Roku growth strategyThe TV streaming platform behind Roku TVs and players, with The Roku Channel, Howdy, Premium Subscriptions, smart home products and a…21 growth ideas
  • Lance growth strategyCollaborative AI for hotels: an AI front desk that answers guest calls 24/7, guest messaging, an AI sales agent for group and event…23 growth ideas
  • Juno Veterinary growth strategyFounder-owned, design-led veterinary clinics offering primary, urgent and surgical care for dogs and cats, plus 24/7 Virtual Care by…22 growth ideas
  • TryNearby growth strategyA done-for-you local creator service for restaurants. Every month it sends a new group of vetted nearby food creators to visit, film, edit…22 growth ideas
  • Faraday Future growth strategyAn AI electric vehicle and embodied-AI robotics company: humanoid robots (FF Futurist, FF Master), quadruped and wheeled robots (FX…22 growth ideas
  • Trustpilot growth strategyThe world's largest open customer review platform; businesses claim profiles for free and pay for invitations, widgets, analytics, AI…21 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. Sim did not commission, review or endorse it, and Programmable is not affiliated with Sim. 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 Sim runs its business.

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

    Connect the free tools and pages to Sim: calculator to credits and plan, model pages to a preselected agent, solution buttons and library articles to templates, a credits FAQ, and assisted n8n moves.

  2. Days 31 to 6011 ideas

    Proof, activation and speed: measured customer stories, current numbers, a path from self-host to Enterprise, run comparison, template intent through sign-up, Core Web Vitals, a community template gallery, integration partners, demo routing, a monthly digest and library trust.

  3. Days 61 to 905 ideas

    Commit to the bets: a workflow importer, a free AI spend audit, the production-agents report, launch-day model swaps and a run-only seat test.

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 A visual canvas that makes complex agent workflows understandable. The most cited problem: young docs and edge cases.

  • Open source under Apache 2.0, with self-hosting
  • Debugging failed runs through dense logs
  • In their words: “agent workflows”

Market

Competitive landscape

4 competitors compared: n8n, Dust, Gumloop and Zapier and Make.

  • Gap to exploit: Cost certainty for agents that call many models
  • n8n: Not Apache 2.0
  • Dust: Not open source or self-hostable

Hiring signals

Sim is a 10-person team in San Francisco making its first go-to-market hires.

  • Founding Marketing: Owns discovery and adoption, measured on activation. Ideas 1-4, 12.
  • Founding Sales: A repeatable sales process from existing enterprise demand. Ideas 8, 10, 17, 18.
  • Forward Deployed Engineer: Customer workflows into production agents. Ideas 6, 17.

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