ProgrammableMarketing/workos.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 · 9
  • Big bets · 3
  • Wildcards · 3
  • How we can help
Generated Oct 21, 2026
  1. Programmable
  2. Playbooks
  3. WorkOS
WorkOS logo

growth playbook · Oct 21, 2026

workos.com (opens in a new tab)

WorkOS growth playbook

Diagnosis

WorkOS has a strong developer-led motion, a $100M Series C at a $2B valuation, and customers across the AI industry, and its 29 open roles show it adding a lean sales layer on top: AEs with no formal segmentation, a BDR using AI research, an Account Manager for multi-product expansion, a Growth PM for the product-qualified lead motion, a GTM Engineer running enrichment, and an events-led DevRel and growth team in San Francisco.

Its pricing tells sales where to look: money starts when a customer's own customer turns on SSO, at $125 a connection. The site has small gaps a careful buyer notices: no H1 or description on pricing, three logo labels that are file names, 21 stories for 181 logos, duplicated "alternatives" posts and off-category comparisons, and an F for security headers.

This playbook makes the first SSO connection the sales signal, cleans the proof, measures the agent-led channel, segments by connection count and builds toward an open agent identity standard.

Growth Score

8/10

Biggest Opportunity

The first SSO connection is a precise, product-visible signal that a customer has begun selling to enterprises; building the sales motion around it fits WorkOS's pricing and its bottom-up model.

Biggest Risk

Every major identity vendor now claims agentic identity, and bulk-made comparison content plus thin proof for the biggest logos make WorkOS easier to dismiss as one more option.

01

Start here

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

  1. 1

    Treat a customer's first SSO connection as the sales signal

    Pull the accounts that created a first connection in the last 90 days and see how many an AE ever talked to.

    High impact First result in 2 weeks
  2. 2

    Give the pricing page a heading, a description and calculator text that makes sense without JavaScript

    Check what three AI assistants say WorkOS costs for 10 SSO connections.

    Medium impact First result in 1 day
  3. 3

    Fix the three logo labels that read as file names

    Edit the three labels in Webflow.

    Low impact First result in 1 day

02

Your idea portfolio

21 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 · 2Big bets · 8Fill-ins · 6Reconsider · 5
Effort →

Showing 21 of 21 ideas

This week 6

