Ready to build your own Founder-Led Growth engine? Book a Strategy Call
Frontlines.io | Where B2B Founders Talk GTM.
Strategic Communications Advisory For Visionary Founders
HUMAN had a defensible position in bot detection. When agentic AI arrived, the temptation is to pivot. John's framing: it's an expansion, not a revolution. Existing customers still need bot mitigation. New buyers need agentic trust. Running both in parallel lets you grow into new personas without abandoning the base. "It is the natural evolution. It is expected from our customers that we give them insights into that automation. And it's just a different type now."
HUMAN didn't go looking for new personas — customers sent them there. Security buyers started saying the CMO needed this data immediately. That inbound pull is the signal to expand GTM motion before you've built the full story. "We're finding ourselves much more in conversations with commerce teams, digital teams, marketing teams, saying, hey, you need to give me this visibility so I can better prepare for how I attain new customers, whether that's a human or an agent, on that human's behalf."
Most operators are talking about AEO/GEO at the content layer. HUMAN's product operates at the edge — meaning they can identify when an LLM crawler hits a customer's site, serve it optimized data, and then when an agent returns to transact, verify it, allow it, or gate it. That's a three-stage loop: crawl visibility, data presentation, transaction verification. "We deploy at the edge on everyone's site... if the crawler is coming here, maybe we present different data, maybe we present better data... if an agent comes back in and tries to buy in an automated fashion, can we verify it?"
Everyone is claiming AI capability. The credibility signal that cuts through is live customer data. HUMAN prioritized getting to nearly 200 deployed customers before leaning into broader category messaging. The sequence matters: build, deploy, collect real signal, then amplify. "Let's actually build it, right. Let's deploy it." And: "let's actually get real data so we can not just be talking about concepts and like let's really use this thing."
A standalone product requires behavior change. John's bet is inserting HUMAN's data as a trust layer into the tools customers already operate in — SIEMs for security buyers, web analytics for digital teams. The insight isn't just "meet buyers where they are" — it's that becoming embedded in existing workflows is what converts a point solution into infrastructure. "Not everyone's going to come to our product specifically. I need to meet them where they work."
The signal isn't headcount or revenue stage — it's when your product strategy, data strategy, GTM, partner ecosystem, and integration roadmap are being optimized in silos. The CSO role exists to hold that full picture simultaneously. "Who's able to look at it from our product strategy, our data strategy, how does that relate to our go to market and our partner ecosystems and our integration strategy? I think that's when you realize you need this sort of role."
Overnight, the thing HUMAN Security was built to stop became something their customers needed to welcome.
HUMAN had spent years becoming the most sophisticated bot detection company in the market — deployed at the edge across household-name platforms, processing 20 trillion interactions per week. Their core business was built on a simple premise: automation interacting with your digital assets is a threat. Identify it. Block it. Protect the consumer journey from login through transaction.
Then AI agents arrived in consumer hands. Suddenly the same autonomous, non-human traffic HUMAN was built to detect was legitimate — shopping, searching, comparing products, planning trips, and increasingly, transacting on behalf of real people. The thing they protected against and the thing their customers needed to enable were becoming indistinguishable.
Most companies in that position either ignore the shift until customers force the conversation, or they panic-pivot and abandon the positioning that made them credible. HUMAN did neither.
In a recent episode of BUILDERS, John Searby, Chief Strategy Officer at HUMAN Security, shared how they navigated the disruption — and the specific sequencing of decisions that turned a potential category crisis into an expansion.
The first and most consequential decision HUMAN made was about category architecture. Bot detection wasn’t going away. Bad actors haven’t stopped using automation to commit fraud — the financial incentives are unchanged. Security professionals still need that capability and still understand the language around it.
But a new conversation was emerging in parallel, one that had nothing to do with threat mitigation. Commerce teams, digital teams, and marketing leaders needed to understand how AI agents were interacting with their properties — not to block them, but to prepare for them as a legitimate and growing customer segment.
John’s framing was deliberate: “It is the natural evolution. It is expected from our customers that we give them insights into that automation. And it’s just a different type now.”
Running two category narratives simultaneously is operationally harder than collapsing into one. But collapsing into one meant either abandoning the security buyer they owned or failing to capture the commercial opportunity in front of them. The answer was expansion, not replacement. Bot detection and agentic trust as parallel tracks — same underlying capability, different buyers, different conversations.
HUMAN didn’t decide to go after CMOs and commerce teams. Their existing security buyers told them to.
The signal came directly from the customer base: “We’ve heard directly from them, hey, you need to get this data to my CMO, they need to use it today because we’re all having this conversation and we’re flying blind.”
This is a pattern worth extracting. When a market shift creates a new buyer persona, the fastest path to that persona often runs through the customers you already have. They feel the internal pressure before you do. They know which stakeholder in their organization is asking questions you could answer. And when they ask you to reach someone new in their company, that’s a warmer entry point than any outbound motion you could build.
HUMAN’s security buyers became the bridge to a completely different GTM conversation — not through a structured referral program or an account expansion playbook, but because the disruption created internal urgency that pointed directly back to HUMAN’s data.
In a market where every vendor is claiming an AI capability, the credibility problem is real. Category noise is high. Buyer skepticism is justified.
John’s sequencing was direct: “Let’s actually build it, right. Let’s deploy it.” Before HUMAN pushed the agentic trust narrative broadly, they got nearly 200 customers live on the solution. Real deployments. Real data. Live signal from agents in the wild.
The principle here isn’t humility — it’s strategy. In a noisy market, deployment is proof and proof is differentiation. Arriving at a customer conversation or an industry conference with live data from 200 deployed accounts is a different kind of credibility than arriving with a product roadmap and a category thesis.
Once HUMAN identified the new buyer personas — security, commerce, digital, marketing — they faced a practical problem. Each function lives in different tools, uses different language, and measures different outcomes. Building a parallel direct sales motion for each was not the answer.
Their bet instead: become embedded infrastructure inside the tools buyers already operate in. “Not everyone’s going to come to our product specifically. I need to meet them where they work. It might be in their web analytics platform or in this case, of security, in their SIEM.”
This reframes the product adoption question entirely. A standalone platform requires behavior change — new logins, new workflows, new budget justification. A trust layer embedded in the SIEM a security team already lives in requires none of that. The data appears where decisions are already being made.
The same logic applies to their go-to-market motion. Rather than building direct routes to each new persona, HUMAN activated the partner ecosystems already advising those functions — ad agencies advising CMOs on spend allocation, security partners already inside enterprise security stacks.
What makes HUMAN’s position defensible through this shift isn’t just their data volume — it’s where they sit. Edge deployment means they see the crawler before the customer does, optimize what that crawler sees, and verify the agent when it returns to transact. That three-stage loop — visibility, optimization, verification — is something you can only build from the edge. It’s not replicable without the deployment footprint HUMAN already has.
For founders watching a market shift hit their category, that’s the real question to ask: what does the disruption expose that you’re uniquely positioned to see? HUMAN’s answer was the autonomous agent layer of the consumer journey. Their data was already there. The problem just changed shape around it.
HUMAN’s position through this shift comes down to where they sit in the stack. Edge deployment isn’t a feature — it’s the reason they can see the crawler, shape what it ingests, and gate the agent when it returns to buy. That capability existed before agentic commerce was a conversation. The disruption didn’t create their advantage. It revealed it.