ProgrammableMarketing/antigen.sh (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 · 12
  • Big bets · 3
  • Wildcards · 2
Generated Nov 10, 2026
  1. Programmable
  2. Playbooks
  3. Antigen
Antigen logo

growth playbook · Nov 10, 2026

antigen.sh (opens in a new tab)

Antigen growth playbook

Diagnosis

Antigen is a five-person Y Combinator company (Fall 2025, backed by Lightspeed, DST Global and Susa Ventures) selling continuous, AI-driven pentesting with human experts in the loop. The product story is strong and specific, and the site is fast.

But the public surface does not yet earn the trust a security vendor needs: 65 of the 176 pages in the docs index are a template "demo help center" (fake plans, an "illustrative" subprocessor list naming nobody, "EU data residency options in this demo help center"), the Enterprise page's Trust Center button returns 404, the blog has 0 articles, and seven logos carry no stories.

Rivals XBOW, Horizon3.ai and Cobalt lead with proof, pricing signals and research. This playbook first cleans up what buyers and AI assistants read during diligence, then turns findings, fixes and the new Security Researcher's work into proof, opens healthcare, finance and pipeline-native entry points, and finishes with a self-serve external check, an annual findings report and a public-sector authorization path.

Growth Score

6/10

Biggest Opportunity

Every engagement already produces the best possible marketing material, exploits found and fixes verified. Publishing that proof (sanitized write-ups, sample reports, verified-fix stats) and making diligence painless would let a five-person team out-trust larger rivals.

Biggest Risk

Better-known rivals (XBOW with 200+ security teams, Horizon3.ai with 7,012 customers, Cobalt with 500+ testers) set buyer expectations on proof and compliance; a vendor whose public docs contain placeholder legal pages risks failing security review before the demo even starts.

01

Start here

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

  1. 1

    Replace the 65 "demo help center" template pages in the docs with the real pages buyers check: subprocessors, DPA, retention and plans

    Remove the help-center group from the docs navigation and from llms.txt today.

    High impact First result in 1 week
  2. 2

    Fix the Enterprise page's Trust Center button (it returns 404) and put the Trust Center on every page

    Add a redirect from /trust to trust.antigen.sh.

    High impact First result in Same day
  3. 3

    Publish a sample report so buyers can see a finding, its exploit and its retest before the demo

    Choose or build a vulnerable demo target that Antigen owns.

    High impact First result in 2 weeks

02

Your idea portfolio

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

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

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 · 4Big bets · 10Fill-ins · 5Reconsider · 4
Effort →

Showing 23 of 23 ideas

This week 6

Quick wins with a clear first action.

  • 01

    Antigen's docs index (llms.txt, the file AI assistants and crawlers read) lists 176 pages. About 110 are excellent product docs. The other 65 are a starter template that was never replaced: "Compare plans" describes "Free, Team, and Enterprise tiers for this demo help center", "Subprocessors" is an "Illustrative list of subprocessors for this demo" that names nobody, and "EU data residency" describes options "in this demo help center". There are also pages on editor drafts, projects and Salesforce and HubSpot connectors that have nothing to do with pentesting, and the help-center home shows unrendered code. A security reviewer, or an AI assistant asked "does Antigen publish its subprocessors?", lands on placeholder text from a vendor asking for access to production.

    High impactLow effort First result in 1 week Founder & CTO

    First action

    Remove the help-center group from the docs navigation and from llms.txt today.

    How to measure it

    Template pages in llms.txt

    Now
    –
    Target
    0 (from 65)
    By
    7 days

    Steps

    1. 1

      List the template pages

      All 65 help-center entries in llms.txt (items under /docs/help).

      Founder & CTO 1 hour

    2. 2

      Unpublish or noindex

      Remove them from navigation and llms.txt; return 410 or redirect to the docs home.

      Founding Engineer 2 hours

    3. 3

      Write the diligence set

      Subprocessors, DPA/MSA request, retention, data location, engagement model, support, deletion.

      Founder (CEO) 3 days

    4. 4

      Check against the site

      Make every statement match the Enterprise and Government pages and the Trust Center.

      Founder & CTO 1 day

    5. 5

      Publish and link

      Link from the Trust Center, the Enterprise page and the docs home.

      Founding Engineer 1 day

    6. 6

      Ask the assistants

      Run ten diligence questions through AI assistants and search; note which pages they cite.

      Founder (CEO) 2 hours

    7. 7

      Add a review owner

      Quarterly check that docs, Trust Center and site still agree.

      Founder & CTO quarterly

    First result
    1 week
    Cost
    $0, about a week of founder and engineer time
    Owner
    Founder & CTO

    Smallest test

    Pull the help-center group from llms.txt and the docs navigation today, then publish a real Subprocessors page.

    Why it works

    In one week: unpublish the 65 template pages (or noindex them and drop them from llms.txt), then publish a small set of real replacements built from what the Enterprise and Government pages already say: Subprocessors (the actual vendors, with a change-notice process), DPA and MSA (how to request them), Data retention (30, 90 or custom days, on-demand purging, KMS encryption), Data location (what runs where for managed vs dedicated deployments), Engagement and plans (how a managed or dedicated engagement is scoped, even without prices), Support (dedicated expert, office hours) and Account and data deletion. Link each page from the Trust Center and the Enterprise page so diligence starts in the right place.

    Security buyers read vendors' docs and legal pages before a demo, and AI assistants increasingly answer vendor-diligence questions from llms.txt. Removing placeholder legal text removes an easy reason to fail review, and real pages turn existing enterprise claims into something a reviewer can cite.

    Ready to use

    ChecklistDiligence pages to publish in place of the template

    [ ] Subprocessors: real vendor list, purpose, region, change-notice window
    [ ] DPA and MSA: how to request, standard terms
    [ ] Data retention: 30 / 90 / custom days, on-demand purge, KMS encryption
    [ ] Data location: managed vs dedicated (Helm chart or container image)
    [ ] Engagement model: how scope, targets and approvals work
    [ ] Support: dedicated expert, office hours, response times
    [ ] Account and data deletion
    [ ] Remove /docs/help template pages from llms.txt and navigation
    [ ] Link all of the above from trust.antigen.sh and /enterprise

    Risks and how to handle them

    • Deleting pages breaks inbound links

      Redirect each removed URL to the closest real page.

    • New legal pages overstate commitments

      Have counsel review the subprocessor and DPA pages before publishing.

    Evidence

    • Your websiteDocs index llms.txt (checked November 9, 2026): 176 entries. About 110 are real product docs (Asset Map, Runs, tCell, SDK, CLI with CI/CD integration, a "Pentest after a deployment" example, 21 integrations including GitLab, Jira, ServiceNow, Cursor Cloud and Devin, and an API reference). The other 65 are a help center from a template: "Compare plans" describes "Free, Team, and Enterprise tiers for this demo help center"; "Subprocessors" is an "Illustrative list of subprocessors for this demo" naming none; "EU data residency options in this demo help center"; plus pages on editor drafts, projects, keyboard shortcuts and Salesforce and HubSpot connectors. The help-center home shows unrendered code.Source
    • Your websiteEnterprise page: "Continuous offensive security without giving up control." HIPAA compliant; "An independent SOC 2 Type II audit is underway"; compliance-mapped findings for PCI DSS, NIST 800-171, ISO 27001 and CWE; procurement documents (DPA, MSA, security questionnaire responses, a named security contact); 30-day, 90-day or custom retention; 12 integrations including Jira, ServiceNow, Splunk and Tenable; a healthcare section on the proposed HIPAA Security Rule's annual penetration-testing requirement. Its "Visit the Trust Center" button links to antigen.sh/trust, which returned 404 Not Found on two checks on November 9, 2026; the Trust Center itself lives at trust.antigen.sh.Source
    • Your websiteGovernment page: "Security testing built for government boundaries"; dedicated on-premises deployment as a Helm chart or container image; SSO, SCIM and audit streaming to Splunk, Sentinel and others; support for GovRAMP and FISMA reporting work (stated as not a certification); mapping to NIST, CJIS, FERPA and CIRCIA; sectors: state and local government, public utilities and education; procurement through Pursuit, a public-sector reseller, plus cooperative purchasing.Source
  • 02

    The Enterprise page is where security and procurement teams go to check controls, and its "Visit the Trust Center" button points to antigen.sh/trust, which returned 404 on two checks. The real Trust Center runs on Vanta at trust.antigen.sh. The one click that should start diligence ends in an error.

    High impactLow effort First result in Same day Founding Engineer

    First action

    Add a redirect from /trust to trust.antigen.sh.

    How to measure it

    Demo-to-security-approval time

    Now
    –
    Target
    -25%
    By
    90 days

    Steps

    1. 1

      Redirect

      /trust to trust.antigen.sh (permanent).

      Founding Engineer 30 minutes

    2. 2

      Fix the button

      Point it straight to the Trust Center.

      Founding Engineer 15 minutes

    3. 3

      Link everywhere

      Header or footer on Enterprise, Government and docs.

      Founding Engineer 2 hours

    4. 4

      Complete the Trust Center

      SOC 2 status and window, HIPAA, DPA/MSA request, subprocessors.

      Founder (CEO) 1 day

    5. 5

      Add link checks

      Fail the build on internal 404s.

      Founding Engineer 2 hours

    6. 6

      Track

      Trust Center requests per demo and time to approval.

      Founder (CEO) monthly

    First result
    Same day
    Cost
    $0
    Owner
    Founding Engineer

    Smallest test

    Ship the redirect today and click the button.

    Why it works

    Redirect /trust to trust.antigen.sh, fix the button, and add the Trust Center to the header or footer of the Government page and docs. On the Trust Center, state the SOC 2 Type II audit status plainly ("underway", with an expected report window), HIPAA, the DPA and MSA, and the new subprocessor page from idea 1. Add an automated link check to the site build so this cannot recur.

    Enterprise and public-sector deals stall in security review; a working, complete Trust Center lets the champion forward one link instead of waiting on a questionnaire.

    Risks and how to handle them

    • SOC 2 timeline slips after it is published

      Give a window, not a date, and update it monthly.

    Builds on

    Evidence

    • Your websiteEnterprise page: "Continuous offensive security without giving up control." HIPAA compliant; "An independent SOC 2 Type II audit is underway"; compliance-mapped findings for PCI DSS, NIST 800-171, ISO 27001 and CWE; procurement documents (DPA, MSA, security questionnaire responses, a named security contact); 30-day, 90-day or custom retention; 12 integrations including Jira, ServiceNow, Splunk and Tenable; a healthcare section on the proposed HIPAA Security Rule's annual penetration-testing requirement. Its "Visit the Trust Center" button links to antigen.sh/trust, which returned 404 Not Found on two checks on November 9, 2026; the Trust Center itself lives at trust.antigen.sh.Source
    • Your websiteTrust Center at trust.antigen.sh (run on Vanta) and a public status page at status.antigen.sh ("All systems operational"). The site's links include Docs, Blog, Trust Center, Status, X and LinkedIn; no newsletter signup was found.Source
  • 03

    The blog is in the navigation and sitemap and promises "security research from the Antigen team", but it has 0 articles. Meanwhile the homepage's sample board already names the finding types tCell catches: cross-tenant report access, unsigned webhook endpoints, over-scoped CI tokens, sessions that survive workspace removal. Each is a ready-made post.

    High impactMedium effort First result in 1 month Security Researcher

    First action

    Pick the cross-tenant access finding and outline the post.

    How to measure it

    Blog-sourced demos

    Now
    –
    Target
    4 a month
    By
    90 days

    Steps

    1. 1

      Pick six classes

      From the sample board and recent engagements.

      Security Researcher 1 day

    2. 2

      Set a disclosure rule

      No customer names, hosts or identifying code; customer sign-off where needed.

      Founder (CEO) 1 day

    3. 3

      Write the first post

      Chain, discovery, fix, retest.

      Security Researcher 3 days

    4. 4

      Review

      Technical and disclosure review.

      Founder & CTO 1 day

    5. 5

      Publish and share

      Blog, X and LinkedIn.

      Founder (CEO) 1 day

    6. 6

      Keep the cadence

      One post every two weeks.

      Security Researcher biweekly

    7. 7

      Measure

      Visits, demo clicks and demos by post.

      Founder (CEO) monthly

    First result
    1 month
    Cost
    Researcher time, about a day per post
    Owner
    Security Researcher

    Smallest test

    Publish the cross-tenant access write-up and track demo clicks for two weeks.

    Why it works

    Publish one sanitized write-up every two weeks on a finding class: how an attacker chains it, how tCell found it, the fix (as the pull request would look) and how the retest verified it. No customer names or identifying details. End each post with "Book a 30m demo" and a link to the sample report (idea 5). Share each on X and LinkedIn.

    Security buyers trust vendors who show their work; rivals lead with research credibility. Posts on specific bug classes also match the searches engineers make when they worry about their own app.

    Risks and how to handle them

    • A post identifies a customer

      Strip details and get sign-off before publishing.

    Evidence

    • Your websiteBlog (checked November 9, 2026): linked from the site and listed in the sitemap, it promises "Company updates, product thinking, and security research from the Antigen team" with filters for Product, Research, Company, Ideas and Customers, but shows 0 articles.Source
    • Your websiteHomepage (checked November 9, 2026): H1 "Antigen is the defense factory that maps, exploits, and secures your entire attack surface." The offensive agent tCell chains exploits; "Every finding arrives with a reproducible exploit attached"; Antigen opens pull requests and retests each fix. Each customer gets "a dedicated security expert" and every report is reviewed by a researcher. Managed deployment: "Run your first pentest in under 30 minutes"; dedicated self-hosted workers on AWS, Azure, GCP or Kubernetes. Seven customer logos (Antimetal, Enzo Health, Orkes, Harper, Retell AI, Pursuit, Faye) and no written testimonials; industries listed: Technology, Financial Services, Healthcare, Government; no pricing; the only conversion path is "Book a 30m demo" on Cal.com. The sample board lists findings such as cross-tenant report access, an unsigned webhook endpoint, over-scoped CI tokens and sessions that stay valid after workspace removal.Source
    • Competitor researchRivals' own homepages: XBOW, "Every finding is a working exploit", 200+ security teams, #1 on HackerOne, a Pricing page, free unlimited re-testing, SOC 2, ISO 27001 and ISO 42001; Horizon3.ai NodeZero, "Go hack yourself. Before they do.", 7,012 customers, a NodeZero Federal offering, 4.7 on Gartner Peer Insights; Cobalt, "Continuous Offensive Security Testing" with 500+ vetted testers, a usage-based credit model and a downloadable State of Pentesting 2026 report.Source
  • 04

    The homepage shows seven customer logos and no written testimonials, and the six-page sitemap has no case studies. For a security purchase, a logo says "we bought it"; a story says what was found, how fast it was fixed and what the team stopped doing.

    High impactMedium effort First result in 1 month Founder

    First action

    Email three logo customers asking for a 20-minute interview.

    How to measure it

    Homepage visit-to-demo rate

    Now
    –
    Target
    +20%
    By
    60 days

    Steps

    1. 1

      Pick three

      Different industries, happy and willing.

      Founder (CEO) 1 day

    2. 2

      Pull the numbers

      Findings, time to first finding, time to verified fix.

      Founder & CTO 2 days

    3. 3

      Interview

      20 minutes each.

      Founder (CEO) 1 week

    4. 4

      Write and approve

      One page each; customer approves every line.

      Founder (CEO) 1 week

    5. 5

      Publish

      A /customers section and quotes under the logo bar.

      Founding Engineer 1 day

    6. 6

      Use in sales

      Send the matching story after each demo.

      Founder (CEO) ongoing

    First result
    1 month
    Cost
    Founder time
    Owner
    Founder (CEO)

    Smallest test

    One quote with one number under the logo bar this week.

    Why it works

    Ask three logo customers (ideally one technology, one healthcare, one public-sector-adjacent) for a 20-minute interview and publish short stories: what they used before, time to first validated finding, number of exploitable findings, median time from finding to verified fix, and one quote. Add one quote under the logo bar and link each story from the relevant industry page.

    Peer proof shortens security buying, and numbers on time-to-verified-fix show the find-fix-verify loop that sets Antigen apart.

    Risks and how to handle them

    • Customers will not name security weaknesses publicly

      Publish aggregate numbers and outcomes, not vulnerabilities.

    Evidence

    • Your websiteHomepage (checked November 9, 2026): H1 "Antigen is the defense factory that maps, exploits, and secures your entire attack surface." The offensive agent tCell chains exploits; "Every finding arrives with a reproducible exploit attached"; Antigen opens pull requests and retests each fix. Each customer gets "a dedicated security expert" and every report is reviewed by a researcher. Managed deployment: "Run your first pentest in under 30 minutes"; dedicated self-hosted workers on AWS, Azure, GCP or Kubernetes. Seven customer logos (Antimetal, Enzo Health, Orkes, Harper, Retell AI, Pursuit, Faye) and no written testimonials; industries listed: Technology, Financial Services, Healthcare, Government; no pricing; the only conversion path is "Book a 30m demo" on Cal.com. The sample board lists findings such as cross-tenant report access, an unsigned webhook endpoint, over-scoped CI tokens and sessions that stay valid after workspace removal.Source
    • Your websiteSitemap (checked November 9, 2026): 6 URLs in total: /, /blog, /enterprise, /government, /privacy and /terms, last updated in August 2026. No pricing, case study, comparison, healthcare or financial-services pages.Source
  • 05

    Antigen's strongest claim is that every finding has a reproducible exploit, a fix pull request and a retest, and the docs describe evidence as HTTP requests and responses, screenshots or exploit recordings. But a buyer can only see this after booking a demo. XBOW offers "See a finding trace" on its homepage.

    High impactLow effort First result in 2 weeks Founder & CTO

    First action

    Choose or build a vulnerable demo target that Antigen owns.

    How to measure it

    Report-viewer demo rate

    Now
    –
    Target
    10%
    By
    60 days

    Steps

    1. 1

      Build the target

      A small multi-tenant demo app with planted flaws.

      Founding Engineer 2 days

    2. 2

      Run tCell

      Full run with remediation and retest.

      Security Researcher 1 day

    3. 3

      Export the report

      Web page plus PDF.

      Founder & CTO 1 day

    4. 4

      Annotate

      Short notes explaining each section.

      Founder & CTO 1 day

    5. 5

      Publish ungated

      Link from hero, Enterprise and blog.

      Founding Engineer 1 day

    6. 6

      Measure

      Views, time on page, demo clicks.

      Founder (CEO) monthly

    First result
    2 weeks
    Cost
    A few engineering days
    Owner
    Founder & CTO

    Smallest test

    Publish one annotated finding with its retest log.

    Why it works

    Run tCell against a deliberately vulnerable demo app you own, and publish the resulting report as an ungated web page and PDF: one critical chained finding with evidence, the remediation PR, the retest log that moved it to Verified, and the compliance mapping (CWE, PCI DSS, NIST). Link it from the homepage hero, the Enterprise page and every blog post.

    It lets the champion show their team what they will receive, and makes the difference from a PDF-only point-in-time pentest concrete.

    Risks and how to handle them

    • Looks staged

      Say it is a demo app and show the raw logs.

    Evidence

    • Your websiteQuick start: submit a target, which "the Antigen team reviews" for ownership or permission; connect AWS, Vercel or Okta with read-only access, or start with an external assessment; an Antigen expert plans the engagement and runs tCell; triage-agent and remediation-agent investigate and prepare fixes (pull requests with GitHub); after a fix is marked Remediated, tCell retests and moves it to Verified. Evidence includes HTTP requests and responses, screenshots or exploit recordings. No self-serve signup and no time estimate.Source
    • Your websiteEnterprise page: "Continuous offensive security without giving up control." HIPAA compliant; "An independent SOC 2 Type II audit is underway"; compliance-mapped findings for PCI DSS, NIST 800-171, ISO 27001 and CWE; procurement documents (DPA, MSA, security questionnaire responses, a named security contact); 30-day, 90-day or custom retention; 12 integrations including Jira, ServiceNow, Splunk and Tenable; a healthcare section on the proposed HIPAA Security Rule's annual penetration-testing requirement. Its "Visit the Trust Center" button links to antigen.sh/trust, which returned 404 Not Found on two checks on November 9, 2026; the Trust Center itself lives at trust.antigen.sh.Source
    • Competitor researchRivals' own homepages: XBOW, "Every finding is a working exploit", 200+ security teams, #1 on HackerOne, a Pricing page, free unlimited re-testing, SOC 2, ISO 27001 and ISO 42001; Horizon3.ai NodeZero, "Go hack yourself. Before they do.", 7,012 customers, a NodeZero Federal offering, 4.7 on Gartner Peer Insights; Cobalt, "Continuous Offensive Security Testing" with 500+ vetted testers, a usage-based credit model and a downloadable State of Pentesting 2026 report.Source
  • 06

    Healthcare is one of four industries on the homepage, Antigen is HIPAA compliant, a logo customer is a health company, and the Enterprise page already has a paragraph on the proposed HIPAA Security Rule's annual penetration-testing requirement, EHR-connected apps and HL7, FHIR and DICOM paths. But there is no healthcare page in the six-page sitemap. The proposed rule is not final (final action is now projected for July 2027), which gives teams a long runway to plan.

    Medium impactLow effort First result in 1 month Founder

    First action

    Move the Enterprise page's healthcare section into its own page.

    How to measure it

    Demos from /healthcare

    Now
    –
    Target
    3 a month
    By
    90 days

    Steps

    1. 1

      Draft from existing copy

      Expand the Enterprise healthcare section.

      Founder (CEO) 1 day

    2. 2

      Check the rule language

      Describe it as proposed, cite the HHS notice, no legal advice.

      Founder (CEO) 1 day

    3. 3

      Add healthcare paths

      FHIR, HL7, portals, EHR integrations.

      Security Researcher 1 day

    4. 4

      Add proof

      Healthcare customer quote or story.

      Founder (CEO) 1 week

    5. 5

      Publish

      Add to sitemap and homepage industry tile.

      Founding Engineer 1 day

    6. 6

      Promote

      LinkedIn posts to health-tech security leaders.

      Founder (CEO) ongoing

    First result
    1 month
    Cost
    $0
    Owner
    Founder (CEO)

    Smallest test

    Publish the page and send it to five health-tech prospects.

    Why it works

    Publish /healthcare from the existing Enterprise copy: what the proposed rule would require (stated as proposed), how continuous testing plus verified fixes produces the evidence, which healthcare paths tCell tests (EHR-connected apps, FHIR APIs, patient portals), the dedicated deployment for PHI-sensitive environments, and a healthcare customer story (idea 4). Offer a "readiness review" as the demo framing.

    A dedicated page ranks for healthcare-specific searches and gives health-tech champions something to forward to compliance teams.

    Risks and how to handle them

    • The rule changes or is withdrawn

      Lead with risk and evidence, not the deadline; update the page when HHS acts.

    Builds on

    Evidence

    • Your websiteEnterprise page: "Continuous offensive security without giving up control." HIPAA compliant; "An independent SOC 2 Type II audit is underway"; compliance-mapped findings for PCI DSS, NIST 800-171, ISO 27001 and CWE; procurement documents (DPA, MSA, security questionnaire responses, a named security contact); 30-day, 90-day or custom retention; 12 integrations including Jira, ServiceNow, Splunk and Tenable; a healthcare section on the proposed HIPAA Security Rule's annual penetration-testing requirement. Its "Visit the Trust Center" button links to antigen.sh/trust, which returned 404 Not Found on two checks on November 9, 2026; the Trust Center itself lives at trust.antigen.sh.Source
    • Industry researchHIPAA Security Rule proposed changes (NPRM): penetration tests at least every 12 months and vulnerability scans at least every six months for regulated entities; not final, with final action now projected for July 2027.Source
    • Your websiteSitemap (checked November 9, 2026): 6 URLs in total: /, /blog, /enterprise, /government, /privacy and /terms, last updated in August 2026. No pricing, case study, comparison, healthcare or financial-services pages.Source

This quarter 12

The core plays for the next three months.

  • 07

    Antigen has no pricing page and the only public "plans" page is the template's fake Free/Team/Enterprise matrix. Rivals give buyers a pricing signal: XBOW has a Pricing page and Cobalt explains a usage-based credit model. Security budgets are set annually, and a buyer who cannot tell whether Antigen costs $20k or $200k may not book a call.

    High impactMedium effort First result in 1 quarter Founder

    First action

    List the last ten deals and what drove each price.

    How to measure it

    Demos that reach proposal

    Now
    –
    Target
    +20%
    By
    1 quarter

    Steps

    1. 1

      Analyze deals

      Price drivers in recent contracts.

      Founder (CEO) 2 days

    2. 2

      Choose the unit

      Per target, per environment or per app.

      Founder (CEO) 1 day

    3. 3

      Write the page

      Drivers, inclusions, starting point, FAQ.

      Founder (CEO) 2 days

    4. 4

      Add the comparison

      Against two annual point-in-time tests.

      Founder (CEO) 1 day

    5. 5

      Publish

      Link from navigation and the demo page.

      Founding Engineer 1 day

    6. 6

      Review

      Win rate and deal size before and after.

      Founder (CEO) quarterly

    First result
    1 quarter
    Cost
    $0
    Owner
    Founder (CEO)

    Smallest test

    Add an "engagement and pricing" FAQ to the demo page.

    Why it works

    Publish /pricing that explains what drives price (number of targets or environments, managed vs dedicated deployment, testing frequency, the monthly human red-team assessment), what is always included (dedicated expert, retests, integrations, SSO and audit logs) and a "starting from" figure or typical range. Compare it plainly with the cost of two point-in-time pentests a year.

    Pricing transparency filters out poor-fit leads and lets champions start budgeting before the demo, which shortens cycles.

    Risks and how to handle them

    • Anchors enterprise deals low

      Show a starting point for managed and "contact us" for dedicated.

    Builds on

    Evidence

    • Your websiteSitemap (checked November 9, 2026): 6 URLs in total: /, /blog, /enterprise, /government, /privacy and /terms, last updated in August 2026. No pricing, case study, comparison, healthcare or financial-services pages.Source
    • Competitor researchRivals' own homepages: XBOW, "Every finding is a working exploit", 200+ security teams, #1 on HackerOne, a Pricing page, free unlimited re-testing, SOC 2, ISO 27001 and ISO 42001; Horizon3.ai NodeZero, "Go hack yourself. Before they do.", 7,012 customers, a NodeZero Federal offering, 4.7 on Gartner Peer Insights; Cobalt, "Continuous Offensive Security Testing" with 500+ vetted testers, a usage-based credit model and a downloadable State of Pentesting 2026 report.Source
    • Your websiteDocs index llms.txt (checked November 9, 2026): 176 entries. About 110 are real product docs (Asset Map, Runs, tCell, SDK, CLI with CI/CD integration, a "Pentest after a deployment" example, 21 integrations including GitLab, Jira, ServiceNow, Cursor Cloud and Devin, and an API reference). The other 65 are a help center from a template: "Compare plans" describes "Free, Team, and Enterprise tiers for this demo help center"; "Subprocessors" is an "Illustrative list of subprocessors for this demo" naming none; "EU data residency options in this demo help center"; plus pages on editor drafts, projects, keyboard shortcuts and Salesforce and HubSpot connectors. The help-center home shows unrendered code.Source
  • 08

    The homepage already has a sharp point-in-time vs continuous comparison (weeks of setup, a PDF two weeks later, retests 6-12 months later), but it is buried in the homepage and there are no comparison pages at all. Buyers shortlisting XBOW, Horizon3.ai or Cobalt search for exactly these comparisons.

    High impactMedium effort First result in 1 quarter Founder

    First action

    Turn the homepage comparison into its own page.

    How to measure it

    Comparison-page demos

    Now
    –
    Target
    5 a month
    By
    1 quarter

    Steps

    1. 1

      Pick rivals

      The three most seen in deals.

      Founder (CEO) 1 day

    2. 2

      Check facts

      Each rival's current site and docs.

      Founder (CEO) 2 days

    3. 3

      Write the continuous page

      From the homepage table.

      Founder (CEO) 2 days

    4. 4

      Write rival pages

      Fair tables and when to choose each.

      Founder (CEO) 1 week

    5. 5

      Legal check

      Trademarks and claims.

      Founder (CEO) 2 days

    6. 6

      Publish

      Add to sitemap and footer.

      Founding Engineer 1 day

    7. 7

      Refresh

      Every quarter.

      Founder (CEO) quarterly

    First result
    1 quarter
    Cost
    Founder time
    Owner
    Founder (CEO)

    Smallest test

    Publish the continuous vs point-in-time page first.

    Why it works

    Publish four pages: "Continuous vs point-in-time pentesting" (expanding the homepage table with a cost and coverage view), and fair comparisons with XBOW, Horizon3.ai NodeZero and Cobalt on what matters to Antigen's buyers: fixes delivered as pull requests, automatic retest, a dedicated human expert, self-hosted deployment and cross-tenant testing. Cite each rival's own site and date every page.

    Comparison searches are late-stage and high intent, and the pages also shape how AI assistants describe Antigen against better-known names.

    Risks and how to handle them

    • Out-of-date claims about rivals

      Cite sources and date each page.

    Evidence

    • Your websiteHomepage comparison: point-in-time pentesting means weeks of setup, a PDF report about two weeks later, patching left to your team and retesting 6-12 months later; continuous means easy onboarding, findings on a board in real time, pull requests opened by Antigen and immediate end-to-end retesting.Source
    • Competitor researchRivals' own homepages: XBOW, "Every finding is a working exploit", 200+ security teams, #1 on HackerOne, a Pricing page, free unlimited re-testing, SOC 2, ISO 27001 and ISO 42001; Horizon3.ai NodeZero, "Go hack yourself. Before they do.", 7,012 customers, a NodeZero Federal offering, 4.7 on Gartner Peer Insights; Cobalt, "Continuous Offensive Security Testing" with 500+ vetted testers, a usage-based credit model and a downloadable State of Pentesting 2026 report.Source
    • Your websiteSitemap (checked November 9, 2026): 6 URLs in total: /, /blog, /enterprise, /government, /privacy and /terms, last updated in August 2026. No pricing, case study, comparison, healthcare or financial-services pages.Source
  • 09

    The docs already include a CLI with a CI/CD integration guide and an SDK example called "Pentest after a deployment", and the Enterprise page promises triggering pentests from CI/CD (Buildkite, Jenkins, GitHub). That is a developer entry point most rivals do not lead with, but it lives only inside the docs.

    Medium impactMedium effort First result in 1 month Founding Engineer

    First action

    Turn the "Pentest after a deployment" example into a repo with an action.yml.

    How to measure it

    Share of customers running from CI

    Now
    –
    Target
    50%
    By
    2 quarters

    Steps

    1. 1

      Package the action

      From the SDK example and CLI.

      Founding Engineer 3 days

    2. 2

      Add GitLab

      A CI template for GitLab users.

      Founding Engineer 2 days

    3. 3

      Write the README

      Setup in five lines, sample output.

      Founding Engineer 1 day

    4. 4

      List in the Marketplace

      GitHub Marketplace listing.

      Founding Engineer 1 day

    5. 5

      Landing page and post

      "Pentest every release".

      Founder (CEO) 2 days

    6. 6

      Make it onboarding

      Default step for new customers.

      Founder & CTO ongoing

    First result
    1 month
    Cost
    About a week of engineering
    Owner
    Founding Engineer

    Smallest test

    Publish the repo and share it with existing customers.

    Why it works

    Package the existing example as a public GitHub Action (and GitLab CI template) listed in the GitHub Marketplace, with a README that shows a run starting after deploy and posting results to the pull request. Write a landing page and a blog post, and offer it as the default onboarding step for new customers.

    Marketplace listings and repos are found by the engineers who will champion Antigen, and a pipeline hook makes Antigen part of every release, which raises retention.

    Risks and how to handle them

    • Runs triggered against unapproved targets

      Only run against targets Antigen has already approved.

    Evidence

    • Your websiteDocs index llms.txt (checked November 9, 2026): 176 entries. About 110 are real product docs (Asset Map, Runs, tCell, SDK, CLI with CI/CD integration, a "Pentest after a deployment" example, 21 integrations including GitLab, Jira, ServiceNow, Cursor Cloud and Devin, and an API reference). The other 65 are a help center from a template: "Compare plans" describes "Free, Team, and Enterprise tiers for this demo help center"; "Subprocessors" is an "Illustrative list of subprocessors for this demo" naming none; "EU data residency options in this demo help center"; plus pages on editor drafts, projects, keyboard shortcuts and Salesforce and HubSpot connectors. The help-center home shows unrendered code.Source
    • Your websiteEnterprise page: "Continuous offensive security without giving up control." HIPAA compliant; "An independent SOC 2 Type II audit is underway"; compliance-mapped findings for PCI DSS, NIST 800-171, ISO 27001 and CWE; procurement documents (DPA, MSA, security questionnaire responses, a named security contact); 30-day, 90-day or custom retention; 12 integrations including Jira, ServiceNow, Splunk and Tenable; a healthcare section on the proposed HIPAA Security Rule's annual penetration-testing requirement. Its "Visit the Trust Center" button links to antigen.sh/trust, which returned 404 Not Found on two checks on November 9, 2026; the Trust Center itself lives at trust.antigen.sh.Source
  • 10

    Antigen's docs list integrations with coding-agent tools (Cursor Cloud and Devin) and a page on "Assigning to your own agents", so a confirmed finding can go straight to the team's coding agent and come back as a fix that tCell retests. This closes the loop that point-in-time pentests leave open, but it appears nowhere on the marketing site.

    Medium impactMedium effort First result in 1 quarter Founder & CTO

    First action

    Record the end-to-end loop on the demo app from idea 5.

    How to measure it

    Integration-sourced demos

    Now
    –
    Target
    3 a month
    By
    2 quarters

    Steps

    1. 1

      Record the loop

      Finding to Verified on the demo app.

      Founding Engineer 2 days

    2. 2

      Write integration pages

      One per tool, from the docs.

      Founder & CTO 3 days

    3. 3

      Pitch partners

      Directory listings and joint posts.

      Founder (CEO) 1 month

    4. 4

      Update the homepage

      Show the hand-off in the remediation section.

      Founding Engineer 1 day

    5. 5

      Measure

      Customers using agent hand-off and fix-to-verify time.

      Founder & CTO monthly

    6. 6

      Expand

      Add the next tool customers ask for.

      Founder & CTO quarterly

    First result
    1 quarter
    Cost
    Staff time only
    Owner
    Founder & CTO

    Smallest test

    Publish the video on X and LinkedIn and track demo clicks.

    Why it works

    Build one integration page per coding-agent tool showing the loop end to end (finding, hand-off, fix PR, retest, Verified), record a two-minute video, and pitch each tool's partnerships team for a joint post or integration-directory listing. Use the same story on the homepage remediation section.

    Teams already using coding agents are the most likely to accept automated fixes, and partner directories send qualified traffic at no cost.

    Risks and how to handle them

    • Automated fixes worry security teams

      Lead with the required human approval before merge.

    Builds on

    Evidence

    • Your websiteDocs index llms.txt (checked November 9, 2026): 176 entries. About 110 are real product docs (Asset Map, Runs, tCell, SDK, CLI with CI/CD integration, a "Pentest after a deployment" example, 21 integrations including GitLab, Jira, ServiceNow, Cursor Cloud and Devin, and an API reference). The other 65 are a help center from a template: "Compare plans" describes "Free, Team, and Enterprise tiers for this demo help center"; "Subprocessors" is an "Illustrative list of subprocessors for this demo" naming none; "EU data residency options in this demo help center"; plus pages on editor drafts, projects, keyboard shortcuts and Salesforce and HubSpot connectors. The help-center home shows unrendered code.Source
    • Your websiteQuick start: submit a target, which "the Antigen team reviews" for ownership or permission; connect AWS, Vercel or Okta with read-only access, or start with an external assessment; an Antigen expert plans the engagement and runs tCell; triage-agent and remediation-agent investigate and prepare fixes (pull requests with GitHub); after a fix is marked Remediated, tCell retests and moves it to Verified. Evidence includes HTTP requests and responses, screenshots or exploit recordings. No self-serve signup and no time estimate.Source
  • 11

    The Government page names three sectors (state and local government, public utilities, education), sells through Pursuit, a public-sector reseller, and supports cooperative purchasing and GovRAMP and FISMA reporting work. Public buyers need documents before meetings, and a reseller sells what it can forward.

    High impactMedium effort First result in 1 quarter Founder

    First action

    Ask the reseller which documents its buyers request most often.

    How to measure it

    Public-sector opportunities

    Now
    –
    Target
    5 a quarter
    By
    2 quarters

    Steps

    1. 1

      Ask the reseller

      Most-requested documents and objections.

      Founder (CEO) 1 day

    2. 2

      Write the overviews

      One per sector.

      Founder (CEO) 1 week

    3. 3

      Compile mappings

      Controls the page already claims, nothing more.

      Founder & CTO 1 week

    4. 4

      Assemble the kit

      Overview, security, mappings, sample report, answers.

      Founder (CEO) 3 days

    5. 5

      Train the reseller

      30-minute session and a recording.

      Founder (CEO) 1 day

    6. 6

      Publish on /government

      Request form per sector.

      Founding Engineer 1 day

    7. 7

      Review

      Opportunities and stalls each quarter.

      Founder (CEO) quarterly

    First result
    1 quarter
    Cost
    Founder time
    Owner
    Founder (CEO)

    Smallest test

    Send one sector kit to the reseller and track forwards.

    Why it works

    Create one kit per sector: a two-page overview, the security and deployment summary (dedicated on-premises option, SSO, SCIM, audit streaming), control mappings (NIST, CJIS, FERPA, CIRCIA as the page states), a sample report (idea 5), an accessibility statement (idea 18) and standard procurement answers. Host the kits on the Government page behind a simple request form, and train the reseller's team in a 30-minute session.

    Public-sector cycles are long and document-driven; a kit lets the reseller and the champion move without waiting on a five-person team.

    Risks and how to handle them

    • Mappings read as certifications

      Keep the page's own wording: support, not authorization.

    Builds on

    Evidence

    • Your websiteGovernment page: "Security testing built for government boundaries"; dedicated on-premises deployment as a Helm chart or container image; SSO, SCIM and audit streaming to Splunk, Sentinel and others; support for GovRAMP and FISMA reporting work (stated as not a certification); mapping to NIST, CJIS, FERPA and CIRCIA; sectors: state and local government, public utilities and education; procurement through Pursuit, a public-sector reseller, plus cooperative purchasing.Source
  • 12

    The Enterprise page says findings are compliance-mapped to PCI DSS, NIST 800-171, ISO 27001 and CWE, and every fix is retested to Verified. Auditors want exactly that: what was tested, what was found, what was fixed and proof it was retested. Today that value is a line on the Enterprise page.

    High impactMedium effort First result in 1 quarter Founder & CTO

    First action

    Ask three customers what their auditor asked for last time.

    How to measure it

    Evidence-pack exports

    Now
    –
    Target
    60% of customers
    By
    2 quarters

    Steps

    1. 1

      Interview customers

      What auditors requested.

      Founder (CEO) 1 week

    2. 2

      Design the pack

      Scope, findings, controls, fixes, retests.

      Founder & CTO 1 week

    3. 3

      Build the export

      From existing report data.

      Founding Engineer 3 weeks

    4. 4

      Expert sign-off

      Reviewed by the assigned expert.

      Security Researcher per pack

    5. 5

      Publish a sample

      Redacted, on a compliance page.

      Founder (CEO) 2 days

    6. 6

      Track renewals

      Renewal rate of pack users.

      Founder (CEO) quarterly

    First result
    1 quarter
    Cost
    About a month of engineering
    Owner
    Founder & CTO

    Smallest test

    Assemble one pack by hand for a customer's next audit.

    Why it works

    Add a one-click export per framework: scope, test dates, findings mapped to controls, remediation PRs and retest evidence, signed by the assigned Antigen expert. Market it as "your pentest evidence, always current" on a compliance page, and show a redacted sample.

    Compliance budgets are reliable, and a pack that replaces the annual pentest letter turns continuous testing into something the audit team asks to renew.

    Risks and how to handle them

    • Auditors reject automated evidence

      Include the human expert's review and signature.

    Evidence

    • Your websiteEnterprise page: "Continuous offensive security without giving up control." HIPAA compliant; "An independent SOC 2 Type II audit is underway"; compliance-mapped findings for PCI DSS, NIST 800-171, ISO 27001 and CWE; procurement documents (DPA, MSA, security questionnaire responses, a named security contact); 30-day, 90-day or custom retention; 12 integrations including Jira, ServiceNow, Splunk and Tenable; a healthcare section on the proposed HIPAA Security Rule's annual penetration-testing requirement. Its "Visit the Trust Center" button links to antigen.sh/trust, which returned 404 Not Found on two checks on November 9, 2026; the Trust Center itself lives at trust.antigen.sh.Source
    • Your websiteQuick start: submit a target, which "the Antigen team reviews" for ownership or permission; connect AWS, Vercel or Okta with read-only access, or start with an external assessment; an Antigen expert plans the engagement and runs tCell; triage-agent and remediation-agent investigate and prepare fixes (pull requests with GitHub); after a fix is marked Remediated, tCell retests and moves it to Verified. Evidence includes HTTP requests and responses, screenshots or exploit recordings. No self-serve signup and no time estimate.Source
  • 13

    The homepage promises "Run your first pentest in under 30 minutes", but the quick start involves a target review by the Antigen team and an expert planning the engagement, and gives no time estimate. Buyers comparing XBOW ("first validated findings within hours") will want to know how long from signature to first real finding.

    High impactMedium effort First result in 1 month Founder & CTO

    First action

    Pull timestamps for the last ten onboardings.

    How to measure it

    Signature to first validated finding

    Now
    –
    Target
    under 48 hours
    By
    1 quarter

    Steps

    1. 1

      Pull history

      Timestamps from the last ten onboardings.

      Founder & CTO 1 day

    2. 2

      Find the bottleneck

      Approval, access or scheduling.

      Founder & CTO 1 day

    3. 3

      Set an approval SLA

      Same business day target review.

      Security Researcher 1 week

    4. 4

      Scope template

      Pre-filled by deployment type.

      Founder & CTO 3 days

    5. 5

      Instrument

      Track each step automatically.

      Founding Engineer 1 week

    6. 6

      Publish the median

      Homepage and sales deck.

      Founder (CEO) 1 day

    First result
    1 month
    Cost
    Staff time only
    Owner
    Founder & CTO

    Smallest test

    Time the next three onboardings by hand.

    Why it works

    Instrument the onboarding path: contract signed, target submitted, target approved, first run started, first validated finding. Find the slowest step (usually target approval or access), add a same-day approval commitment and a pre-filled scope template, and then publish the median on the homepage and in sales decks.

    A fast first finding is the moment a new customer sees value; measuring it shortens onboarding and gives sales a credible, specific claim.

    Risks and how to handle them

    • Dedicated deployments are much slower

      Publish separate numbers for managed and dedicated.

    Evidence

    • Your websiteHomepage (checked November 9, 2026): H1 "Antigen is the defense factory that maps, exploits, and secures your entire attack surface." The offensive agent tCell chains exploits; "Every finding arrives with a reproducible exploit attached"; Antigen opens pull requests and retests each fix. Each customer gets "a dedicated security expert" and every report is reviewed by a researcher. Managed deployment: "Run your first pentest in under 30 minutes"; dedicated self-hosted workers on AWS, Azure, GCP or Kubernetes. Seven customer logos (Antimetal, Enzo Health, Orkes, Harper, Retell AI, Pursuit, Faye) and no written testimonials; industries listed: Technology, Financial Services, Healthcare, Government; no pricing; the only conversion path is "Book a 30m demo" on Cal.com. The sample board lists findings such as cross-tenant report access, an unsigned webhook endpoint, over-scoped CI tokens and sessions that stay valid after workspace removal.Source
    • Your websiteQuick start: submit a target, which "the Antigen team reviews" for ownership or permission; connect AWS, Vercel or Okta with read-only access, or start with an external assessment; an Antigen expert plans the engagement and runs tCell; triage-agent and remediation-agent investigate and prepare fixes (pull requests with GitHub); after a fix is marked Remediated, tCell retests and moves it to Verified. Evidence includes HTTP requests and responses, screenshots or exploit recordings. No self-serve signup and no time estimate.Source
    • Competitor researchRivals' own homepages: XBOW, "Every finding is a working exploit", 200+ security teams, #1 on HackerOne, a Pricing page, free unlimited re-testing, SOC 2, ISO 27001 and ISO 42001; Horizon3.ai NodeZero, "Go hack yourself. Before they do.", 7,012 customers, a NodeZero Federal offering, 4.7 on Gartner Peer Insights; Cobalt, "Continuous Offensive Security Testing" with 500+ vetted testers, a usage-based credit model and a downloadable State of Pentesting 2026 report.Source
  • 14

    Antigen's board tracks every finding from Open to Remediated to Verified, and each customer has a dedicated expert. But continuous testing gets quieter as the product works: fewer new criticals can look like less value at renewal. The proof is in the fixes verified, not the findings opened.

    High impactLow effort First result in 1 month Security Researcher

    First action

    Draft the template from one customer's last month of data.

    How to measure it

    Renewal rate

    Now
    –
    Target
    95%+
    By
    4 quarters

    Steps

    1. 1

      Draft the template

      One page, five numbers, three highlights.

      Security Researcher 2 days

    2. 2

      Pull the data

      From the vulnerability lifecycle.

      Founding Engineer 1 week

    3. 3

      Expert notes

      Two paragraphs from the assigned expert.

      Security Researcher monthly

    4. 4

      Send

      To the champion with a forward-ready version.

      Security Researcher monthly

    5. 5

      Automate

      Generate from the platform.

      Founding Engineer 1 month

    6. 6

      Use at renewal

      Twelve-month trend in the renewal deck.

      Founder (CEO) per renewal

    First result
    1 month
    Cost
    Expert time, then automated
    Owner
    Security Researcher

    Smallest test

    Send one hand-made summary to one customer this month.

    Why it works

    Send each customer a one-page monthly summary, written with their expert: exploitable paths closed and retested, median time from finding to verified fix, new attack surface discovered, and the human red-team highlights. Make it easy to forward to a CISO, CTO or board, and use the trend in renewal conversations.

    Security tools are renewed when leadership can see risk going down; a forwardable summary puts Antigen in front of the budget owner every month.

    Risks and how to handle them

    • Summaries reveal sensitive details when forwarded

      Keep the forwardable version to counts and trends.

    Evidence

    • Your websiteHomepage (checked November 9, 2026): H1 "Antigen is the defense factory that maps, exploits, and secures your entire attack surface." The offensive agent tCell chains exploits; "Every finding arrives with a reproducible exploit attached"; Antigen opens pull requests and retests each fix. Each customer gets "a dedicated security expert" and every report is reviewed by a researcher. Managed deployment: "Run your first pentest in under 30 minutes"; dedicated self-hosted workers on AWS, Azure, GCP or Kubernetes. Seven customer logos (Antimetal, Enzo Health, Orkes, Harper, Retell AI, Pursuit, Faye) and no written testimonials; industries listed: Technology, Financial Services, Healthcare, Government; no pricing; the only conversion path is "Book a 30m demo" on Cal.com. The sample board lists findings such as cross-tenant report access, an unsigned webhook endpoint, over-scoped CI tokens and sessions that stay valid after workspace removal.Source
    • Y CombinatorY Combinator profile: Fall 2025 batch, team of 5, San Francisco; backed by Lightspeed, DST Global and Susa Ventures. Describes "an AI adversary" that tests the attack surface nightly plus "monthly human red team assessments", with customers in "financial services, healthcare, retail, and government".Source
  • 15

    Antigen's customers are mostly software companies that sell to other companies' security teams, and many publish their own trust centers, just as Antigen does on Vanta. A line saying their product is continuously pentested, with fixes verified, helps them close their own deals and shows Antigen to every buyer who checks them.

    Medium impactLow effort First result in 1 quarter Founder

    First action

    Ask three customers whether they would display it.

    How to measure it

    Badge-referred demos

    Now
    –
    Target
    2 a month
    By
    2 quarters

    Steps

    1. 1

      Ask customers

      Would they show it, and where.

      Founder (CEO) 1 week

    2. 2

      Define the rules

      Active contract, recent retest, no open criticals past an agreed window.

      Founder & CTO 2 days

    3. 3

      Build the page

      Status page with dates only.

      Founding Engineer 1 week

    4. 4

      Design the badge

      Simple, links back.

      Founding Engineer 1 day

    5. 5

      Add a referral credit

      For customers who introduce peers.

      Founder (CEO) 1 day

    6. 6

      Track

      Referral traffic and demos.

      Founder (CEO) monthly

    First result
    1 quarter
    Cost
    About a week of engineering
    Owner
    Founder (CEO)

    Smallest test

    One customer adds a text line and link to its trust center.

    Why it works

    Offer customers an opt-in badge and a short verification page ("Continuously tested since <month>, last retest <date>") they can link from their trust center or security page, showing no findings. Each badge links back to Antigen. Pair it with a customer referral credit.

    It turns customers' security reviews into Antigen's distribution: the people reading are exactly the next buyers.

    Risks and how to handle them

    • A badge implies a guarantee

      State what it means: tested continuously, not "secure".

    Evidence

    • Your websiteTrust Center at trust.antigen.sh (run on Vanta) and a public status page at status.antigen.sh ("All systems operational"). The site's links include Docs, Blog, Trust Center, Status, X and LinkedIn; no newsletter signup was found.Source
    • Your websiteHomepage (checked November 9, 2026): H1 "Antigen is the defense factory that maps, exploits, and secures your entire attack surface." The offensive agent tCell chains exploits; "Every finding arrives with a reproducible exploit attached"; Antigen opens pull requests and retests each fix. Each customer gets "a dedicated security expert" and every report is reviewed by a researcher. Managed deployment: "Run your first pentest in under 30 minutes"; dedicated self-hosted workers on AWS, Azure, GCP or Kubernetes. Seven customer logos (Antimetal, Enzo Health, Orkes, Harper, Retell AI, Pursuit, Faye) and no written testimonials; industries listed: Technology, Financial Services, Healthcare, Government; no pricing; the only conversion path is "Book a 30m demo" on Cal.com. The sample board lists findings such as cross-tenant report access, an unsigned webhook endpoint, over-scoped CI tokens and sessions that stay valid after workspace removal.Source
  • 16

    Antigen's one open role, Security Researcher, exists to watch "how the agent chains attacks and where it gets stuck" and turn that into research. Buyers' biggest doubt about AI pentesting is what it misses, and the honest answer is exactly this researcher's job. Rivals publish wins; nobody publishes the limits.

    Medium impactLow effort First result in 2 months Security Researcher

    First action

    Agree with the new researcher that one note a month is part of the role.

    How to measure it

    Monthly research readers

    Now
    –
    Target
    2,000
    By
    2 quarters

    Steps

    1. 1

      Write it into the role

      One note a month.

      Founder & CTO 1 day

    2. 2

      Pick the first chain

      A completed and a stalled case.

      Security Researcher 1 day

    3. 3

      Write

      800 words, sanitized.

      Security Researcher 2 days

    4. 4

      Review

      Disclosure and accuracy.

      Founder & CTO 1 day

    5. 5

      Publish and share

      Blog, X, LinkedIn and security forums.

      Founder (CEO) 1 day

    6. 6

      Link to hiring

      From the careers page.

      Founder & CTO 1 hour

    First result
    2 months
    Cost
    Two researcher days a month
    Owner
    Security Researcher

    Smallest test

    Publish one note and compare engagement with the finding write-ups.

    Why it works

    Once a month, publish a short research note: one attack chain the agent completed, one where it stalled, what the human expert did, and what changed in the agent afterwards. Use the job post's language in the hiring pitch too: the research notes become the best recruiting material for the next researcher.

    Candor about limits builds trust with security practitioners, makes the human-in-the-loop model concrete, and gives the empty blog a steady research series.

    Risks and how to handle them

    • Competitors use the limits against Antigen

      Always pair a limit with the fix and the human step that covers it.

    Builds on

    Evidence

    • HiringSecurity Researcher (San Francisco, $150K-$220K, 0.5%-1.0% equity), the one open role: an "expert-in-the-loop" who deploys tCell into real environments, watches "how the agent chains attacks and where it gets stuck", and turns that into research that improves the agent.Source
    • Your websiteBlog (checked November 9, 2026): linked from the site and listed in the sitemap, it promises "Company updates, product thinking, and security research from the Antigen team" with filters for Product, Research, Company, Ideas and Customers, but shows 0 articles.Source
  • 17

    The homepage lists Financial Services as a target industry and the YC profile says customers include financial services and retail, but the site has pages only for Enterprise and Government. Retail is not mentioned on the site at all.

    Medium impactLow effort First result in 1 quarter Founder

    First action

    Draft the financial-services page from the Enterprise page's controls.

    How to measure it

    Industry-page demos

    Now
    –
    Target
    4 a month
    By
    2 quarters

    Steps

    1. 1

      List the paths

      Top attack paths per industry.

      Security Researcher 1 day

    2. 2

      Draft finance

      Controls, retention, audit, PCI DSS mapping.

      Founder (CEO) 2 days

    3. 3

      Draft retail

      Checkout and account paths.

      Founder (CEO) 2 days

    4. 4

      Add proof

      One write-up and one quote each.

      Founder (CEO) 2 weeks

    5. 5

      Publish

      Sitemap and homepage tiles.

      Founding Engineer 1 day

    6. 6

      Measure

      Demos by page.

      Founder (CEO) monthly

    First result
    1 quarter
    Cost
    $0
    Owner
    Founder (CEO)

    Smallest test

    Publish the finance page first.

    Why it works

    Publish /financial-services (audit trails, data retention, PCI DSS mapping, dedicated deployment) and /retail (checkout, loyalty and customer-account takeover paths, PCI DSS mapping), each with a relevant finding write-up and a customer quote. Add both to the homepage industry tiles.

    Industry pages rank for vertical searches and let champions forward something that speaks their regulator's language.

    Risks and how to handle them

    • Thin pages

      Publish only with a real write-up and quote.

    Evidence

    • Y CombinatorY Combinator profile: Fall 2025 batch, team of 5, San Francisco; backed by Lightspeed, DST Global and Susa Ventures. Describes "an AI adversary" that tests the attack surface nightly plus "monthly human red team assessments", with customers in "financial services, healthcare, retail, and government".Source
    • Your websiteSitemap (checked November 9, 2026): 6 URLs in total: /, /blog, /enterprise, /government, /privacy and /terms, last updated in August 2026. No pricing, case study, comparison, healthcare or financial-services pages.Source
  • 18

    The site is fast: real visitors pass Core Web Vitals (LCP 1.16 s, INP 73 ms, CLS 0) and mobile scores 97. The only gaps PageSpeed reports are accessibility: invalid aria attribute values and low colour contrast (score 92). Schools, utilities and agencies often ask vendors for accessibility documentation.

    Low impactLow effort First result in 1 week Founding Engineer

    First action

    Fix the two homepage issues.

    How to measure it

    Accessibility score

    Now
    –
    Target
    100
    By
    30 days

    Steps

    1. 1

      Fix aria

      Invalid aria attribute values.

      Founding Engineer 2 hours

    2. 2

      Fix contrast

      Adjust the low-contrast text colours.

      Founding Engineer 2 hours

    3. 3

      Check other pages

      Enterprise, Government, docs.

      Founding Engineer 1 day

    4. 4

      Check the platform

      Main dashboard screens.

      Founding Engineer 2 days

    5. 5

      Write the statement

      Standard, scope and contact.

      Founder (CEO) 1 day

    6. 6

      Link it

      Government page and procurement kit.

      Founding Engineer 1 hour

    First result
    1 week
    Cost
    $0
    Owner
    Founding Engineer

    Smallest test

    Re-run PageSpeed after the two fixes.

    Why it works

    Fix the aria values and contrast on the homepage, run the same check on the Enterprise and Government pages and the platform's main screens, and publish a short accessibility statement (and a VPAT when asked) linked from the Government page and the procurement kit (idea 11).

    Removing a small procurement blocker is cheap, and the speed advantage is already there.

    Risks and how to handle them

    • Design changes

      Adjust shades, not the palette.

    Evidence

    • PageSpeedHomepage, Google PageSpeed (November 2026): mobile performance 97, desktop 100, SEO 100, accessibility 92 with two issues (invalid aria attribute values and low colour contrast). Real visitors pass Core Web Vitals: LCP 1.16 s, INP 73 ms, CLS 0 at the 75th percentile.Source
    • Your websiteGovernment page: "Security testing built for government boundaries"; dedicated on-premises deployment as a Helm chart or container image; SSO, SCIM and audit streaming to Splunk, Sentinel and others; support for GovRAMP and FISMA reporting work (stated as not a certification); mapping to NIST, CJIS, FERPA and CIRCIA; sectors: state and local government, public utilities and education; procurement through Pursuit, a public-sector reseller, plus cooperative purchasing.Source

Big bets 3

Larger plays that can change the trajectory.

  • 19

    Today the only way in is "Book a 30m demo", and the quick start already supports starting with an external assessment before infrastructure is connected. Antigen also already reviews every target for ownership. A limited, self-serve external check (domain ownership verified by DNS) would let a prospect see one real, validated finding about their own app before talking to sales.

    High impactHigh effort First result in 2 quarters Founder & CTO

    First action

    Define the safe check set and the DNS verification flow.

    How to measure it

    Check-to-customer conversion

    Now
    –
    Target
    10%
    By
    3 quarters

    Steps

    1. 1

      Define safe scope

      External, non-destructive, rate-limited.

      Security Researcher 2 weeks

    2. 2

      Ownership verification

      DNS TXT record before any run.

      Founding Engineer 1 week

    3. 3

      Legal terms

      Authorization and acceptable use.

      Founder (CEO) 2 weeks

    4. 4

      Build the flow

      Verify, run, expert review, report.

      Founding Engineer 6 weeks

    5. 5

      Expert review

      Every report reviewed before sending.

      Security Researcher ongoing

    6. 6

      Pilot

      With 20 invited companies.

      Founder (CEO) 1 month

    7. 7

      Launch

      Homepage CTA next to the demo.

      Founder (CEO) 1 day

    First result
    2 quarters
    Cost
    A quarter of engineering plus compute and expert time
    Owner
    Founder & CTO

    Smallest test

    Offer a manual external check to ten demo no-shows.

    Why it works

    Build a gated-by-verification external check: the prospect verifies a domain, tCell maps the external surface and runs a small set of safe, non-destructive checks, and an expert reviews the top findings within 48 hours. The result is a short report with one or two validated issues and an offer for the full engagement. Hard limits on scope, rate and techniques; nothing runs against unverified targets.

    A real finding about the buyer's own system is the most persuasive demo possible, and it creates qualified pipeline from engineers who would never book a sales call first.

    Risks and how to handle them

    • Abuse against third parties

      Verified ownership only, strict limits and manual approval for the pilot.

    • Expert time does not scale

      Cap weekly checks and prioritize by company fit.

    Evidence

    • Your websiteQuick start: submit a target, which "the Antigen team reviews" for ownership or permission; connect AWS, Vercel or Okta with read-only access, or start with an external assessment; an Antigen expert plans the engagement and runs tCell; triage-agent and remediation-agent investigate and prepare fixes (pull requests with GitHub); after a fix is marked Remediated, tCell retests and moves it to Verified. Evidence includes HTTP requests and responses, screenshots or exploit recordings. No self-serve signup and no time estimate.Source
    • Your websiteHomepage (checked November 9, 2026): H1 "Antigen is the defense factory that maps, exploits, and secures your entire attack surface." The offensive agent tCell chains exploits; "Every finding arrives with a reproducible exploit attached"; Antigen opens pull requests and retests each fix. Each customer gets "a dedicated security expert" and every report is reviewed by a researcher. Managed deployment: "Run your first pentest in under 30 minutes"; dedicated self-hosted workers on AWS, Azure, GCP or Kubernetes. Seven customer logos (Antimetal, Enzo Health, Orkes, Harper, Retell AI, Pursuit, Faye) and no written testimonials; industries listed: Technology, Financial Services, Healthcare, Government; no pricing; the only conversion path is "Book a 30m demo" on Cal.com. The sample board lists findings such as cross-tenant report access, an unsigned webhook endpoint, over-scoped CI tokens and sessions that stay valid after workspace removal.Source
  • 20

    Cobalt anchors its brand with a downloadable State of Pentesting report. Antigen holds data nobody else publishes: which finding classes appear between releases, how long exploitable paths stay open, and how fast fixes move from Remediated to Verified when the PR is written for the team.

    High impactHigh effort First result in 2 quarters Security Researcher

    First action

    Decide the ten metrics and check the data supports them.

    How to measure it

    Report-sourced demos

    Now
    –
    Target
    30 in 90 days
    By
    3 quarters

    Steps

    1. 1

      Pick metrics

      Ten that the data supports.

      Security Researcher 1 week

    2. 2

      Get consent

      Aggregate use in contracts or opt-in.

      Founder (CEO) 1 month

    3. 3

      Analyze

      Anonymized and aggregated.

      Security Researcher 1 month

    4. 4

      Write and design

      Report and charts.

      Founder (CEO) 1 month

    5. 5

      Launch

      Webinar, press and social.

      Founder (CEO) 2 weeks

    6. 6

      Reuse

      Charts in sales and pages.

      Founder (CEO) ongoing

    First result
    2 quarters
    Cost
    Design and launch costs plus staff time
    Owner
    Security Researcher

    Smallest test

    Publish one chart from the data as a blog post.

    Why it works

    Publish an annual, anonymized and aggregated report: finding classes by industry, share found between releases, median days from finding to verified fix with and without automated PRs, and what the human red team found that the agent missed. Release it with a webinar and use the charts in sales and the comparison pages.

    Original data earns press, links and analyst attention, and it makes the find-fix-verify loop measurable in public.

    Risks and how to handle them

    • Small sample

      Report ranges, state sample size, and add more each year.

    Builds on

    Evidence

    • Competitor researchRivals' own homepages: XBOW, "Every finding is a working exploit", 200+ security teams, #1 on HackerOne, a Pricing page, free unlimited re-testing, SOC 2, ISO 27001 and ISO 42001; Horizon3.ai NodeZero, "Go hack yourself. Before they do.", 7,012 customers, a NodeZero Federal offering, 4.7 on Gartner Peer Insights; Cobalt, "Continuous Offensive Security Testing" with 500+ vetted testers, a usage-based credit model and a downloadable State of Pentesting 2026 report.Source
    • Y CombinatorY Combinator profile: Fall 2025 batch, team of 5, San Francisco; backed by Lightspeed, DST Global and Susa Ventures. Describes "an AI adversary" that tests the attack surface nightly plus "monthly human red team assessments", with customers in "financial services, healthcare, retail, and government".Source
  • 21

    The Government page is careful to say Antigen supports GovRAMP and FISMA reporting work but is not certified or authorized. Horizon3.ai sells a dedicated federal offering. For state and local buyers, a vendor's own authorization status often decides whether a deal can start; the dedicated deployment (Helm chart or container image inside the customer's network) may be the shortest path because data stays on the buyer's side.

    High impactHigh effort First result in 3 quarters Founder

    First action

    Ask the reseller which authorization its buyers require most often.

    How to measure it

    Public-sector ARR

    Now
    –
    Target
    a quarter of new ARR
    By
    4 quarters

    Steps

    1. 1

      Ask the market

      Required authorizations by buyer type.

      Founder (CEO) 2 weeks

    2. 2

      Map deployments

      Which authorization fits managed vs dedicated.

      Founder & CTO 2 weeks

    3. 3

      Finish SOC 2 Type II

      Base for later frameworks.

      Founder & CTO ongoing

    4. 4

      Pick an assessor

      Scope and cost.

      Founder (CEO) 1 month

    5. 5

      Design partners

      One or two agencies via the reseller.

      Founder (CEO) 1 quarter

    6. 6

      Publish status

      On the Trust Center.

      Founder (CEO) monthly

    First result
    3 quarters
    Cost
    Assessor fees and significant founder time
    Owner
    Founder (CEO)

    Smallest test

    Get a scoping quote from one assessor.

    Why it works

    Scope which deployment needs which authorization: the managed SaaS for GovRAMP, the dedicated deployment for agency-hosted use. Finish SOC 2 Type II first, then engage an assessor for the GovRAMP path with one or two design-partner agencies through the reseller. Publish the status on the Trust Center as it progresses.

    Authorization is a durable moat in public-sector sales and unlocks larger, multi-year contracts that fit continuous testing.

    Risks and how to handle them

    • Distracts a five-person team

      Only start with a committed design partner.

    Builds on

    Evidence

    • Your websiteGovernment page: "Security testing built for government boundaries"; dedicated on-premises deployment as a Helm chart or container image; SSO, SCIM and audit streaming to Splunk, Sentinel and others; support for GovRAMP and FISMA reporting work (stated as not a certification); mapping to NIST, CJIS, FERPA and CIRCIA; sectors: state and local government, public utilities and education; procurement through Pursuit, a public-sector reseller, plus cooperative purchasing.Source
    • Competitor researchRivals' own homepages: XBOW, "Every finding is a working exploit", 200+ security teams, #1 on HackerOne, a Pricing page, free unlimited re-testing, SOC 2, ISO 27001 and ISO 42001; Horizon3.ai NodeZero, "Go hack yourself. Before they do.", 7,012 customers, a NodeZero Federal offering, 4.7 on Gartner Peer Insights; Cobalt, "Continuous Offensive Security Testing" with 500+ vetted testers, a usage-based credit model and a downloadable State of Pentesting 2026 report.Source
    • Your websiteEnterprise page: "Continuous offensive security without giving up control." HIPAA compliant; "An independent SOC 2 Type II audit is underway"; compliance-mapped findings for PCI DSS, NIST 800-171, ISO 27001 and CWE; procurement documents (DPA, MSA, security questionnaire responses, a named security contact); 30-day, 90-day or custom retention; 12 integrations including Jira, ServiceNow, Splunk and Tenable; a healthcare section on the proposed HIPAA Security Rule's annual penetration-testing requirement. Its "Visit the Trust Center" button links to antigen.sh/trust, which returned 404 Not Found on two checks on November 9, 2026; the Trust Center itself lives at trust.antigen.sh.Source