Quick wins with a clear first action.

  • 01

    WorkOS sells bottom-up and has no formal sales segmentation, and a Growth PM is to strengthen the product-qualified lead motion. The pricing makes the right signal obvious: AuthKit is free to a million users, and money starts when a customer's own enterprise customer turns on SSO or Directory Sync at $125 a connection. The first connection is the moment that customer starts selling to enterprises.

    High impactLow effort First result in 2 weeks PM

    First action

    Pull the accounts that created a first connection in the last 90 days and see how many an AE ever talked to.

    How to measure it

    First-connection accounts reaching 5+ connections within 6 months

    Now
    –
    Target
    30%
    By
    2 quarters

    Steps

    1. 1

      Size the signal

      First connections per month over the last year, and how many grew past five.

      PM, Growth 1 day

    2. 2

      Add the trigger

      First SSO or Directory Sync connection fires an event to the pipeline.

      GTM Engineer 2 days

    3. 3

      Enrich and route

      Score the account and assign an AE within one business day.

      GTM Engineer 2 days

    4. 4

      Write the offer

      The 20-minute enterprise checklist review and a follow-up email.

      Account Executives 1 day

    5. 5

      Run it

      AEs contact every routed account.

      Account Executives ongoing

    6. 6

      Compare cohorts

      Connection growth for contacted vs. uncontacted accounts.

      PM, Growth monthly

    First result
    2 weeks
    Cost
    $0 (internal time)
    Owner
    PM, Growth

    Smallest test

    Run the trigger by hand for one month of first connections and compare their growth with the previous month.

    Run this outreach. The sequence sent for you: addresses found and verified, replies routed to your CRM. Usually live within days.

    Book a working session

    Why it works

    When an account creates its first SSO or Directory Sync connection, the GTM Engineer's pipeline enriches it and routes it to an AE within one business day with context: the account's product, the identity provider their customer uses, and how many organisations they have. The AE's offer is practical: a 20-minute review of the enterprise checklist their next deals will ask for (SCIM, audit logs, admin portal, custom domain).

    A company that has just closed its first enterprise customer will close more, and each one is another connection. Reaching it at that moment, with help rather than a pitch, sets up the expansion the Account Manager is hired to run.

    Ready to use

    EmailFirst connection email

    Subject: Your first enterprise SSO connection is live
    
    Hi {first_name},
    
    I saw {company} just connected its first customer through {idp}. Congratulations on the enterprise deal.
    
    The next enterprise buyers usually ask for the same few things: user provisioning (SCIM), audit logs, an admin portal for their IT team and your own domain on the login page. If it helps, I can walk your team through that list in 20 minutes and point out what is already switched on.
    
    Pick a time here: {calendar_link}
    
    {ae_name}, WorkOS

    Risks and how to handle them

    • Developers dislike sales contact

      Lead with the checklist review and let the developer choose a time; no calls without consent.

    • Too many small accounts

      Route by fit score and send the rest an automated checklist email.

    Evidence

    • HiringSales - Account Executive (San Francisco): "WorkOS has a strong bottoms-up, developer-focused GTM motion, and we're growing our lean sales team to complement it"; AEs from 2 to 10 years' experience; "We don't have formal sales segmentation: customer coverage is fluid"; AEs are to "test outreach, messaging, and sales approaches" and "help develop repeatable practices".Source
    • HiringProduct Manager - Growth: own "activation, adoption, monetization, expansion, and retention across the platform", "build and scale a product experimentation program", "improve onboarding and reduce time-to-value", "work with Marketing to improve acquisition and attribution" and "partner with Sales to strengthen the product-qualified lead motion and enterprise expansion path".Source
    • Your websitePricing: AuthKit is free up to 1 million users, then $2,500 a month per additional million; Single Sign-On and Directory Sync are $125 per connection per month for 1-15 connections, falling to $65 at 51-100; Radar is free for 1,000 checks, then $100 per 50,000; a custom domain is $99 a month; annual credits add discounts and migration help. The page has no H1 heading and no meta description, and its server-rendered calculator text reads "$0 / month vs $100 to build it yourself".Source
    • HiringGTM Engineer: maintain "our core enrichment pipeline: the workflows that take a new signup or a conference attendee list and return a fully enriched, scored, and Salesforce-upserted record", built on Cargo, Clay, Snowflake, Apollo, Linkup and Exa; own fit scoring.Source
  • 02

    The pricing page has no H1 and no meta description, and its server-rendered calculator text reads "$0 / month vs $100 to build it yourself". That is what search engines and AI assistants read when someone asks what WorkOS costs.

    Medium impactLow effort First result in 1 day Web team

    First action

    Check what three AI assistants say WorkOS costs for 10 SSO connections.

    How to measure it

    Correct answers to five pricing questions

    Now
    –
    Target
    5 of 5
    By
    1 quarter

    Steps

    1. 1

      Test the answers

      Five pricing questions in three assistants.

      PM, Growth 1 hour

    2. 2

      Add the H1

      One heading on the page.

      Web team 15 minutes

    3. 3

      Write the description

      Free to 1M users; $125 per connection.

      Marketing 15 minutes

    4. 4

      Fix the default

      Render a 10-connection example server-side.

      Web team 2 hours

    5. 5

      Repeat on key pages

      Homepage, compare and switch descriptions.

      Web team 1 hour

    6. 6

      Retest

      Same questions a month later.

      PM, Growth 1 hour

    First result
    1 day
    Cost
    $0
    Owner
    Web team

    Smallest test

    Fix the pricing page alone and recheck the assistants in a month.

    Why it works

    Add an H1 ("WorkOS pricing"), a meta description that states the free tier and the per-connection price, and server-render a real example (for example 10 SSO connections) so the static text shows a sensible monthly figure and build-it-yourself estimate.

    Pricing questions are high intent. A page that reads correctly to machines gets quoted correctly in AI answers and search snippets.

    Risks and how to handle them

    • Example misread as a quote

      Label it as an example with the inputs shown.

    Evidence

    • Your websitePricing: AuthKit is free up to 1 million users, then $2,500 a month per additional million; Single Sign-On and Directory Sync are $125 per connection per month for 1-15 connections, falling to $65 at 51-100; Radar is free for 1,000 checks, then $100 per 50,000; a custom domain is $99 a month; annual credits add discounts and migration help. The page has no H1 heading and no meta description, and its server-rendered calculator text reads "$0 / month vs $100 to build it yourself".Source
    • Your websiteThe homepage, /pricing, /compare/auth0 and /switch serve no meta description. The homepage announces launches from WorkOS's init() event: Passport, Atlas ("your AI coworker") and Airlock ("Intent-Based Access Control"), alongside auth.md ("User registration for agents") and MCP Auth.Source
  • 03

    The customers page is WorkOS's strongest proof: 181 logos from OpenAI to Snowflake. Three of the hidden labels screen readers and AI tools read are file names, such as "68f7b8469a33c174c66b5f42_physical intelligence" and "Privy_Brandmark_Black".

    Low impactLow effort First result in 1 day Web team

    First action

    Edit the three labels in Webflow.

    How to measure it

    Logos with correct labels

    Now
    –
    Target
    181 of 181
    By
    1 week

    Steps

    1. 1

      Edit the three

      Physical Intelligence, Privy, Increase.

      Web team 15 minutes

    2. 2

      Audit the rest

      Scan all labels for file-name patterns.

      Web team 15 minutes

    3. 3

      Add alt text

      Company name on each image.

      Web team 30 minutes

    4. 4

      Add a check

      Publishing checklist rule for logo labels.

      Web team 15 minutes

    5. 5

      Confirm

      Read the page with a screen reader.

      Web team 15 minutes

    6. 6

      Repeat yearly

      Part of the site audit.

      Web team 15 minutes a year

    First result
    1 day
    Cost
    $0
    Owner
    Web team

    Smallest test

    Fix the three labels and confirm with a screen reader.

    Why it works

    Replace the three labels with the company names, add a check to the Webflow publishing step that rejects logo labels containing underscores, hashes or email addresses, and give every logo alt text with the company name.

    Small errors on a proof page are what a careful buyer notices. Clean labels also let AI assistants list WorkOS customers correctly.

    Risks and how to handle them

    • None meaningful

      It is a quick fix.

    Evidence

    • Your websiteCustomers page: 181 logos, from OpenAI, Anthropic, Cursor, Sierra and Plaid to Snowflake and Vanta, including app-building platforms such as Replit, Bolt and Convex. Three screen-reader labels are file names ("68f7b8469a33c174c66b5f42_physical intelligence", "Privy_Brandmark_Black", "[email removed]"). There are 21 written customer stories (AI21 Labs, Cerkl, Chromatic, Copy.ai, Drata, EnjoyHQ, Gretel, Hopin, Hypercare, incident.io, Indeed, Magical, Netlify, OpenAI, Patch, Perplexity, PlanetScale, Prefect, Tactic, Warp, Webflow); none for Anthropic, Cursor, Sierra or Plaid.Source
  • 04

    WorkOS has 12 "alternatives" posts, including both "auth0-alternatives" and "auth0-alternatives-2025", and "the-5-best-clerk-alternatives-in-2024" next to "clerk-alternatives". Two pages on the same question compete with each other, and a dated title looks stale to readers and search engines.

    Medium impactLow effort First result in 1 week Content lead

    First action

    List the duplicate pairs and their search traffic.

    How to measure it

    Organic visits to the merged pages

    Now
    –
    Target
    +25%
    By
    1 quarter

    Steps

    1. 1

      Find duplicates

      Pairs answering the same question.

      Content lead 2 hours

    2. 2

      Pick the keeper

      The one with more traffic and links.

      Content lead 1 hour

    3. 3

      Merge content

      Best sections into the keeper.

      Content lead 1 day

    4. 4

      Redirect

      Permanent redirects from the others.

      Web team 1 hour

    5. 5

      Drop years from URLs

      Show a review date instead.

      Web team 1 hour

    6. 6

      Set reviews

      Quarterly review of each page.

      Content lead ongoing

    First result
    1 week
    Cost
    $0
    Owner
    Content lead

    Smallest test

    Merge the Auth0 pair first and track its traffic for a month.

    Why it works

    Keep one evergreen page per competitor, merge the best content from the duplicates into it, redirect the others, remove years from the URLs, and show a "last reviewed" date on the page instead.

    One strong page ranks better than two weak ones, and a review date keeps it fresh without new URLs.

    Risks and how to handle them

    • Temporary ranking dip

      Redirects carry signals over; monitor for a month.

    Evidence

    • Your websiteComparison content: three /compare pages (Auth0, Clerk, Frontegg); 37 blog posts titled "<tool> vs WorkOS", many about tools in other categories (Semgrep, Snyk, Promptfoo, HiddenLayer, Google Vertex AI, OpenAI, Nightfall AI); and 12 "alternatives" posts, including both "auth0-alternatives" and "auth0-alternatives-2025", and "the-5-best-clerk-alternatives-in-2024" next to "clerk-alternatives".Source
    • Your websiteSitemaps: 1,504 website URLs (1,022 blog posts, 301 changelog entries, 84 guide pages, 32 podcast episodes) plus 845 docs pages. Between 50 and 119 website URLs were last modified in each month of 2026.Source
  • 05

    WorkOS sells identity and security to companies whose own customers run security reviews. Its marketing site sends no Strict-Transport-Security, X-Content-Type-Options or Referrer-Policy header, and Mozilla Observatory grades it F.

    Medium impactLow effort First result in 1 week Security team

    First action

    Run the Mozilla Observatory scan and list the missing headers.

    How to measure it

    Observatory grade

    Now
    –
    Target
    A
    By
    2 weeks

    Steps

    1. 1

      Scan

      Record the current findings.

      Security team 15 minutes

    2. 2

      Draft headers

      HSTS, nosniff, referrer, permissions, CSP.

      Security team 2 hours

    3. 3

      Test on staging

      Check Webflow scripts and HubSpot forms still work.

      Web team 1 day

    4. 4

      Deploy

      Through Cloudflare rules.

      Security team 1 hour

    5. 5

      Rescan

      Confirm the grade.

      Security team 15 minutes

    6. 6

      Monitor

      Monthly scan in the security checklist.

      Security team 15 minutes a month

    First result
    1 week
    Cost
    $0
    Owner
    Security team

    Smallest test

    Add HSTS and nosniff first and rescan.

    Why it works

    Add HSTS, X-Content-Type-Options, Referrer-Policy, a Permissions-Policy and a fuller Content-Security-Policy through Cloudflare, test them on staging, and rerun the scan. Add the grade to the trust center.

    Security reviewers and prospects run these scans in seconds. For an identity vendor, an F on its own homepage is an easy objection to remove.

    Risks and how to handle them

    • A strict CSP breaks scripts

      Start in report-only mode and tighten over two weeks.

    Evidence

    • Your websiteworkos.com responses carry only a frame-ancestors Content-Security-Policy and X-Frame-Options; there is no Strict-Transport-Security, X-Content-Type-Options or Referrer-Policy header. programmable.info reports a Mozilla Observatory grade of F (5/100).Source
    • programmable.infoWebflow site with HubSpot and Google Tag Manager; mobile LCP 1.45s and 11% faster than a year ago; DMARC "reject"; YouTube 6,570 subscribers and 352 videos; the authkit GitHub repo has 3,353 stars; the workos PyPI package is at 10.5.0; 75 Hacker News mentions. Its leadership scrape returned a job title as the CEO's name, and its "notable customers" are identity providers (Okta, Azure, OneLogin).Source
    • HiringEvery post opens with the same paragraph: "a $100M Series C, valuing the company at $2B", customers "including OpenAI, Cursor, and Perplexity, Sierra, and Plaid", the question "who are your agents, and what are they allowed to do?", and "hundreds of modern software companies". All 29 open roles are in San Francisco or "United States & Canada".Source
  • 06

    WorkOS runs developer events, dinners and conferences, and its GTM Engineer maintains a pipeline that already turns "a conference attendee list" into scored Salesforce records. The value of an event fades within days if follow-up waits for a manual list.

    High impactLow effort First result in 2 weeks Growth Marketing Generalist

    First action

    Time how long the last three events took from attendee list to first follow-up.

    How to measure it

    Median hours from event end to first follow-up

    Now
    –
    Target
    24
    By
    1 quarter

    Steps

    1. 1

      Measure today

      Last three events, list to follow-up time.

      Growth Marketing Generalist 1 hour

    2. 2

      Automate the load

      Attendee list into the pipeline the same night.

      GTM Engineer 2 days

    3. 3

      Add notes

      Check-in and session data on each record.

      Growth Marketing Generalist 1 day

    4. 4

      Assign high-fit

      AE or BDR task by morning.

      GTM Engineer 1 day

    5. 5

      Send the rest

      Talk recording and guide email.

      Growth Marketing Generalist 1 day

    6. 6

      Report

      Meetings per event within two weeks.

      Growth lead per event

    First result
    2 weeks
    Cost
    $0
    Owner
    Growth Marketing Generalist

    Smallest test

    Run the next event with same-night enrichment and compare meetings booked with the last one.

    Why it works

    Make the pipeline run the night of each event: attendees enriched and scored, high-fit accounts assigned to an AE or BDR with a short note of what they asked or attended, and everyone else sent a useful follow-up (the talk, the slides, a relevant guide) the next morning.

    Fast, relevant follow-up is the difference between an event that produces pipeline and one that produces photos.

    Risks and how to handle them

    • Follow-up feels automated

      Personal note from the person they met for high-fit accounts.

    Evidence

    • HiringGTM Engineer: maintain "our core enrichment pipeline: the workflows that take a new signup or a conference attendee list and return a fully enriched, scored, and Salesforce-upserted record", built on Cargo, Clay, Snowflake, Apollo, Linkup and Exa; own fit scoring.Source
    • HiringDeveloper Relations (San Francisco): "an events-forward DevRel leader" to run meetups, panels and workshops and "support talent and pipeline generation"; Growth Marketing Generalist: developer events, conferences and dinners, newsletter sponsorships and campaign copy, working with the Growth lead.Source
    • HiringBusiness Development Representative: outbound into enterprise and mid-market; "use LLMs and AI tooling to research accounts, personalize outreach at scale"; "understand what a company is actually building — their stack, their auth setup, their scaling problems".Source

