ProgrammableMarketing/casco.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 · 4
  • This quarter · 14
  • Big bets · 3
  • Wildcards · 2
Generated Nov 10, 2026
  1. Programmable
  2. Playbooks
  3. Casco
Casco logo

growth playbook · Nov 10, 2026

casco.com (opens in a new tab)

Casco growth playbook

Diagnosis

Casco is a young, well-funded AI pentesting company ($100M-valuation Series A in July 2026, 400+ companies tested, FedRAMP 20x Class A) that is now building its go-to-market from scratch: its first Technical AE, SDR and Growth Engineer, plus a Product Engineer and Customer Success Engineer for onboarding.

The product story is strong; the funnel around it is thin. Every buying button ends in the same six-field form with no calendar, the sample report has no page of its own, there is no pricing guidance, one customer story and no numbers on it, and the content hub ranks Casco first in its own lists.

This playbook fixes the booking path, proof and pricing first, then builds the loops a security company can own: research for Hacker News and Reddit, the free CVE MCP as a funnel, retest-window upsells, compliance-trigger pages, partners and a shareable "Tested by Casco" page.

Growth Score

7/10

Biggest Opportunity

Turn buyer intent Casco already captures (demo clicks, CVE MCP users, research readers, partner referrals) into booked meetings and continuous contracts, with proof a skeptical AppSec leader can check.

Biggest Risk

XBOW, Cobalt and Horizon3.ai sell the same promise of validated findings with larger customer counts, and self-promotional content or unsourced numbers can cost trust with exactly the expert buyers Casco needs.

01

Start here

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

  1. 1

    Turn the one-step "Continue" demo form into a routed booking page: security leaders pick a time, everyone else gets the right next step

    Pull last quarter's demo submissions by role and measure the time from "Continue" to a booked meeting.

    High impact First result in 2 weeks
  2. 2

    Give the sample pentest report its own page and put it in every follow-up

    Move the existing sample report to its own URL and add it to the sitemap.

    High impact First result in 2 weeks
  3. 3

    Put a source and date under every homepage number, starting with "400+ trusted companies"

    List every number on the homepage and who can back it.

    Medium impact First result in 1 week

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

Showing 23 of 23 ideas

This week 4

