ProgrammableMarketing/mazehq.com (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 6
  • This quarter · 9
  • Big bets · 2
  • Wildcards · 3
  • How we can help
Generated Nov 4, 2026 3 views
  1. Programmable
  2. Playbooks
  3. Maze
Maze logo

growth playbook · Nov 4, 2026

mazehq.com (opens in a new tab)

Maze growth playbook

Diagnosis

Maze is a London-based, Series A security company with a sharp product story (90% of investigated vulnerabilities are not exploitable), real research (bugs found in Langfuse, Saleor, Plane and PyJWT) and an unusual media asset, the Exploit. Its hiring is about marketing reach: two satire creators whose best pieces get paid spend, and a coordinator for events, HubSpot and the CMS.

The gaps are the links between those assets and buying: Exploit readers all land on the homepage, advisories end with a generic demo button, event guests have no follow-up, llms.txt shows AI agents ad pages first, and there are no head-to-head or pricing pages. The site itself is fast.

Growth Score

7/10

Biggest Opportunity

Connect the Exploit, the vulnerability research and the events to specific next steps, so the attention Maze already earns turns into measurable demos.

Biggest Risk

Snyk, Semgrep, Endor Labs, Aikido and ZeroPath all now claim AI-native or agentic AppSec, so without visible proof and comparisons Maze's difference can blur.

01

Start here

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

  1. 1

    Give every Exploit article a "the unfunny version" link to the Maze page it is secretly about

    Add a themed "unfunny version" card to the ten most-read Exploit articles.

    High impact First result in 1 month
  2. 2

    End every "Are you affected?" post with "Let Maze check whether it is exploitable for you"

    Add the box to the PHP2Shell post today.

    High impact First result in 2 weeks
  3. 3

    A 48-hour follow-up for every event guest, built once in HubSpot

    Write the follow-up for the next event on the calendar.

    High impact First result in 1 month

02

Your idea portfolio

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

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

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 3Big bets · 7Fill-ins · 6Reconsider · 4
Effort →

Showing 20 of 20 ideas

This week 6

Quick wins with a clear first action.

  • 01

    Maze is hiring two satire creators and puts ad money behind the pieces that land, so the Exploit is becoming a real channel. But every Maze ad and logo on the Exploit sends readers to the homepage with only utm_source=theexploit, whatever they just read. A practitioner laughing at "Vulnerability Scanner Now Offers Discounts for Every Finding It Gets Wrong" is one click from Maze's actual claim, that 90% of the vulnerabilities it investigates are not exploitable, and the site never shows it to them. Nor can Maze tell which articles or writers bring demos, which is what decides where the ad money and the 3% writer share should go.

    High impactLow effort First result in 1 month Head of Marketing

    First action

    Add a themed "unfunny version" card to the ten most-read Exploit articles.

    How to measure it

    Exploit-sourced demo requests

    Now
    –
    Target
    10 a month
    By
    90 days

    Steps

    1. 1

      Pick themes

      Five Maze themes and the real page for each.

      Head of Marketing 1 day

    2. 2

      Tag the archive

      One theme per article, starting with the most read.

      Marketing Coordinator 2 days

    3. 3

      Build the card

      A small, clearly labelled card below each story.

      Web Developer 2 days

    4. 4

      Tag the links

      utm_campaign by article slug and writer.

      Marketing Coordinator 1 day

    5. 5

      Match paid

      Boosted pieces land on a themed page with a demo form.

      Head of Marketing 1 week

    6. 6

      Brief writers

      Each pitch names its Maze theme, without changing the joke.

      Staff Writer (Satire), the Exploit 1 day

    7. 7

      Report monthly

      Visits, sign-ups and demos by article and writer.

      Head of Marketing monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Head of Marketing

    Smallest test

    Put the card on the scanner article and five others, and compare click-through for a month.

    Why it works

    Tag each Exploit article with one Maze theme (scanner noise, exploitability, remediation ownership, CISO burnout, AI code) and add a small card under the story: "The unfunny version", one sentence and a link to the matching real page (the exploitability post, the Cohere Health story, the remediation page or a vulnerability write-up). Give each link a utm_campaign with the article slug and writer, swap the generic banner for the themed one, and when an article is boosted with paid spend, send the ad to a themed landing page, not the homepage. Report Exploit-sourced visits, newsletter sign-ups and demos by article every month.

    The joke has already done the hard part: it got a sceptical practitioner to recognise their own problem. A themed link catches that moment, and per-article tracking turns the Exploit from brand spend into a channel Maze can budget like any other.

    Ready to use

    CopyExploit "unfunny version" card

    THE UNFUNNY VERSION
    [One sentence of the real problem, e.g. "Most scanner findings are not exploitable in your environment. Maze investigates every one and shows the few that are."]
    [Read how Maze checks exploitability ->] (link with utm_source=theexploit&utm_medium=article_card&utm_campaign=<slug>-<writer>)

    Risks and how to handle them

    • Selling inside the satire spoils it

      Keep the card outside the story and clearly labelled.

    • Small numbers at first

      Judge articles on sign-ups as well as demos.

    Evidence

    • HiringStaff Writer (Satire), the Exploit (posted November 1, 2026): "the Exploit ... is a satirical publication from Maze"; Maze is hiring "two satire content creators" who each ship "5 articles and 5 videos a month", every story becoming "a short social video, usually a 30- to 90-second news segment". "When one of your pieces performs organically, we often put ad money behind it", and the writer earns "3% of the spend". Writers must have "Real practitioner experience" in security or software.Source
    • The Exploittheexploit.co ("Breaking Satire Before Its Patched"; in Maze's menu as "Like the Onion, but for security") has 56 linked articles on its homepage, a newsletter, "Submit Story" and "Advertise". Its Maze ads and "Brought to you by" logo all link to the mazehq.com homepage with only "utm_source=theexploit", whatever the article is about: the piece "Vulnerability Scanner Now Offers Discounts for Every Finding It Gets Wrong" carries the same homepage link as the RSA Conference jokes. Other ad slots rotate parody ads for invented vendors.Source
    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
    • Your blogVulnerability research posts: "PHP2Shell: two critical PHP RCEs, and how to tell if you're affected" (October 22, 2026), "Removed from a Plane project? One invite can bring you back as admin" (October 20), "There's a ten-year-old key confusion bug in PyJWT" (September 16), "Maze Code found a Langfuse SSO bug" (July 2), "Maze Code found an account takeover bug in Saleor" and "79 Gadgets Hidden in a Single Deserialization Flaw". The PHP2Shell post walks readers through a manual "Are you affected?" check; its only Maze calls to action are the site-wide "See Maze investigate a real vulnerability. Book a demo" footer and a newsletter box.Source
  • 02

    Maze's vulnerability write-ups (PHP2Shell, Plane, PyJWT, Langfuse, Saleor) are exactly the pages security teams read when a critical CVE lands. The PHP2Shell post gives a careful manual "Are you affected?" checklist, but the only next step is the site-wide demo footer and a newsletter box, even though answering "is it exploitable here?" is what Maze does.

    High impactLow effort First result in 2 weeks Security Researcher

    First action

    Add the box to the PHP2Shell post today.

    How to measure it

    Demo requests from advisories

    Now
    –
    Target
    +50%
    By
    60 days

    Steps

    1. 1

      Write the box

      One version per post type: CVE, open-source bug.

      Product Marketing Manager 1 day

    2. 2

      Add to posts

      All advisory posts.

      Marketing Coordinator 1 day

    3. 3

      Fast-track form

      Short form tagged with the CVE.

      Marketing Coordinator 1 day

    4. 4

      Alert list

      Separate HubSpot list for critical advisories.

      Marketing Coordinator 1 day

    5. 5

      Sales follow-up

      Same-day reply for CVE-tagged demos.

      Account Executive ongoing

    6. 6

      Measure

      Demos per post.

      Head of Marketing monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Security Researcher

    Smallest test

    Add the box to the PHP2Shell and Plane posts.

    Why it works

    Add a short box after the checklist in each advisory: "Not sure? Maze investigates this CVE across your code and cloud and tells you whether it is exploitable", with a fast-track demo or pilot link tagged with the CVE. Offer an alert list for critical-vulnerability write-ups.

    The reader has the exact problem Maze solves at that moment; a specific offer beats a generic demo button.

    Risks and how to handle them

    • Looks like ambulance chasing

      Keep the advice complete and the offer short.

    Evidence

    • Your blogVulnerability research posts: "PHP2Shell: two critical PHP RCEs, and how to tell if you're affected" (October 22, 2026), "Removed from a Plane project? One invite can bring you back as admin" (October 20), "There's a ten-year-old key confusion bug in PyJWT" (September 16), "Maze Code found a Langfuse SSO bug" (July 2), "Maze Code found an account takeover bug in Saleor" and "79 Gadgets Hidden in a Single Deserialization Flaw". The PHP2Shell post walks readers through a manual "Are you affected?" check; its only Maze calls to action are the site-wide "See Maze investigate a real vulnerability. Book a demo" footer and a newsletter box.Source
    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
  • 03

    Maze runs a lot of field events: re:Invent, KubeCon, Black Hat Europe, OWASP receptions, a frontier AI lunch in New York and London socials. The new coordinator will build invites, track RSVPs and upload attendee lists, but the role does not mention what happens next.

    High impactLow effort First result in 1 month Marketing Coordinator

    First action

    Write the follow-up for the next event on the calendar.

    How to measure it

    Post-event meetings

    Now
    –
    Target
    10% of guests
    By
    1 quarter

    Steps

    1. 1

      Templates

      Three sequences by event type.

      Head of Marketing 2 days

    2. 2

      Upload rule

      Lists in HubSpot within 24 hours.

      Marketing Coordinator ongoing

    3. 3

      Content match

      One relevant asset per event.

      Marketing Coordinator 1 day

    4. 4

      Target accounts

      Flag and route to AEs.

      Account Executive 1 day

    5. 5

      Send

      Within 48 hours.

      Marketing Coordinator ongoing

    6. 6

      Report

      Meetings per event.

      Head of Marketing monthly

    First result
    1 month
    Cost
    $0
    Owner
    Marketing Coordinator

    Smallest test

    Follow up the next event within 48 hours and count replies.

    Why it works

    Create one HubSpot sequence per event type (party, roundtable, meetup): a thank-you, the most relevant write-up or video, and an invitation to "see Maze investigate a real vulnerability". Route guests from target accounts to an AE within a day.

    Event guests remember Maze for a few days; a quick, relevant follow-up turns goodwill into meetings.

    Risks and how to handle them

    • Social guests dislike sales emails

      Lead with content and a light ask.

    Evidence

    • Your websiteEvents: a lunch roundtable on frontier AI and cyber in New York, an OWASP Global AppSec reception, a KubeCon after-party, a re:Invent 2026 bar night, a Black Hat Europe happy hour, a fwd:cloudsec Europe social, a padel social in London, OWASP chapter meetups and a webinar "The hardest problems we solved building Maze".Source
    • HiringMarketing Coordinator (Part Time, posted October 21, 2026): "Build event landing pages and invite emails in HubSpot from our templates", "Send invite reminders, track RSVPs and follow up with guests", "Upload attendee lists into HubSpot after each event", "Update pages on our website through our CMS", "Build and schedule marketing emails in HubSpot", schedule social posts and "repurpose content into new formats". Maze describes itself as "an AI-native code security company" and "a well-funded Series A startup".Source
    • Your blogVulnerability research posts: "PHP2Shell: two critical PHP RCEs, and how to tell if you're affected" (October 22, 2026), "Removed from a Plane project? One invite can bring you back as admin" (October 20), "There's a ten-year-old key confusion bug in PyJWT" (September 16), "Maze Code found a Langfuse SSO bug" (July 2), "Maze Code found an account takeover bug in Saleor" and "79 Gadgets Hidden in a Single Deserialization Flaw". The PHP2Shell post walks readers through a manual "Are you affected?" check; its only Maze calls to action are the site-wide "See Maze investigate a real vulnerability. Book a demo" footer and a newsletter box.Source
  • 04

    Maze openly welcomes AI agents, with llms.txt, a Markdown sitemap and Markdown twins of every page. But the lists are alphabetical, so the first seven entries an assistant reads are paid-ad landing pages, and the internal content style guide is listed too.

    Medium impactLow effort First result in 1 week Web Developer

    First action

    Remove paid and internal pages from llms.txt.

    How to measure it

    Correct descriptions in AI assistant spot checks

    Now
    –
    Target
    8 of 10
    By
    1 month

    Steps

    1. 1

      Write summary

      What Maze is, in five lines.

      Product Marketing Manager 1 hour

    2. 2

      Order sections

      Product, proof, research, learn.

      Web Developer 2 hours

    3. 3

      Exclude pages

      Paid and internal pages.

      Web Developer 1 hour

    4. 4

      Sitemap.md

      Same rule.

      Web Developer 1 hour

    5. 5

      Spot check

      Ask three assistants about Maze.

      Marketing Coordinator 1 hour

    6. 6

      Repeat

      Monthly.

      Marketing Coordinator monthly

    First result
    1 week
    Cost
    $0
    Owner
    Web Developer

    Smallest test

    Edit llms.txt by hand today.

    Why it works

    Rewrite llms.txt by hand: a one-paragraph summary of Maze, then platform and product pages, customer proof, research posts and the Learning Center. Leave out paid landing pages and internal pages, and generate the Markdown sitemap the same way.

    When buyers ask an assistant about AI vulnerability management, the summary it builds from llms.txt is Maze's pitch. The order decides what it says.

    Risks and how to handle them

    • Plugin regenerates the file

      Override it with a static file.

    Evidence

    • Your websiterobots.txt welcomes AI agents and points to /llms.txt, a Markdown sitemap and /openapi.json; "Every page also has a Markdown twin". The llms.txt and Markdown sitemap (about 128 entries) are alphabetical, so the first seven entries are paid-ad landing pages (noindex pages, labelled as paid in their titles), and the list also includes the internal content style guide.Source
    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
  • 05

    The Learning Center ranks tools in listicles ("Best SAST tools for 2026: 15 solutions compared", "Top 14 SCA tools compared") but has no "Maze vs" pages. ZeroPath and Endor Labs now pitch AI-native, agentic AppSec too, so buyers compare directly.

    High impactMedium effort First result in 1 month Product Marketing Manager

    First action

    Write "Maze vs Snyk" first.

    How to measure it

    Comparison-page demos

    Now
    –
    Target
    10 a month
    By
    90 days

    Steps

    1. 1

      Pick rivals

      From lost and won deals.

      Account Executive 1 day

    2. 2

      Check facts

      Each rival's own site.

      Product Marketing Manager 3 days

    3. 3

      Write

      Five pages.

      Product Marketing Manager 2 weeks

    4. 4

      Review

      Founders and legal.

      Co-founder and CEO 3 days

    5. 5

      Publish and link

      From listicles.

      Marketing Coordinator 1 day

    6. 6

      Refresh

      Quarterly.

      Product Marketing Manager quarterly

    First result
    1 month
    Cost
    Writing time
    Owner
    Product Marketing Manager

    Smallest test

    Publish one page and track demos.

    Why it works

    Write fair head-to-head pages: approach (investigating exploitability vs scanning), code and cloud context, false positives, fixes, integrations and when each fits. Link them from the listicles.

    Comparison searches are late-stage, and Maze's founders promised marketing that informs rather than confuses; fair comparisons fit that brand.

    Risks and how to handle them

    • Out-of-date claims

      Date and source each page.

    Evidence

    • Your websiteLearning Center listicles such as "Best SAST tools for 2026: 15 solutions compared", "Top 14 SCA tools compared", "Best AI-powered vulnerability management platforms: top 8 in 2026" and "Kubernetes security tools: 15 solutions"; there are no head-to-head "Maze vs" pages. One customer story (Cohere Health "cleared 92% of its critical and high findings").Source
    • Competitor researchRivals' own homepages: Snyk, "Snyk AI Security Platform | Secure Code, Agents & Apps" with "Get started for free or book a demo"; Semgrep, "AI-assisted SAST, SCA and Secrets Detection"; Endor Labs, "Agentic Application Security Platform"; Aikido, "Secure everything your devs build, ship & run"; ZeroPath, "AI-native SAST that finds 2x more vulnerabilities with 75% fewer false positives".Source
    • Company recordsMAZE AI LIMITED, UK company 15203461, headquartered in London; the founders started Maze in 2024 after "many years working for security vendors" and promise to "Treat customers with respect" and avoid "Marketing designed to confuse rather than inform".Source
    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
  • 06

    /pricing returns a 404 and "Book a demo" is the only call to action. Snyk offers a free start beside its demo. Security buyers want to know the pilot length, what access Maze needs and how pricing is counted before they book.

    Medium impactLow effort First result in 2 weeks Product Marketing Manager

    First action

    Draft the pilot section.

    How to measure it

    Buying-page demos

    Now
    –
    Target
    15% of visitors
    By
    60 days

    Steps

    1. 1

      Pilot facts

      Length, scope, success measures.

      Account Executive 1 day

    2. 2

      Security facts

      Access and data handling.

      Security Researcher 1 day

    3. 3

      Pricing basis

      How it scales, without list prices if needed.

      Co-founder and CEO 1 day

    4. 4

      Write

      One page.

      Product Marketing Manager 2 days

    5. 5

      Publish

      Redirect /pricing.

      Web Developer 1 hour

    6. 6

      Measure

      Visits to demos.

      Head of Marketing monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Product Marketing Manager

    Smallest test

    Redirect /pricing to the demo page with a pilot FAQ.

    Why it works

    Publish a short page: the pilot (length, scope, what success looks like), access and data handling, how pricing scales (assets, repos or seats) and a typical timeline. Point /pricing at it.

    Removing unknowns lets buyers book sooner, and it fits the "treat customers with respect" promise.

    Risks and how to handle them

    • Revealing too much to rivals

      Share the basis, not the price list.

    Evidence

    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
    • Competitor researchRivals' own homepages: Snyk, "Snyk AI Security Platform | Secure Code, Agents & Apps" with "Get started for free or book a demo"; Semgrep, "AI-assisted SAST, SCA and Secrets Detection"; Endor Labs, "Agentic Application Security Platform"; Aikido, "Secure everything your devs build, ship & run"; ZeroPath, "AI-native SAST that finds 2x more vulnerabilities with 75% fewer false positives".Source
    • Company recordsMAZE AI LIMITED, UK company 15203461, headquartered in London; the founders started Maze in 2024 after "many years working for security vendors" and promise to "Treat customers with respect" and avoid "Marketing designed to confuse rather than inform".Source

This quarter 9

The core plays for the next three months.

  • 07

    The Exploit has its own newsletter and Maze has a "Get more insights from Maze" box on blog posts. The audiences overlap (security practitioners), but there is no bridge between the two lists.

    Medium impactLow effort First result in 1 month Head of Marketing

    First action

    Add the line to the next Exploit newsletter.

    How to measure it

    New Maze subscribers

    Now
    –
    Target
    500
    By
    1 quarter

    Steps

    1. 1

      Write the line

      Template for each send.

      Marketing Coordinator 1 hour

    2. 2

      Tag links

      UTMs per issue.

      Marketing Coordinator 1 hour

    3. 3

      Invite

      Alert list offer.

      Marketing Coordinator 1 day

    4. 4

      Sync lists

      In HubSpot.

      Marketing Coordinator 1 day

    5. 5

      Measure

      Sign-ups per issue.

      Head of Marketing monthly

    6. 6

      Adjust

      Test placement.

      Head of Marketing monthly

    First result
    1 month
    Cost
    $0
    Owner
    Head of Marketing

    Smallest test

    Run it on one newsletter issue.

    Why it works

    Add one line to each Exploit newsletter ("This week, for real:") linking to Maze's latest research post, and invite Exploit subscribers to the Maze alert list. Measure overlap and sign-ups.

    It moves people who already like Maze's voice toward its research and product, for free.

    Risks and how to handle them

    • Exploit readers want jokes only

      One line, at the end.

    Evidence

    • The Exploittheexploit.co ("Breaking Satire Before Its Patched"; in Maze's menu as "Like the Onion, but for security") has 56 linked articles on its homepage, a newsletter, "Submit Story" and "Advertise". Its Maze ads and "Brought to you by" logo all link to the mazehq.com homepage with only "utm_source=theexploit", whatever the article is about: the piece "Vulnerability Scanner Now Offers Discounts for Every Finding It Gets Wrong" carries the same homepage link as the RSA Conference jokes. Other ad slots rotate parody ads for invented vendors.Source
    • Your blogVulnerability research posts: "PHP2Shell: two critical PHP RCEs, and how to tell if you're affected" (October 22, 2026), "Removed from a Plane project? One invite can bring you back as admin" (October 20), "There's a ten-year-old key confusion bug in PyJWT" (September 16), "Maze Code found a Langfuse SSO bug" (July 2), "Maze Code found an account takeover bug in Saleor" and "79 Gadgets Hidden in a Single Deserialization Flaw". The PHP2Shell post walks readers through a manual "Are you affected?" check; its only Maze calls to action are the site-wide "See Maze investigate a real vulnerability. Book a demo" footer and a newsletter box.Source
    • HiringMarketing Coordinator (Part Time, posted October 21, 2026): "Build event landing pages and invite emails in HubSpot from our templates", "Send invite reminders, track RSVPs and follow up with guests", "Upload attendee lists into HubSpot after each event", "Update pages on our website through our CMS", "Build and schedule marketing emails in HubSpot", schedule social posts and "repurpose content into new formats". Maze describes itself as "an AI-native code security company" and "a well-funded Series A startup".Source
  • 08

    The homepage quotes security leaders at Alloy, Cohere Health, Forge and PartsSource, but only Cohere Health has a full story ("cleared 92% of its critical and high findings"). Buyers want numbers from peers.

    High impactMedium effort First result in 1 quarter Product Marketing Manager

    First action

    Ask the three customers for a 30-minute interview.

    How to measure it

    Full customer stories

    Now
    –
    Target
    4
    By
    1 quarter

    Steps

    1. 1

      Ask

      Three customers.

      Co-founder and CEO 1 week

    2. 2

      Interview

      Numbers and quotes.

      Product Marketing Manager 2 weeks

    3. 3

      Write

      Stories.

      Product Marketing Manager 2 weeks

    4. 4

      Video

      Short clips.

      Staff Writer (Satire), the Exploit 2 weeks

    5. 5

      Publish

      Customer pages.

      Marketing Coordinator 1 day

    6. 6

      Use

      Ads and sequences.

      Head of Marketing ongoing

    First result
    1 quarter
    Cost
    Staff time only
    Owner
    Product Marketing Manager

    Smallest test

    Publish one story this month.

    Why it works

    Interview Alloy, Forge and PartsSource on findings closed, time saved and false positives removed, and publish stories with a short video each. Use them in ads and follow-ups.

    Peer numbers are the strongest proof in security buying, and the relationships already exist.

    Risks and how to handle them

    • Approval delays

      Offer anonymous versions.

    Evidence

    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
    • Your websiteLearning Center listicles such as "Best SAST tools for 2026: 15 solutions compared", "Top 14 SCA tools compared", "Best AI-powered vulnerability management platforms: top 8 in 2026" and "Kubernetes security tools: 15 solutions"; there are no head-to-head "Maze vs" pages. One customer story (Cohere Health "cleared 92% of its critical and high findings").Source
  • 09

    Maze Code has found and disclosed real bugs in open-source projects (Langfuse SSO, Saleor account takeover, Plane access control, PyJWT key confusion). Each is a separate blog post, so the strongest proof that AI-SAST finds what scanners miss is scattered.

    High impactMedium effort First result in 1 month Security Researcher

    First action

    List the disclosures published so far.

    How to measure it

    Disclosure-page demos

    Now
    –
    Target
    5 a month
    By
    1 quarter

    Steps

    1. 1

      Collect

      All disclosures.

      Security Researcher 1 day

    2. 2

      Design

      Simple table.

      Web Developer 2 days

    3. 3

      Publish

      Linked from Maze Code.

      Marketing Coordinator 1 day

    4. 4

      Add new ones

      With each post.

      Security Researcher ongoing

    5. 5

      Promote

      Social and newsletter.

      Marketing Coordinator monthly

    6. 6

      Measure

      Visits and demos.

      Head of Marketing monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Security Researcher

    Smallest test

    Publish the table with the existing five.

    Why it works

    Build one page listing every disclosure: project, bug class, severity, CVE, date fixed and a link to the write-up, with a line on how Maze Code found it. Add each new finding as it is published.

    A growing list of real, fixed bugs is concrete evidence buyers and press can check, and it ranks for project names.

    Risks and how to handle them

    • Projects dislike attention

      List only coordinated, fixed disclosures.

    Evidence

    • Your blogVulnerability research posts: "PHP2Shell: two critical PHP RCEs, and how to tell if you're affected" (October 22, 2026), "Removed from a Plane project? One invite can bring you back as admin" (October 20), "There's a ten-year-old key confusion bug in PyJWT" (September 16), "Maze Code found a Langfuse SSO bug" (July 2), "Maze Code found an account takeover bug in Saleor" and "79 Gadgets Hidden in a Single Deserialization Flaw". The PHP2Shell post walks readers through a manual "Are you affected?" check; its only Maze calls to action are the site-wide "See Maze investigate a real vulnerability. Book a demo" footer and a newsletter box.Source
    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
  • 10

    The writer role says Maze often puts ad money behind organic winners. Without a rule, budget goes to what is funniest, not what reaches buyers.

    High impactMedium effort First result in 1 quarter Head of Marketing

    First action

    Set the engagement threshold from the last ten pieces.

    How to measure it

    Cost per demo

    Now
    –
    Target
    below LinkedIn average
    By
    1 quarter

    Steps

    1. 1

      Baseline

      Last ten pieces.

      Head of Marketing 1 day

    2. 2

      Rule

      Threshold and cap.

      Head of Marketing 1 day

    3. 3

      Landing

      Themed pages.

      Web Developer 1 week

    4. 4

      Boost

      Weekly.

      Head of Marketing weekly

    5. 5

      Review

      Cost per demo.

      Head of Marketing monthly

    6. 6

      Share

      Results with writers.

      Staff Writer (Satire), the Exploit monthly

    First result
    1 quarter
    Cost
    Ad budget
    Owner
    Head of Marketing

    Smallest test

    Apply the rule to the next three boosts.

    Why it works

    Boost pieces that beat a set organic engagement level among security titles, send paid clicks to the themed page from idea 1, cap spend per piece, and review cost per sign-up and demo monthly.

    A rule keeps satire spend accountable and makes the writer share fair and predictable.

    Risks and how to handle them

    • Funny but no buyers

      Target security job titles.

    Builds on

    Evidence

    • HiringStaff Writer (Satire), the Exploit (posted November 1, 2026): "the Exploit ... is a satirical publication from Maze"; Maze is hiring "two satire content creators" who each ship "5 articles and 5 videos a month", every story becoming "a short social video, usually a 30- to 90-second news segment". "When one of your pieces performs organically, we often put ad money behind it", and the writer earns "3% of the spend". Writers must have "Real practitioner experience" in security or software.Source
    • The Exploittheexploit.co ("Breaking Satire Before Its Patched"; in Maze's menu as "Like the Onion, but for security") has 56 linked articles on its homepage, a newsletter, "Submit Story" and "Advertise". Its Maze ads and "Brought to you by" logo all link to the mazehq.com homepage with only "utm_source=theexploit", whatever the article is about: the piece "Vulnerability Scanner Now Offers Discounts for Every Finding It Gets Wrong" carries the same homepage link as the RSA Conference jokes. Other ad slots rotate parody ads for invented vendors.Source
  • 11

    Maze Code already finds business-logic bugs in open-source projects. ZeroPath claims 2x more findings with fewer false positives; buyers want to see results on code they know.

    High impactMedium effort First result in 1 quarter Security Researcher

    First action

    Set the monthly limit and the report template.

    How to measure it

    Review-to-demo rate

    Now
    –
    Target
    25%
    By
    1 quarter

    Steps

    1. 1

      Rules

      Public repos, monthly cap.

      Security Researcher 1 week

    2. 2

      Form

      Submission page.

      Web Developer 1 week

    3. 3

      Run

      Reviews and short reports.

      Security Researcher ongoing

    4. 4

      Disclose

      Coordinate any real bugs with maintainers.

      Security Researcher ongoing

    5. 5

      Follow up

      Demo offer.

      Account Executive ongoing

    6. 6

      Measure

      Demos and pipeline.

      Head of Marketing monthly

    First result
    1 quarter
    Cost
    Compute and researcher time
    Owner
    Security Researcher

    Smallest test

    Review five repos from target accounts.

    Why it works

    Let engineers submit a public repository for a free Maze Code review, limited each month, and return a short report with any confirmed findings. Follow up with a demo on their private code.

    Seeing a real finding on familiar code is the most convincing proof and gives AEs a warm reason to talk.

    Risks and how to handle them

    • Findings in projects, not buyers

      Prioritise repos owned by the submitter's company.

    Evidence

    • Your blogVulnerability research posts: "PHP2Shell: two critical PHP RCEs, and how to tell if you're affected" (October 22, 2026), "Removed from a Plane project? One invite can bring you back as admin" (October 20), "There's a ten-year-old key confusion bug in PyJWT" (September 16), "Maze Code found a Langfuse SSO bug" (July 2), "Maze Code found an account takeover bug in Saleor" and "79 Gadgets Hidden in a Single Deserialization Flaw". The PHP2Shell post walks readers through a manual "Are you affected?" check; its only Maze calls to action are the site-wide "See Maze investigate a real vulnerability. Book a demo" footer and a newsletter box.Source
    • Competitor researchRivals' own homepages: Snyk, "Snyk AI Security Platform | Secure Code, Agents & Apps" with "Get started for free or book a demo"; Semgrep, "AI-assisted SAST, SCA and Secrets Detection"; Endor Labs, "Agentic Application Security Platform"; Aikido, "Secure everything your devs build, ship & run"; ZeroPath, "AI-native SAST that finds 2x more vulnerabilities with 75% fewer false positives".Source
    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
  • 12

    Maze publishes a "Maze + Wiz" resource. Many cloud security teams run Wiz and still face the vulnerability backlog Maze investigates.

    Medium impactMedium effort First result in 2 quarters Co founder and CEO

    First action

    Ask the Wiz partner team about a joint webinar.

    How to measure it

    Wiz-user opportunities

    Now
    –
    Target
    10
    By
    2 quarters

    Steps

    1. 1

      Partner talk

      Joint options.

      Co-founder and CEO 2 weeks

    2. 2

      Landing page

      For Wiz customers.

      Product Marketing Manager 1 week

    3. 3

      Webinar

      Joint session.

      Head of Marketing 1 month

    4. 4

      Directory

      Integration listing.

      Product Marketing Manager 1 month

    5. 5

      Follow up

      Attendees.

      Account Executive 1 week

    6. 6

      Measure

      Pipeline.

      Head of Marketing quarterly

    First result
    2 quarters
    Cost
    Staff time
    Owner
    Co founder and CEO

    Smallest test

    Publish the Wiz landing page.

    Why it works

    Run a joint webinar and a "for Wiz customers" landing page showing how Maze investigates Wiz findings, and list Maze in Wiz's integration directory if eligible.

    An existing platform audience lowers acquisition cost and answers "does it fit our stack?" up front.

    Risks and how to handle them

    • Partner says no

      Run the page and webinar alone.

    Evidence

    • Your websiteProof and partners: "Maze Named a Cloud Security Segment Leader in the 2025 Latio Cloud Security Report", a Latio datasheet, "An Analyst's Take on Maze", a security creator's "First Look at Maze" video, "Maze + Wiz", "Should CISOs Build or Buy?" and "Build your own agent". The Videos page holds four videos.Source
    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
  • 13

    Maze was named a Cloud Security Segment Leader in the 2025 Latio report and has an analyst take and a security creator's first look, but they sit in Resources. The demo page and homepage do not use them.

    Medium impactLow effort First result in 2 weeks Product Marketing Manager

    First action

    Add the badge to the demo page.

    How to measure it

    Demo-page conversion

    Now
    –
    Target
    +10%
    By
    60 days

    Steps

    1. 1

      Pick quotes

      Analyst and creator.

      Product Marketing Manager 1 day

    2. 2

      Design

      Badge row.

      Web Developer 1 day

    3. 3

      Add

      Homepage and demo.

      Marketing Coordinator 1 day

    4. 4

      Video

      Confirmation page.

      Marketing Coordinator 1 day

    5. 5

      Sales

      Follow-up templates.

      Account Executive 1 day

    6. 6

      Measure

      Conversion.

      Head of Marketing monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Product Marketing Manager

    Smallest test

    Add the badge today.

    Why it works

    Add the Latio badge and a short quote to the homepage and demo page, and the first-look video to the demo confirmation page and sales follow-ups.

    Independent voices reassure buyers who distrust vendor claims.

    Risks and how to handle them

    • Dated recognition

      Refresh with 2026 reports.

    Evidence

    • Your websiteProof and partners: "Maze Named a Cloud Security Segment Leader in the 2025 Latio Cloud Security Report", a Latio datasheet, "An Analyst's Take on Maze", a security creator's "First Look at Maze" video, "Maze + Wiz", "Should CISOs Build or Buy?" and "Build your own agent". The Videos page holds four videos.Source
    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
  • 14

    Maze already appears at OWASP meetups and the Global AppSec reception. Chapters need speakers, and Maze has real disclosures to talk about.

    Medium impactLow effort First result in 2 quarters Security Researcher

    First action

    Write the talk outline.

    How to measure it

    Chapter talks

    Now
    –
    Target
    6
    By
    2 quarters

    Steps

    1. 1

      Outline

      Five real bugs.

      Security Researcher 1 week

    2. 2

      Slides

      Reusable deck.

      Security Researcher 1 week

    3. 3

      Offer

      To chapters.

      Marketing Coordinator 2 weeks

    4. 4

      Give talks

      Monthly.

      Security Researcher monthly

    5. 5

      Follow up

      Slides and alert list.

      Marketing Coordinator monthly

    6. 6

      Measure

      Contacts and pipeline.

      Head of Marketing quarterly

    First result
    2 quarters
    Cost
    Travel or remote time
    Owner
    Security Researcher

    Smallest test

    Give the talk at one chapter.

    Why it works

    Prepare one talk ("Business-logic bugs scanners miss: five real examples"), offer it to OWASP chapters monthly, and share the slides with a link to the disclosure page.

    Teaching practitioners earns trust that sponsorship alone does not.

    Risks and how to handle them

    • Seen as a pitch

      Keep product to one slide.

    Evidence

    • Your websiteEvents: a lunch roundtable on frontier AI and cyber in New York, an OWASP Global AppSec reception, a KubeCon after-party, a re:Invent 2026 bar night, a Black Hat Europe happy hour, a fwd:cloudsec Europe social, a padel social in London, OWASP chapter meetups and a webinar "The hardest problems we solved building Maze".Source
    • Your blogVulnerability research posts: "PHP2Shell: two critical PHP RCEs, and how to tell if you're affected" (October 22, 2026), "Removed from a Plane project? One invite can bring you back as admin" (October 20), "There's a ten-year-old key confusion bug in PyJWT" (September 16), "Maze Code found a Langfuse SSO bug" (July 2), "Maze Code found an account takeover bug in Saleor" and "79 Gadgets Hidden in a Single Deserialization Flaw". The PHP2Shell post walks readers through a manual "Are you affected?" check; its only Maze calls to action are the site-wide "See Maze investigate a real vulnerability. Book a demo" footer and a newsletter box.Source
  • 15

    The site's closing line is "See Maze investigate a real vulnerability. Book a demo", but the only way to see it is a meeting. The Videos page has four videos, none a product walkthrough.

    Medium impactMedium effort First result in 1 month Product Marketing Manager

    First action

    Pick one CVE to show.

    How to measure it

    Viewer-to-demo rate

    Now
    –
    Target
    8%
    By
    1 quarter

    Steps

    1. 1

      Pick CVE

      Recent and well known.

      Security Researcher 1 day

    2. 2

      Script

      Five minutes.

      Product Marketing Manager 2 days

    3. 3

      Record

      Screen and voice.

      Product Marketing Manager 1 week

    4. 4

      Publish

      Homepage and demo page.

      Marketing Coordinator 1 day

    5. 5

      Clips

      Social cuts.

      Staff Writer (Satire), the Exploit 1 week

    6. 6

      Measure

      Views to demos.

      Head of Marketing monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Product Marketing Manager

    Smallest test

    Record the walkthrough on one CVE.

    Why it works

    Record a five-minute walkthrough of Maze investigating one real CVE end to end, put it on the homepage and demo page, and offer the demo after it.

    Many engineers want to see before they talk; a walkthrough qualifies them.

    Risks and how to handle them

    • Showing customer data

      Use a test environment.

    Evidence

    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
    • Your websiteProof and partners: "Maze Named a Cloud Security Segment Leader in the 2025 Latio Cloud Security Report", a Latio datasheet, "An Analyst's Take on Maze", a security creator's "First Look at Maze" video, "Maze + Wiz", "Should CISOs Build or Buy?" and "Build your own agent". The Videos page holds four videos.Source
    • Google PageSpeedmazehq.com scores 94 on mobile and 96 on desktop, with accessibility and SEO at 100. Real visitors (Chrome UX Report) see the main content in 1.2 s at the 75th percentile with no layout shift, so speed is not the problem. The lab's largest element on mobile is the cookie banner text.Source

Big bets 2

Larger plays that can change the trajectory.

  • 16

    Maze says 90% of the vulnerabilities it investigates are not exploitable, and it writes up major CVEs such as PHP2Shell. Security teams and journalists want to know which headline CVEs really matter.

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

    First action

    Agree the aggregation rules with customers' consent.

    How to measure it

    Sign-ups per index

    Now
    –
    Target
    300
    By
    3 quarters

    Steps

    1. 1

      Rules

      Consent and aggregation.

      Co-founder and CEO 1 month

    2. 2

      Pipeline

      Monthly data pull.

      Security Researcher 1 month

    3. 3

      Write

      Index and notes.

      Security Researcher monthly

    4. 4

      Publish

      Blog and newsletter.

      Marketing Coordinator monthly

    5. 5

      Pitch

      Security press.

      Head of Marketing monthly

    6. 6

      Review

      After three issues.

      Co-founder and CEO quarterly

    First result
    2 quarters
    Cost
    Researcher time
    Owner
    Co founder and CEO

    Smallest test

    Publish one index on last month's CVEs.

    Why it works

    Each month, publish an index of the top CVEs with how often they were exploitable in practice (aggregated, anonymised) and why. Pitch it to security press and newsletters.

    Recurring, unique data builds authority and links, and it proves Maze's core claim every month.

    Risks and how to handle them

    • Customer data concerns

      Publish only aggregates with consent.

    Evidence

    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
    • Your blogVulnerability research posts: "PHP2Shell: two critical PHP RCEs, and how to tell if you're affected" (October 22, 2026), "Removed from a Plane project? One invite can bring you back as admin" (October 20), "There's a ten-year-old key confusion bug in PyJWT" (September 16), "Maze Code found a Langfuse SSO bug" (July 2), "Maze Code found an account takeover bug in Saleor" and "79 Gadgets Hidden in a Single Deserialization Flaw". The PHP2Shell post walks readers through a manual "Are you affected?" check; its only Maze calls to action are the site-wide "See Maze investigate a real vulnerability. Book a demo" footer and a newsletter box.Source
    • Company recordsMAZE AI LIMITED, UK company 15203461, headquartered in London; the founders started Maze in 2024 after "many years working for security vendors" and promise to "Treat customers with respect" and avoid "Marketing designed to confuse rather than inform".Source
  • 17

    Maze sends fixes "to your coding agent or engineer", and its site already welcomes AI agents with an OpenAPI description. Developers increasingly work inside coding assistants.

    High impactHigh effort First result in 3 quarters Co founder and CEO

    First action

    Scope the read-only version.

    How to measure it

    Active agent-tool teams

    Now
    –
    Target
    100
    By
    3 quarters

    Steps

    1. 1

      Scope

      Tools and limits.

      Co-founder and CEO 1 month

    2. 2

      Build

      First version.

      Founding Engineer 2 months

    3. 3

      Security review

      Access and data.

      Security Researcher 2 weeks

    4. 4

      Docs

      Setup guide.

      Product Marketing Manager 2 weeks

    5. 5

      Directories

      Listings.

      Marketing Coordinator 1 week

    6. 6

      Measure

      Usage and upgrades.

      Head of Marketing monthly

    First result
    3 quarters
    Cost
    Engineering time
    Owner
    Co founder and CEO

    Smallest test

    Release to ten design partners.

    Why it works

    Offer a Maze tool for coding agents (for example an MCP server) that checks whether a finding is exploitable and returns a verified fix, with a free tier for open-source projects. List it in public tool directories.

    Being inside the developer's agent puts Maze in daily work and creates bottom-up demand.

    Risks and how to handle them

    • Support load

      Start with a waitlist.

    Evidence

    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
    • Your websiterobots.txt welcomes AI agents and points to /llms.txt, a Markdown sitemap and /openapi.json; "Every page also has a Markdown twin". The llms.txt and Markdown sitemap (about 128 entries) are alphabetical, so the first seven entries are paid-ad landing pages (noindex pages, labelled as paid in their titles), and the list also includes the internal content style guide.Source

Wildcards 3

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

  • 18

    Maze already hosts parties at re:Invent, KubeCon and Black Hat Europe, and the Exploit's best pieces are about conferences ("Judge Sentences CISO to 8 Consecutive Hours on RSA Expo Floor").

    Medium impactMedium effort First result in 2 quarters Head of Marketing

    First action

    Pick the conference and venue.

    How to measure it

    Guests

    Now
    –
    Target
    150
    By
    2 quarters

    Steps

    1. 1

      Pick event

      One conference.

      Head of Marketing 1 week

    2. 2

      Book venue

      Near the venue.

      Marketing Coordinator 1 month

    3. 3

      Write set

      Fifteen minutes.

      Staff Writer (Satire), the Exploit 2 weeks

    4. 4

      Invite

      HubSpot page and emails.

      Marketing Coordinator 1 month

    5. 5

      Film

      Clips for social.

      Staff Writer (Satire), the Exploit on the night

    6. 6

      Follow up

      48-hour sequence.

      Marketing Coordinator 1 week

    First result
    2 quarters
    Cost
    Event budget
    Owner
    Head of Marketing

    Smallest test

    Run a ten-minute set at the next London social.

    Why it works

    Host a short live Exploit news desk at the next big conference: the writers read the week's satire, then drinks. Collect RSVPs in HubSpot and follow up with the themed pages.

    A memorable event beats another happy hour and gives the writers video material.

    Risks and how to handle them

    • Jokes miss

      Test the set at a London social first.

    Evidence

    • HiringStaff Writer (Satire), the Exploit (posted November 1, 2026): "the Exploit ... is a satirical publication from Maze"; Maze is hiring "two satire content creators" who each ship "5 articles and 5 videos a month", every story becoming "a short social video, usually a 30- to 90-second news segment". "When one of your pieces performs organically, we often put ad money behind it", and the writer earns "3% of the spend". Writers must have "Real practitioner experience" in security or software.Source
    • The Exploittheexploit.co ("Breaking Satire Before Its Patched"; in Maze's menu as "Like the Onion, but for security") has 56 linked articles on its homepage, a newsletter, "Submit Story" and "Advertise". Its Maze ads and "Brought to you by" logo all link to the mazehq.com homepage with only "utm_source=theexploit", whatever the article is about: the piece "Vulnerability Scanner Now Offers Discounts for Every Finding It Gets Wrong" carries the same homepage link as the RSA Conference jokes. Other ad slots rotate parody ads for invented vendors.Source
    • Your websiteEvents: a lunch roundtable on frontier AI and cyber in New York, an OWASP Global AppSec reception, a KubeCon after-party, a re:Invent 2026 bar night, a Black Hat Europe happy hour, a fwd:cloudsec Europe social, a padel social in London, OWASP chapter meetups and a webinar "The hardest problems we solved building Maze".Source
    • HiringMarketing Coordinator (Part Time, posted October 21, 2026): "Build event landing pages and invite emails in HubSpot from our templates", "Send invite reminders, track RSVPs and follow up with guests", "Upload attendee lists into HubSpot after each event", "Update pages on our website through our CMS", "Build and schedule marketing emails in HubSpot", schedule social posts and "repurpose content into new formats". Maze describes itself as "an AI-native code security company" and "a well-funded Series A startup".Source
  • 19

    Maze published "2025: The Year Vulnerabilities Broke Every Record". Each customer has its own year of investigations and fixes.

    Medium impactMedium effort First result in 1 quarter Product Marketing Manager

    First action

    Define the five numbers.

    How to measure it

    Reports shared internally

    Now
    –
    Target
    50% of customers
    By
    1 quarter

    Steps

    1. 1

      Numbers

      Five metrics.

      Product Marketing Manager 1 week

    2. 2

      Template

      Report and card.

      Web Developer 2 weeks

    3. 3

      Generate

      Per customer.

      Founding Engineer 2 weeks

    4. 4

      Send

      Year end.

      Account Executive 1 week

    5. 5

      Collect quotes

      For stories.

      Product Marketing Manager 1 month

    6. 6

      Measure

      Shares and renewals.

      Head of Marketing quarterly

    First result
    1 quarter
    Cost
    Staff time
    Owner
    Product Marketing Manager

    Smallest test

    Make one report for one customer.

    Why it works

    Send each customer a short personal year-end report: findings investigated, share not exploitable, fixes shipped and hours saved, with a shareable card for their security team.

    It reminds buyers of value before renewal and gives champions something to show leadership.

    Risks and how to handle them

    • Small numbers for new customers

      Send only after three months of use.

    Evidence

    • Your websiteHomepage: "Autonomous security for modern software"; "Maze's agents find and fix vulnerabilities using the full context of your code and cloud"; "90% of the vulnerabilities analyzed by Maze are not exploitable when investigated"; "1 fix can resolve hundreds of vulnerabilities"; products Maze Cloud, Maze Code (AI-SAST, AI-SCA), container security and remediation; quotes from security leaders at Alloy, Cohere Health, Forge and PartsSource; "Book a demo" is the only call to action. /pricing returns 404.Source
    • Your websiteLearning Center listicles such as "Best SAST tools for 2026: 15 solutions compared", "Top 14 SCA tools compared", "Best AI-powered vulnerability management platforms: top 8 in 2026" and "Kubernetes security tools: 15 solutions"; there are no head-to-head "Maze vs" pages. One customer story (Cohere Health "cleared 92% of its critical and high findings").Source
  • 20

    Maze is based in London and has run a padel social and a Cyber Peterborough deep dive. Regular, local events build a community that one-off parties do not.

    Medium impactLow effort First result in 2 quarters Marketing Coordinator

    First action

    Book the next three dates.

    How to measure it

    Regulars

    Now
    –
    Target
    40
    By
    2 quarters

    Steps

    1. 1

      Dates

      Three months.

      Marketing Coordinator 1 week

    2. 2

      Venue

      One regular place.

      Marketing Coordinator 1 week

    3. 3

      Talks

      Ten minutes each.

      Security Researcher monthly

    4. 4

      Invites

      HubSpot.

      Marketing Coordinator monthly

    5. 5

      Follow up

      Content and alert list.

      Marketing Coordinator monthly

    6. 6

      Review

      After three.

      Head of Marketing quarterly

    First result
    2 quarters
    Cost
    Small event budget
    Owner
    Marketing Coordinator

    Smallest test

    Run the next social with a short talk.

    Why it works

    Run a monthly London social with a ten-minute talk (a disclosure or an Exploit reading), rotate hosts with friendly companies, and keep a HubSpot list of regulars.

    A steady local community feeds hiring, partnerships and UK pipeline.

    Risks and how to handle them

    • Low turnout

      Co-host with a local group.

    Evidence

    • Your websiteEvents: a lunch roundtable on frontier AI and cyber in New York, an OWASP Global AppSec reception, a KubeCon after-party, a re:Invent 2026 bar night, a Black Hat Europe happy hour, a fwd:cloudsec Europe social, a padel social in London, OWASP chapter meetups and a webinar "The hardest problems we solved building Maze".Source
    • Company recordsMAZE AI LIMITED, UK company 15203461, headquartered in London; the founders started Maze in 2024 after "many years working for security vendors" and promise to "Treat customers with respect" and avoid "Marketing designed to confuse rather than inform".Source
    • HiringMarketing Coordinator (Part Time, posted October 21, 2026): "Build event landing pages and invite emails in HubSpot from our templates", "Send invite reminders, track RSVPs and follow up with guests", "Upload attendee lists into HubSpot after each event", "Update pages on our website through our CMS", "Build and schedule marketing emails in HubSpot", schedule social posts and "repurpose content into new formats". Maze describes itself as "an AI-native code security company" and "a well-funded Series A startup".Source

03

How Programmable can help

Where an idea in this playbook is something Programmable builds or runs, it's listed here with what we'd do. Everything else is yours to run.

ProgrammableTalk

Fill the events in this plan

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

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

More growth playbooks

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

  • Soda Web Media growth strategyAn Atlanta Shopify Partner agency that designs, builds and migrates Shopify stores and grows them with SEO, CRO, paid ads, email and SMS…21 growth ideas
  • ProcIndex growth strategyAI accounting agents for construction and manufacturing finance teams: AP capture, matching, coding and posting to the ERP, a…24 growth ideas
  • DataDome growth strategyBot and AI agent trust management: real-time detection of bots, fraud and AI agents across websites, apps, APIs and MCP servers, with…20 growth ideas
  • SupplyOne growth strategyA packaging manufacturer and distributor: custom corrugated, foam, wood and plastics converting, packaging supplies, equipment and…24 growth ideas
  • Hatch growth strategyAn AI communications platform for the trades: AI CSRs that answer calls, texts, emails and web chat, qualify leads and book jobs 24/7…21 growth ideas
  • New Relic growth strategyAn intelligent observability platform: APM, infrastructure, logs, digital experience, AI monitoring, security and AI agents (SRE Agent…21 growth ideas
  • Kitab growth strategyA wisdom app with Kavi, an AI companion that turns what is on your mind into key ideas from books, 3-minute Wisdom Bites and guided…21 growth ideas
  • Check growth strategyEmbedded payroll infrastructure: an API, UI components, tax filing and support that let software platforms offer payroll to the businesses…21 growth ideas

See every playbook and website review

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

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

    Exploit article cards, advisory calls to action, event follow-up, llms.txt, comparison pages and a buying page.

  2. Days 31 to 6010 ideas

    Newsletter bridge, customer stories, disclosure page, paid-boost rule, free repo review, Wiz co-marketing, proof on the demo page, OWASP talks and a recorded walkthrough; start London socials.

  3. Days 61 to 904 ideas

    Commit to the exploitability index, the coding-agent tool, the Exploit Live night and customer year-end reports.

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 less scanner noise. The most cited problem: vulnerability backlogs from scanners.

  • Knowing what is actually exploitable
  • CVSS scores that ignore context
  • In their words: “noise”

Market

Competitive landscape

5 competitors compared: Snyk, Semgrep, Endor Labs, Aikido and 1 more.

  • Gap to exploit: Proof of exploitability, not just findings
  • Snyk: Scanner-style volume of findings
  • Semgrep: Less cloud context

Hiring signals

Maze's open roles are about reach.

  • Staff Writer (Satire), the Exploit: Satire articles and videos, boosted with paid spend. Ideas 1, 10, 18.
  • Marketing Coordinator (Part Time): Events, HubSpot and CMS. Ideas 3, 4, 7, 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 firstNew accounts get 100,000 free enrichment credits with code BETA100K (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)
  • ProgrammableMediaAn AI note taker, interpreter and webinar host for your calls (opens programmable.media 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