This quarter 9

The core plays for the next three months.

  • 07

    WorkOS shows 181 logos but only 21 written stories, and the names its own job posts lead with (Cursor, Sierra, Plaid) and Anthropic have none. Stories like Hopin and EnjoyHQ carry the proof instead.

    High impactMedium effort First result in 1 quarter Account Manager

    First action

    Ask the four account owners which customer contact would agree to a 20-minute interview.

    How to measure it

    Opportunities where a new story was shared

    Now
    –
    Target
    40
    By
    2 quarters

    Steps

    1. 1

      Pick the accounts

      Four large AI logos with an engaged contact.

      Account Manager 1 week

    2. 2

      Interview

      20 minutes each with an engineering lead.

      Content lead 3 weeks

    3. 3

      Get one number

      Time saved or enterprise customers onboarded.

      Account Manager 2 weeks

    4. 4

      Write and approve

      Short format, customer approval.

      Content lead 3 weeks

    5. 5

      Publish

      On /customers with a quote on the homepage.

      Web team 1 week

    6. 6

      Enable

      Sales email templates using each story.

      Account Executives 1 day

    First result
    1 quarter
    Cost
    $0
    Owner
    Account Manager

    Smallest test

    Interview one engineering lead and publish a quote-length version.

    Why it works

    Ask the Account Manager's top accounts for short stories built around one question each buyer has: how long SSO and SCIM took to ship, how many enterprise customers were onboarded through the Admin Portal, and what the team stopped building. Publish four this quarter.

    An AI company evaluating auth trusts what Cursor or Anthropic did more than a feature list. Stories also give the AEs and BDRs reasons to reach out.

    Risks and how to handle them

    • Large customers rarely approve stories

      Offer a quote-only format or a joint engineering blog post.

    Evidence

    • Your websiteCustomers page: 181 logos, from OpenAI, Anthropic, Cursor, Sierra and Plaid to Snowflake and Vanta, including app-building platforms such as Replit, Bolt and Convex. Three screen-reader labels are file names ("68f7b8469a33c174c66b5f42_physical intelligence", "Privy_Brandmark_Black", "[email removed]"). There are 21 written customer stories (AI21 Labs, Cerkl, Chromatic, Copy.ai, Drata, EnjoyHQ, Gretel, Hopin, Hypercare, incident.io, Indeed, Magical, Netlify, OpenAI, Patch, Perplexity, PlanetScale, Prefect, Tactic, Warp, Webflow); none for Anthropic, Cursor, Sierra or Plaid.Source
    • HiringEvery post opens with the same paragraph: "a $100M Series C, valuing the company at $2B", customers "including OpenAI, Cursor, and Perplexity, Sierra, and Plaid", the question "who are your agents, and what are they allowed to do?", and "hundreds of modern software companies". All 29 open roles are in San Francisco or "United States & Canada".Source
    • HiringAccount Manager: own "the expansion of our most complex accounts"; "identify unadopted products and untapped teams"; "drive adoption of the full WorkOS platform — SSO, Directory Sync, AuthKit, Audit Logs, and beyond — across new teams, new products, and new geographies"; run executive business reviews.Source
  • 08

    WorkOS says "increasingly their agents do it for them" and ships an AI installer CLI, MCP servers and agent skills. If those installs are counted as ordinary sign-ups, nobody can see whether the channel is growing or where agent-led setups get stuck.

    High impactMedium effort First result in 6 weeks PM

    First action

    Add a source tag to accounts created through the AI installer CLI.

    How to measure it

    Agent-led accounts with a working sign-in in 24 hours

    Now
    –
    Target
    70%
    By
    2 quarters

    Steps

    1. 1

      Tag the sources

      CLI, MCP server, agent skills.

      Developer & Agent Experience team 1 week

    2. 2

      Define the funnel

      Install to first connection.

      PM, Growth 2 days

    3. 3

      Build the dashboard

      Agent vs. human funnel.

      Data Engineer 1 week

    4. 4

      Find the drop

      Steepest step for agent-led accounts.

      PM, Growth 1 week

    5. 5

      Fix it

      Docs, skill or CLI change.

      Developer & Agent Experience team 1 month

    6. 6

      Run evals

      Agent integration success on test projects.

      Developer & Agent Experience team monthly

    First result
    6 weeks
    Cost
    $0
    Owner
    PM, Growth

    Smallest test

    Tag CLI installs for one month and compare their activation with web sign-ups.

    Why it works

    Tag every account created or configured through the CLI, MCP server or an agent skill, and track its own funnel: install, first sign-in working, first organisation, first SSO connection. Review it monthly alongside the human funnel and fix the steepest drop.

    A channel that is measured gets improved. The agent funnel may already be a large share of new accounts and could become the cheapest one.

    Risks and how to handle them

    • Attribution is fuzzy for agents

      Tag what can be seen (CLI, MCP) and survey new accounts for the rest.

    Evidence

    • HiringDeveloper & Agent Experience Engineer: "Developers still integrate WorkOS, but increasingly their agents do it for them." The team owns "SDKs in 9 languages, now generated from our API spec; an AI installer CLI that sets up AuthKit in any project; our MCP servers and agent skills", and writes evaluations "to measure whether what you ship actually improves developer outcomes".Source
    • HiringProduct Manager - Growth: own "activation, adoption, monetization, expansion, and retention across the platform", "build and scale a product experimentation program", "improve onboarding and reduce time-to-value", "work with Marketing to improve acquisition and attribution" and "partner with Sales to strengthen the product-qualified lead motion and enterprise expansion path".Source
    • Your websiteThe homepage, /pricing, /compare/auth0 and /switch serve no meta description. The homepage announces launches from WorkOS's init() event: Passport, Atlas ("your AI coworker") and Airlock ("Intent-Based Access Control"), alongside auth.md ("User registration for agents") and MCP Auth.Source
  • 09

    AEs are told there is "no formal sales segmentation", and customers range from AI startups to large enterprises. Company size is a poor guide for WorkOS, because a small AI company with 40 enterprise customers pays more than a large company with two.

    High impactMedium effort First result in 1 month Head of Sales

    First action

    Pull revenue by account against connection count and company size.

    How to measure it

    Accounts above 5 connections with a named owner

    Now
    –
    Target
    100%
    By
    1 quarter

    Steps

    1. 1

      Analyse revenue

      By connections and by headcount.

      Data Engineer 1 week

    2. 2

      Set the tiers

      Three bands with thresholds.

      Head of Sales 2 days

    3. 3

      Assign owners

      Accounts to AE or AM.

      Head of Sales 1 week

    4. 4

      Automate re-scoring

      Monthly from billing.

      GTM Engineer 1 week

    5. 5

      Write plays per tier

      What each owner does.

      Account Executives 1 week

    6. 6

      Review

      Quarterly threshold check.

      Head of Sales 1 day a quarter

    First result
    1 month
    Cost
    $0
    Owner
    Head of Sales

    Smallest test

    Assign owners to the top 50 accounts by connection count and compare expansion after a quarter.

    Why it works

    Define coverage by the number and growth of connections: under five stays product-led with automated help, five to 30 goes to AEs, above 30 or growing fast goes to the Account Manager. Re-score monthly from billing data.

    Revenue follows connections. Aligning people to the measure the price is built on puts sellers where the money and the expansion are.

    Risks and how to handle them

    • Fast-growing small accounts missed

      Add a growth trigger (three new connections in a month).

    Evidence

    • HiringSales - Account Executive (San Francisco): "WorkOS has a strong bottoms-up, developer-focused GTM motion, and we're growing our lean sales team to complement it"; AEs from 2 to 10 years' experience; "We don't have formal sales segmentation: customer coverage is fluid"; AEs are to "test outreach, messaging, and sales approaches" and "help develop repeatable practices".Source
    • Your websitePricing: AuthKit is free up to 1 million users, then $2,500 a month per additional million; Single Sign-On and Directory Sync are $125 per connection per month for 1-15 connections, falling to $65 at 51-100; Radar is free for 1,000 checks, then $100 per 50,000; a custom domain is $99 a month; annual credits add discounts and migration help. The page has no H1 heading and no meta description, and its server-rendered calculator text reads "$0 / month vs $100 to build it yourself".Source
    • HiringAccount Manager: own "the expansion of our most complex accounts"; "identify unadopted products and untapped teams"; "drive adoption of the full WorkOS platform — SSO, Directory Sync, AuthKit, Audit Logs, and beyond — across new teams, new products, and new geographies"; run executive business reviews.Source
  • 10

    The Account Manager is to "identify unadopted products and untapped teams" across SSO, Directory Sync, AuthKit and Audit Logs. Many enterprise buyers ask for provisioning and audit logs soon after SSO.

    High impactMedium effort First result in 1 quarter Account Manager

    First action

    Count SSO accounts that use none of the other products.

    How to measure it

    SSO accounts adding a second product

    Now
    –
    Target
    25%
    By
    2 quarters

    Steps

    1. 1

      Build the list

      SSO-only accounts by size.

      Data Engineer 2 days

    2. 2

      Add the evidence

      Their organisations' identity providers that support SCIM.

      Data Engineer 1 week

    3. 3

      Write the play

      Email, setup session, annual-credit bundle.

      Account Manager 1 week

    4. 4

      Run it

      Top 50 accounts.

      Account Manager 1 quarter

    5. 5

      Add Radar

      Accounts with high sign-up volume.

      Account Manager 1 month

    6. 6

      Measure

      Adds per product.

      Data Engineer monthly

    First result
    1 quarter
    Cost
    $0
    Owner
    Account Manager

    Smallest test

    Run the play on 20 SSO-only accounts.

    Why it works

    List accounts with SSO connections but no Directory Sync, Audit Logs or Radar, and run a play: show the account how many of its enterprise organisations already use SCIM-capable identity providers, offer a setup session, and price the bundle on annual credits.

    Each extra product attaches to the same enterprise customers, so the upsell sells itself when the data shows those customers are ready.

    Risks and how to handle them

    • Discounting erodes price

      Bundle on annual credits rather than cutting list prices.

    Evidence

    • HiringAccount Manager: own "the expansion of our most complex accounts"; "identify unadopted products and untapped teams"; "drive adoption of the full WorkOS platform — SSO, Directory Sync, AuthKit, Audit Logs, and beyond — across new teams, new products, and new geographies"; run executive business reviews.Source
    • Your websitePricing: AuthKit is free up to 1 million users, then $2,500 a month per additional million; Single Sign-On and Directory Sync are $125 per connection per month for 1-15 connections, falling to $65 at 51-100; Radar is free for 1,000 checks, then $100 per 50,000; a custom domain is $99 a month; annual credits add discounts and migration help. The page has no H1 heading and no meta description, and its server-rendered calculator text reads "$0 / month vs $100 to build it yourself".Source
    • HiringProduct Engineer - Radar: a "real-time identity intelligence layer" for bots, fraud and abuse; "Radar serves some of the fastest-growing AI companies in the world, which gives us one of the richest fraud-and-abuse datasets in the identity space"; work measured "often in the millions of dollars of fraud and abuse we save customers".Source
  • 11

    The Radar team says it has "one of the richest fraud-and-abuse datasets in the identity space" because it serves many fast-growing AI companies, and its work saves customers "millions of dollars". AI apps with free tiers are targets for fake sign-ups and abuse.

    High impactMedium effort First result in 1 quarter Radar team

    First action

    Pick five aggregate numbers Radar can publish without identifying any customer.

    How to measure it

    Radar opportunities from report readers

    Now
    –
    Target
    30
    By
    2 quarters

    Steps

    1. 1

      Pick metrics

      Five aggregates with privacy review.

      Radar team 1 week

    2. 2

      Privacy review

      No customer identifiable.

      Legal 2 weeks

    3. 3

      Write the report

      Findings and defences.

      Content lead 3 weeks

    4. 4

      Launch

      Webinar, post, social.

      Growth lead 2 weeks

    5. 5

      Route readers

      Downloads at target accounts to AEs.

      GTM Engineer 1 day

    6. 6

      Repeat

      Every six months.

      Radar team ongoing

    First result
    1 quarter
    Cost
    $5k
    Owner
    Radar team

    Smallest test

    Publish one chart (bot share of sign-ups after a launch) as a blog post.

    Why it works

    A twice-yearly report with aggregated, anonymised findings: the share of sign-ups blocked as bots, the most common abuse patterns against AI free tiers, how attacks change after a launch, and what defences work. Release it with a webinar and a short checklist.

    Original data earns attention from engineering and security leaders, and it introduces Radar to AI companies that use WorkOS only for SSO.

    Risks and how to handle them

    • Helps attackers

      Publish patterns and defences in aggregate, not detection rules.

    Evidence

    • HiringProduct Engineer - Radar: a "real-time identity intelligence layer" for bots, fraud and abuse; "Radar serves some of the fastest-growing AI companies in the world, which gives us one of the richest fraud-and-abuse datasets in the identity space"; work measured "often in the millions of dollars of fraud and abuse we save customers".Source
    • HiringEvery post opens with the same paragraph: "a $100M Series C, valuing the company at $2B", customers "including OpenAI, Cursor, and Perplexity, Sierra, and Plaid", the question "who are your agents, and what are they allowed to do?", and "hundreds of modern software companies". All 29 open roles are in San Francisco or "United States & Canada".Source
    • Your websitePricing: AuthKit is free up to 1 million users, then $2,500 a month per additional million; Single Sign-On and Directory Sync are $125 per connection per month for 1-15 connections, falling to $65 at 51-100; Radar is free for 1,000 checks, then $100 per 50,000; a custom domain is $99 a month; annual credits add discounts and migration help. The page has no H1 heading and no meta description, and its server-rendered calculator text reads "$0 / month vs $100 to build it yourself".Source
  • 12

    Only Auth0, Clerk and Frontegg have /compare pages. Meanwhile 37 blog posts are titled "<tool> vs WorkOS", many about tools that are not identity products (Semgrep, Snyk, Promptfoo, Google Vertex AI). Readers comparing Stytch or Descope get a blog post; readers searching Semgrep find a comparison that does not make sense.

    Medium impactMedium effort First result in 2 months Content lead

    First action

    Rank competitors by how often they appear in won and lost deals.

    How to measure it

    Monthly sign-ups from /compare pages

    Now
    –
    Target
    +50%
    By
    2 quarters

    Steps

    1. 1

      Rank rivals

      From CRM win/loss.

      Account Executives 2 days

    2. 2

      Build the template

      Table, pricing model, migration notes.

      Content lead 1 week

    3. 3

      Publish six pages

      One a week.

      Content lead 6 weeks

    4. 4

      Review off-category posts

      Rewrite, noindex or remove.

      Content lead 2 weeks

    5. 5

      Link from the switch guide

      Each compare page links to /switch.

      Web team 1 day

    6. 6

      Track

      Rankings and sign-ups.

      Growth lead monthly

    First result
    2 months
    Cost
    $0
    Owner
    Content lead

    Smallest test

    Publish the Stytch page and noindex five off-category posts; watch sign-ups and rankings for a month.

    Why it works

    Build /compare pages for the rivals buyers actually weigh (Stytch, Descope, AWS Cognito, Firebase Auth, Better Auth, Keycloak) with a feature table, pricing model and migration notes. Review the off-category posts: rewrite those that explain how WorkOS fits beside the tool as "works with" posts, and remove or noindex the rest.

    Comparison pages convert buyers who are already choosing. Off-category comparisons look like content made in bulk, which search engines discount and readers distrust.

    Risks and how to handle them

    • Traffic from removed posts

      Keep and redirect posts with real traffic to the closest relevant page.

    Evidence

    • Your websiteComparison content: three /compare pages (Auth0, Clerk, Frontegg); 37 blog posts titled "<tool> vs WorkOS", many about tools in other categories (Semgrep, Snyk, Promptfoo, HiddenLayer, Google Vertex AI, OpenAI, Nightfall AI); and 12 "alternatives" posts, including both "auth0-alternatives" and "auth0-alternatives-2025", and "the-5-best-clerk-alternatives-in-2024" next to "clerk-alternatives".Source
    • Your websiteSitemaps: 1,504 website URLs (1,022 blog posts, 301 changelog entries, 84 guide pages, 32 podcast episodes) plus 845 docs pages. Between 50 and 119 website URLs were last modified in each month of 2026.Source
    • Competitor researchRivals' own positioning: Auth0, "Secure AI Agent & User Authentication"; Clerk, "Authentication and User Management", "Purpose-built for React, Next.js, Remix"; Stytch, "A better way to build auth"; Frontegg, "the first identity layer for agentic SaaS"; Descope, "Customer and Agentic Identity Platform".Source
  • 13

    WorkOS's promise is "Your app, Enterprise Ready", and the moment it matters most is a startup's first enterprise deal, when a security questionnaire arrives asking about SSO, SCIM, audit logs and data handling. The /startups page and the podcast reach founders but do not hand them the answers.

    Medium impactMedium effort First result in 1 quarter /startups owner

    First action

    Collect the identity questions from five real enterprise security questionnaires.

    How to measure it

    Kit downloads converting to accounts

    Now
    –
    Target
    25%
    By
    2 quarters

    Steps

    1. 1

      Collect questions

      Five questionnaires from customers.

      Account Executives 1 week

    2. 2

      Write answers

      Model answers with WorkOS features.

      Security team 2 weeks

    3. 3

      Design the kit

      PDF and editable doc.

      Design 1 week

    4. 4

      Publish

      On /startups and the blog.

      Web team 3 days

    5. 5

      Promote

      Podcast, newsletters, accelerators.

      Growth lead ongoing

    6. 6

      Route

      Downloads with high fit to AEs.

      GTM Engineer 1 day

    First result
    1 quarter
    Cost
    $3k
    Owner
    /startups owner

    Smallest test

    Share the question list and draft answers with ten founders and ask whether it saved them time.

    Why it works

    A free kit: the 30 questions enterprise security questionnaires ask about identity and access, model answers for a startup that uses WorkOS, a checklist of what to switch on, and a short talk track for the founder's sales call. Gate the editable version behind sign-up.

    Founders search for help exactly when the deal is at risk. A kit that wins the deal makes WorkOS the obvious choice for the integration that follows.

    Risks and how to handle them

    • Answers taken as legal advice

      Mark as examples to adapt.

    Evidence

    • Your websiteThe homepage, /pricing, /compare/auth0 and /switch serve no meta description. The homepage announces launches from WorkOS's init() event: Passport, Atlas ("your AI coworker") and Airlock ("Intent-Based Access Control"), alongside auth.md ("User registration for agents") and MCP Auth.Source
    • Your websiteCustomer logos include companies headquartered outside North America, such as Synthesia, Paddle and Prezi, while all hiring is in the US and Canada. The site has a /startups page, a /switch migration guide and a podcast.Source
    • HiringProduct Manager - Growth: own "activation, adoption, monetization, expansion, and retention across the platform", "build and scale a product experimentation program", "improve onboarding and reduce time-to-value", "work with Marketing to improve acquisition and attribution" and "partner with Sales to strengthen the product-qualified lead motion and enterprise expansion path".Source
  • 14

    Pricing is per connection with volume tiers, and annual credits add pre-pay discounts and migration help, but the page asks buyers to "Schedule a call" to learn whether credits pay off. The Growth PM owns monetisation.

    Medium impactMedium effort First result in 6 weeks PM

    First action

    Work out the break-even point for annual credits at three account sizes.

    How to measure it

    Annual-credit requests from pricing

    Now
    –
    Target
    20 a month
    By
    1 quarter

    Steps

    1. 1

      Model break-even

      Three account sizes.

      Finance 1 week

    2. 2

      Design the view

      Saving shown as inputs change.

      Design 1 week

    3. 3

      Build it

      Calculator update.

      Web team 2 weeks

    4. 4

      Pre-fill requests

      Inputs sent with the quote request.

      GTM Engineer 2 days

    5. 5

      Train sales

      Respond within a day.

      Account Executives 1 day

    6. 6

      Measure

      Requests and close rate.

      PM, Growth monthly

    First result
    6 weeks
    Cost
    $0
    Owner
    PM, Growth

    Smallest test

    Add a "credits could save you about X" line at one threshold.

    Why it works

    Extend the calculator: as connections and users rise, show when annual credits beat pay-as-you-go and by how much, with a button to request a credit quote that pre-fills the inputs for sales.

    Buyers approaching the threshold are ready to commit. Showing the saving turns a vague "talk to us" into a qualified, pre-sized request.

    Risks and how to handle them

    • Reveals discount levels

      Show a range, not exact contract terms.

    Evidence

    • Your websitePricing: AuthKit is free up to 1 million users, then $2,500 a month per additional million; Single Sign-On and Directory Sync are $125 per connection per month for 1-15 connections, falling to $65 at 51-100; Radar is free for 1,000 checks, then $100 per 50,000; a custom domain is $99 a month; annual credits add discounts and migration help. The page has no H1 heading and no meta description, and its server-rendered calculator text reads "$0 / month vs $100 to build it yourself".Source
    • HiringProduct Manager - Growth: own "activation, adoption, monetization, expansion, and retention across the platform", "build and scale a product experimentation program", "improve onboarding and reduce time-to-value", "work with Marketing to improve acquisition and attribution" and "partner with Sales to strengthen the product-qualified lead motion and enterprise expansion path".Source
    • HiringSales - Account Executive (San Francisco): "WorkOS has a strong bottoms-up, developer-focused GTM motion, and we're growing our lean sales team to complement it"; AEs from 2 to 10 years' experience; "We don't have formal sales segmentation: customer coverage is fluid"; AEs are to "test outreach, messaging, and sales approaches" and "help develop repeatable practices".Source
  • 15

    WorkOS is hiring an events-forward DevRel lead and a growth generalist to run dinners and meetups in San Francisco, where much of its AI customer base is. The most valuable guests are technical founders just starting to sell to enterprises.

    Medium impactMedium effort First result in 1 quarter Developer Relations

    First action

    Ask two customer CTOs to host the first two dinners.

    How to measure it

    Guests' accounts converting to paid within 6 months

    Now
    –
    Target
    40%
    By
    2 quarters

    Steps

    1. 1

      Find hosts

      Two customer CTOs.

      Developer Relations 2 weeks

    2. 2

      Build invite list

      From first-connection accounts and targets.

      GTM Engineer 1 week

    3. 3

      Run monthly

      Dinner with a 15-minute talk.

      Growth Marketing Generalist monthly

    4. 4

      Follow up

      Notes and introductions within two days.

      Account Executives 2 days

    5. 5

      Share recaps

      With guest permission.

      Developer Relations 1 week

    6. 6

      Measure

      Accounts and revenue from guests.

      Growth lead quarterly

    First result
    1 quarter
    Cost
    $4k a dinner
    Owner
    Developer Relations

    Smallest test

    Run one dinner with one host and 12 guests.

    Why it works

    A monthly dinner of 12 to 15 CTOs and founding engineers from AI companies at their first enterprise deals, with one customer CTO sharing how they handled SSO, SCIM and security reviews. Invite lists come from the first-connection signal and the BDR's target accounts.

    Small rooms build relationships that large meetups do not. Peers who just did it are the most credible speakers on enterprise readiness.

    Risks and how to handle them

    • Guests feel sold to

      No pitch; the host talks, WorkOS listens.

    Evidence

    • HiringDeveloper Relations (San Francisco): "an events-forward DevRel leader" to run meetups, panels and workshops and "support talent and pipeline generation"; Growth Marketing Generalist: developer events, conferences and dinners, newsletter sponsorships and campaign copy, working with the Growth lead.Source
    • HiringBusiness Development Representative: outbound into enterprise and mid-market; "use LLMs and AI tooling to research accounts, personalize outreach at scale"; "understand what a company is actually building — their stack, their auth setup, their scaling problems".Source
    • HiringGTM Engineer: maintain "our core enrichment pipeline: the workflows that take a new signup or a conference attendee list and return a fully enriched, scored, and Salesforce-upserted record", built on Cargo, Clay, Snowflake, Apollo, Linkup and Exa; own fit scoring.Source