Wildcards 2

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

  • 22

    Antigen's integrations read like a modern startup stack (Vercel, Supabase, Railway, Clerk, Tailscale, n8n), its logos are mostly young software companies, and it is itself a Y Combinator company. Startups ship daily, often have their first enterprise customer asking for a pentest, and are found together in accelerator networks. The enterprise-led site does not speak to them.

    Medium impactMedium effort First result in 1 quarter Founder

    First action

    Offer the track to ten startups in founder networks Antigen belongs to.

    How to measure it

    Startup-track signings

    Now
    –
    Target
    15
    By
    2 quarters

    Steps

    1. 1

      Define the package

      Fixed scope, fixed price, pentest letter.

      Founder (CEO) 1 week

    2. 2

      Integration onboarding

      Vercel, Supabase, Railway, Clerk first.

      Founding Engineer 2 weeks

    3. 3

      Write the guide

      Pentest before your first enterprise deal.

      Founder (CEO) 1 week

    4. 4

      Perks listings

      Accelerator and cloud perks programs.

      Founder (CEO) 1 month

    5. 5

      Pilot

      Ten startups.

      Founder (CEO) 1 month

    6. 6

      Measure expansion

      Upgrade to continuous within six months.

      Founder (CEO) quarterly

    First result
    1 quarter
    Cost
    Discounted engagements and staff time
    Owner
    Founder (CEO)

    Smallest test

    Sell five startup-track engagements by hand.

    Why it works

    Launch a startup track: a fixed-scope managed engagement for seed to Series A companies, connected through the startup-stack integrations, with a pentest letter for their first enterprise security review and continuous testing after. Distribute it through accelerator perks programs and founder communities, and publish a "pentest before your first enterprise deal" guide.

    Startups decide fast, grow into larger contracts, and become the logo wall; the integrations to win them already exist.

    Risks and how to handle them

    • Expert time spent on small accounts

      Fixed scope and capped expert hours.

    Evidence

    • Your websiteHomepage integrations: Amazon Web Services, Railway, Vercel, Astro, Clerk, Okta, GitHub, Linear, n8n, Tailscale and Supabase, connected to build a live map of exposed assets.Source
    • Your websiteHomepage (checked November 9, 2026): H1 "Antigen is the defense factory that maps, exploits, and secures your entire attack surface." The offensive agent tCell chains exploits; "Every finding arrives with a reproducible exploit attached"; Antigen opens pull requests and retests each fix. Each customer gets "a dedicated security expert" and every report is reviewed by a researcher. Managed deployment: "Run your first pentest in under 30 minutes"; dedicated self-hosted workers on AWS, Azure, GCP or Kubernetes. Seven customer logos (Antimetal, Enzo Health, Orkes, Harper, Retell AI, Pursuit, Faye) and no written testimonials; industries listed: Technology, Financial Services, Healthcare, Government; no pricing; the only conversion path is "Book a 30m demo" on Cal.com. The sample board lists findings such as cross-tenant report access, an unsigned webhook endpoint, over-scoped CI tokens and sessions that stay valid after workspace removal.Source
    • Y CombinatorY Combinator profile: Fall 2025 batch, team of 5, San Francisco; backed by Lightspeed, DST Global and Susa Ventures. Describes "an AI adversary" that tests the attack surface nightly plus "monthly human red team assessments", with customers in "financial services, healthcare, retail, and government".Source
  • 23

    Antigen runs its own Trust Center on Vanta, maps findings to PCI DSS, NIST 800-171 and ISO 27001, and is going through SOC 2 Type II itself. Auditors, compliance-platform partner networks and fractional CISOs are constantly asked by clients "who should do our pentest?" They are an existing referral market that does not need Antigen to build demand.

    Medium impactMedium effort First result in 2 quarters Founder

    First action

    Ask Antigen's own auditor how their clients choose a pentest vendor.

    How to measure it

    Partner referrals

    Now
    –
    Target
    6 a quarter
    By
    3 quarters

    Steps

    1. 1

      Ask your own auditor

      How clients source pentests.

      Founder (CEO) 1 week

    2. 2

      List partners

      Ten audit firms and vCISO firms.

      Founder (CEO) 1 week

    3. 3

      Design the offer

      Referral fee or client discount.

      Founder (CEO) 3 days

    4. 4

      Auditor-ready pack

      From idea 12.

      Founder & CTO 2 weeks

    5. 5

      Partner page

      Terms and a referral form.

      Founding Engineer 2 days

    6. 6

      Brief partners

      Quarterly session.

      Founder (CEO) quarterly

    First result
    2 quarters
    Cost
    Referral fees on closed deals
    Owner
    Founder (CEO)

    Smallest test

    Sign two vCISO partners and track referrals for a quarter.

    Why it works

    Build a partner program for audit firms, compliance-automation partner networks and vCISO firms: a partner page, a referral fee or client discount, the evidence pack (idea 12) formatted for auditors, and a quarterly partner briefing. Start by asking Antigen's own SOC 2 auditor and compliance platform how their clients currently source pentests.

    Partners recommend at the moment of need, and continuous testing with verified fixes makes their audits easier, so the referral helps both sides.

    Risks and how to handle them

    • Auditor independence concerns

      Keep referrals separate from the audit relationship and disclose any fees.

    Builds on

    Evidence

    • Your websiteTrust Center at trust.antigen.sh (run on Vanta) and a public status page at status.antigen.sh ("All systems operational"). The site's links include Docs, Blog, Trust Center, Status, X and LinkedIn; no newsletter signup was found.Source
    • Your websiteEnterprise page: "Continuous offensive security without giving up control." HIPAA compliant; "An independent SOC 2 Type II audit is underway"; compliance-mapped findings for PCI DSS, NIST 800-171, ISO 27001 and CWE; procurement documents (DPA, MSA, security questionnaire responses, a named security contact); 30-day, 90-day or custom retention; 12 integrations including Jira, ServiceNow, Splunk and Tenable; a healthcare section on the proposed HIPAA Security Rule's annual penetration-testing requirement. Its "Visit the Trust Center" button links to antigen.sh/trust, which returned 404 Not Found on two checks on November 9, 2026; the Trust Center itself lives at trust.antigen.sh.Source