Quick wins with a clear first action.

  • 01

    Almost every buying button on casco.com (the header's "Book a demo", Supervised's "Schedule a pentest", "See an AI pentest", the partner perks and the reseller page's "Bring us a customer") lands on the same page: six fields and a "Continue" button, with no calendar, no customer proof and no word on what happens next. The site removed its Google appointment schedule in the last year. Yet the form already asks the one question needed to route: role. A CISO, a practitioner, a would-be reseller and a "Personal interest" visitor all get the same treatment, while the new SDR and Technical AE are hired to create the right meetings fast.

    High impactLow effort First result in 2 weeks Growth Engineer

    First action

    Pull last quarter's demo submissions by role and measure the time from "Continue" to a booked meeting.

    How to measure it

    Submit-to-meeting rate (buyer roles)

    Now
    –
    Target
    +30%
    By
    60 days

    Steps

    1. 1

      Baseline

      Submissions by role and source button, and time to a booked meeting.

      Sales Development Representative 2 days

    2. 2

      Tag the source

      Pass the clicked button (demo, pentest, AI pentest, partner, reseller) into a hidden field.

      Growth Engineer 1 day

    3. 3

      Add the calendar

      Embedded scheduler for the two buyer roles, round-robin across the Technical AE and founders.

      Growth Engineer 2 days

    4. 4

      Route everyone else

      Practitioners get the sample report and a calendar; partners a partner call; "Personal interest" the newsletter and CVE MCP.

      Growth Engineer 2 days

    5. 5

      Show what happens next

      Three steps, three logos and one quote beside the form.

      Product Engineer 1 day

    6. 6

      Confirm with prep

      Confirmation email asking for target URLs and a test-account plan before the call.

      Sales Development Representative 1 day

    7. 7

      Measure

      Meetings held by role and source each week.

      Growth Engineer weekly

    First result
    2 weeks
    Cost
    A scheduler licence and a few days of engineering
    Owner
    Growth Engineer

    Smallest test

    Show a calendar only to "CISO or security team leader" for two weeks and compare the meeting rate with the previous two weeks.

    Why it works

    Keep the six fields, then branch. "CISO or security team leader" and "Executive responsible for security purchasing" see a calendar right away for a 20-minute scope call with the Technical AE. "Security practitioner evaluating tools" sees the calendar plus the sample report and a short "what to bring" note (a target and test accounts). Visitors arriving from partner or reseller buttons go to a partner call. "Personal interest" goes to the newsletter and the free CVE MCP instead of the sales queue. Beside the form, add three steps (scope call, approve targets and test accounts, a human-approved report within five business days), three customer logos and the customer quote that Casco is "mission-critical for enterprise deals". Pass the clicked button into the CRM so every meeting has a source.

    Security leaders who can book a slot while the problem is on their mind do not go cold waiting for an email, and routing keeps AE time for buyers. Showing the five-business-day promise next to the form answers the first question a buyer with an audit deadline has.

    Ready to use

    ChecklistRouted demo page launch list

    [ ] Hidden source field on every Book a demo / Schedule a pentest / partner / reseller button
    [ ] Calendar for CISO / security leader and purchasing executive roles
    [ ] Calendar + sample report for practitioners
    [ ] Partner call link for partner and reseller sources
    [ ] Newsletter + CVE MCP for Personal interest
    [ ] Three-step 'what happens next' block
    [ ] Three logos and one customer quote
    [ ] Confirmation email asking for targets and test accounts
    [ ] Weekly report: meetings held by role and source

    Risks and how to handle them

    • Unqualified visitors book AE time

      Show the calendar only for buyer roles with a work-email domain.

    • Founder calendars overflow

      Use 20-minute scope slots and round-robin.

    Evidence

    • Your websiteDemo page: "Tell us about your role and organization to get started." Six fields (first name, last name, email, role, organization, company website) and a "Continue" button; roles offered are "CISO or security team leader", "Security practitioner evaluating tools for my team", "Executive responsible for security purchasing", "Another role" and "Personal interest". No calendar, no customer proof and no description of what happens next. The header's "Book a demo", Supervised's "Schedule a pentest", "See an AI pentest", the partner perks and the reseller page's "Bring us a customer" all lead here.Source
    • Site historyChanges to casco.com since November 16, 2025: Google Analytics and Google Tag Manager added; the Google appointment schedule removed; headline changed from "Autonomous Security Testing" to "Security that understands the software you ship."Source
    • HiringTechnical Account Executive ($350,000 OTE): "Run the full sales cycle from first touch to close" in a "messy early sales motion building" phase, selling to AppSec leaders and CISOs. Sales Development Representative ($120,000 OTE, San Francisco): account-specific outreach "across email, phone, LinkedIn, and other channels", security events with fast follow-up; "You would rather create the right meeting than hit a vanity activity number."Source
    • Your websiteHomepage (checked November 9, 2026): "Security that understands the software you ship."; stats "400+ trusted companies", "99%+ true positive rate", "5.8× better price-performance vs. frontier models", "68% of high/critical findings required signed-in access" and "90% more findings with source code connected"; pricing "depends on scope and the frequency of product changes. Book a demo to learn more."; human-approved pentests within five business days; logos include Microsoft, Gusto, Substack, CrewAI and Baseten; a customer CEO's quote: "Casco is mission-critical for enterprise deals."Source
  • 02

    Casco's own buyer guide tells buyers to read a redacted sample finding before picking a quote, and the homepage, Supervised and enterprise pages all point to a sample pentest report. But the report is reached through a homepage anchor, not a page of its own, and is not in the sitemap, so it cannot be found in search, linked cleanly in SDR outreach or measured.

    High impactLow effort First result in 2 weeks Growth Engineer

    First action

    Move the existing sample report to its own URL and add it to the sitemap.

    How to measure it

    Sample-report-to-meeting rate

    Now
    –
    Target
    10% of identified viewers
    By
    60 days

    Steps

    1. 1

      Give it a URL

      /sample-report with its own title and description.

      Growth Engineer 1 day

    2. 2

      Walk one finding

      Impact, proof, fix, retest and remediation report.

      Offensive Security Engineer 2 days

    3. 3

      Add the optional ask

      Work email for a stack-specific sample.

      Growth Engineer 1 day

    4. 4

      Link everywhere

      Solution pages, buyer guide, demo confirmation.

      Growth Engineer 1 day

    5. 5

      Use in outreach

      SDR sequences open with the sample.

      Sales Development Representative ongoing

    6. 6

      Measure

      Views, downloads and meetings by source.

      Growth Engineer weekly

    First result
    2 weeks
    Cost
    Staff time only
    Owner
    Growth Engineer

    Smallest test

    Send the sample link in the next 20 SDR emails and compare reply rates.

    Why it works

    Publish /sample-report: one redacted finding walked through end to end (impact, reproduction evidence, fix guidance, the retest and the remediation report that keeps the original finding), with the full PDF ungated and an optional work-email field for "a sample scoped to your stack". Link it from the demo confirmation, SDR sequences, the five-things buyer guide and every solution page.

    The report is the product a pentest buyer actually receives; showing it early answers the quality question before the call and gives the SDR a useful reason to reach out.

    Risks and how to handle them

    • Competitors copy the format

      The format is not the moat; the proof and retest are.

    Evidence

    • Your websiteBlog, "5 things to compare before choosing a pentest quote": compare scope, testing approach, a redacted sample finding, schedule, and remediation and retesting ("The work between those two points is part of what you are paying for"); no price ranges; ends with "Book a Casco walkthrough".Source
    • Your websiteEnterprise page: tests production through existing controls with dedicated identities; SSO via Okta, Microsoft Entra ID, Google Workspace and Auth0; source IPs and request IDs for SOC verification; links to the Trust Center and sample pentest report; no customer names or case studies on the page.Source
    • Your websiteSitemap (127 URLs, checked November 9, 2026): eight solution pages organised by what is tested (AI, web app, API, cloud, mobile, AI agent and network pentesting, plus vulnerability prioritization); 39 blog posts, of which one is a customer story (CrewAI) and seven are CVE remediation guides; no pricing page, no customers index, no sample report page and no "Casco vs" pages; two free tools (CVSS and bug bounty calculators); RSAC and Black Hat event pages; partner and reseller pages.Source
  • 03

    The homepage says "400+ trusted companies", while the Series A post says Casco "found critical vulnerabilities in 400+ companies"; those are different claims. "99%+ true positive rate" and "5.8× better price-performance vs. frontier models" show no method. Casco's buyers are skeptical AppSec leaders (the AE interview includes a pitch to one), and the brand sells reproducible proof.

    Medium impactLow effort First result in 1 week Growth Engineer

    First action

    List every number on the homepage and who can back it.

    How to measure it

    Proof objections per 10 calls

    Now
    –
    Target
    -50%
    By
    60 days

    Steps

    1. 1

      List the numbers

      Homepage, enterprise and solution pages.

      Growth Engineer 1 hour

    2. 2

      Find the source

      Query, sample and period for each.

      Software Engineer 1 day

    3. 3

      Pick the 400+ wording

      Customers or companies tested, not both.

      Technical Account Executive 1 hour

    4. 4

      Write /methods

      One paragraph per number.

      Offensive Security Engineer 1 day

    5. 5

      Add footnotes

      Under each stat.

      Growth Engineer 2 hours

    6. 6

      Align collateral

      Deck, careers pages, outreach.

      Sales Development Representative 1 day

    First result
    1 week
    Cost
    $0
    Owner
    Growth Engineer

    Smallest test

    Footnote the 400+ and 99%+ stats today.

    Why it works

    Add a one-line footnote to each stat (definition, sample, period), link a short /methods page, and choose one wording for the 400+ figure (customers, or companies tested). Use the same wording in the deck, job posts and outreach.

    A sourced number survives a skeptical reader and an AI summary; an unsourced one invites the first objection on the call.

    Risks and how to handle them

    • Some numbers shrink once defined

      A smaller, defined number is more persuasive to this buyer than a larger vague one.

    Evidence

    • Your websiteHomepage (checked November 9, 2026): "Security that understands the software you ship."; stats "400+ trusted companies", "99%+ true positive rate", "5.8× better price-performance vs. frontier models", "68% of high/critical findings required signed-in access" and "90% more findings with source code connected"; pricing "depends on scope and the frequency of product changes. Book a demo to learn more."; human-approved pentests within five business days; logos include Microsoft, Gusto, Substack, CrewAI and Baseten; a customer CEO's quote: "Casco is mission-critical for enterprise deals."Source
    • Your websiteSeries A post (July 13, 2026): a "$100M valuation Series A" led by Standard Capital with FundersClub, Y Combinator and Rebel Fund, bringing total funding to $17M; Casco "already found critical vulnerabilities in 400+ companies"; Standard Capital's general partner, formerly Stripe's head of security: "Casco is the tool I wish I'd had at Stripe."Source
    • HiringTechnical Account Executive ($350,000 OTE): "Run the full sales cycle from first touch to close" in a "messy early sales motion building" phase, selling to AppSec leaders and CISOs. Sales Development Representative ($120,000 OTE, San Francisco): account-specific outreach "across email, phone, LinkedIn, and other channels", security events with fast follow-up; "You would rather create the right meeting than hit a vanity activity number."Source
  • 04

    Real visitors already see the main content quickly (LCP 2.2 s), but the homepage fails Core Web Vitals on responsiveness (INP 240 ms against a 200 ms target). It weighs 11.1 MB across 110 requests, and Google Tag Manager alone loads 830 KB and blocks the main thread for 872 ms. Analytics and Tag Manager were added in the last year, alongside ad and social pixels.

    Medium impactLow effort First result in 1 month Software Engineer

    First action

    Export the Tag Manager container and list each tag's owner.

    How to measure it

    Homepage INP (p75)

    Now
    –
    Target
    under 200 ms
    By
    60 days

    Steps

    1. 1

      Inventory tags

      Nine services, owner and purpose.

      Growth Engineer 1 day

    2. 2

      Remove duplicates

      Tags without an owner or doing the same job.

      Growth Engineer 1 day

    3. 3

      Delay pixels

      Load marketing pixels after interaction.

      Software Engineer 1 day

    4. 4

      Trim JavaScript

      Unused and legacy bundles.

      Software Engineer 2 days

    5. 5

      Compress images

      Modern formats and sizes.

      Software Engineer 1 day

    6. 6

      Re-test

      PageSpeed now, field data in four weeks.

      Software Engineer 4 weeks

    First result
    1 month
    Cost
    Engineering time
    Owner
    Software Engineer

    Smallest test

    Delay the ad pixels for a week and compare INP and conversions.

    Why it works

    List the nine third-party services with an owner and purpose for each; remove any nobody owns or that duplicate another tool; load the remaining marketing pixels after the first interaction; trim unused JavaScript (about 569 KB) and compress images (about 499 KB). Re-test with PageSpeed and watch the field INP.

    A security buyer's first click should feel instant, and a smaller tag set is easier to own and audit.

    Risks and how to handle them

    • Attribution data drops

      Check conversions in analytics before and after each removal.

    Evidence

    • PageSpeedHomepage, November 9, 2026: mobile performance 52, desktop 73; accessibility and SEO 100; lab LCP 3.8 s; 11.1 MB across 110 requests; Google Tag Manager loads 830 KB with 872 ms of main-thread blocking; nine third-party services including ad and social pixels; savings available from unused JavaScript (about 569 KB) and images (about 499 KB). Real visitors: LCP 2.2 s (good) but INP 240 ms, so the page fails Core Web Vitals on responsiveness.Source
    • Site historyChanges to casco.com since November 16, 2025: Google Analytics and Google Tag Manager added; the Google appointment schedule removed; headline changed from "Autonomous Security Testing" to "Security that understands the software you ship."Source

This quarter 14

The core plays for the next three months.

  • 05

    Casco has no pricing page: the homepage says pricing "depends on scope and the frequency of product changes", Supervised says it is "based on the scope of the test", and even the buyer guide on comparing pentest quotes gives no ranges. Casco already writes about "predictable priced pentesting", and Cobalt shows buyers a credit model. A team with an audit deadline wants a budget number before a call.

    High impactMedium effort First result in 1 month Technical Account Executive

    First action

    Pull the last 20 closed deals and group them into three scope bands.

    How to measure it

    Pricing-page meetings

    Now
    –
    Target
    25 a month
    By
    90 days

    Steps

    1. 1

      Group past deals

      Three scope bands from closed deals.

      Technical Account Executive 2 days

    2. 2

      Agree the drivers

      What moves the price and by how much.

      Technical Account Executive 2 days

    3. 3

      Write the examples

      Three scopes, bands and inclusions.

      Growth Engineer 3 days

    4. 4

      Build the scope form

      Inputs passed to the CRM.

      Growth Engineer 3 days

    5. 5

      Publish and link

      From homepage, Supervised and the buyer guide.

      Growth Engineer 1 day

    6. 6

      Review quarterly

      Bands against new deals.

      Technical Account Executive quarterly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Technical Account Executive

    Smallest test

    Add one example scope with a price band to the Supervised page.

    Why it works

    Publish /pricing with the drivers (number of apps and APIs, roles and test accounts, cloud and network scope, how often you ship, supervised or autonomous) and three worked examples, for example a seed-stage SaaS before SOC 2, a Series B with an API and mobile app, and an enterprise with continuous testing, each with a price band and what is included (retest window, attestation letter). Add a short scope form that hands the inputs to the AE.

    Ranges qualify buyers before the call and remove the fear of an open-ended quote; competitors that hide prices make Casco's openness a difference.

    Risks and how to handle them

    • Anchoring big deals low

      Show bands with clear drivers, and a separate enterprise row.

    Evidence

    • Your websiteCasco Supervised: "Our pentest pricing is based on the scope of the test."; reports "Within 5 business days latest", or "within a few business hours for a rush fee"; free retesting for 90 days by default, longer at extra cost; remediation reports keep original findings (no "clean" reports); attestation letters and a trust-center summary available.Source
    • Your websiteBlog, "5 things to compare before choosing a pentest quote": compare scope, testing approach, a redacted sample finding, schedule, and remediation and retesting ("The work between those two points is part of what you are paying for"); no price ranges; ends with "Book a Casco walkthrough".Source
    • Your websiteContent hub titles include "What Do Companies Use to Map Penetration Test Evidence to CMMC Level 2 Controls", "NIS2 and Continuous Security Testing: What EU Essential Entities Are Doing", an FAQ on predictable-priced pentesting, "Paying Per Retest Round: What Fast Shipping Teams Use Instead" and "Paying for a Scanner, a Bug Bounty and an Annual Pentest: How Startups Consolidate".Source
    • Competitor researchRivals' own homepages: XBOW, "Every finding is a working exploit", free unlimited retesting, "#1 on HackerOne", demo only; Cobalt, "Go from scope to active pentest in hours", a credit model and a downloadable "State of Pentesting 2026" report; Horizon3.ai, "7,012 customers" and a 4.7 Gartner Peer Insights rating, demo only. Casco's own listicles also name Strix and FireCompass.Source
  • 06

    Casco's content hub has 12 listicles. The one on continuous pentesting platforms for enterprise buyers ranks four options "with Casco at the top", ahead of XBOW, Strix and FireCompass, shows no author or date, and links only Casco's entry. There are no "Casco vs" pages in the sitemap. The buyer is a skeptical AppSec leader who will notice a vendor ranking itself first.

    High impactMedium effort First result in 1 month Growth Engineer

    First action

    Add author, date and method to the five most-visited listicles.

    How to measure it

    Comparison-sourced meetings

    Now
    –
    Target
    15 a month
    By
    90 days

    Steps

    1. 1

      Rank by traffic

      The 12 listicles and 4 decision guides.

      Growth Engineer 1 day

    2. 2

      Add method and author

      Criteria, checks, date and disclosure.

      Offensive Security Engineer 1 week

    3. 3

      Link fairly

      Every vendor named gets a link.

      Growth Engineer 1 day

    4. 4

      Write vs pages

      XBOW, Cobalt, Horizon3.ai from their own sites.

      Technical Account Executive 2 weeks

    5. 5

      Legal review

      Claims and trademarks.

      Founder (CEO) 3 days

    6. 6

      Refresh

      Quarterly, with a changelog.

      Growth Engineer quarterly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Growth Engineer

    Smallest test

    Rewrite one listicle with author, date and method and compare time on page and demo clicks.

    Why it works

    For each listicle, add a named author from the security team, a date, the criteria and how each was checked, links to every vendor, and a line saying Casco wrote it. Then publish three fair comparison pages (Casco vs XBOW, Cobalt and Horizon3.ai) covering approach, authenticated testing, retest terms, reporting, compliance and pricing model, dated and refreshed each quarter.

    Transparent comparisons earn the trust that self-ranking spends, and they still answer the questions buyers and AI assistants ask.

    Risks and how to handle them

    • Casco no longer ranks first everywhere

      Say where each tool fits; buyers trust a vendor that admits fit.

    Evidence

    • Your websiteContent hub at /content with 50 article links (12 listicles, 8 FAQs, 4 decision guides, 1 explainer, 25 recommended posts). The listicle "Continuous Penetration Testing Platforms That Prove Security to Enterprise Buyers" ranks four options "with Casco at the top", ahead of XBOW, Strix and FireCompass; no author or date is shown, and only Casco's entry carries links.Source
    • Your websiteSitemap (127 URLs, checked November 9, 2026): eight solution pages organised by what is tested (AI, web app, API, cloud, mobile, AI agent and network pentesting, plus vulnerability prioritization); 39 blog posts, of which one is a customer story (CrewAI) and seven are CVE remediation guides; no pricing page, no customers index, no sample report page and no "Casco vs" pages; two free tools (CVSS and bug bounty calculators); RSAC and Black Hat event pages; partner and reseller pages.Source
    • Competitor researchRivals' own homepages: XBOW, "Every finding is a working exploit", free unlimited retesting, "#1 on HackerOne", demo only; Cobalt, "Go from scope to active pentest in hours", a credit model and a downloadable "State of Pentesting 2026" report; Horizon3.ai, "7,012 customers" and a 4.7 Gartner Peer Insights rating, demo only. Casco's own listicles also name Strix and FireCompass.Source
    • HiringTechnical Account Executive ($350,000 OTE): "Run the full sales cycle from first touch to close" in a "messy early sales motion building" phase, selling to AppSec leaders and CISOs. Sales Development Representative ($120,000 OTE, San Francisco): account-specific outreach "across email, phone, LinkedIn, and other channels", security events with fast follow-up; "You would rather create the right meeting than hit a vanity activity number."Source
  • 07

    Casco says it has tested 400+ companies and shows logos such as Microsoft, Gusto, Substack and CrewAI, but the site has a single customer story (CrewAI), with strong quotes and no figures, and no customers index. The enterprise page names no customers at all. A customer CEO already says Casco is "mission-critical for enterprise deals": that outcome can be measured.

    High impactMedium effort First result in 6 weeks Customer Success Engineer

    First action

    Ask the three customers with quotes on the homepage for a 30-minute interview.

    How to measure it

    Quantified case studies

    Now
    –
    Target
    5 published
    By
    90 days

    Steps

    1. 1

      Pick customers

      Five segments, with permission.

      Customer Success Engineer 1 week

    2. 2

      Pull the data

      Findings, retest dates and outcomes per account.

      Software Engineer 1 week

    3. 3

      Interview

      30 minutes each.

      Customer Success Engineer 2 weeks

    4. 4

      Write and approve

      One number per story, customer sign-off.

      Growth Engineer 2 weeks

    5. 5

      Publish /customers

      Index plus links from solution and enterprise pages.

      Growth Engineer 2 days

    6. 6

      Use in deals

      Matched story in each proposal.

      Technical Account Executive ongoing

    First result
    6 weeks
    Cost
    Staff time only
    Owner
    Customer Success Engineer

    Smallest test

    Add one number to the CrewAI story.

    Why it works

    Interview five customers across segments (AI startup, fintech, enterprise, a compliance-driven buyer, an agent platform) and publish each with one number: critical findings missed by the previous pentest, days to a clean retest, enterprise deals unblocked, or hours saved on triage. Add a /customers index and link the right story from each solution page and the enterprise page.

    Peer proof with a number is what a CISO forwards to their CFO; logos alone do not say what changed.

    Risks and how to handle them

    • Security customers decline to be named

      Offer anonymised stories by industry and size.

    Evidence

    • Your websiteCrewAI customer story: quotes from CrewAI's CEO ("Casco is the obvious security solution for AI systems") and Head of Security ("the first cybersecurity product that makes security testing high-quality, fast, and easy"); no figures on results and no link to other customer stories.Source
    • Your websiteHomepage (checked November 9, 2026): "Security that understands the software you ship."; stats "400+ trusted companies", "99%+ true positive rate", "5.8× better price-performance vs. frontier models", "68% of high/critical findings required signed-in access" and "90% more findings with source code connected"; pricing "depends on scope and the frequency of product changes. Book a demo to learn more."; human-approved pentests within five business days; logos include Microsoft, Gusto, Substack, CrewAI and Baseten; a customer CEO's quote: "Casco is mission-critical for enterprise deals."Source
    • Your websiteEnterprise page: tests production through existing controls with dedicated identities; SSO via Okta, Microsoft Entra ID, Google Workspace and Auth0; source IPs and request IDs for SOC verification; links to the Trust Center and sample pentest report; no customer names or case studies on the page.Source
  • 08

    Casco's solution pages are organised by what gets tested (web app, API, cloud, mobile, network, AI agents), but many buyers arrive because an auditor or a customer asked for a pentest. Casco already supports SOC 2, ISO 27001 and HIPAA reviews, signs BAAs and issues attestation letters, and its content hub already answers CMMC Level 2 and NIS2 questions, yet there is no landing page per framework.

    High impactMedium effort First result in 2 months Growth Engineer

    First action

    Ask the Technical AE which framework comes up most in current deals and write that page first.

    How to measure it

    Compliance-page meetings

    Now
    –
    Target
    20 a month
    By
    2 quarters

    Steps

    1. 1

      Rank frameworks

      By deal mentions.

      Technical Account Executive 1 day

    2. 2

      Map controls

      Which findings and reports answer which control.

      Offensive Security Engineer 1 week

    3. 3

      Write pages

      Five frameworks with timeline and sample mapping.

      Growth Engineer 2 weeks

    4. 4

      Link content

      CMMC FAQ and NIS2 explainer to the new pages.

      Growth Engineer 1 day

    5. 5

      Route leads

      Framework passed to the demo form.

      Growth Engineer 1 day

    6. 6

      Measure

      Search entries and meetings per framework.

      Growth Engineer monthly

    First result
    2 months
    Cost
    Staff time only
    Owner
    Growth Engineer

    Smallest test

    Publish the SOC 2 page and link it from the Supervised page.

    Why it works

    Publish five pages: "Pentest for SOC 2", "for ISO 27001", "for HIPAA", "for CMMC Level 2" and "for NIS2". Each covers what the auditor expects, what scope usually satisfies it, the report and attestation letter, how retesting works within the audit window, a timeline from scope call to report, and a sample control mapping. Link the existing FAQ and explainer articles to them.

    Compliance deadlines create urgent, budgeted demand, and buyers search by framework, not by asset type.

    Risks and how to handle them

    • Overpromising audit outcomes

      Say what the report provides and advise confirming scope with the auditor, as the AI pentesting FAQ already does.

    Evidence

    • Your websiteSitemap (127 URLs, checked November 9, 2026): eight solution pages organised by what is tested (AI, web app, API, cloud, mobile, AI agent and network pentesting, plus vulnerability prioritization); 39 blog posts, of which one is a customer story (CrewAI) and seven are CVE remediation guides; no pricing page, no customers index, no sample report page and no "Casco vs" pages; two free tools (CVSS and bug bounty calculators); RSAC and Black Hat event pages; partner and reseller pages.Source
    • Your websiteHomepage products: AI and supervised pentesting for web, API, cloud, mobile, AI apps and agents, and networks; connected workflows "Email Triage, MCP Workflows, Context Refinement, Slack Bot, and Network Observability"; testing "even behind Cloudflare challenges, CAPTCHAs, and firewall rules"; testing keeps scope and attack history and replays proven attacks to verify fixes; support for SOC 2, ISO 27001 and HIPAA reviews, and a Business Associate Agreement on request.Source
    • Your websiteContent hub titles include "What Do Companies Use to Map Penetration Test Evidence to CMMC Level 2 Controls", "NIS2 and Continuous Security Testing: What EU Essential Entities Are Doing", an FAQ on predictable-priced pentesting, "Paying Per Retest Round: What Fast Shipping Teams Use Instead" and "Paying for a Scanner, a Bug Bounty and an Annual Pentest: How Startups Consolidate".Source
    • Your websiteAI pentesting page: Casco is "a CREST-accredited penetration testing provider"; a table compares scanners, manual tests and AI pentesting; the FAQ says AI cannot fully replace a human tester in every case and advises confirming scope and report format with the auditor before a SOC 2 or ISO 27001 test; final CTA "Provide a target and test accounts"; no pricing or turnaround on the page.Source
  • 09

    Casco's free CVE MCP needs no signup, OAuth or API key and checks up to 100 package versions per call, so developers' agents use it anonymously. Casco publishes no usage figures and cannot see which companies rely on it. The tool itself warns that "no_known_vulnerabilities" is "not proof of safety", which is exactly the gap Casco's paid testing fills. The new Growth Engineer is hired to wire product triggers into upsells.

    High impactMedium effort First result in 2 months Growth Engineer

    First action

    Add request counting by client and publish a weekly internal usage number.

    How to measure it

    CVE MCP-sourced meetings

    Now
    –
    Target
    10 a month
    By
    2 quarters

    Steps

    1. 1

      Count usage

      Requests and clients per week.

      Software Engineer 2 days

    2. 2

      Add an optional key

      Email only, anonymous use stays.

      Software Engineer 1 week

    3. 3

      Build the digest

      New CVEs for checked packages, weekly.

      Growth Engineer 1 week

    4. 4

      Add the offer

      Reachability test offer on CVE pages and in the digest.

      Growth Engineer 2 days

    5. 5

      Route signals

      Company domains with many checks go to the SDR.

      Sales Development Representative ongoing

    6. 6

      Measure

      Keys, digest clicks, meetings.

      Growth Engineer weekly

    First result
    2 months
    Cost
    Two to three weeks of engineering
    Owner
    Growth Engineer

    Smallest test

    Add the reachability offer to the CVE pages and count clicks for a month.

    Why it works

    Keep the anonymous endpoint and keep tool output strictly factual. Add an optional free key (email only) that unlocks a weekly digest of new CVEs for the packages the key has checked. On the CVE web pages and in the digest (not in tool responses), offer "Is this reachable in your app? Casco can test it" with a link to the routed demo page. Count requests, keys and companies per week.

    A developer whose agent flags a vulnerable dependency has a live question that only an exploit test answers; the digest keeps Casco in front of them until the next one.

    Risks and how to handle them

    • Developers see it as bait

      Keep the free endpoint unchanged and the tool output free of marketing.

    • Privacy of package lists

      Store checked packages only for key holders who opt in to the digest.

    Builds on

    Evidence

    • Your websiteCVE Intelligence for Agents: a free CVE MCP with "No signup, OAuth, API key, or local server to install"; four read-only tools, including a dependency check of up to 100 package versions per call; it warns that unknown results are not clean and "no_known_vulnerabilities" is "not proof of safety"; links to "Book a demo"; a separate authenticated MCP serves customers' own findings; no usage figures published.Source
    • HiringGrowth Engineer (San Francisco, $180,000 base): wire "the automation layer (APIs, webhooks, LLM agents)" that turns product triggers into upsells; test channels by hand before automating them; channels are HackerNews, Reddit and LinkedIn; "We care about pipeline, product usage, and revenue."Source
  • 10

    The newsletter promises "A bi-weekly cybersecurity briefing", and its archive's latest issue is October 21. Meanwhile Casco publishes CVE remediation guides within days of disclosure and runs a CVE feed, but the only way to follow them is RSS. Issues like "Attack probes arrived 10 minutes after an OCaml security fix went public" show the team has the material.

    Medium impactLow effort First result in 1 month Offensive Security Engineer

    First action

    Send the next issue and schedule the following two.

    How to measure it

    Work-email subscribers

    Now
    –
    Target
    +100%
    By
    2 quarters

    Steps

    1. 1

      Set the cadence

      Fixed day, two issues in reserve.

      Offensive Security Engineer 1 day

    2. 2

      Add ecosystem choices

      Checkboxes on the signup form.

      Growth Engineer 2 days

    3. 3

      Automate alerts

      New remediation guide triggers a send to matching subscribers.

      Growth Engineer 1 week

    4. 4

      Add the retest offer

      One line and a link per alert.

      Growth Engineer 1 hour

    5. 5

      Promote

      Signup on CVE pages and remediation guides.

      Growth Engineer 1 day

    6. 6

      Measure

      Subscribers, opens and meetings.

      Growth Engineer monthly

    First result
    1 month
    Cost
    Email tool and staff time
    Owner
    Offensive Security Engineer

    Smallest test

    Offer Rails alerts only for a month.

    Why it works

    Fix a publishing day and a two-issue buffer. Add a signup option to receive remediation guides for chosen ecosystems (Rails, Go, Node, Python, Java) as they publish. Each alert carries the fix, how to verify it, and a link to the routed demo page for teams that want the fix retested.

    Ecosystem alerts are useful enough to subscribe to at work, and each one is a reason to talk about verifying fixes, which is what Casco sells.

    Risks and how to handle them

    • Alert fatigue

      Only critical and high CVEs, and a weekly roll-up option.

    Evidence

    • Your websiteNewsletter: "A bi-weekly cybersecurity briefing from Casco" with a work-email signup; five issues from July 22 to October 21, 2026, including "9,308 leaked AWS keys still work" and "Attack probes arrived 10 minutes after an OCaml security fix went public".Source
    • Your websiteSitemap (127 URLs, checked November 9, 2026): eight solution pages organised by what is tested (AI, web app, API, cloud, mobile, AI agent and network pentesting, plus vulnerability prioritization); 39 blog posts, of which one is a customer story (CrewAI) and seven are CVE remediation guides; no pricing page, no customers index, no sample report page and no "Casco vs" pages; two free tools (CVSS and bug bounty calculators); RSAC and Black Hat event pages; partner and reseller pages.Source
    • Your websiteCVE Intelligence for Agents: a free CVE MCP with "No signup, OAuth, API key, or local server to install"; four read-only tools, including a dependency check of up to 100 package versions per call; it warns that unknown results are not clean and "no_known_vulnerabilities" is "not proof of safety"; links to "Book a demo"; a separate authenticated MCP serves customers' own findings; no usage figures published.Source
  • 11

    Casco is hiring a Product Engineer to own the journey "from contract signature through onboarding, activation" and a Customer Success Engineer to get customers to "fully operational". Casco's own data says 68% of high and critical findings required signed-in access, and its AI pentesting page ends with "Provide a target and test accounts": the speed at which a customer hands over working test accounts likely decides how fast value shows up.

    High impactMedium effort First result in 2 months Product Engineer

    First action

    Compute days from signature to first verified finding for the last 20 customers.

    How to measure it

    Time to first verified finding

    Now
    –
    Target
    -50%
    By
    2 quarters

    Steps

    1. 1

      Measure today

      Days to first finding, and where time is lost.

      Customer Success Engineer 3 days

    2. 2

      Design the setup

      Targets, test users per role, connection test.

      Product Engineer 1 week

    3. 3

      Build it

      In the console with progress state.

      Product Engineer 3 weeks

    4. 4

      Add nudges

      Email and Slack when a step stalls.

      Product Engineer 1 week

    5. 5

      Alert CS

      48 hours without progress.

      Customer Success Engineer 2 days

    6. 6

      Review

      Monthly by customer segment.

      Customer Success Engineer monthly

    First result
    2 months
    Cost
    Product and engineering time
    Owner
    Product Engineer

    Smallest test

    Send a test-account checklist the day a contract is signed and compare time to first finding.

    Why it works

    Define "first verified finding" as the activation event and track days from signature to it for every customer. Build a guided setup in the console: approve targets, create test users per role with a checklist for MFA and SSO, a connection test, then a first run. Send nudges by email and Slack when a step stalls, and alert the Customer Success Engineer after 48 hours of no progress.

    Early proof of value drives renewal and expansion, and a guided checklist removes the manual back-and-forth both new roles are hired to reduce.

    Risks and how to handle them

    • Customers cannot create test accounts quickly

      Offer a short call with the CSE to set them up together.

    Evidence

    • HiringProduct Engineer ($200,000 base): "Map and improve the experience from contract signature through onboarding, activation" and on to renewal, across email, Slack or Teams, notifications and the console, so new customers reach "meaningful product value with less friction and less manual guidance". Customer Success Engineer: guide customers from "signed contract" to "fully operational".Source
    • Your websiteHomepage (checked November 9, 2026): "Security that understands the software you ship."; stats "400+ trusted companies", "99%+ true positive rate", "5.8× better price-performance vs. frontier models", "68% of high/critical findings required signed-in access" and "90% more findings with source code connected"; pricing "depends on scope and the frequency of product changes. Book a demo to learn more."; human-approved pentests within five business days; logos include Microsoft, Gusto, Substack, CrewAI and Baseten; a customer CEO's quote: "Casco is mission-critical for enterprise deals."Source
    • Your websiteAI pentesting page: Casco is "a CREST-accredited penetration testing provider"; a table compares scanners, manual tests and AI pentesting; the FAQ says AI cannot fully replace a human tester in every case and advises confirming scope and report format with the auditor before a SOC 2 or ISO 27001 test; final CTA "Provide a target and test accounts"; no pricing or turnaround on the page.Source
  • 12

    Supervised pentests include free retesting for 90 days, and longer periods cost extra. Casco writes about teams "paying per retest round", and XBOW advertises free unlimited retesting. The Growth Engineer is hired to turn product triggers into upsells. The day retesting stops being free is a natural, product-generated trigger that no one has to remember.

    High impactLow effort First result in 1 month Technical Account Executive

    First action

    List customers whose retest window closes in the next 60 days.

    How to measure it

    Pentest-to-continuous conversion

    Now
    –
    Target
    25%
    By
    2 quarters

    Steps

    1. 1

      List windows

      Retest end dates by customer.

      Customer Success Engineer 1 day

    2. 2

      Build the summary

      Fixed, open, releases since test.

      Growth Engineer 1 week

    3. 3

      Set the offer

      Continuous plan with a pentest credit.

      Technical Account Executive 2 days

    4. 4

      Automate the trigger

      Send 30 days before the window ends.

      Growth Engineer 3 days

    5. 5

      Follow up

      Accounts with open findings or many releases.

      Technical Account Executive ongoing

    6. 6

      Measure

      Conversion by segment.

      Growth Engineer monthly

    First result
    1 month
    Cost
    Staff time; a pentest credit
    Owner
    Technical Account Executive

    Smallest test

    Send the summary by hand to five customers this month.

    Why it works

    Thirty days before each customer's retest window closes, send the security lead a short summary: findings fixed and verified, findings still open, and releases shipped since the test. Offer continuous testing that keeps retesting every fix, with a price that credits part of the pentest fee. The Technical AE follows up with accounts that have open findings or frequent releases.

    It turns a one-off pentest into a subscription at the moment the customer can see what continuous testing would have caught, and it answers the competitor's unlimited-retest offer.

    Risks and how to handle them

    • Feels like a hard sell

      Lead with the useful summary; the offer is one line.

    Evidence

    • Your websiteCasco Supervised: "Our pentest pricing is based on the scope of the test."; reports "Within 5 business days latest", or "within a few business hours for a rush fee"; free retesting for 90 days by default, longer at extra cost; remediation reports keep original findings (no "clean" reports); attestation letters and a trust-center summary available.Source
    • HiringGrowth Engineer (San Francisco, $180,000 base): wire "the automation layer (APIs, webhooks, LLM agents)" that turns product triggers into upsells; test channels by hand before automating them; channels are HackerNews, Reddit and LinkedIn; "We care about pipeline, product usage, and revenue."Source
    • Your websiteContent hub titles include "What Do Companies Use to Map Penetration Test Evidence to CMMC Level 2 Controls", "NIS2 and Continuous Security Testing: What EU Essential Entities Are Doing", an FAQ on predictable-priced pentesting, "Paying Per Retest Round: What Fast Shipping Teams Use Instead" and "Paying for a Scanner, a Bug Bounty and an Annual Pentest: How Startups Consolidate".Source
    • Competitor researchRivals' own homepages: XBOW, "Every finding is a working exploit", free unlimited retesting, "#1 on HackerOne", demo only; Cobalt, "Go from scope to active pentest in hours", a credit model and a downloadable "State of Pentesting 2026" report; Horizon3.ai, "7,012 customers" and a 4.7 Gartner Peer Insights rating, demo only. Casco's own listicles also name Strix and FireCompass.Source
  • 13

    Continuous testing is valuable precisely when nothing goes wrong, which makes it easy to forget at renewal. Casco's testing keeps scope and attack history and replays proven attacks to verify fixes, and the Product Engineer is hired to decide what customers are told, when and through which channel.

    Medium impactMedium effort First result in 2 months Customer Success Engineer

    First action

    Hand-build the report for three customers from existing data.

    How to measure it

    Gross revenue retention

    Now
    –
    Target
    95%+
    By
    4 quarters

    Steps

    1. 1

      Pick the fields

      Coverage, tests, findings, verified fixes, time to fix.

      Customer Success Engineer 2 days

    2. 2

      Hand-build three

      Test with real customers.

      Customer Success Engineer 1 week

    3. 3

      Automate

      Generate from the console data.

      Product Engineer 2 weeks

    4. 4

      Deliver

      Email and Slack on the first of the month.

      Product Engineer 1 week

    5. 5

      Add a board view

      One forwardable summary.

      Product Engineer 1 week

    6. 6

      Track

      Opens, forwards and renewals.

      Customer Success Engineer monthly

    First result
    2 months
    Cost
    Product time
    Owner
    Customer Success Engineer

    Smallest test

    Email three customers a hand-made report next month.

    Why it works

    Send each customer a one-page monthly report by email and Slack: new endpoints and releases covered, tests run, findings opened and closed, fixes verified by replayed attacks, and time to fix compared with last month. Give the security lead a version they can forward to their CTO or board.

    It makes invisible work visible to the person who renews the contract and gives the security lead something to show upward.

    Risks and how to handle them

    • Quiet months look empty

      Show coverage and tests run, not only findings.

    Builds on

    Evidence

    • HiringProduct Engineer ($200,000 base): "Map and improve the experience from contract signature through onboarding, activation" and on to renewal, across email, Slack or Teams, notifications and the console, so new customers reach "meaningful product value with less friction and less manual guidance". Customer Success Engineer: guide customers from "signed contract" to "fully operational".Source
    • Your websiteHomepage products: AI and supervised pentesting for web, API, cloud, mobile, AI apps and agents, and networks; connected workflows "Email Triage, MCP Workflows, Context Refinement, Slack Bot, and Network Observability"; testing "even behind Cloudflare challenges, CAPTCHAs, and firewall rules"; testing keeps scope and attack history and replays proven attacks to verify fixes; support for SOC 2, ISO 27001 and HIPAA reviews, and a Business Associate Agreement on request.Source
  • 14

    The Growth Engineer post names Hacker News, Reddit and LinkedIn as the channels. Casco already has research that travels (hacking YC companies' AI agents, a $130k Ford write-up, a North Korean open-source attack), yet Hacker News shows only 8 mentions with a top story of 32 points, and the YouTube channel has 69 subscribers. The Offensive Security Engineer is hired to research AI and LLM attack vectors.

    High impactMedium effort First result in 1 month Offensive Security Engineer

    First action

    Pick the next three research topics and their release weeks.

    How to measure it

    Research-sourced meetings

    Now
    –
    Target
    10 a month
    By
    2 quarters

    Steps

    1. 1

      Plan topics

      Three months of research with owners.

      Offensive Security Engineer 2 days

    2. 2

      Disclose first

      Coordinated disclosure before publishing.

      Offensive Security Engineer per post

    3. 3

      Write for engineers

      Method, demo, no sales copy.

      Offensive Security Engineer 1 week

    4. 4

      Launch

      Hacker News and the right subreddit, engineer replies.

      Growth Engineer 1 day

    5. 5

      Repurpose

      LinkedIn thread, newsletter, short video.

      Growth Engineer 2 days

    6. 6

      Attribute

      Tracked links to meetings.

      Growth Engineer monthly

    First result
    1 month
    Cost
    Research time
    Owner
    Offensive Security Engineer

    Smallest test

    Relaunch one existing research post with a new dataset and track the response.

    Why it works

    Commit to one substantial piece of original research a month (a new attack class, a dataset or a tool), released with a technical write-up, a reproducible demo and responsible-disclosure notes. Post it to Hacker News and the relevant subreddit from an engineer's account, answer comments for the first hours, and end each post with one next step: the newsletter, the CVE MCP or a scoped test.

    Security engineers trust research over ads, and one strong post can reach more of the target audience than a month of outbound.

    Risks and how to handle them

    • Research names other companies

      Publish only after fixes or with consent, and anonymise where needed.

    Evidence

    • ChannelsBlog research includes "We hacked YC agents", "How to hack Ford for $130k", an ElectricSQL SQL injection and "The Blueprint of a North Korean Attack on Open-Source". Hacker News: 8 mentions, top story 32 points, last mention October 30, 2026. YouTube @getcasco: 21 videos, 69 subscribers, 17,610 views.Source
    • HiringGrowth Engineer (San Francisco, $180,000 base): wire "the automation layer (APIs, webhooks, LLM agents)" that turns product triggers into upsells; test channels by hand before automating them; channels are HackerNews, Reddit and LinkedIn; "We care about pipeline, product usage, and revenue."Source
    • HiringSeven open roles on casco.com/careers: Software Engineer (remote US), Product Engineer, Offensive Security Engineer (remote US; "Research emerging attack vectors, particularly those involving AI/LLM systems and applications"), Customer Success Engineer, Sales Development Representative, Technical Account Executive and Growth Engineer, the rest in San Francisco.Source
  • 15

    Casco's reseller page invites MSPs, MSSPs, consultancies, vCISOs and compliance advisors into referral and managed-service models, but publishes no revenue share or discount, and both "Bring us a customer" and "Design your partner motion" go to the same demo form as buyers. A vCISO deciding whether to recommend Casco wants to know what they earn and what the client receives before booking a call.

    Medium impactMedium effort First result in 1 quarter Technical Account Executive

    First action

    Decide the referral share and write it on the reseller page.

    How to measure it

    Partner-sourced pipeline

    Now
    –
    Target
    15% of new pipeline
    By
    3 quarters

    Steps

    1. 1

      Set the economics

      Referral share and discount range.

      Founder (CEO) 1 week

    2. 2

      Build the kit

      One-pager, sample report, scoping checklist.

      Technical Account Executive 1 week

    3. 3

      Add deal registration

      A partner form separate from buyer demos.

      Growth Engineer 3 days

    4. 4

      Recruit a cohort

      Ten vCISOs and compliance advisors.

      Sales Development Representative 1 month

    5. 5

      Run pilots

      One customer each.

      Technical Account Executive 1 quarter

    6. 6

      Review

      Pipeline and partner feedback.

      Technical Account Executive monthly

    First result
    1 quarter
    Cost
    Revenue share on closed deals
    Owner
    Technical Account Executive

    Smallest test

    Offer the published referral share to five advisors you already know.

    Why it works

    Publish the referral share and a reseller discount range, a partner pilot kit (a client-ready one-pager, the sample report, a scoping checklist and a white-label report example), and a partner registration form that protects the partner's deal. Recruit ten vCISOs and compliance advisors for a first cohort.

    Advisors already own the moment a company is told it needs a pentest; clear economics let them recommend Casco without a negotiation.

    Risks and how to handle them

    • Channel conflict with direct sales

      Deal registration decides ownership.

    Evidence

    • Your websitePartners page: perks with Vouch Insurance (5% off premiums and 20% off annual pentesting), Scout (20% off) and Network Right (up to 20% off), plus "Priority scheduling for security reviews". Reseller page: referral and managed-service models for MSPs, MSSPs, consultancies, vCISOs and compliance advisors, paid by revenue share or reseller discount with no published rates; "Bring us a customer" and "Design your partner motion" both go to the demo page.Source
    • HiringTechnical Account Executive ($350,000 OTE): "Run the full sales cycle from first touch to close" in a "messy early sales motion building" phase, selling to AppSec leaders and CISOs. Sales Development Representative ($120,000 OTE, San Francisco): account-specific outreach "across email, phone, LinkedIn, and other channels", security events with fast follow-up; "You would rather create the right meeting than hit a vanity activity number."Source
  • 16

    Casco's perks run with an insurer, an AI workflow platform and a fractional IT firm, each offering up to 20% off annual pentesting. Their "Schedule Annual Pentest" buttons go to the general demo form, so Casco cannot easily see which partner sends which deal. The moments a company learns it needs a pentest (a compliance program, a cyber-insurance application, an accelerator's security checklist) are mostly not covered yet.

    Medium impactLow effort First result in 2 months Growth Engineer

    First action

    Give the three current partners their own tracked landing pages.

    How to measure it

    Perk-sourced meetings

    Now
    –
    Target
    15 a month
    By
    2 quarters

    Steps

    1. 1

      Track current partners

      One page per partner with a source tag.

      Growth Engineer 2 days

    2. 2

      List targets

      Compliance, accelerator, insurer and startup banking programs.

      Growth Engineer 2 days

    3. 3

      Pitch

      A perk for their members and a co-written guide.

      Founder (CEO) 1 month

    4. 4

      Launch pages

      Perk, terms and pre-filled form.

      Growth Engineer 1 day each

    5. 5

      Report

      Monthly to each partner.

      Growth Engineer monthly

    6. 6

      Prune

      Drop partners that send nothing in two quarters.

      Growth Engineer semiannual

    First result
    2 months
    Cost
    Discounts on closed deals
    Owner
    Growth Engineer

    Smallest test

    Tag the three current partner buttons and count meetings for a month.

    Why it works

    Recruit three to five perk partners at those moments (compliance automation platforms, startup accelerators and banking or credit programs for startups, more insurers), each with a dedicated page that states the perk and pre-fills the partner on the routed demo form. Report partner-sourced meetings monthly and share them with each partner.

    Perks placed where the need first appears catch buyers before they collect three quotes, and tracking makes each partnership worth renewing.

    Risks and how to handle them

    • Discounts erode price

      Cap perks at the current 20% and tie them to annual terms.

    Builds on

    Evidence

    • Your websitePartners page: perks with Vouch Insurance (5% off premiums and 20% off annual pentesting), Scout (20% off) and Network Right (up to 20% off), plus "Priority scheduling for security reviews". Reseller page: referral and managed-service models for MSPs, MSSPs, consultancies, vCISOs and compliance advisors, paid by revenue share or reseller discount with no published rates; "Bring us a customer" and "Design your partner motion" both go to the demo page.Source
    • Your websiteDemo page: "Tell us about your role and organization to get started." Six fields (first name, last name, email, role, organization, company website) and a "Continue" button; roles offered are "CISO or security team leader", "Security practitioner evaluating tools for my team", "Executive responsible for security purchasing", "Another role" and "Personal interest". No calendar, no customer proof and no description of what happens next. The header's "Book a demo", Supervised's "Schedule a pentest", "See an AI pentest", the partner perks and the reseller page's "Bring us a customer" all lead here.Source
  • 17

    Casco's Bug Bounty Budget Calculator estimates program costs from company size and expected findings using "real market data from 2024-2025", and Casco's content hub already argues that startups paying for a scanner, a bug bounty and an annual pentest should consolidate. Someone sizing a bounty budget is already planning to pay for findings: the best moment to show the alternative.

    Medium impactLow effort First result in 1 month Growth Engineer

    First action

    Update the calculator's data year and add the comparison block under the result.

    How to measure it

    Calculator-to-meeting rate

    Now
    –
    Target
    5%
    By
    90 days

    Steps

    1. 1

      Refresh data

      2026 market figures.

      Offensive Security Engineer 2 days

    2. 2

      Design the comparison

      Same budget, two approaches.

      Growth Engineer 2 days

    3. 3

      Add triage offer

      Email Triage for incoming reports.

      Growth Engineer 1 day

    4. 4

      Pass the estimate

      To the demo form for the AE.

      Growth Engineer 1 day

    5. 5

      Promote

      Link from the consolidation FAQ and newsletter.

      Growth Engineer 1 day

    6. 6

      Measure

      Uses, clicks, meetings.

      Growth Engineer monthly

    First result
    1 month
    Cost
    A few days of engineering
    Owner
    Growth Engineer

    Smallest test

    Add one line and a button under the result for two weeks.

    Why it works

    After the estimate, show the same budget side by side with continuous testing (coverage, time to finding, retesting, triage effort), offer Email Triage for the reports a bounty will bring, and add one button to the routed demo page with the estimate passed along. Refresh the market data to 2026 and say so.

    It meets a budget holder at the moment they are comparing spend, with their own numbers on the screen.

    Risks and how to handle them

    • Comparison looks rigged

      Show where a bounty is the better fit.

    Builds on

    Evidence

    • Your websiteBug Bounty Budget Calculator: "Estimate your bug bounty program costs based on company size and expected vulnerability findings" from "real market data from 2024-2025".Source
    • Your websiteContent hub titles include "What Do Companies Use to Map Penetration Test Evidence to CMMC Level 2 Controls", "NIS2 and Continuous Security Testing: What EU Essential Entities Are Doing", an FAQ on predictable-priced pentesting, "Paying Per Retest Round: What Fast Shipping Teams Use Instead" and "Paying for a Scanner, a Bug Bounty and an Annual Pentest: How Startups Consolidate".Source
    • Your websiteHomepage products: AI and supervised pentesting for web, API, cloud, mobile, AI apps and agents, and networks; connected workflows "Email Triage, MCP Workflows, Context Refinement, Slack Bot, and Network Observability"; testing "even behind Cloudflare challenges, CAPTCHAs, and firewall rules"; testing keeps scope and attack history and replays proven attacks to verify fixes; support for SOC 2, ISO 27001 and HIPAA reviews, and a Business Associate Agreement on request.Source
  • 18

    Casco keeps RSAC and Black Hat pages, writes packing guides for both, and covered "five launches and a $20K test" from Black Hat in its newsletter. The new SDR's job explicitly includes attending security events and following up quickly. Generic "great to meet you" emails waste the one conversation an AppSec leader gave you.

    Medium impactLow effort First result in next event Sales Development Representat…

    First action

    Write the three-question capture card and the follow-up template.

    How to measure it

    Event-to-meeting rate

    Now
    –
    Target
    20%
    By
    next two events

    Steps

    1. 1

      Capture card

      Stack, deadline, current provider.

      Sales Development Representative 1 day

    2. 2

      Content map

      Guide or research per stack.

      Offensive Security Engineer 2 days

    3. 3

      Template

      Short note, sample report, calendar.

      Sales Development Representative 1 day

    4. 4

      CRM tags

      Event, persona, outcome.

      Sales Development Representative 1 day

    5. 5

      Send within 48 hours

      Every conversation.

      Sales Development Representative per event

    6. 6

      Compare events

      Meetings and pipeline per event.

      Technical Account Executive per event

    First result
    next event
    Cost
    Staff time only
    Owner
    Sales Development Representative

    Smallest test

    Use the card at the next local meetup.

    Why it works

    Capture three things per conversation on the floor (stack, compliance deadline, current pentest provider). Within 48 hours, send a note with the most relevant remediation guide or research post for their stack, the sample report and a calendar link for a scoped walkthrough. Tag every event lead in the CRM and compare meeting rates by event.

    Speed and relevance decide event ROI, and Casco's CVE guides and research give a ready, specific reason to write.

    Risks and how to handle them

    • Scanned badges without a conversation

      Send those the newsletter, not a sales note.

    Builds on

    Evidence

    • Your websiteSitemap (127 URLs, checked November 9, 2026): eight solution pages organised by what is tested (AI, web app, API, cloud, mobile, AI agent and network pentesting, plus vulnerability prioritization); 39 blog posts, of which one is a customer story (CrewAI) and seven are CVE remediation guides; no pricing page, no customers index, no sample report page and no "Casco vs" pages; two free tools (CVSS and bug bounty calculators); RSAC and Black Hat event pages; partner and reseller pages.Source
    • HiringTechnical Account Executive ($350,000 OTE): "Run the full sales cycle from first touch to close" in a "messy early sales motion building" phase, selling to AppSec leaders and CISOs. Sales Development Representative ($120,000 OTE, San Francisco): account-specific outreach "across email, phone, LinkedIn, and other channels", security events with fast follow-up; "You would rather create the right meeting than hit a vanity activity number."Source
    • Your websiteNewsletter: "A bi-weekly cybersecurity briefing from Casco" with a work-email signup; five issues from July 22 to October 21, 2026, including "9,308 leaked AWS keys still work" and "Attack probes arrived 10 minutes after an OCaml security fix went public".Source

Big bets 3

Larger plays that can change the trajectory.

  • 19

    Casco already has striking aggregate numbers: 68% of high and critical findings required signed-in access, and connecting source code produced 90% more findings. Cobalt publishes a "State of Pentesting 2026" report as a lead magnet. Casco's data covers what scanners and unauthenticated tests miss, which no rival's report centres on.

    High impactHigh effort First result in 2 quarters Offensive Security Engineer

    First action

    Check customer contracts for permission to publish anonymised aggregates.

    How to measure it

    Qualified downloads

    Now
    –
    Target
    1,500
    By
    60 days after launch

    Steps

    1. 1

      Confirm permissions

      Aggregate-data terms.

      Founder (CEO) 2 weeks

    2. 2

      Define the dataset

      Period, sample, definitions.

      Software Engineer 2 weeks

    3. 3

      Analyse

      Headline findings and charts.

      Offensive Security Engineer 1 month

    4. 4

      Write

      Method first, then findings.

      Offensive Security Engineer 1 month

    5. 5

      Launch

      Hacker News, LinkedIn, newsletter, press briefing.

      Growth Engineer 2 weeks

    6. 6

      Follow up

      SDR outreach to downloaders.

      Sales Development Representative ongoing

    First result
    2 quarters
    Cost
    Research time and design
    Owner
    Offensive Security Engineer

    Smallest test

    Publish the 68% figure with its method as a single post.

    Why it works

    Publish an annual report from anonymised findings across 400+ companies: share of critical issues behind login, the most common authorization flaws, issues in AI agents and MCP integrations, time to fix and how often fixes fail retest. Release the headline numbers free with a method section, the full report with a work-email download, a launch on Hacker News and LinkedIn, and a briefing for security press.

    Original data earns links, press and AI citations for a year, and it sells the thesis that testing must happen signed-in and continuously.

    Risks and how to handle them

    • Any customer becomes identifiable

      Publish only aggregates above a minimum sample.

    Builds on

    Evidence

    • Your websiteHomepage (checked November 9, 2026): "Security that understands the software you ship."; stats "400+ trusted companies", "99%+ true positive rate", "5.8× better price-performance vs. frontier models", "68% of high/critical findings required signed-in access" and "90% more findings with source code connected"; pricing "depends on scope and the frequency of product changes. Book a demo to learn more."; human-approved pentests within five business days; logos include Microsoft, Gusto, Substack, CrewAI and Baseten; a customer CEO's quote: "Casco is mission-critical for enterprise deals."Source
    • Competitor researchRivals' own homepages: XBOW, "Every finding is a working exploit", free unlimited retesting, "#1 on HackerOne", demo only; Cobalt, "Go from scope to active pentest in hours", a credit model and a downloadable "State of Pentesting 2026" report; Horizon3.ai, "7,012 customers" and a 4.7 Gartner Peer Insights rating, demo only. Casco's own listicles also name Strix and FireCompass.Source
    • ChannelsBlog research includes "We hacked YC agents", "How to hack Ford for $130k", an ElectricSQL SQL injection and "The Blueprint of a North Korean Attack on Open-Source". Hacker News: 8 mentions, top story 32 points, last mention October 30, 2026. YouTube @getcasco: 21 videos, 69 subscribers, 17,610 views.Source
  • 20

    A customer CEO says Casco is "mission-critical for enterprise deals": customers use Casco's reports to pass their own buyers' security reviews. Supervised already offers a trust-center summary and attestation letters, and the blog explains what to share when clients ask for a pentest report. Every one of those reviews is read by another company's security team, which is Casco's buyer.

    High impactHigh effort First result in 2 quarters Product Engineer

    First action

    Ask five customers who share reports with their buyers what a reviewer needs to see.

    How to measure it

    Verification-page referrals

    Now
    –
    Target
    10 a month
    By
    3 quarters

    Steps

    1. 1

      Interview customers

      What reviewers ask for.

      Customer Success Engineer 2 weeks

    2. 2

      Define the fields

      Scope, cadence, last test, verified fixes.

      Product Engineer 1 week

    3. 3

      Build permissions

      Customer controls what is shown.

      Software Engineer 1 month

    4. 4

      Design the page

      Trust-center ready, attestation download.

      Product Engineer 2 weeks

    5. 5

      Pilot

      Ten customers.

      Customer Success Engineer 1 month

    6. 6

      Track referrals

      Visits to meetings.

      Growth Engineer monthly

    First result
    2 quarters
    Cost
    One quarter of product work
    Owner
    Product Engineer

    Smallest test

    Make a static version for one customer's trust center.

    Why it works

    Give each customer an optional, permissioned verification page: tested scope, testing cadence, date of last test, the share of findings fixed and verified by retest, and an attestation download, with no technical detail. Customers link it from their trust center and questionnaires. The page footer says how the testing works and links to Casco, and each referral visit is tracked.

    It saves customers time in every security review and puts Casco in front of the reviewers who buy pentests themselves; continuous status rewards staying on continuous testing.

    Risks and how to handle them

    • Page read as a guarantee of security

      State what was tested and when, never "secure".

    • Customers fear exposure

      Opt-in, no technical details, revocable at any time.

    Builds on

    Evidence

    • Your websiteHomepage (checked November 9, 2026): "Security that understands the software you ship."; stats "400+ trusted companies", "99%+ true positive rate", "5.8× better price-performance vs. frontier models", "68% of high/critical findings required signed-in access" and "90% more findings with source code connected"; pricing "depends on scope and the frequency of product changes. Book a demo to learn more."; human-approved pentests within five business days; logos include Microsoft, Gusto, Substack, CrewAI and Baseten; a customer CEO's quote: "Casco is mission-critical for enterprise deals."Source
    • Your websiteCasco Supervised: "Our pentest pricing is based on the scope of the test."; reports "Within 5 business days latest", or "within a few business hours for a rush fee"; free retesting for 90 days by default, longer at extra cost; remediation reports keep original findings (no "clean" reports); attestation letters and a trust-center summary available.Source
    • Your websiteSitemap (127 URLs, checked November 9, 2026): eight solution pages organised by what is tested (AI, web app, API, cloud, mobile, AI agent and network pentesting, plus vulnerability prioritization); 39 blog posts, of which one is a customer story (CrewAI) and seven are CVE remediation guides; no pricing page, no customers index, no sample report page and no "Casco vs" pages; two free tools (CVSS and bug bounty calculators); RSAC and Black Hat event pages; partner and reseller pages.Source
  • 21

    Casco for Government is "FedRAMP Certified under the 20x Program path at Class A" with a published UEI, CAGE code and a capability statement dated November 2026, but the page names no contract vehicles and offers only an email contact. Agencies usually buy through existing vehicles, and Casco already runs a managed-service reseller model.

    High impactHigh effort First result in 3 quarters Founder

    First action

    List integrators already reselling security testing to agencies and contact three.

    How to measure it

    Public-sector pipeline

    Now
    –
    Target
    5 qualified opportunities
    By
    3 quarters

    Steps

    1. 1

      Map routes

      Integrators and resellers with vehicles.

      Founder (CEO) 2 weeks

    2. 2

      Sign partners

      Two or three on managed-service terms.

      Founder (CEO) 1 quarter

    3. 3

      Build the kit

      Scope template, capability statement, package link.

      Technical Account Executive 2 weeks

    4. 4

      Update /gov

      How to buy, by route.

      Growth Engineer 1 day

    5. 5

      Target programs

      Agency teams running web apps and AI pilots.

      Sales Development Representative ongoing

    6. 6

      Review

      Pipeline by partner each quarter.

      Founder (CEO) quarterly

    First result
    3 quarters
    Cost
    Partner margin and founder time
    Owner
    Founder (CEO)

    Smallest test

    Brief one integrator and ask for a single agency introduction.

    Why it works

    Recruit two or three government-focused resellers or integrators that hold contract vehicles agencies already use, give them the managed-service terms and a government pilot kit (scope template, capability statement, FedRAMP package link, sample report), and target small and mid-size agency programs that need continuous testing of web apps and AI systems. Add a "How to buy" section to /gov listing each route as it goes live.

    Partners with vehicles remove the slowest step in public-sector buying, and a certified, continuous product is easier to place than a new contract.

    Risks and how to handle them

    • Long public-sector cycles

      Keep the commercial motion as the core and treat government as a parallel bet.

    Builds on

    Evidence

    • Your websiteCasco for Government: "FedRAMP Certified under the 20x Program path at Class A" (Marketplace package FR2632731472, status as of November 5, 2026); UEI and CAGE code published; a one-page capability statement dated November 2026; enterprise customers listed include Microsoft, Gusto, Sprout Social and CrewAI; no contract vehicles named; contact is a government team email address.Source
    • Your websitePartners page: perks with Vouch Insurance (5% off premiums and 20% off annual pentesting), Scout (20% off) and Network Right (up to 20% off), plus "Priority scheduling for security reviews". Reseller page: referral and managed-service models for MSPs, MSSPs, consultancies, vCISOs and compliance advisors, paid by revenue share or reseller discount with no published rates; "Bring us a customer" and "Design your partner motion" both go to the demo page.Source

Wildcards 2

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

  • 22

    Casco's best-known research showed how AI agents from a startup batch could be exploited, it counts an agent platform (CrewAI) as a customer, and it sells AI agent security as a solution. AI startups often ship agents before they have a security team, and their founders read exactly the research Casco publishes.

    Medium impactMedium effort First result in 2 months Offensive Security Engineer

    First action

    Write the authorization form and the scope for one agent check.

    How to measure it

    Check-to-paid conversion

    Now
    –
    Target
    20%
    By
    2 quarters

    Steps

    1. 1

      Define scope

      One agent, fixed checks, written authorization.

      Offensive Security Engineer 1 week

    2. 2

      Build intake

      Application and authorization flow.

      Growth Engineer 1 week

    3. 3

      Recruit

      Accelerators, founder communities, research readers.

      Growth Engineer ongoing

    4. 4

      Run checks

      A fixed monthly quota.

      Offensive Security Engineer monthly

    5. 5

      Report and offer

      Findings, fixes and a startup plan.

      Technical Account Executive per check

    6. 6

      Measure

      Conversions and time to paid.

      Growth Engineer monthly

    First result
    2 months
    Cost
    Engineer time per check
    Owner
    Offensive Security Engineer

    Smallest test

    Offer five checks to one accelerator's current companies.

    Why it works

    Offer a limited number of free, scoped checks per month: one agent, with written authorization from the startup, focused on tool permissions, data exposure and prompt-injection paths, delivered as a short report with fixes. Recruit through accelerators, founder communities and the research posts. Convert with a startup plan for continuous testing once they raise or sign their first enterprise customer.

    It turns Casco's most memorable research into a service founders ask for, and it captures AI companies before their first enterprise security review.

    Risks and how to handle them

    • Demand exceeds capacity

      Fixed monthly quota and a waitlist.

    • Testing without proper consent

      Only after signed authorization from the agent's owner.

    Builds on

    Evidence

    • ChannelsBlog research includes "We hacked YC agents", "How to hack Ford for $130k", an ElectricSQL SQL injection and "The Blueprint of a North Korean Attack on Open-Source". Hacker News: 8 mentions, top story 32 points, last mention October 30, 2026. YouTube @getcasco: 21 videos, 69 subscribers, 17,610 views.Source
    • Your websiteCrewAI customer story: quotes from CrewAI's CEO ("Casco is the obvious security solution for AI systems") and Head of Security ("the first cybersecurity product that makes security testing high-quality, fast, and easy"); no figures on results and no link to other customer stories.Source
    • Your websiteSitemap (127 URLs, checked November 9, 2026): eight solution pages organised by what is tested (AI, web app, API, cloud, mobile, AI agent and network pentesting, plus vulnerability prioritization); 39 blog posts, of which one is a customer story (CrewAI) and seven are CVE remediation guides; no pricing page, no customers index, no sample report page and no "Casco vs" pages; two free tools (CVSS and bug bounty calculators); RSAC and Black Hat event pages; partner and reseller pages.Source
  • 23

    Email Triage is one of Casco's connected workflows, and Casco argues that startups paying for a scanner, a bug bounty and an annual pentest should consolidate. Small companies get unsolicited vulnerability reports long before they buy a pentest, and have no one to tell a real issue from noise.

    Medium impactMedium effort First result in 1 quarter Product Engineer

    First action

    Set the free cap and the in-scope rules for reproduction.

    How to measure it

    Free-to-paid upgrades

    Now
    –
    Target
    10% within 6 months
    By
    3 quarters

    Steps

    1. 1

      Set limits

      One inbox, monthly report cap.

      Product Engineer 2 days

    2. 2

      Self-serve setup

      Forwarding rule and consent for in-scope checks.

      Software Engineer 2 weeks

    3. 3

      Upgrade triggers

      Confirmed issue or cap reached.

      Growth Engineer 1 week

    4. 4

      Launch

      Research posts, newsletter, partner perks.

      Growth Engineer 1 week

    5. 5

      Support

      Questions from free teams.

      Customer Success Engineer ongoing

    6. 6

      Measure

      Active inboxes, confirmed issues, upgrades.

      Growth Engineer monthly

    First result
    1 quarter
    Cost
    Compute and support time
    Owner
    Product Engineer

    Smallest test

    Offer it to twenty startups from the partner perks and newsletter.

    Why it works

    Offer Email Triage free for one security@ inbox and a capped number of reports a month: each report is classified, de-duplicated and, where safe and in scope, reproduced. When a report is confirmed as real, offer a scoped Casco test of the affected area. Upgrade to paid on volume or when the team wants continuous testing.

    A free tool that handles a real weekly annoyance gets Casco inside small companies early, and a confirmed report is the strongest buying trigger there is.

    Risks and how to handle them

    • Cost of free usage

      A low monthly cap and reproduction only for in-scope, authorized targets.

    Evidence

    • Your websiteHomepage products: AI and supervised pentesting for web, API, cloud, mobile, AI apps and agents, and networks; connected workflows "Email Triage, MCP Workflows, Context Refinement, Slack Bot, and Network Observability"; testing "even behind Cloudflare challenges, CAPTCHAs, and firewall rules"; testing keeps scope and attack history and replays proven attacks to verify fixes; support for SOC 2, ISO 27001 and HIPAA reviews, and a Business Associate Agreement on request.Source
    • Your websiteContent hub titles include "What Do Companies Use to Map Penetration Test Evidence to CMMC Level 2 Controls", "NIS2 and Continuous Security Testing: What EU Essential Entities Are Doing", an FAQ on predictable-priced pentesting, "Paying Per Retest Round: What Fast Shipping Teams Use Instead" and "Paying for a Scanner, a Bug Bounty and an Annual Pentest: How Startups Consolidate".Source
More example playbooks and reviews

More growth playbooks

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

  • Dealpath growth strategyAn AI-powered operating system for real estate investing: deal pipeline and execution, comps and market tracking, CRM, reporting and…22 growth ideas
  • Waabi growth strategyBuilds the Waabi Driver, an end-to-end AI driving system for autonomous trucks and robotaxis, trained with its own neural simulator; runs…22 growth ideas
  • Liverpool Los Angeles growth strategyA Los Angeles denim and casual sportswear brand: fit-first jeans, ponte trousers such as the Kelsey, jackets, sweaters and tops for women…21 growth ideas
  • Meadowvale Ford growth strategyA Ford dealership in Mississauga selling new and used vehicles, with a large F-150 and commercial inventory, service, parts, tires and…22 growth ideas
  • OSC Professionals growth strategyA Nagpur-based ecommerce agency (since 2000) building Shopify and Magento stores, migrations, speed optimisation and custom apps, with…22 growth ideas
  • Dream Three growth strategyA New York and Los Angeles story studio developing and producing film, series, theater, music, publishing and immersive work, and…20 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
  • Frescobene Foods growth strategyA woman-owned Connecticut maker of frozen artisan pasta sauces (sausage ragu, vodka, marinara, Amatriciana) in heat-and-serve pouches…20 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. Casco did not commission, review or endorse it, and Programmable is not affiliated with Casco. 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 Casco runs its business.

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

30/60/90 roadmap

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

  1. Days 1 to 307 ideas

    Routed booking page, sample report page, sourced homepage numbers, lighter homepage, pricing guide, newsletter and CVE alerts, event follow-up.

  2. Days 31 to 6011 ideas

    Honest comparisons, customer stories, compliance pages, CVE MCP funnel, onboarding speed, retest-window upsell, monthly value report, research cadence, partners and the bounty calculator.

  3. Days 61 to 905 ideas

    Commit to the big bets: the annual signed-in attack surface report, the shareable "Tested by Casco" page and government pipeline through partners; run the two wildcards as small tests.

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 finding critical issues other pentesters missed, within hours. The most cited problem: annual pentests and noisy scanners cannot keep up with how fast teams ship.

  • Reports that help win enterprise deals
  • Paying separately for a scanner, a bug bounty and an annual pentest
  • In their words: “verified findings, not noise”

Market

Competitive landscape

4 competitors compared: XBOW, Cobalt, Horizon3.ai and Traditional pentest firms and bug bounty platforms.

  • Gap to exploit: Transparent pentest pricing for fast-shipping teams
  • XBOW: Demo-only buying path
  • Cobalt: Human-network model is less continuous

Hiring signals

Casco is building its go-to-market from scratch after its Series A.

  • Technical Account Executive: Full cycle, early sales motion, AppSec leaders and CISOs. Ideas 1, 5, 12, 15.
  • Sales Development Representative: Account-specific outreach and event follow-up. Ideas 1, 18.
  • Growth Engineer: Product-triggered upsells; HN, Reddit and LinkedIn. Ideas 9, 12, 14, 17.

From the team that wrote this playbook

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

© 2026 AI-Powered Growth Intelligence