Big bets 3

Larger plays that can change the trajectory.

  • 16

    WorkOS frames its future around "who are your agents, and what are they allowed to do?" and has shipped auth.md, MCP Auth, Passport and Airlock. Auth0, Frontegg and Descope now all describe themselves as agentic identity platforms. In a crowded new category, whoever defines the standard tends to win.

    High impactHigh effort First result in 3 quarters Head of Product

    First action

    Ask three agent framework teams whether they would implement an open agent registration spec.

    How to measure it

    Third-party implementations

    Now
    –
    Target
    10
    By
    4 quarters

    Steps

    1. 1

      Gauge interest

      Three frameworks and two AI labs.

      Head of Product 1 month

    2. 2

      Write the spec

      From auth.md, versioned.

      Identity team 2 months

    3. 3

      Build conformance tests

      Open source.

      Developer & Agent Experience team 2 months

    4. 4

      Set governance

      Public process for changes.

      Head of Product 1 month

    5. 5

      Launch

      With partner implementations.

      Growth lead 1 month

    6. 6

      Track

      Implementations and spec traffic.

      PM, Growth ongoing

    First result
    3 quarters
    Cost
    Engineering time
    Owner
    Head of Product

    Smallest test

    Publish auth.md as a draft spec with a test suite and invite comments for a month.

    Why it works

    Turn auth.md into an open, versioned specification for how agents register and are authorised, publish a conformance test suite, invite identity vendors, agent frameworks and AI labs to implement it, and host the reference implementation on GitHub.

    Standards decide categories. If agent builders adopt WorkOS's spec, every implementation points back to WorkOS as the easiest compliant choice.

    Risks and how to handle them

    • Competitors ignore it

      Recruit frameworks and labs first; vendors follow developers.

    Evidence

    • Your websiteThe homepage, /pricing, /compare/auth0 and /switch serve no meta description. The homepage announces launches from WorkOS's init() event: Passport, Atlas ("your AI coworker") and Airlock ("Intent-Based Access Control"), alongside auth.md ("User registration for agents") and MCP Auth.Source
    • Competitor researchRivals' own positioning: Auth0, "Secure AI Agent & User Authentication"; Clerk, "Authentication and User Management", "Purpose-built for React, Next.js, Remix"; Stytch, "A better way to build auth"; Frontegg, "the first identity layer for agentic SaaS"; Descope, "Customer and Agentic Identity Platform".Source
    • HiringDeveloper & Agent Experience Engineer: "Developers still integrate WorkOS, but increasingly their agents do it for them." The team owns "SDKs in 9 languages, now generated from our API spec; an AI installer CLI that sets up AuthKit in any project; our MCP servers and agent skills", and writes evaluations "to measure whether what you ship actually improves developer outcomes".Source
    • HiringEvery post opens with the same paragraph: "a $100M Series C, valuing the company at $2B", customers "including OpenAI, Cursor, and Perplexity, Sierra, and Plaid", the question "who are your agents, and what are they allowed to do?", and "hundreds of modern software companies". All 29 open roles are in San Francisco or "United States & Canada".Source
  • 17

    Customers include app-building platforms such as Replit, Bolt and Convex. The Developer & Agent Experience team already ships framework libraries for Next.js, Remix and TanStack. Apps created in those tools need enterprise auth the moment they land a business customer.

    High impactHigh effort First result in 3 quarters Partnerships lead

    First action

    List the app-building platforms already on the customer page and contact two.

    How to measure it

    Accounts from partner templates

    Now
    –
    Target
    2,000
    By
    4 quarters

    Steps

    1. 1

      Pick partners

      Two or three platforms.

      Partnerships lead 1 month

    2. 2

      Build templates

      Pre-wired WorkOS for each.

      Developer & Agent Experience team 1 month

    3. 3

      Agree terms

      Co-marketing or revenue share.

      Partnerships lead 1 month

    4. 4

      Launch

      Joint announcement and docs.

      Growth lead 2 weeks

    5. 5

      Tag accounts

      Source by partner.

      GTM Engineer 1 day

    6. 6

      Review

      Quarterly per partner.

      Partnerships lead quarterly

    First result
    3 quarters
    Cost
    Partner incentives
    Owner
    Partnerships lead

    Smallest test

    Ship one template on one platform and count accounts created through it.

    Why it works

    Partner with two or three app-building platforms to offer "enterprise-ready" templates with WorkOS pre-wired, a one-click upgrade path from basic auth to SSO, and revenue share or co-marketing. Measure accounts created through each partner.

    Distribution inside the build tool reaches developers before they choose auth. Becoming the template is cheaper than winning each comparison later.

    Risks and how to handle them

    • Partners build their own auth

      Position WorkOS for the enterprise features they do not want to maintain.

    Evidence

    • HiringDeveloper & Agent Experience Engineer: "Developers still integrate WorkOS, but increasingly their agents do it for them." The team owns "SDKs in 9 languages, now generated from our API spec; an AI installer CLI that sets up AuthKit in any project; our MCP servers and agent skills", and writes evaluations "to measure whether what you ship actually improves developer outcomes".Source
    • Your websiteCustomers page: 181 logos, from OpenAI, Anthropic, Cursor, Sierra and Plaid to Snowflake and Vanta, including app-building platforms such as Replit, Bolt and Convex. Three screen-reader labels are file names ("68f7b8469a33c174c66b5f42_physical intelligence", "Privy_Brandmark_Black", "[email removed]"). There are 21 written customer stories (AI21 Labs, Cerkl, Chromatic, Copy.ai, Drata, EnjoyHQ, Gretel, Hopin, Hypercare, incident.io, Indeed, Magical, Netlify, OpenAI, Patch, Perplexity, PlanetScale, Prefect, Tactic, Warp, Webflow); none for Anthropic, Cursor, Sierra or Plaid.Source
    • HiringProduct Manager - Growth: own "activation, adoption, monetization, expansion, and retention across the platform", "build and scale a product experimentation program", "improve onboarding and reduce time-to-value", "work with Marketing to improve acquisition and attribution" and "partner with Sales to strengthen the product-qualified lead motion and enterprise expansion path".Source
  • 18

    All 29 open roles are in the US and Canada, while customers include European companies such as Synthesia, Paddle and Prezi. Expansion into a new region is expensive to get wrong.

    High impactHigh effort First result in 3 quarters Head of Sales

    First action

    Pull revenue and first connections by customer country for the last year.

    How to measure it

    European new revenue during the test

    Now
    –
    Target
    $1M ARR
    By
    4 quarters

    Steps

    1. 1

      Pull the data

      Revenue and connections by region.

      Data Engineer 1 week

    2. 2

      Set the threshold

      What justifies a test.

      Head of Sales 1 day

    3. 3

      Hire one AE

      Remote in a European time zone.

      Recruiter 2 months

    4. 4

      Run local programs

      One dinner, one compliance page.

      Growth lead 1 quarter

    5. 5

      Measure

      Pipeline and win rate vs. US.

      Data Engineer monthly

    6. 6

      Decide

      Scale, hold or stop.

      Head of Sales 1 week

    First result
    3 quarters
    Cost
    One hire plus programs
    Owner
    Head of Sales

    Smallest test

    Pull the regional data and share it at the next planning meeting.

    Why it works

    Measure first: sign-ups, first connections and revenue by customer region, plus the share of connections whose end customers are in Europe. If Europe passes a threshold, run a two-quarter test with one remote AE in a European time zone, a European customer dinner and a localised compliance page, before opening an office.

    Data-led expansion avoids building a team for a region that is not ready, and moves quickly where it is.

    Risks and how to handle them

    • Time-zone gap with the team

      Overlap hours and a US-based manager.

    Evidence

    • HiringEvery post opens with the same paragraph: "a $100M Series C, valuing the company at $2B", customers "including OpenAI, Cursor, and Perplexity, Sierra, and Plaid", the question "who are your agents, and what are they allowed to do?", and "hundreds of modern software companies". All 29 open roles are in San Francisco or "United States & Canada".Source
    • Your websiteCustomer logos include companies headquartered outside North America, such as Synthesia, Paddle and Prezi, while all hiring is in the US and Canada. The site has a /startups page, a /switch migration guide and a podcast.Source
    • HiringAccount Manager: own "the expansion of our most complex accounts"; "identify unadopted products and untapped teams"; "drive adoption of the full WorkOS platform — SSO, Directory Sync, AuthKit, Audit Logs, and beyond — across new teams, new products, and new geographies"; run executive business reviews.Source

Wildcards 3

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

  • 19

    WorkOS has 32 podcast episodes and an outbound BDR team working target accounts. A podcast invitation is one of the few cold messages engineering leaders say yes to.

    Medium impactLow effort First result in 1 quarter Podcast host

    First action

    Choose five target-account leaders and send podcast invitations.

    How to measure it

    Guest accounts with an opportunity within 6 months

    Now
    –
    Target
    50%
    By
    3 quarters

    Steps

    1. 1

      Pick guests

      Five target-account leaders.

      Podcast host 1 week

    2. 2

      Invite

      Personal invitation with topic.

      Podcast host 1 week

    3. 3

      Record

      Usual format.

      Podcast host per episode

    4. 4

      Promote

      Guest and WorkOS channels.

      Growth lead per episode

    5. 5

      Introduce

      AE follow-up offered after airing.

      Account Executives per episode

    6. 6

      Track

      Pipeline from guest accounts.

      Growth lead quarterly

    First result
    1 quarter
    Cost
    $0
    Owner
    Podcast host

    Smallest test

    Invite three target-account leaders this month.

    Why it works

    Pick half of future guests from target accounts (CTOs and heads of platform at companies approaching enterprise sales), give each a great episode, and after it airs, introduce the guest to an AE for an optional architecture review.

    Guests become champions, and the episode gives the BDR a warm reason to reach the rest of the guest's team.

    Risks and how to handle them

    • Guests feel used

      The episode stands on its own; the AE intro is optional.

    Evidence

    • Your websiteSitemaps: 1,504 website URLs (1,022 blog posts, 301 changelog entries, 84 guide pages, 32 podcast episodes) plus 845 docs pages. Between 50 and 119 website URLs were last modified in each month of 2026.Source
    • HiringBusiness Development Representative: outbound into enterprise and mid-market; "use LLMs and AI tooling to research accounts, personalize outreach at scale"; "understand what a company is actually building — their stack, their auth setup, their scaling problems".Source
    • HiringSales - Account Executive (San Francisco): "WorkOS has a strong bottoms-up, developer-focused GTM motion, and we're growing our lean sales team to complement it"; AEs from 2 to 10 years' experience; "We don't have formal sales segmentation: customer coverage is fluid"; AEs are to "test outreach, messaging, and sales approaches" and "help develop repeatable practices".Source
  • 20

    WorkOS's buyers are SaaS companies that do not yet offer SSO. Whether a login page offers SSO, social login or MFA is visible from outside, and founders want to know how they compare with competitors.

    Medium impactMedium effort First result in 6 weeks GTM Engineer

    First action

    Hand-check 20 target accounts' login pages for SSO options.

    How to measure it

    Meetings from scan-based outbound

    Now
    –
    Target
    15 a month
    By
    1 quarter

    Steps

    1. 1

      Define checks

      SSO button, social login, MFA prompts.

      GTM Engineer 1 week

    2. 2

      Build the scanner

      Public login pages only.

      GTM Engineer 2 weeks

    3. 3

      Publish the tool

      Simple page with a checklist.

      Web team 1 week

    4. 4

      Run on targets

      Score target accounts.

      GTM Engineer 1 day

    5. 5

      Write outbound

      Email referencing the gap.

      BDR 1 day

    6. 6

      Measure

      Runs, shares, meetings.

      Growth lead monthly

    First result
    6 weeks
    Cost
    $0
    Owner
    GTM Engineer

    Smallest test

    Hand-check 20 login pages and email the ten without SSO.

    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

    A free tool: enter a SaaS domain and see which enterprise sign-in features its login page shows, compared with others in its category, with a checklist to close the gaps. The same scan, run on a target list, tells BDRs which companies lack SSO.

    A free tool with a shareable result spreads among founders, and the scan gives outbound a precise reason to reach out.

    Risks and how to handle them

    • Scanning feels intrusive

      Only public login pages, no sign-in attempts, and clear wording about what is checked.

    Evidence

    • HiringBusiness Development Representative: outbound into enterprise and mid-market; "use LLMs and AI tooling to research accounts, personalize outreach at scale"; "understand what a company is actually building — their stack, their auth setup, their scaling problems".Source
    • HiringGTM Engineer: maintain "our core enrichment pipeline: the workflows that take a new signup or a conference attendee list and return a fully enriched, scored, and Salesforce-upserted record", built on Cargo, Clay, Snowflake, Apollo, Linkup and Exa; own fit scoring.Source
    • Your websiteThe homepage, /pricing, /compare/auth0 and /switch serve no meta description. The homepage announces launches from WorkOS's init() event: Passport, Atlas ("your AI coworker") and Airlock ("Intent-Based Access Control"), alongside auth.md ("User registration for agents") and MCP Auth.Source
  • 21

    Companies hiring their first enterprise account executive are about to face security reviews that ask for SSO and SCIM. The BDR is to understand "their stack, their auth setup, their scaling problems", and the GTM Engineer's pipeline can watch job boards.

    Medium impactLow effort First result in 1 month BDR

    First action

    Search job boards for "founding enterprise AE" at 100 target accounts.

    How to measure it

    Meetings from hiring signals

    Now
    –
    Target
    10 a month
    By
    1 quarter

    Steps

    1. 1

      Define titles

      Founding or first enterprise AE, head of security.

      GTM Engineer 1 day

    2. 2

      Add the signal

      Job-board checks in the pipeline.

      GTM Engineer 1 week

    3. 3

      Write the email

      Kit plus auth review offer.

      BDR 2 hours

    4. 4

      Route

      Same-week BDR task.

      GTM Engineer 1 day

    5. 5

      Measure

      Reply and meeting rates.

      Growth lead monthly

    6. 6

      Refine

      Drop titles that do not convert.

      GTM Engineer monthly

    First result
    1 month
    Cost
    $0
    Owner
    BDR

    Smallest test

    Run the search by hand for 100 accounts and email the matches.

    Why it works

    Add a signal for companies posting first enterprise sales roles or "head of security" roles, and send a same-week email from the BDR with the first-enterprise-deal kit and an offer to review their auth setup.

    A first enterprise sales hire is a dated, public sign that SSO will be needed within months.

    Risks and how to handle them

    • Too early in the deal

      Lead with the kit, which is useful before the questionnaire arrives.

    Evidence

    • HiringBusiness Development Representative: outbound into enterprise and mid-market; "use LLMs and AI tooling to research accounts, personalize outreach at scale"; "understand what a company is actually building — their stack, their auth setup, their scaling problems".Source
    • HiringGTM Engineer: maintain "our core enrichment pipeline: the workflows that take a new signup or a conference attendee list and return a fully enriched, scored, and Salesforce-upserted record", built on Cargo, Clay, Snowflake, Apollo, Linkup and Exa; own fit scoring.Source
    • HiringEvery post opens with the same paragraph: "a $100M Series C, valuing the company at $2B", customers "including OpenAI, Cursor, and Perplexity, Sierra, and Plaid", the question "who are your agents, and what are they allowed to do?", and "hundreds of modern software companies". All 29 open roles are in San Francisco or "United States & Canada".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 21 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.