More example playbooks and reviews

More growth playbooks

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

  • Susan Shaw growth strategyA San Antonio jewellery brand founded in 1979 that designs and hand-makes 24K gold and sterling silver plated jewellery (necklaces…21 growth ideas
  • Multiplier growth strategyAn agent platform for fundamental equity investors. Multiplier runs in each fund's own cloud and connects AI agents to the fund's data…23 growth ideas
  • Outro Health growth strategyA virtual clinic for tapering off antidepressants with licensed clinicians, using hyperbolic tapering co-developed by co-founder Dr. Mark…21 growth ideas
  • befree growth strategyMakes zipOns, patented adaptive pants and shorts with full-length zippers on both legs that open from waist to hem, for dressing while…22 growth ideas
  • Boulevard growth strategyA client experience platform for appointment-based self-care businesses: booking and Precision Scheduling, POS and payments, marketing…22 growth ideas
  • Flying Tiger Copenhagen growth strategyA Danish variety retailer of playful, low-priced design products (home, party, Christmas, crafts, toys, school and office, food) sold in…22 growth ideas
  • Gusto growth strategyPayroll, benefits, 401(k), HR and compliance software for small businesses, sold directly, through accountants (Gusto Pro) and embedded in…21 growth ideas
  • Zeta Global growth strategyAn AI marketing cloud (NYSE: ZETA): the Zeta Data Cloud and identity graph, the Zeta Marketing Platform (CDP, email and messaging…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. Antigen did not commission, review or endorse it, and Programmable is not affiliated with Antigen. 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 Antigen runs its business.

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

    Clean up diligence surfaces (docs template pages, Trust Center link), fill the blog with finding write-ups, publish customer proof, a sample report and a healthcare page.

  2. Days 31 to 6012 ideas

    Pricing signal, comparison pages, pipeline and coding-agent entry points, reseller kit, compliance evidence packs, time to first finding, verified-fix reporting, customer badges, research notes, finance and retail pages, accessibility.

  3. Days 61 to 905 ideas

    Commit to the big bets and wildcards: a self-serve external check, an annual findings report, a public-sector authorization path, a startup motion and an auditor partner channel.

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 findings that arrive with a reproducible exploit, not scanner noise. The most cited problem: point-in-time pentests that take weeks to set up and are stale by the next release.

  • Fixes delivered as pull requests and retested automatically
  • Patching left to the team, with retests 6-12 months later
  • In their words: “attack surface”

Market

Competitive landscape

3 competitors compared: XBOW, Horizon3.ai (NodeZero) and Cobalt.

  • Gap to exploit: Find, fix and verify in one loop, with fixes delivered as pull requests
  • XBOW: Less emphasis on writing and merging fixes
  • Horizon3.ai (NodeZero): Network and infrastructure heritage rather than app and cross-tenant testing

Hiring signals

Antigen is a five-person team with one open role, a Security Researcher who works "expert-in-the-loop": deploying tCell into real environments, watching where it gets stuck and turning that into research.

  • Security Researcher: Expert-in-the-loop research on where the agent gets stuck. Ideas 3, 14, 16, 20.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks first (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence