ProgrammableMarketing/ghosteye.ai (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

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

growth playbook · Nov 10, 2026

ghosteye.ai (opens in a new tab)

GhostEye growth playbook

Diagnosis

GhostEye (YC Summer 2025, a team of 6 in New York) has a sharp story and an unusually deep library for its size: 274 glossary terms, 93 blog posts and 24 free worksheets, on a site that scores 100 for speed. The gaps are in the paths from that library to a sale.

The glossary, two-thirds of the site, has no route to the free campaign. The free-campaign page is a bare calendar for an event called "demo", with a duplicate Book a Demo page next to it. The worksheets have names nobody searches for, and there are no case studies, no newsletter, no pricing guidance and nothing on the events page except past events.

This playbook connects the library to the free campaign first, then adds proof, complement pages, packaging and retests, and puts the two engineers being hired on a self-serve scoped test and a results API.

Growth Score

6/10

Biggest Opportunity

Turn the large, fast, well-written library into a pipeline: every glossary term, worksheet and scenario post should lead to a free campaign scoped around the attack the reader just studied.

Biggest Risk

Adaptive Security, Hoxhunt and KnowBe4 sell social engineering simulations to the same buyers at far greater scale (2,000 to 70,000 customers), and GhostEye currently relies on onboarding work by its own team to run each campaign.

01

Start here

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

  1. 1

    Put the free first campaign on all 274 glossary pages, matched to each page's topic

    Write the nine topic lines and add the block to the glossary template, keyed on the topic field.

    High impact First result in 2-4 weeks
  2. 2

    Ask three scoping questions before the calendar, and retire the duplicate Book a Demo page

    Add the three questions to the booking calendar's intake and rename the event.

    High impact First result in 2 weeks
  3. 3

    Rename the 24 worksheets after the job they do, so people search for them and forward them

    List the 24 worksheets with the job each one does and a new title.

    Medium impact First result in 1 month

02

Your idea portfolio

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

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

Showing 22 of 22 ideas

This week 6

Quick wins with a clear first action.

  • 01

    Two-thirds of ghosteye.ai's 415 indexed pages are glossary definitions: 274 terms in nine topics, from Help-desk & recovery to Email & fraud. Every blog post ends with "Request Your Free Campaign", but the glossary pages checked (the index, "Vishing", "Access token" and "Access review") have no link to the free campaign, the platform or the booking page. A security lead who arrives from search on "help-desk vishing" or "MFA fatigue" reads a careful definition and can only leave through a related post or an outside source. The site is not losing them to speed: it scores 100 and real visitors pass Core Web Vitals. The missing piece is the next step.

    High impactLow effort First result in 2-4 weeks Founding Head of Marketing

    First action

    Write the nine topic lines and add the block to the glossary template, keyed on the topic field.

    How to measure it

    Glossary-to-free-campaign click rate

    Now
    –
    Target
    1.5% of glossary visits
    By
    60 days

    Steps

    1. 1

      Check topic tags

      Confirm each of the 274 terms has one of the nine topics, and tag any that do not.

      Founding Head of Marketing 1 day

    2. 2

      Write nine lines

      One question and one offer per topic, in the plain voice of the existing pages, with no fear statistics.

      Founding Head of Marketing 1 day

    3. 3

      Build the block

      One component in the glossary template, after the definition, linking to /book-demo/ with the term as a URL parameter.

      Software Engineer, Full Stack 1 day

    4. 4

      Pass the term to the booking

      Carry the parameter into the calendar booking so the scoping call opens with the term the visitor read.

      Software Engineer, Full Stack 2 hours

    5. 5

      Pick a fallback post

      For each topic, choose the best scenario post for readers who are not ready to book.

      Founding Head of Marketing 1 day

    6. 6

      Measure by topic

      Clicks and bookings by topic each week, with the blog's closing button as the baseline.

      Founding Head of Marketing weekly

    7. 7

      Rewrite the weakest

      After 30 days, rewrite the two lowest-performing topic lines.

      Founding Head of Marketing 30 days

    First result
    2-4 weeks
    Cost
    Staff time only
    Owner
    Founding Head of Marketing

    Smallest test

    Add the block to the Help-desk & recovery and Social engineering terms only, and compare their click rate with the blog posts for a month.

    Why it works

    Add one block to the glossary template, chosen by the topic each term already carries. Nine short variants, one per topic, each asking the question that term raises and offering the free campaign as a scoped test of it. Example for Help-desk & recovery: "Would your help desk reset this account for the wrong caller? Your first campaign tests one recovery route, scoped and stopped where you choose." Place it after the definition and before Sources. Link to /book-demo/ with the term in the URL, so the scoping call starts from the attack the reader just studied. For topics where a test is a less natural ask (Data & incident response, for example), lead with the best scenario post and keep the button second.

    Glossary readers are looking up the exact attacks GhostEye simulates. Offering a scoped test of that attack at the moment they understand it turns reference traffic into scoping calls. Every term already carries one of nine topics, so one template component with nine lines covers all 274 pages.

    Ready to use

    CopyNine glossary call-to-action lines, one per topic

    Help-desk & recovery: Would your help desk reset this account for the wrong caller? Your first campaign tests one recovery route, scoped and stopped where you choose.
    Social engineering: See whether this works on your team, by voice, SMS, email or chat. Your first campaign is on us.
    Tokens & sessions: If someone handed over a session, what could it reach? Test it on designated accounts in your first campaign.
    Identity controls: Find out whether this control holds when someone asks politely. Scope a free first campaign.
    Security testing: Run this test against your people and controls, with evidence for the control owner. Your first campaign is on us.
    Email & fraud: Would a payment or supplier change get through? Test one approval route in a free campaign.
    Devices & software: Would someone install this because 'IT' asked? Find out in your first campaign.
    Applications & supply chain: Test whether a convincing request can open this door. Scope your first campaign.
    Data & incident response: Read the scenario first, then test whether your team would spot it. Your first campaign is on us.

    Risks and how to handle them

    • Reference pages start to feel like sales pages

      One line and one button below the definition; Sources and related terms stay as they are.

    • Glossary traffic is mostly students or researchers

      Judge by bookings, not clicks; if quality is low, offer the matching worksheet instead of the call.

    Evidence

    • Your websiteGlossary (checked November 9, 2026: the index and the "Vishing", "Access token" and "Access review" pages): 400-500-word definitions with sources, related terms and "See it in practice" links to blog posts, filed under nine topics (Help-desk & recovery, Social engineering, Tokens & sessions, Identity controls, Security testing, Email & fraud, Devices & software, Applications & supply chain, Data & incident response); none of these pages links to the free campaign, the platform or the booking page, and none shows a date.Source
    • Your websiteSitemap (415 URLs, checked November 9, 2026): 274 glossary terms plus an index, 93 blog posts, 12 event pages, worksheet and resource listings, and core pages (platform, integrations, why-ghosteye, company, book-demo, contact, information-security); no pricing, comparison, industry, solution or case-study pages.Source
    • Your websiteBlog post "Run an Account Recovery Tabletop: A Facilitator's Guide" (published August 21, 2026, by the CEO): a 90-minute agenda, four CSV facilitator files, links to the help-desk verification guide, and a closing section "Put a tabletop finding to the test." with the "Request Your Free Campaign" button; its structured data carries a dateModified of 2026-10-15 that readers do not see.Source
    • PageSpeedGoogle PageSpeed (November 9, 2026): mobile and desktop performance 100, accessibility 96 (one colour-contrast issue), SEO 100; real visitors pass Core Web Vitals (field LCP 1.5 s, CLS 0); homepage weight 126 KB.Source
  • 02

    The homepage's only button promises a free campaign, but /book-demo/ is a bare calendar for an event named "demo", with no questions. A second page, /book-a-demo/, sells "a demo" through the same calendar and is missing from the sitemap. GhostEye's platform page shows every campaign starts from a brief (objective, scope, team, stopping point), so the first call is spent collecting answers a short form could have gathered.

    High impactLow effort First result in 2 weeks Founder & CEO

    First action

    Add the three questions to the booking calendar's intake and rename the event.

    How to measure it

    Scoping-call-to-campaign rate

    Now
    –
    Target
    +25%
    By
    90 days

    Steps

    1. 1

      Write the questions

      Three multiple-choice questions taken from the campaign brief.

      Founder & CEO 1 hour

    2. 2

      Add them to the booking

      Intake questions on the calendar event, which is renamed "Free campaign scoping".

      Founding Head of Marketing 1 hour

    3. 3

      Redirect the duplicate

      301 from /book-a-demo/ to /book-demo/, and update any menu links.

      Software Engineer, Full Stack 1 hour

    4. 4

      Draft briefs ahead

      Before each call, prefill a campaign brief from the answers.

      Founder & CEO per call

    5. 5

      Track the funnel

      Page visits, bookings, show rate and campaigns launched.

      Founding Head of Marketing weekly

    6. 6

      Tune the choices

      After 20 bookings, reorder the route options by how often they are picked.

      Founder & CEO 1 month

    First result
    2 weeks
    Cost
    $0
    Owner
    Founder & CEO

    Smallest test

    Add one question (which route worries you most) this week.

    Why it works

    Before the calendar, ask three questions: which route worries you most (help-desk account recovery, payroll or supplier changes, MFA resets, executive impersonation), which identity provider you use (the six directory integrations), and roughly how many employees. Pass the answers into the booking and rename the event "Free campaign scoping". Redirect /book-a-demo/ to /book-demo/ so every button leads to one page and one measure.

    Buyers who name their worry before the call arrive with intent, and the founder can open with a draft brief instead of discovery questions. One page also gives one conversion rate to improve.

    Ready to use

    CopyScoping questions

    1. Which route worries you most? Help-desk account recovery / Payroll or supplier bank-detail changes / MFA reset or enrolment / Executive impersonation / Not sure yet
    2. Which identity provider do you use? Microsoft Entra ID / Okta / Google Workspace / OneLogin / JumpCloud / Other
    3. Roughly how many employees? Under 250 / 250-1,000 / 1,000-5,000 / 5,000+

    Risks and how to handle them

    • Questions lower the booking rate

      Keep them optional and multiple-choice; compare bookings for two weeks before and after.

    Evidence

    • Your websiteFree-campaign page /book-demo/ ("Request Your Free Campaign | GhostEye"): "Your first campaign is on us." and "Book Your Scoping Call", with no form fields, only an "Open booking calendar" link to a calendar event named "demo". A second page, /book-a-demo/ ("Book a Demo": "See how far an attacker could go in your organization"), uses the same calendar and is not in the sitemap.Source
    • Your websitePlatform page: hero "Find where impersonation could lead to access."; a campaign brief (objective, scope, team, before launch, stopping point); a four-step help-desk recovery workflow run by "a configured voice agent"; the platform automates "voice and message steps", recurring execution and campaign metrics, while GhostEye's team "defines the scenario, prepares campaigns and sign-in pages during onboarding"; outcome cards such as "The help desk blocks the request" and "Recovery succeeds without required verification"; reporting is a dashboard and an Excel export, and "A reporting API is not currently available."Source
    • Your websiteIntegrations page: 19 integrations in six groups: Directory sync (Google Workspace, Microsoft Entra ID, Okta, OneLogin, JumpCloud, SCIM 2.0), Email simulations (Google and Microsoft DMI), Messaging (Slack, Microsoft Teams), Email gateways (Mimecast, Proofpoint, Defender for Office 365), Ticketing (Jira, Linear, ServiceNow) and Compliance (Vanta, Drata, Secureframe); no SIEM, EDR or phone group, although the homepage example shows Splunk, Microsoft Sentinel, CrowdStrike and SentinelOne.Source
  • 03

    GhostEye gives away 24 practical worksheets with no email form, but many are named for what they are inside the article rather than what a reader needs: "Fictional join ledger", "Fictional evidence CSV", "Review instructions", "Handoff card". Two cards even point to the same article. A help-desk manager searching for an "MFA reset call log template" will never find a "Fictional join ledger".

    Medium impactLow effort First result in 1 month Founding Head of Marketing

    First action

    List the 24 worksheets with the job each one does and a new title.

    How to measure it

    Monthly worksheet downloads

    Now
    –
    Target
    2x
    By
    90 days

    Steps

    1. 1

      List the jobs

      For each worksheet, the task it helps with and who does it.

      Founding Head of Marketing 1 day

    2. 2

      Retitle

      Task-first names with the format in brackets.

      Founding Head of Marketing 1 day

    3. 3

      Fix the duplicate

      Give the two cards for the same article distinct roles or merge them.

      Founding Head of Marketing 1 hour

    4. 4

      Add download pages

      One short page per worksheet with a preview, the article link and the free-campaign link.

      Software Engineer, Full Stack 2 days

    5. 5

      Link from the glossary

      Show the matching worksheet on related glossary terms.

      Software Engineer, Full Stack 1 day

    6. 6

      Measure

      Downloads and search impressions per worksheet.

      Founding Head of Marketing monthly

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

    Smallest test

    Retitle the five worksheets with the most generic names and compare their downloads after a month.

    Why it works

    Give each worksheet a searchable title and a one-line "use this when" (for example, "Help-desk MFA reset call log (CSV template): use this when reviewing who approved a reset"). Merge or relabel the duplicate pair, and add a short download page per worksheet, so each can rank, be shared and carry a link to the matching free campaign.

    Templates are among the most searched and most forwarded security resources, and a clear name is what makes someone send one to a colleague. The content already exists; only the labels change.

    Risks and how to handle them

    • Old download links break

      Keep the file URLs the same and change only titles and pages.

    Evidence

    • Your websiteWorksheets page: 24 free worksheets as CSV or Markdown downloads with no email form; many carry generic names such as "Fictional join ledger", "Fictional evidence CSV", "Review instructions" and "Handoff card", and two cards point to the same article.Source
    • Your websiteBlog post "Run an Account Recovery Tabletop: A Facilitator's Guide" (published August 21, 2026, by the CEO): a 90-minute agenda, four CSV facilitator files, links to the help-desk verification guide, and a closing section "Put a tabletop finding to the test." with the "Request Your Free Campaign" button; its structured data carries a dateModified of 2026-10-15 that readers do not see.Source
  • 04

    The homepage's example attack ends in reporting and detection, shown with Splunk, Microsoft Sentinel, CrowdStrike and SentinelOne. The integrations page lists 19 integrations in six groups, and none of those four, and no SIEM, EDR or phone group. A SOC lead who checks the integrations page after the homepage cannot tell whether GhostEye connects to their tools or reviews their records during the campaign.

    Medium impactLow effort First result in 2 weeks Founder & CEO

    First action

    Write three sentences on how SIEM and EDR evidence is gathered today.

    How to measure it

    Integrations-to-booking clicks

    Now
    –
    Target
    +20%
    By
    60 days

    Steps

    1. 1

      Agree the facts

      Which SOC, EDR and phone records each past campaign used, and how.

      Founder & CEO 1 day

    2. 2

      Write the group

      "Evidence sources" with each tool and how its records are used.

      Founding Head of Marketing 2 hours

    3. 3

      Add it to the page

      A seventh group on the integrations page, searchable like the rest.

      Software Engineer, Full Stack 2 hours

    4. 4

      Match the homepage

      Make the homepage example link to the new group.

      Software Engineer, Full Stack 1 hour

    5. 5

      Brief the calls

      Use the same wording on scoping calls.

      Founder & CEO 1 hour

    6. 6

      Review quarterly

      Move tools into connected groups as integrations ship.

      Founder & CEO quarterly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founder & CEO

    Smallest test

    Add one sentence under the integrations search box this week.

    Why it works

    Add an "Evidence sources" group that says plainly how SOC, EDR and help-desk records are used today: connected, exported by the customer, or reviewed together during the evidence review. Name the tools that have been used in campaigns, and say what is planned. Add the same answer to the scoping call notes.

    Security buyers rule tools out early on integration fit. A clear, honest answer keeps the SOC owner in the deal instead of leaving them with an open question.

    Risks and how to handle them

    • Overstating integrations

      Label each tool as connected or evidence reviewed with your team.

    Evidence

    • Your websiteIntegrations page: 19 integrations in six groups: Directory sync (Google Workspace, Microsoft Entra ID, Okta, OneLogin, JumpCloud, SCIM 2.0), Email simulations (Google and Microsoft DMI), Messaging (Slack, Microsoft Teams), Email gateways (Mimecast, Proofpoint, Defender for Office 365), Ticketing (Jira, Linear, ServiceNow) and Compliance (Vanta, Drata, Secureframe); no SIEM, EDR or phone group, although the homepage example shows Splunk, Microsoft Sentinel, CrowdStrike and SentinelOne.Source
    • Your websiteHomepage (checked November 9, 2026): H1 "How far would an attacker go?"; GhostEye "pairs social engineering testing with breach and attack simulation" and traces an example SMS attack through account, API and directory access (Microsoft Graph, Entra ID) to reporting and detection (Splunk, Microsoft Sentinel, CrowdStrike, SentinelOne); logos of Eight Sleep, Everest Global Insurance, Day One Agency, Fella Health, Precision Medicine Group, Kontigo and Essential Personnel; quotes from Eight Sleep's Head of Information Security ("GhostEye showed us how real attackers would target our team, not just through email") and Fella Health's VP of Engineering ("move beyond checkbox security awareness with realistic, role-specific simulations"); one call to action, "Request Your Free Campaign" ("Your first campaign is on us."); no statistics.Source
  • 05

    None of the glossary pages checked shows a date, and their structured data has none either. Blog posts show a publish date, but the update date (2026-10-15 on the tabletop guide) is only in the code. Security readers, search engines and AI answer tools all weigh how current a security source is, and attack techniques date quickly.

    Medium impactLow effort First result in 1 month Software Engineer

    First action

    Add a reviewed-date field to the glossary content and fill it with the last commit date.

    How to measure it

    Glossary organic clicks

    Now
    –
    Target
    +15%
    By
    90 days

    Steps

    1. 1

      Add the field

      A reviewed date on each glossary entry, filled from history.

      Software Engineer, Full Stack half a day

    2. 2

      Show it

      "Last reviewed" under the title; "Updated" on changed posts.

      Software Engineer, Full Stack 2 hours

    3. 3

      Add structured data

      datePublished and dateModified on glossary pages.

      Software Engineer, Full Stack 2 hours

    4. 4

      Set a review cycle

      Quarterly for Help-desk & recovery and Tokens & sessions; yearly for the rest.

      Founding Head of Marketing 1 hour

    5. 5

      Review the top 20

      Check the most visited terms first and update their dates honestly.

      Founding Head of Marketing 1 week

    6. 6

      Measure

      Search clicks for glossary pages in Search Console.

      Founding Head of Marketing monthly

    First result
    1 month
    Cost
    $0
    Owner
    Software Engineer, Full Stack

    Smallest test

    Show dates on the Help-desk & recovery topic first.

    Why it works

    Show "Last reviewed" on every glossary term and "Updated" on blog posts that changed, from one field in the site's content files. Add datePublished and dateModified to the glossary structured data, and set a review cycle for the help-desk and token topics, where techniques change fastest.

    Visible review dates make a careful library look maintained, which matters for buyers judging a security vendor's expertise and for answer engines choosing which source to quote.

    Risks and how to handle them

    • Dates show pages as old

      Review the most visited terms before switching dates on.

    Evidence

    • Your websiteGlossary (checked November 9, 2026: the index and the "Vishing", "Access token" and "Access review" pages): 400-500-word definitions with sources, related terms and "See it in practice" links to blog posts, filed under nine topics (Help-desk & recovery, Social engineering, Tokens & sessions, Identity controls, Security testing, Email & fraud, Devices & software, Applications & supply chain, Data & incident response); none of these pages links to the free campaign, the platform or the booking page, and none shows a date.Source
    • Your websiteBlog post "Run an Account Recovery Tabletop: A Facilitator's Guide" (published August 21, 2026, by the CEO): a 90-minute agenda, four CSV facilitator files, links to the help-desk verification guide, and a closing section "Put a tabletop finding to the test." with the "Request Your Free Campaign" button; its structured data carries a dateModified of 2026-10-15 that readers do not see.Source
  • 06

    GhostEye attended or sponsored 12 events in a year, from RSAC and Black Hat USA to a gold sponsorship at SecureWorld New York on October 29, 2026. All 12 now sit under "Past Events", with nothing upcoming, and the event pages have no recordings, slides or recaps. Contacts met at a booth who check the site afterwards find a team that seems to have gone quiet.

    Medium impactLow effort First result in Next event Founding Head of Marketing

    First action

    List the next six events and publish them under an "Upcoming" heading.

    How to measure it

    Pre-booked event meetings

    Now
    –
    Target
    8 per event
    By
    next two events

    Steps

    1. 1

      List upcoming events

      The next six, with dates and whether GhostEye speaks or sponsors.

      Founding Head of Marketing 1 day

    2. 2

      Split the page

      "Upcoming" above "Past", with a booking link on each upcoming card.

      Software Engineer, Full Stack half a day

    3. 3

      Tag the bookings

      Event name passed to the scoping page.

      Software Engineer, Full Stack 1 hour

    4. 4

      Write recaps

      One scenario, one question and one worksheet per past event.

      Founding Head of Marketing 1 week

    5. 5

      Follow up in 48 hours

      Send booth contacts the recap and the free-campaign offer.

      Founder & CEO per event

    6. 6

      Count pipeline

      Meetings and campaigns per event, to choose next year's list.

      Founding Head of Marketing quarterly

    First result
    Next event
    Cost
    Staff time only
    Owner
    Founding Head of Marketing

    Smallest test

    Publish the next confirmed event with a booking link today.

    Why it works

    Publish the next six planned events with a "book 20 minutes with us there" link that goes to the scoping page tagged by event. Turn each past event page into a short recap: the scenario shown, the most common question asked, and a worksheet. Send booth contacts the recap within 48 hours.

    Conferences are GhostEye's most visible spend. Booking meetings before the event and following up with something useful afterwards is where event pipeline is won or lost.

    Risks and how to handle them

    • Plans change

      List only confirmed events and update the page monthly.

    Evidence

    • Your websiteEvents page: all 12 events (October 2025 to October 29, 2026, including RSAC, Black Hat USA, SecTor, GrrCON, BSides NYC and SecureWorld New York as a gold sponsor) sit under "Past Events", with nothing upcoming; event pages link to the free campaign but carry no recordings, slides or recaps.Source
    • Your websiteFree-campaign page /book-demo/ ("Request Your Free Campaign | GhostEye"): "Your first campaign is on us." and "Book Your Scoping Call", with no form fields, only an "Open booking calendar" link to a calendar event named "demo". A second page, /book-a-demo/ ("Book a Demo": "See how far an attacker could go in your organization"), uses the same calendar and is not in the sitemap.Source

This quarter 11

The core plays for the next three months.

  • 07

    The homepage shows seven customer logos (Eight Sleep, Everest Global Insurance, Fella Health, Precision Medicine Group and others) and quotes from Eight Sleep's Head of Information Security and Fella Health's VP of Engineering. The site has no case-study pages, and the resources hub has no reports, so a CISO evaluating GhostEye cannot see what a campaign found or what changed.

    High impactMedium effort First result in 6 weeks Founding Head of Marketing

    First action

    Ask the two quoted customers whether they will approve a one-page story.

    How to measure it

    Case-study-assisted bookings

    Now
    –
    Target
    30% of bookings
    By
    1 quarter

    Steps

    1. 1

      Ask for approval

      Named or anonymised, with the customer's security lead.

      Founder & CEO 1 week

    2. 2

      Pull the evidence

      Outcome cards, timeline and retest result from each campaign.

      Founder & CEO 2 days

    3. 3

      Write three stories

      Scenario, response, access, detection, fix, retest.

      Founding Head of Marketing 2 weeks

    4. 4

      Customer review

      Remove anything sensitive before publishing.

      Founder & CEO 1 week

    5. 5

      Publish and link

      Homepage, free-campaign page and matching glossary topics.

      Software Engineer, Full Stack 1 day

    6. 6

      Use in sales

      Send the closest story after every scoping call.

      Founder & CEO ongoing

    First result
    6 weeks
    Cost
    Staff time only
    Owner
    Founding Head of Marketing

    Smallest test

    Publish one anonymised story and send it after the next five scoping calls.

    Why it works

    Write three one-page stories in the shape the platform already reports: the scenario, what the help desk or employee did, what access followed, what the SOC saw, the fix, and the retest result. Use named customers where they agree and an anonymised industry label ("a specialty insurer") where they do not. Link each from the homepage, the free-campaign page and the matching glossary topic.

    Security buyers want proof from peers before they let a vendor call their help desk. Stories told as outcome cards are specific enough to trust and short enough to forward.

    Risks and how to handle them

    • Customers will not publish test results

      Offer anonymised stories and share only the fix and retest, not the weakness.

    Evidence

    • Your websiteHomepage (checked November 9, 2026): H1 "How far would an attacker go?"; GhostEye "pairs social engineering testing with breach and attack simulation" and traces an example SMS attack through account, API and directory access (Microsoft Graph, Entra ID) to reporting and detection (Splunk, Microsoft Sentinel, CrowdStrike, SentinelOne); logos of Eight Sleep, Everest Global Insurance, Day One Agency, Fella Health, Precision Medicine Group, Kontigo and Essential Personnel; quotes from Eight Sleep's Head of Information Security ("GhostEye showed us how real attackers would target our team, not just through email") and Fella Health's VP of Engineering ("move beyond checkbox security awareness with realistic, role-specific simulations"); one call to action, "Request Your Free Campaign" ("Your first campaign is on us."); no statistics.Source
    • Your websiteResources hub: a search box but no topic filters, no newsletter or email signup, and no case studies or reports; the only offer is "Your first campaign is on us."Source
    • Your websitePlatform page: hero "Find where impersonation could lead to access."; a campaign brief (objective, scope, team, before launch, stopping point); a four-step help-desk recovery workflow run by "a configured voice agent"; the platform automates "voice and message steps", recurring execution and campaign metrics, while GhostEye's team "defines the scenario, prepares campaigns and sign-in pages during onboarding"; outcome cards such as "The help desk blocks the request" and "Recovery succeeds without required verification"; reporting is a dashboard and an Excel export, and "A reporting API is not currently available."Source
  • 08

    GhostEye's Why page tells buyers to "Keep your awareness program and technical assessments." The largest rivals sell awareness training and simulations to the same buyers: KnowBe4 claims 70,000 customers, Adaptive Security over 2,000, and Hoxhunt runs email, SMS, phone and Teams simulations. The site has no comparison pages at all, so the buyer who already owns one of those tools gets no answer to "why add GhostEye?"

    High impactMedium effort First result in 6 weeks Founding Head of Marketing

    First action

    List what each of the four tools tests, from their own pages.

    How to measure it

    Complement-page bookings

    Now
    –
    Target
    6 a month
    By
    1 quarter

    Steps

    1. 1

      Check each tool

      What each rival's own site says it tests, by channel.

      Founding Head of Marketing 2 days

    2. 2

      Map the gap

      Scenarios GhostEye tests that each tool does not describe.

      Founder & CEO 1 day

    3. 3

      Write four pages

      Covered, not covered, side by side, and how results feed training.

      Founding Head of Marketing 2 weeks

    4. 4

      Fact check

      Date each page and cite the rival's own pages; review claims and trademarks.

      Founder & CEO 2 days

    5. 5

      Publish

      Linked from the Why page and the integrations page.

      Software Engineer, Full Stack 1 day

    6. 6

      Refresh

      Check every rival claim each quarter.

      Founding Head of Marketing quarterly

    First result
    6 weeks
    Cost
    Staff time only
    Owner
    Founding Head of Marketing

    Smallest test

    Publish the KnowBe4 page first and track bookings.

    Why it works

    Write four factual pages: GhostEye with KnowBe4, with Hoxhunt, with Adaptive Security, and with a breach-and-attack-simulation tool such as Picus. Each explains what the existing tool already covers, what it does not test (the help-desk recovery call, the access after the click, the SOC's view), how the two run side by side, and how GhostEye results can inform the existing training. End with the free campaign scoped to the gap.

    Most buyers already pay for awareness training and will not replace it. Pages that add to the tool they own match how the Why page already sells, and capture searches for those brands from people evaluating what else they need.

    Risks and how to handle them

    • Claims about rivals go stale

      Quote only their own pages, with dates.

    Evidence

    • Your websiteWhy GhostEye page: "Keep your awareness program and technical assessments."; impersonation tests across "voice, email, SMS, and chat"; a section "What a CISO should ask to see"; "A conversation alone cannot establish account compromise"; a "Read the verification guide" link; no vendor comparisons and no statistics.Source
    • Competitor researchRivals' own homepages: Adaptive Security, "Protect your workforce from AI threats", with email, voice and SMS simulations and "over 2,000 customers"; Hoxhunt, "Measurably reduce human cyber risk, at scale", with email, SMS, phone and Teams simulations and ROI and risk calculators; KnowBe4, "70,000 global customers"; Picus, an "Autonomous Exposure Validation Platform" that includes breach and attack simulation.Source
    • Your websiteSitemap (415 URLs, checked November 9, 2026): 274 glossary terms plus an index, 93 blog posts, 12 event pages, worksheet and resource listings, and core pages (platform, integrations, why-ghosteye, company, book-demo, contact, information-security); no pricing, comparison, industry, solution or case-study pages.Source
  • 09

    GhostEye has no pricing page and no named plans. Its YC profile promises an "always-on red team" that will "retest until the fix holds", while the platform supports recurring execution for selected groups. A buyer finishing a free campaign has no picture of what comes next or what it costs, which slows budget conversations.

    High impactMedium effort First result in 1 quarter Founder & CEO

    First action

    Write down what the last five paying customers bought and group it into three shapes.

    How to measure it

    Free-to-paid conversion

    Now
    –
    Target
    40%
    By
    2 quarters

    Steps

    1. 1

      Group past deals

      Scope, channels and retests in recent deals.

      Founder & CEO 1 day

    2. 2

      Define three packages

      Inclusions, limits and price factors.

      Founder & CEO 1 week

    3. 3

      Write the page

      "After your first campaign", linked from the free-campaign page.

      Founding Head of Marketing 3 days

    4. 4

      Add to the readout

      End every free-campaign review with the three options.

      Founder & CEO 1 day

    5. 5

      Publish

      Indexed page, no gate.

      Software Engineer, Full Stack 1 day

    6. 6

      Review mix

      Which package buyers pick, every quarter.

      Founder & CEO quarterly

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

    Smallest test

    Show the three packages on one slide at the next three campaign readouts.

    Why it works

    Publish a short "After your first campaign" page with three packages: a single-route test (one scenario, one retest), a quarterly program (four scenarios a year with retests and a leadership summary), and always-on (recurring campaigns across voice, SMS, email and chat). Show what each includes and either a "from" price or the factors that set it (employees, scenarios, channels). Present the same three options at the end of every free campaign.

    Named packages make the step from free to paid concrete, and they set the quarterly program as the default, which turns one-off tests into recurring revenue.

    Risks and how to handle them

    • Public prices anchor too low for enterprise

      Show "from" prices for the smallest package only and price factors for the rest.

    Evidence

    • Your websiteSitemap (415 URLs, checked November 9, 2026): 274 glossary terms plus an index, 93 blog posts, 12 event pages, worksheet and resource listings, and core pages (platform, integrations, why-ghosteye, company, book-demo, contact, information-security); no pricing, comparison, industry, solution or case-study pages.Source
    • Y CombinatorYC profile: Summer 2025 batch, team of 6, New York; "Your always-on red team."; "We emulate the attacks real adversaries run today: help-desk vishing, deepfaked executives, MFA fatigue, and the payloads that follow"; "retest until the fix holds, and give your leadership the evidence that risk actually went down"; the CEO is a former BlackRock red team lead who worked in offensive cyber operations at MITRE.Source
    • Your websitePlatform page: hero "Find where impersonation could lead to access."; a campaign brief (objective, scope, team, before launch, stopping point); a four-step help-desk recovery workflow run by "a configured voice agent"; the platform automates "voice and message steps", recurring execution and campaign metrics, while GhostEye's team "defines the scenario, prepares campaigns and sign-in pages during onboarding"; outcome cards such as "The help desk blocks the request" and "Recovery succeeds without required verification"; reporting is a dashboard and an Excel export, and "A reporting API is not currently available."Source
  • 10

    GhostEye's own promise is to "retest until the fix holds, and give your leadership the evidence that risk actually went down". The platform's outcome cards already name an owner for each result, and the Why page recommends retesting after a change. But a retest that depends on the customer remembering to ask is easy to lose, and it is the moment that proves value before renewal.

    High impactMedium effort First result in 1-2 months Founder & CEO

    First action

    Add "book the retest" as the last item of the campaign review agenda.

    How to measure it

    Retest completion rate

    Now
    –
    Target
    70% of campaigns
    By
    2 quarters

    Steps

    1. 1

      Change the review agenda

      End with the fix, its owner and the retest date.

      Founder & CEO 1 hour

    2. 2

      Schedule in the product

      Use recurring execution to queue the same scenario.

      Software Engineer, Backend / Platform 1 week

    3. 3

      Design the page

      Before and after outcome cards on one page.

      Software Engineer, Full Stack 1 week

    4. 4

      Send to leadership

      Through the CISO, with a two-line summary.

      Founder & CEO per retest

    5. 5

      Track

      Scheduled, completed and passed retests.

      Founder & CEO monthly

    6. 6

      Tie to renewal

      Open each renewal call with the before-and-after pages.

      Founder & CEO per renewal

    First result
    1-2 months
    Cost
    Staff and engineering time
    Owner
    Founder & CEO

    Smallest test

    Book retests for the next three campaigns on the review call.

    Why it works

    At the end of every campaign review, book the retest date with the control owner on the call, 30 days after the agreed fix. Run the same scenario, then send a one-page before-and-after ("The help desk blocked the request" replacing "Recovery succeeds without required verification") to the CISO, written for their leadership. Track retests scheduled, completed and passed.

    A passed retest is the clearest proof the product works, and it lands with the people who sign renewals. Booking it on the review call stops it from slipping.

    Risks and how to handle them

    • The fix is not made in 30 days

      Run the retest anyway; an unchanged result is still useful evidence for leadership.

    Evidence

    • Y CombinatorYC profile: Summer 2025 batch, team of 6, New York; "Your always-on red team."; "We emulate the attacks real adversaries run today: help-desk vishing, deepfaked executives, MFA fatigue, and the payloads that follow"; "retest until the fix holds, and give your leadership the evidence that risk actually went down"; the CEO is a former BlackRock red team lead who worked in offensive cyber operations at MITRE.Source
    • Your websitePlatform page: hero "Find where impersonation could lead to access."; a campaign brief (objective, scope, team, before launch, stopping point); a four-step help-desk recovery workflow run by "a configured voice agent"; the platform automates "voice and message steps", recurring execution and campaign metrics, while GhostEye's team "defines the scenario, prepares campaigns and sign-in pages during onboarding"; outcome cards such as "The help desk blocks the request" and "Recovery succeeds without required verification"; reporting is a dashboard and an Excel export, and "A reporting API is not currently available."Source
    • Your websiteWhy GhostEye page: "Keep your awareness program and technical assessments."; impersonation tests across "voice, email, SMS, and chat"; a section "What a CISO should ask to see"; "A conversation alone cannot establish account compromise"; a "Read the verification guide" link; no vendor comparisons and no statistics.Source
  • 11

    GhostEye already lists Vanta, Drata and Secureframe under Compliance, and it has completed its own SOC 2 Type II. But the integrations page only lists the names. Security teams that run their audits in those tools spend time each year collecting evidence that their people and processes were tested; GhostEye could make that evidence appear by itself.

    Medium impactMedium effort First result in 1 quarter Software Engineer

    First action

    Screenshot what a finished campaign looks like inside one compliance tool.

    How to measure it

    Compliance integration adoption

    Now
    –
    Target
    50% of paying customers
    By
    2 quarters

    Steps

    1. 1

      Document the output

      What each integration sends today and where it lands.

      Software Engineer, Backend / Platform 2 days

    2. 2

      Fill any gaps

      Add the retest result and scope if they are missing.

      Software Engineer, Backend / Platform 2 weeks

    3. 3

      Write three pages

      One per compliance tool, with screenshots.

      Founding Head of Marketing 1 week

    4. 4

      Add to scoping

      Ask which compliance tool the buyer uses.

      Founder & CEO 1 hour

    5. 5

      Switch it on in onboarding

      Default step for customers who use one.

      Founder & CEO ongoing

    6. 6

      Measure

      Adoption and renewal rate with and without it.

      Founder & CEO quarterly

    First result
    1 quarter
    Cost
    Engineering and writing time
    Owner
    Software Engineer, Backend / Platform

    Smallest test

    Show the compliance-tool screenshot at the next five scoping calls.

    Why it works

    Write one page per compliance tool showing exactly what GhostEye sends (campaign dates, scenario, scope, outcome summary, retest result), where it appears in that tool, and who sees it. Add a short version to the free-campaign page ("evidence lands in your compliance tool") and to the scoping questions.

    It turns a test into recurring paperwork the customer no longer has to do, which helps the deal through procurement and makes the subscription harder to drop.

    Risks and how to handle them

    • Implying audit requirements

      Describe the evidence sent, not what any framework or auditor requires.

    Evidence

    • Your websiteIntegrations page: 19 integrations in six groups: Directory sync (Google Workspace, Microsoft Entra ID, Okta, OneLogin, JumpCloud, SCIM 2.0), Email simulations (Google and Microsoft DMI), Messaging (Slack, Microsoft Teams), Email gateways (Mimecast, Proofpoint, Defender for Office 365), Ticketing (Jira, Linear, ServiceNow) and Compliance (Vanta, Drata, Secureframe); no SIEM, EDR or phone group, although the homepage example shows Splunk, Microsoft Sentinel, CrowdStrike and SentinelOne.Source
    • Your websiteInformation security page: "GhostEye has completed a SOC 2 Type II examination"; it is pursuing ISO 27001, GDPR, HIPAA and FedRAMP 20x; annual penetration tests of the platform; a Trust Center to request the SOC 2 report.Source
    • Your websitePlatform page: hero "Find where impersonation could lead to access."; a campaign brief (objective, scope, team, before launch, stopping point); a four-step help-desk recovery workflow run by "a configured voice agent"; the platform automates "voice and message steps", recurring execution and campaign metrics, while GhostEye's team "defines the scenario, prepares campaigns and sign-in pages during onboarding"; outcome cards such as "The help desk blocks the request" and "Recovery succeeds without required verification"; reporting is a dashboard and an Excel export, and "A reporting API is not currently available."Source
  • 12

    GhostEye's job posts say customers include government organizations and Fortune 100 companies, and the security page lists FedRAMP 20x among the standards it is pursuing. The site has no industry or sector pages, so a public-sector security lead has to piece together GhostEye's fit from the security page and a job post.

    High impactMedium effort First result in 1 quarter Founder & CEO

    First action

    Write the exact current FedRAMP 20x status in one sentence.

    How to measure it

    Public-sector bookings

    Now
    –
    Target
    3 a month
    By
    2 quarters

    Steps

    1. 1

      State the status

      SOC 2 Type II done; FedRAMP 20x exactly where it stands.

      Founder & CEO 1 hour

    2. 2

      Pick scenarios

      Three that matter most for agencies.

      Founder & CEO 1 day

    3. 3

      Write the page

      Scenarios, authorisation, data handling and buying routes.

      Founding Head of Marketing 1 week

    4. 4

      Get a reference

      Ask a government customer whether a description can be shared.

      Founder & CEO 2 weeks

    5. 5

      Publish and link

      From the security page and the Trust Center.

      Software Engineer, Full Stack 1 day

    6. 6

      Use in outreach

      Send to public-sector contacts from events.

      Founder & CEO ongoing

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

    Smallest test

    Send the draft page to three public-sector contacts for feedback.

    Why it works

    Publish one public-sector page: what GhostEye tests for agencies (help-desk recovery, impersonation of officials by voice and SMS), how campaigns are authorised and scoped, the SOC 2 Type II and the current FedRAMP 20x status stated exactly, data handling, and how to buy. Link it from the security page and use it in outreach and at public-sector events.

    Government buyers screen vendors on authorisation and buying routes first. One page that answers those questions shortens the first conversation and makes existing government work visible.

    Risks and how to handle them

    • Overstating authorisation status

      Use the exact wording from the security page and update it when the status changes.

    Evidence

    • HiringSoftware Engineer, Backend / Platform (New York, $150K-$225K, 0.50%-2.50% equity): GhostEye is "building an automated social engineer" with its own voice synthesis and self-hosted phone infrastructure; customers include government organizations and Fortune 100 companies; the role connects "campaign configuration, scheduling, execution, and results", phone and SMS delivery, and "scoped account, session, and downstream access checks".Source
    • Your websiteInformation security page: "GhostEye has completed a SOC 2 Type II examination"; it is pursuing ISO 27001, GDPR, HIPAA and FedRAMP 20x; annual penetration tests of the platform; a Trust Center to request the SOC 2 report.Source
    • Your websiteSitemap (415 URLs, checked November 9, 2026): 274 glossary terms plus an index, 93 blog posts, 12 event pages, worksheet and resource listings, and core pages (platform, integrations, why-ghosteye, company, book-demo, contact, information-security); no pricing, comparison, industry, solution or case-study pages.Source
  • 13

    GhostEye's own team "defines the scenario, prepares campaigns and sign-in pages during onboarding", while the platform automates the calls and messages. With a team of six, that onboarding work caps how many customers can start. Virtual CISO firms and security-services providers already run assessments for many mid-sized companies and need a repeatable social engineering test they can deliver.

    High impactMedium effort First result in 1 quarter Founder & CEO

    First action

    List ten vCISO or security-services firms met at this year's events.

    How to measure it

    Partner-delivered campaigns

    Now
    –
    Target
    10 a quarter
    By
    2 quarters

    Steps

    1. 1

      Pick firms

      Ten candidates from event contacts and customers' advisers.

      Founder & CEO 1 week

    2. 2

      Set the terms

      Referral fee or margin, scope approval and evidence review.

      Founder & CEO 1 week

    3. 3

      Package the library

      Scenario briefs partners can choose from.

      Founder & CEO 2 weeks

    4. 4

      Train partners

      One session on scoping, authorisation and readouts.

      Founder & CEO 1 day

    5. 5

      Co-brand the readout

      Partner logo on the campaign summary.

      Software Engineer, Full Stack 1 week

    6. 6

      Review quarterly

      Campaigns, conversions and quality by partner.

      Founder & CEO quarterly

    First result
    1 quarter
    Cost
    Partner margin and staff time
    Owner
    Founder & CEO

    Smallest test

    Run one campaign with one partner for one of their clients.

    Why it works

    Build a small partner program: partners scope and run campaigns for their clients on GhostEye, using a shared scenario library and the campaign brief, with GhostEye reviewing scope and evidence. Offer a margin or referral fee, co-branded readouts and a partner-only training session. Start with five firms that already serve companies of 250-5,000 employees.

    Partners bring trusted relationships and do the onboarding work, so GhostEye reaches more customers without hiring a services team, and the partner's client gets a test their awareness tool does not cover.

    Risks and how to handle them

    • Partners run tests badly or out of scope

      GhostEye approves every scope and keeps the stopping-point controls.

    Evidence

    • Your websitePlatform page: hero "Find where impersonation could lead to access."; a campaign brief (objective, scope, team, before launch, stopping point); a four-step help-desk recovery workflow run by "a configured voice agent"; the platform automates "voice and message steps", recurring execution and campaign metrics, while GhostEye's team "defines the scenario, prepares campaigns and sign-in pages during onboarding"; outcome cards such as "The help desk blocks the request" and "Recovery succeeds without required verification"; reporting is a dashboard and an Excel export, and "A reporting API is not currently available."Source
    • Y CombinatorYC profile: Summer 2025 batch, team of 6, New York; "Your always-on red team."; "We emulate the attacks real adversaries run today: help-desk vishing, deepfaked executives, MFA fatigue, and the payloads that follow"; "retest until the fix holds, and give your leadership the evidence that risk actually went down"; the CEO is a former BlackRock red team lead who worked in offensive cyber operations at MITRE.Source
    • Your websiteEvents page: all 12 events (October 2025 to October 29, 2026, including RSAC, Black Hat USA, SecTor, GrrCON, BSides NYC and SecureWorld New York as a gold sponsor) sit under "Past Events", with nothing upcoming; event pages link to the free campaign but carry no recordings, slides or recaps.Source
  • 14

    GhostEye publishes a lot (93 blog posts, 274 glossary terms, 24 worksheets), but the resources hub has no newsletter or email signup and the worksheets download with no form. Every reader who is not ready for a scoping call today leaves with no way to hear from GhostEye again.

    Medium impactLow effort First result in 1 month Founding Head of Marketing

    First action

    Add a signup box to the blog template.

    How to measure it

    Subscribers

    Now
    –
    Target
    1,000
    By
    2 quarters

    Steps

    1. 1

      Pick a tool

      A simple email tool with double opt-in.

      Founding Head of Marketing 1 day

    2. 2

      Add signups

      Blog, worksheet pages and the glossary block.

      Software Engineer, Full Stack 1 day

    3. 3

      Plan six issues

      One scenario and worksheet each, from existing posts.

      Founding Head of Marketing 2 days

    4. 4

      Send the first

      Help-desk account recovery.

      Founding Head of Marketing 1 day

    5. 5

      Track replies

      Clicks to the free campaign and replies.

      Founding Head of Marketing monthly

    6. 6

      Invite event contacts

      Offer the email to people met at events.

      Founder & CEO per event

    First result
    1 month
    Cost
    Under $50 a month
    Owner
    Founding Head of Marketing

    Smallest test

    Send one issue to event contacts who agreed to hear from GhostEye.

    Why it works

    Send one email a month: one attack scenario, the decision it tests, the worksheet that goes with it, and the free-campaign offer for that scenario. Add a one-field signup to the end of every blog post, to the worksheet pages and to the glossary block, and offer an optional email field next to each worksheet download (downloads stay ungated).

    Security buyers take months to act. A monthly, useful email keeps GhostEye in mind until the budget or the incident arrives, and the content already exists.

    Risks and how to handle them

    • Low signups

      Name the next issue's scenario at the signup box.

    Evidence

    • Your websiteResources hub: a search box but no topic filters, no newsletter or email signup, and no case studies or reports; the only offer is "Your first campaign is on us."Source
    • Your websiteWorksheets page: 24 free worksheets as CSV or Markdown downloads with no email form; many carry generic names such as "Fictional join ledger", "Fictional evidence CSV", "Review instructions" and "Handoff card", and two cards point to the same article.Source
    • Your websiteSitemap (415 URLs, checked November 9, 2026): 274 glossary terms plus an index, 93 blog posts, 12 event pages, worksheet and resource listings, and core pages (platform, integrations, why-ghosteye, company, book-demo, contact, information-security); no pricing, comparison, industry, solution or case-study pages.Source
  • 15

    The account-recovery tabletop guide gives a 90-minute agenda and four facilitator files, then ends: "Put a tabletop finding to the test." The platform's flagship workflow is the same scenario run live, a voice-agent recovery call to the help desk. The path is there in the content, but the free-campaign page does not mention it, so a team that ran the tabletop has to work out the next step for itself.

    Medium impactLow effort First result in 1 month Founder & CEO

    First action

    Add one paragraph on the free-campaign page describing the tabletop-to-test path.

    How to measure it

    Tabletop-sourced campaigns

    Now
    –
    Target
    25% of free campaigns
    By
    2 quarters

    Steps

    1. 1

      Name the offer

      "Tabletop to live test" with a one-paragraph description.

      Founding Head of Marketing 1 hour

    2. 2

      Update the guide

      Explain how the decision record becomes the campaign scope.

      Founder & CEO 1 day

    3. 3

      Add an upload step

      Let teams share the decision record when booking.

      Software Engineer, Full Stack 2 days

    4. 4

      Map to the brief

      Decision-record fields to campaign-brief fields.

      Founder & CEO 1 day

    5. 5

      Promote

      Newsletter, LinkedIn and event follow-ups.

      Founding Head of Marketing ongoing

    6. 6

      Measure

      Bookings mentioning a tabletop and their conversion.

      Founder & CEO monthly

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

    Smallest test

    Offer the tabletop-first route on the next five scoping calls.

    Why it works

    Package it as a named offer: "Tabletop to live test". The team runs the free tabletop with the guide and files, records the checks the help desk is expected to perform, and GhostEye's free first campaign tests exactly those checks by voice. Mention it on the free-campaign page and in the guide, and ask facilitators to share their decision record ahead of the scoping call.

    The tabletop gets the help-desk, identity and SOC owners into a room and agreed on what should happen; the live test then answers whether it does. The scoping call starts with the scope already written.

    Risks and how to handle them

    • Few teams run the tabletop

      Offer to facilitate it on a call as part of scoping.

    Evidence

    • Your websiteBlog post "Run an Account Recovery Tabletop: A Facilitator's Guide" (published August 21, 2026, by the CEO): a 90-minute agenda, four CSV facilitator files, links to the help-desk verification guide, and a closing section "Put a tabletop finding to the test." with the "Request Your Free Campaign" button; its structured data carries a dateModified of 2026-10-15 that readers do not see.Source
    • Your websitePlatform page: hero "Find where impersonation could lead to access."; a campaign brief (objective, scope, team, before launch, stopping point); a four-step help-desk recovery workflow run by "a configured voice agent"; the platform automates "voice and message steps", recurring execution and campaign metrics, while GhostEye's team "defines the scenario, prepares campaigns and sign-in pages during onboarding"; outcome cards such as "The help desk blocks the request" and "Recovery succeeds without required verification"; reporting is a dashboard and an Excel export, and "A reporting API is not currently available."Source
    • Your websiteFree-campaign page /book-demo/ ("Request Your Free Campaign | GhostEye"): "Your first campaign is on us." and "Book Your Scoping Call", with no form fields, only an "Open booking calendar" link to a calendar event named "demo". A second page, /book-a-demo/ ("Book a Demo": "See how far an attacker could go in your organization"), uses the same calendar and is not in the sitemap.Source
  • 16

    GhostEye has a story most security vendors lack: the company began after a caller impersonating the IRS targeted the CEO's mother, and the CEO led a red team at BlackRock and worked in offensive cyber operations at MITRE. It also has 93 scenario posts ready to use, which can be reshaped into one short practitioner post a week.

    Medium impactLow effort First result in 1 month Founding Head of Marketing

    First action

    Pick the first eight scenarios and draft the founding-story post.

    How to measure it

    Site visits from LinkedIn

    Now
    –
    Target
    3x
    By
    1 quarter

    Steps

    1. 1

      Pick scenarios

      Eight posts from the library with a worksheet each.

      Founding Head of Marketing 1 day

    2. 2

      Draft posts

      Request, why it works, the check that stops it.

      Founding Head of Marketing 1 week

    3. 3

      Founder edit

      In the CEO's voice, with one personal detail per post.

      Founder & CEO weekly

    4. 4

      Monthly video

      A short walk-through of a help-desk recovery call.

      Founder & CEO monthly

    5. 5

      Track

      Engagement, profile visits and site visits.

      Founding Head of Marketing weekly

    6. 6

      Reuse

      Best posts become newsletter issues and event talks.

      Founding Head of Marketing monthly

    First result
    1 month
    Cost
    Founder time, about one hour a week
    Owner
    Founding Head of Marketing

    Smallest test

    Publish the founding-story post and two scenarios, and compare site visits.

    Why it works

    Each week the CEO posts one scenario from the library in plain language: the request, why it works, the one check that stops it, and a link to the worksheet. Once a month, a short video from the founder walking through a help-desk recovery call. Open the series with the founding story from the company page.

    Security leaders follow practitioners, not brand pages. A former red-team lead explaining one attack a week builds trust and brings readers to the library, where idea 1's glossary blocks turn them into bookings.

    Risks and how to handle them

    • Posts teach attackers

      Focus each post on the defensive check, as the blog already does.

    Evidence

    • Your websiteCompany page: GhostEye began after a caller impersonating the IRS targeted the CEO's mother, which led to fraudulent loans in her name; the mission is "to help security teams understand how impersonation and pressure can lead to access"; the page lists a Founder & CEO and a Founding Head of Marketing.Source
    • Y CombinatorYC profile: Summer 2025 batch, team of 6, New York; "Your always-on red team."; "We emulate the attacks real adversaries run today: help-desk vishing, deepfaked executives, MFA fatigue, and the payloads that follow"; "retest until the fix holds, and give your leadership the evidence that risk actually went down"; the CEO is a former BlackRock red team lead who worked in offensive cyber operations at MITRE.Source
    • Your websiteSitemap (415 URLs, checked November 9, 2026): 274 glossary terms plus an index, 93 blog posts, 12 event pages, worksheet and resource listings, and core pages (platform, integrations, why-ghosteye, company, book-demo, contact, information-security); no pricing, comparison, industry, solution or case-study pages.Source
  • 22

    GhostEye's YC profile leads with "help-desk vishing, deepfaked executives, MFA fatigue". On ghosteye.ai, the homepage mentions neither deepfakes nor executives, and in the sitemap deepfake, voice cloning and MFA fatigue appear only as glossary terms, with no blog post or product page about executive impersonation. Rivals such as Adaptive Security lead their homepage with AI threats ("Protect your workforce from AI threats"), so buyers searching for those scenarios find them, not GhostEye.

    High impactMedium effort First result in 1-2 months Founding Head of Marketing

    First action

    Write the scenario page outline with the consent and authorisation steps first.

    How to measure it

    Executive-scenario bookings

    Now
    –
    Target
    20% of bookings
    By
    2 quarters

    Steps

    1. 1

      Outline the page

      Consent, targets, evidence and stopping point.

      Founder & CEO 2 days

    2. 2

      Write the page

      Plain language for CISOs and CFOs.

      Founding Head of Marketing 1 week

    3. 3

      Write two posts

      MFA fatigue and a deepfake-call checklist.

      Founding Head of Marketing 2 weeks

    4. 4

      Link the glossary

      From the deepfake, voice cloning and MFA fatigue terms.

      Software Engineer, Full Stack 1 hour

    5. 5

      Add to scoping

      Executive impersonation as a route option.

      Founder & CEO 1 hour

    6. 6

      Measure

      Search impressions and bookings that pick the scenario.

      Founding Head of Marketing monthly

    First result
    1-2 months
    Cost
    Staff time only
    Owner
    Founding Head of Marketing

    Smallest test

    Publish the deepfake-call checklist post and link it from the deepfake glossary term.

    Why it works

    Add one scenario page and two posts. The page: "Executive impersonation by voice", showing how a test is authorised with the impersonated executive's consent, what it targets (payment approvals, access requests, help-desk resets), and the evidence produced. The posts: an MFA-fatigue scenario with its verification check, and a deepfake-call checklist for finance and assistants. Link them from the three glossary terms and the homepage example.

    It matches the site to how GhostEye already describes itself, and to the scenario boards and CFOs ask about most, which opens a second buyer beside the CISO.

    Risks and how to handle them

    • Executive voice tests raise consent concerns

      Lead the page with written consent from the impersonated executive and the approval chain.

    Evidence

    • Your websiteTopic coverage (checked November 9, 2026): the YC profile leads with "deepfaked executives" and "MFA fatigue", but neither appears on the homepage; in the sitemap, deepfake, voice cloning and MFA fatigue exist only as glossary terms (/glossary/deepfake/, /glossary/voice-cloning/, /glossary/mfa-fatigue/), with no blog post or product page about executive impersonation.Source
    • Y CombinatorYC profile: Summer 2025 batch, team of 6, New York; "Your always-on red team."; "We emulate the attacks real adversaries run today: help-desk vishing, deepfaked executives, MFA fatigue, and the payloads that follow"; "retest until the fix holds, and give your leadership the evidence that risk actually went down"; the CEO is a former BlackRock red team lead who worked in offensive cyber operations at MITRE.Source
    • Competitor researchRivals' own homepages: Adaptive Security, "Protect your workforce from AI threats", with email, voice and SMS simulations and "over 2,000 customers"; Hoxhunt, "Measurably reduce human cyber risk, at scale", with email, SMS, phone and Teams simulations and ROI and risk calculators; KnowBe4, "70,000 global customers"; Picus, an "Autonomous Exposure Validation Platform" that includes breach and attack simulation.Source

Big bets 3

Larger plays that can change the trajectory.

  • 17

    Today GhostEye's team defines each scenario and prepares campaigns during onboarding, and the free campaign starts with a call. The new full-stack role is building "campaign setup, targeting, scheduling, and approval workflows" and investigation screens that separate successful, blocked and untested steps. That is most of what a self-serve first test needs.

    High impactHigh effort First result in 2 quarters Software Engineer

    First action

    Write the approval and safety rules a self-serve run must meet before launch.

    How to measure it

    Self-serve tests per month

    Now
    –
    Target
    20
    By
    2 quarters after launch

    Steps

    1. 1

      Write the rules

      Verified domain, named approver, test account only, stopping point.

      Founder & CEO 1 week

    2. 2

      Pick the scenario

      One recovery-call scenario with fixed scope.

      Founder & CEO 1 week

    3. 3

      Build setup and approval

      Directory connection, approver sign-off and window.

      Software Engineer, Full Stack 6 weeks

    4. 4

      Build the run

      Scheduling, call delivery, cancellation and results.

      Software Engineer, Backend / Platform 6 weeks

    5. 5

      Human review

      GhostEye checks every run before launch at first.

      Founder & CEO ongoing

    6. 6

      Beta

      Ten design partners from event and newsletter contacts.

      Founder & CEO 1 month

    7. 7

      Measure

      Completed tests, conversion to paid and support load.

      Founder & CEO monthly

    First result
    2 quarters
    Cost
    About two engineer-quarters
    Owner
    Software Engineer, Full Stack

    Smallest test

    Run the self-serve flow by hand (a form and a human operator) for five companies.

    Why it works

    Let a verified security lead set up one pre-built scenario themselves: a help-desk recovery call against a designated test account. They connect their directory, name the help-desk owner who must approve, choose a window, and get the result screen and outcome cards when it finishes. Every run needs a named approver, a stopping point and a verified company domain, and GhostEye reviews each one before launch until the controls are proven.

    It removes the scheduling wait between interest and evidence, lets one small team serve many more first campaigns, and gives the glossary and content traffic a product to try, not only a call to book.

    Risks and how to handle them

    • Misuse against people who did not agree

      Verified domain, designated test accounts, named approver and human review before every launch.

    • Lower-quality leads

      Keep the scoping call as the next step after the result.

    Builds on

    Evidence

    • HiringSoftware Engineer, Full Stack (New York, same pay band): builds "campaign setup, targeting, scheduling, and approval workflows", live views of calls and messages, investigation screens that separate successful, blocked and untested attack steps, and "customer controls and reporting for post-click and downstream access tests".Source
    • Your websitePlatform page: hero "Find where impersonation could lead to access."; a campaign brief (objective, scope, team, before launch, stopping point); a four-step help-desk recovery workflow run by "a configured voice agent"; the platform automates "voice and message steps", recurring execution and campaign metrics, while GhostEye's team "defines the scenario, prepares campaigns and sign-in pages during onboarding"; outcome cards such as "The help desk blocks the request" and "Recovery succeeds without required verification"; reporting is a dashboard and an Excel export, and "A reporting API is not currently available."Source
    • Your websiteFree-campaign page /book-demo/ ("Request Your Free Campaign | GhostEye"): "Your first campaign is on us." and "Book Your Scoping Call", with no form fields, only an "Open booking calendar" link to a calendar event named "demo". A second page, /book-a-demo/ ("Book a Demo": "See how far an attacker could go in your organization"), uses the same calendar and is not in the sitemap.Source
  • 18

    The platform page states "A reporting API is not currently available"; results come as a dashboard and an Excel export. The homepage example shows detection evidence in Splunk, Microsoft Sentinel, CrowdStrike and SentinelOne, and GhostEye already connects to Jira, Linear and ServiceNow. The new backend role connects "campaign configuration, scheduling, execution, and results", the right moment to expose those results.

    High impactHigh effort First result in 2 quarters Software Engineer

    First action

    Write the API's resource list with three customers' security leads.

    How to measure it

    API adoption

    Now
    –
    Target
    40% of paying customers
    By
    3 quarters

    Steps

    1. 1

      Design with customers

      Resources and fields three customers need.

      Software Engineer, Backend / Platform 2 weeks

    2. 2

      Build read-only API

      Scoped tokens, tenant isolation and rate limits.

      Software Engineer, Backend / Platform 6 weeks

    3. 3

      Ticket connector

      Findings become remediation tickets with owners.

      Software Engineer, Backend / Platform 3 weeks

    4. 4

      SIEM connector

      Campaign events the SOC can match to alerts.

      Software Engineer, Backend / Platform 4 weeks

    5. 5

      Document

      Public docs and examples.

      Software Engineer, Full Stack 2 weeks

    6. 6

      Announce

      Integrations page, newsletter and the next event.

      Founding Head of Marketing 1 week

    First result
    2 quarters
    Cost
    About two engineer-quarters
    Owner
    Software Engineer, Backend / Platform

    Smallest test

    Push one customer's findings into their ticketing tool by script and ask what changed.

    Why it works

    Publish a read-only results API (campaigns, steps, outcomes, evidence links, retest status), then two connectors built on it: findings to the ticketing tools as remediation tickets with an owner, and campaign events to a SIEM so the SOC can match its alerts to the test. Document it in the existing platform documentation and announce it on the integrations page.

    Enterprise and government buyers expect results to flow into their own systems; an Excel export is a common reason security tools lose late-stage deals. Findings that live in the customer's ticket queue also keep GhostEye in their daily work.

    Risks and how to handle them

    • The API exposes sensitive test evidence

      Read-only, scoped tokens, and evidence links that require sign-in.

    Builds on

    Evidence

    • Your websitePlatform page: hero "Find where impersonation could lead to access."; a campaign brief (objective, scope, team, before launch, stopping point); a four-step help-desk recovery workflow run by "a configured voice agent"; the platform automates "voice and message steps", recurring execution and campaign metrics, while GhostEye's team "defines the scenario, prepares campaigns and sign-in pages during onboarding"; outcome cards such as "The help desk blocks the request" and "Recovery succeeds without required verification"; reporting is a dashboard and an Excel export, and "A reporting API is not currently available."Source
    • HiringSoftware Engineer, Backend / Platform (New York, $150K-$225K, 0.50%-2.50% equity): GhostEye is "building an automated social engineer" with its own voice synthesis and self-hosted phone infrastructure; customers include government organizations and Fortune 100 companies; the role connects "campaign configuration, scheduling, execution, and results", phone and SMS delivery, and "scoped account, session, and downstream access checks".Source
    • Your websiteIntegrations page: 19 integrations in six groups: Directory sync (Google Workspace, Microsoft Entra ID, Okta, OneLogin, JumpCloud, SCIM 2.0), Email simulations (Google and Microsoft DMI), Messaging (Slack, Microsoft Teams), Email gateways (Mimecast, Proofpoint, Defender for Office 365), Ticketing (Jira, Linear, ServiceNow) and Compliance (Vanta, Drata, Secureframe); no SIEM, EDR or phone group, although the homepage example shows Splunk, Microsoft Sentinel, CrowdStrike and SentinelOne.Source
  • 19

    Rivals sell on scale (KnowBe4 claims 70,000 customers, Adaptive Security over 2,000), and GhostEye's own homepage carries no statistics at all. GhostEye records something nobody else publishes: for each campaign, whether the help desk blocked the request, whether recovery succeeded without verification, and whether access followed.

    High impactHigh effort First result in 2-3 quarters Founding Head of Marketing

    First action

    Add a consent clause for anonymised, aggregated reporting to new customer agreements.

    How to measure it

    Bookings citing the report

    Now
    –
    Target
    30 in the first quarter after launch
    By
    3 quarters

    Steps

    1. 1

      Get consent

      Aggregated, anonymised reporting clause for new and existing customers.

      Founder & CEO 1 month

    2. 2

      Define measures

      Blocked, succeeded, access reached, fixed and retested.

      Founder & CEO 1 week

    3. 3

      Pull the data

      From campaign results, with minimum group sizes.

      Software Engineer, Backend / Platform 2 weeks

    4. 4

      Write the report

      Findings, method and recommended checks.

      Founding Head of Marketing 1 month

    5. 5

      Launch

      Press outreach and a talk at one major event.

      Founding Head of Marketing 1 month

    6. 6

      Reuse

      One post and one newsletter issue per finding.

      Founding Head of Marketing ongoing

    First result
    2-3 quarters
    Cost
    Staff time plus design
    Owner
    Founding Head of Marketing

    Smallest test

    Publish one finding from the last ten campaigns as a blog post.

    Why it works

    With customer consent and full anonymisation, publish "The Help-Desk Recovery Report": how often recovery requests were blocked, which verification steps failed most, how far a successful request reached, and how results changed after a fix and retest. Release the report ungated, with an optional email field for the data appendix, and present it at one major event.

    First-party numbers get quoted by press, analysts and answer engines, and they make GhostEye the reference for the scenario it owns. The report also feeds a year of posts, talks and sales conversations.

    Risks and how to handle them

    • Too few campaigns for a credible sample

      State the sample size openly, or publish a smaller "first findings" note first.

    • Customers identifiable from data

      Minimum group sizes and no industry splits below them.

    Evidence

    • Your websitePlatform page: hero "Find where impersonation could lead to access."; a campaign brief (objective, scope, team, before launch, stopping point); a four-step help-desk recovery workflow run by "a configured voice agent"; the platform automates "voice and message steps", recurring execution and campaign metrics, while GhostEye's team "defines the scenario, prepares campaigns and sign-in pages during onboarding"; outcome cards such as "The help desk blocks the request" and "Recovery succeeds without required verification"; reporting is a dashboard and an Excel export, and "A reporting API is not currently available."Source
    • Competitor researchRivals' own homepages: Adaptive Security, "Protect your workforce from AI threats", with email, voice and SMS simulations and "over 2,000 customers"; Hoxhunt, "Measurably reduce human cyber risk, at scale", with email, SMS, phone and Teams simulations and ROI and risk calculators; KnowBe4, "70,000 global customers"; Picus, an "Autonomous Exposure Validation Platform" that includes breach and attack simulation.Source
    • Your websiteHomepage (checked November 9, 2026): H1 "How far would an attacker go?"; GhostEye "pairs social engineering testing with breach and attack simulation" and traces an example SMS attack through account, API and directory access (Microsoft Graph, Entra ID) to reporting and detection (Splunk, Microsoft Sentinel, CrowdStrike, SentinelOne); logos of Eight Sleep, Everest Global Insurance, Day One Agency, Fella Health, Precision Medicine Group, Kontigo and Essential Personnel; quotes from Eight Sleep's Head of Information Security ("GhostEye showed us how real attackers would target our team, not just through email") and Fella Health's VP of Engineering ("move beyond checkbox security awareness with realistic, role-specific simulations"); one call to action, "Request Your Free Campaign" ("Your first campaign is on us."); no statistics.Source

Wildcards 2

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

  • 20

    GhostEye sponsors and exhibits at about a dozen security events a year, and its flagship product is a voice agent that calls a help desk with a convincing recovery request. Most booths show a dashboard. GhostEye can let a visitor feel the attack instead.

    Medium impactMedium effort First result in First event Founding Head of Marketing

    First action

    Script one fictional recovery scenario and a three-minute scorecard.

    How to measure it

    Scoping calls per event

    Now
    –
    Target
    15
    By
    first event

    Steps

    1. 1

      Script the scenario

      Fictional company, fictional caller, clear verification steps.

      Founder & CEO 1 week

    2. 2

      Set up the booth line

      Headset, call trigger and result screen.

      Software Engineer, Backend / Platform 1 week

    3. 3

      Make the scorecard

      Verified, escalated or reset, with the worksheet link.

      Founding Head of Marketing 3 days

    4. 4

      Run the leaderboard

      First names or handles only, with consent.

      Founding Head of Marketing per event

    5. 5

      Follow up

      Scorecard and free-campaign offer within 48 hours.

      Founder & CEO per event

    6. 6

      Compare

      Calls booked against previous events.

      Founding Head of Marketing after the event

    First result
    First event
    Cost
    Booth hardware and a week of engineering
    Owner
    Founding Head of Marketing

    Smallest test

    Run it in the office with ten event contacts on a video call.

    Why it works

    At the booth, a visitor puts on a headset and plays a help-desk agent. GhostEye's voice agent calls with a fictional recovery request against a fictional company. The visitor gets three minutes and a verification checklist; the screen shows whether they verified, escalated or reset. Post a daily leaderboard of the best verifiers, and give everyone a scorecard with the matching worksheet and a free-campaign link.

    A live, slightly uncomfortable experience is remembered and talked about, draws a queue, and shows the product's realism better than any slide. Every player is a qualified contact who has just seen why their own help desk needs testing.

    Risks and how to handle them

    • Players feel embarrassed

      Make it a game with a checklist, and praise good verification.

    Builds on

    Evidence

    • Your websiteEvents page: all 12 events (October 2025 to October 29, 2026, including RSAC, Black Hat USA, SecTor, GrrCON, BSides NYC and SecureWorld New York as a gold sponsor) sit under "Past Events", with nothing upcoming; event pages link to the free campaign but carry no recordings, slides or recaps.Source
    • Your websitePlatform page: hero "Find where impersonation could lead to access."; a campaign brief (objective, scope, team, before launch, stopping point); a four-step help-desk recovery workflow run by "a configured voice agent"; the platform automates "voice and message steps", recurring execution and campaign metrics, while GhostEye's team "defines the scenario, prepares campaigns and sign-in pages during onboarding"; outcome cards such as "The help desk blocks the request" and "Recovery succeeds without required verification"; reporting is a dashboard and an Excel export, and "A reporting API is not currently available."Source
    • HiringSoftware Engineer, Backend / Platform (New York, $150K-$225K, 0.50%-2.50% equity): GhostEye is "building an automated social engineer" with its own voice synthesis and self-hosted phone infrastructure; customers include government organizations and Fortune 100 companies; the role connects "campaign configuration, scheduling, execution, and results", phone and SMS delivery, and "scoped account, session, and downstream access checks".Source
  • 21

    GhostEye already publishes a help-desk verification guide (linked from the Why page and the tabletop post), worksheets such as an MFA recovery review card, and a whole glossary topic on help-desk recovery. Every free-campaign scoping call has to learn the customer's verification steps anyway. A tool that reviews those steps is a natural way in.

    Medium impactMedium effort First result in 1-2 months Software Engineer

    First action

    Turn the verification guide into ten yes/no questions.

    How to measure it

    Checker-to-booking rate

    Now
    –
    Target
    10%
    By
    1 quarter after launch

    Steps

    1. 1

      Write the questions

      Ten questions from the verification guide.

      Founder & CEO 2 days

    2. 2

      Write the results

      Gap explanations and the matching scenario.

      Founding Head of Marketing 1 week

    3. 3

      Build the page

      No login; answers stay in the browser unless shared.

      Software Engineer, Full Stack 2 weeks

    4. 4

      Connect to booking

      Pass the weakest gap to the scoping page.

      Software Engineer, Full Stack 1 day

    5. 5

      Promote

      Glossary help-desk topic, newsletter and LinkedIn.

      Founding Head of Marketing ongoing

    6. 6

      Measure

      Completions, shares and bookings.

      Founding Head of Marketing monthly

    First result
    1-2 months
    Cost
    About three weeks of engineering
    Owner
    Software Engineer, Full Stack

    Smallest test

    Put the ten questions in a simple form and score five responses by hand.

    Why it works

    A page where a help-desk or identity lead answers ten questions about their recovery process (how callers are identified, whether callbacks use a number from the directory, who can approve an MFA reset, what happens on escalation) and gets a one-page result: the steps that match GhostEye's verification guide, the gaps, and the scenario that would test the weakest gap. Offer to run that scenario as the free first campaign.

    It gives value before asking for anything, it is shareable inside the team, and the answers become the campaign scope, so the scoping call starts half done.

    Risks and how to handle them

    • Answers reveal a company's weak points

      Keep answers in the browser and never store them without consent.

    Evidence

    • Your websiteWhy GhostEye page: "Keep your awareness program and technical assessments."; impersonation tests across "voice, email, SMS, and chat"; a section "What a CISO should ask to see"; "A conversation alone cannot establish account compromise"; a "Read the verification guide" link; no vendor comparisons and no statistics.Source
    • Your websiteBlog post "Run an Account Recovery Tabletop: A Facilitator's Guide" (published August 21, 2026, by the CEO): a 90-minute agenda, four CSV facilitator files, links to the help-desk verification guide, and a closing section "Put a tabletop finding to the test." with the "Request Your Free Campaign" button; its structured data carries a dateModified of 2026-10-15 that readers do not see.Source
    • Your websiteGlossary (checked November 9, 2026: the index and the "Vishing", "Access token" and "Access review" pages): 400-500-word definitions with sources, related terms and "See it in practice" links to blog posts, filed under nine topics (Help-desk & recovery, Social engineering, Tokens & sessions, Identity controls, Security testing, Email & fraud, Devices & software, Applications & supply chain, Data & incident response); none of these pages links to the free campaign, the platform or the booking page, and none shows a date.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.

  • Keycard growth strategyRuntime authorization for AI agents: each agent gets its own identity, requests are evaluated against policy written as code, and…22 growth ideas
  • AutoDS growth strategyAn all-in-one dropshipping platform: product finding, ads spy tools, store building, importing, price and stock monitoring, automatic…20 growth ideas
  • Yepoda growth strategyA Berlin-based clean K-Beauty brand making vegan Korean skincare and tinted skincare, sold through its own sites in Europe, the UK and the…22 growth ideas
  • Veriff growth strategyIdentity verification and fraud prevention: document and biometric checks, liveness, biometric authentication, AML screening, proof of…21 growth ideas
  • Integral Molecular growth strategyA Philadelphia biotech, founded in 2001, that discovers and characterises antibodies against membrane proteins: the Membrane Proteome…21 growth ideas
  • Funding Circle growth strategyA UK small business finance platform: Term Loans, FlexiPay (pay suppliers and HMRC now, spread the cost), a Cashback business credit card…21 growth ideas
  • Tripledot Studios growth strategyA London-based mobile games group making and publishing casual and puzzle games (Woodoku, Solitaire, Triple Tile, Wordscapes), with…22 growth ideas
  • Serbyte Development growth strategyA Kirkland, Washington studio that designs and hand-builds custom Next.js websites, with SEO, free branding, management dashboards and AI…24 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. GhostEye did not commission, review or endorse it, and Programmable is not affiliated with GhostEye. 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 GhostEye runs its business.

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

30/60/90 roadmap

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

  1. Days 1 to 306 ideas

    Connect the library to the free campaign: glossary calls to action, scoping questions, clearer worksheet names, an integrations answer for SOC tools, visible dates and an upcoming-events list.

  2. Days 31 to 6011 ideas

    Proof and packaging: case studies, complement pages, named packages, the 30-day retest, compliance evidence, the public sector page, partners, the newsletter, the tabletop-to-test path, the LinkedIn series and executive-impersonation content.

  3. Days 61 to 905 ideas

    Commit to the big bets (self-serve scoped test, results API, annual report) and run the two wildcards.

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 seeing how real attackers would target the team, not just through email. The most cited problem: help-desk account recovery that can be talked around.

  • Realistic, role-specific simulations instead of checkbox awareness
  • Awareness programs that test email only
  • In their words: “how far would an attacker go”

Market

Competitive landscape

4 competitors compared: Adaptive Security, Hoxhunt, KnowBe4 and Picus Security.

  • Gap to exploit: One test that connects an impersonation attempt to the access and detection that follow
  • Adaptive Security: Centred on training rather than testing what access an attack reaches
  • Hoxhunt: Measures behaviour more than downstream access

Hiring signals

GhostEye (YC Summer 2025, a team of 6) is hiring two New York engineers, and both posts describe turning existing capabilities into complete customer workflows.

  • Software Engineer - Full Stack: Campaign setup, approval workflows and investigation screens. Ideas 1, 2, 17.
  • Software Engineer - Backend / Platform: Campaign execution and results, phone and SMS, access checks; government and Fortune 100 customers. Ideas…

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