Outreach1The sequence sent for you: addresses found and verified, replies routed to your CRM.

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

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

Book a working session

Usually live within days.

Tools for the rest

ProgrammableInfo

Turn the research into a list you can act on

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

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

New accounts: 100,000 free credits with code BETA100K

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

Fill the events in this plan

These ideas are events. Talk gets registrants for them and tells you who's coming and what their company does before the day.

Plan an event (opens programmable.talk in a new tab)
More example playbooks and reviews

More growth playbooks

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

  • SecurityScorecard growth strategyA cybersecurity ratings and third-party risk platform (TITAN AI: Watch, Assess, Secure, MAX managed services, AI agents and workflows)…22 growth ideas
  • Wayline growth strategyAn AI and human front desk for property managers: Wayline answers every call, text, email and chat, books tours, triages maintenance and…23 growth ideas
  • Replit growth strategyAn AI platform where people describe an app, website or tool in plain language and Replit Agent builds, hosts and runs it, with databases…21 growth ideas
  • MarcoPolo Learning growth strategyEarly-childhood learning content, professional development and family engagement tools for classrooms and homes, the MarcoPolo World…21 growth ideas
  • ComplyAdvantage growth strategyAn AI-native financial crime risk platform (Mesh): customer and company screening, ongoing monitoring, transaction monitoring, payment…22 growth ideas
  • InstaLILY growth strategyEnterprise AI company whose product Lily acts as an AI forward deployed engineer: it learns how an operation works, builds agents for…21 growth ideas
  • Webgrowth growth strategyA full-service digital marketing agency: SEO and generative engine optimization, PPC, social media, web design and development, branding…22 growth ideas
  • Biordi Art Imports growth strategyA San Francisco North Beach store, founded in 1946, importing hand-painted Italian majolica, dinnerware, home décor, religious art and…21 growth ideas

See every playbook and website review

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

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

    First-connection signal, pricing page basics, logo labels, merged alternatives posts, security headers and same-night event follow-up.

    Programmable can ship 1 of these in days.

  2. Days 31 to 605 ideas

    Stories for the biggest logos, the agent-led funnel, connection-count segments, cross-sell plays and the Radar report.

  3. Days 61 to 9010 ideas

    Compare pages, the founder kit, the credits calculator, the dinner series, the wildcards and the decision on the big bets.

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 shipping SSO and SCIM in days instead of months. The most cited problem: enterprise security questionnaires.

  • A self-serve Admin Portal for customers' IT teams
  • Supporting every identity provider
  • In their words: “Enterprise Ready”

Market

Competitive landscape

5 competitors compared: Auth0 (Okta), Clerk, Stytch, Frontegg and 1 more.

  • Gap to exploit: A standard for agent registration and authorisation
  • Auth0 (Okta): Pricing complexity for B2B features
  • Clerk: Less enterprise depth

Hiring signals

WorkOS's 29 roles add a lean, experimental sales and growth layer on top of a developer-led motion.

  • Sales - Account Executive: Lean team, no formal segmentation, experiments expected. Ideas 1, 9.
  • Product Manager - Growth: Activation to retention, experimentation and the PQL motion. Ideas 1, 8, 14.
  • Account Manager: Multi-product expansion in the most complex accounts. Ideas 7, 10.

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