From computer engineering to customer conversations Cornell · Leuven · cybersecurity · Blazeo A career spent closing the gap between theory and practice From computer engineering to customer conversations Cornell · Leuven · cybersecurity · Blazeo A career spent closing the gap between theory and practice

Profile · Product, systems & the human handoff

Aarij Khan Still Wants to Leave a Signature

Long before he joined product, engineering, and marketing under one title at Blazeo, Khan was an engineer impatient with theory that never met the real world. His career has been a decades-long attempt to close that gap.

Advertisement

In an old photograph, Aarij Khan stands between stone figures in Leuven, Belgium, wearing a dark suit and gripping both lapels as if preparing to make a case. It is 2003. He is an exchange student in applied economics, older than many classmates and already carrying the useful inconvenience of experience. He has trained as a computer engineer, worked in software, started a consulting firm, sold it, and returned to school. The campus magazine has come to ask why he has now started something else.

The new project was the Venture Capital and Asset Management Association, or VCAMA. Khan wanted economics students to meet professional investors, hear lectures from practitioners, and eventually manage a fund alongside working managers. He had spotted a gap between classroom knowledge and the world waiting outside. Rather than complain at length, he built an organization in the gap.

“When I go somewhere, I like to leave something lasting behind, a sort of signature.”Aarij Khan, KU Leuven campus interview, 2003

It is the kind of youthful declaration that can become embarrassing with age. Khan's has become explanatory. His later career would keep returning to the same territory: the awkward distance between an idea and its operation, between a technical system and the person expected to use it, between what an organization says matters and what its machinery actually does.

Aarij Khan standing among stone figures at KU Leuven in 2003
The original builder portraitKhan in Leuven in 2003, when a campus profile caught him turning an exchange year into an institution-building exercise. Photograph by Rob Stevens / KU Leuven.

01 · The useful frustrationHe wanted the formulas underneath

Khan arrived at Cornell after finishing secondary school in Pakistan and completed a bachelor's degree in computer engineering in 1995. He then worked at a software company before creating Callisto Systems, his own consultancy. By his account, the business put him on a plane every week. There were road trips too: San Francisco to Colorado and back, and New York to Florida. He liked new places and meeting different people. Movement came naturally.

In 2000, he sold Callisto and returned to Cornell for an MBA. During an exchange at KU Leuven, he added applied economics to the mix. What interested him about the Belgian program was not prestige collecting. It was depth. He found the case-heavy approach in American business education useful but incomplete. The engineer in him wanted the underlying theory, not only the worked example. Leuven, he said, supplied more of the fundamentals.

That tension - application on one side, first principles on the other - became productive. VCAMA was an answer in miniature. The students would not merely read about capital; they would get closer to people allocating it. Theory would have to survive a meeting with practice. Khan also joked about Belgium's greater reliance on a final exam. A semester could turn on one bad day. The remark was light, but the systems objection was serious: good outcomes should not depend on a single fragile moment.

02 · Translating invisible riskThe engineer migrates into marketing

After those early engineering years, Khan moved toward product management and go-to-market work. The industry he chose was cybersecurity, a business full of invisible problems and forbidding nouns. At ArcSight and HP, his work centered on security information and event management. At ThreatMetrix, Tenable, Imperva, and RiskIQ, the subject changed shape - fraud, vulnerabilities, external threats - but the translation problem remained. A product could be technically sound and commercially mute. Someone had to explain the danger, the mechanism, and the decision.

His 2014 articles for Tenable read like a product person determined to make the operational consequences visible. One introduced a redesigned interface and new ways for analysts to move between datasets without losing investigative context. Another explained how cloud services created blind spots inside companies. The prose is less concerned with performing cleverness than with the next action an analyst can take. Context should travel with the user. Information should lead somewhere.

In May 2017, Securonix hired Khan as vice president of marketing. The company put him to work on adoption of its security analytics and user-behavior products. A year later, he was named a silver winner for Cybersecurity Marketer of the Year in North America. His writing at the time pressed companies to examine the parts of their environments they could not see. One line from his work on underperforming security systems distilled the dilemma: you cannot protect an asset you do not know exists.

The deepest marketing problem in technical fields is often not persuasion. It is legibility. Buyers cannot value what they cannot picture, and operators cannot fix what they cannot locate. Khan's engineering training gave him a feel for the machine. His marketing work required him to redraw the machine as a choice.

03 · Building againTwo lines of code and a 2021 exit

Khan eventually returned to the founder's side of the table as a co-founder and chief marketing officer of sken.ai. The company attacked another stubborn handoff: application security tools often sat apart from the daily workflow of developers. Sken.ai's pitch was DevOps-first security testing. It orchestrated several kinds of scan, brought their results into one view, and aimed to integrate with continuous software delivery through a minimal code change.

Fortinet acquired sken.ai in July 2021. The buyer described a product that could cover static analysis, dynamic testing, dependency checks, and secrets while using machine learning to correlate findings and reduce noise. For Khan, the transaction joined a list of exits and growth chapters around enterprise security. More tellingly, it gave his old preoccupation a new object. Once again, the work was about getting a specialized discipline into the path of the people who needed it, without asking them to become specialists first.

20+years across product and marketing
4functions in his current Blazeo remit
2021year Fortinet acquired sken.ai

04 · The customer who vanishedFrom security events to unanswered leads

At Blazeo, Khan's title is Chief Product and Marketing Officer, but the company describes a wider remit: product management, engineering, UI design, and all marketing functions. It is less a departmental perch than a map of every place where a promise can break. A campaign attracts a visitor. An interface invites a question. A system routes it. A person or an automated agent responds. The experience is one chain, even when the organization chart is not.

Blazeo began as ApexChat, a live-chat business, then expanded into voice, text messaging, appointment scheduling, lead management, and automation. The company adopted its new name in 2024 because “chat” had become too small for the offering. Khan wrote about the transition and about the practical arithmetic of lead generation: cost per lead, conversion rates, response times, and the ordinary leaks that turn paid attention into nothing.

In 2025, Blazeo launched a voice product that handles routine calls with AI and passes conversations requiring judgment to live agents with the context intact. It later introduced SmartHub, a common timeline for calls, chats, texts, email, scheduling, and follow-up. The interesting product decision is not automation by itself. It is the handoff. Speed belongs to the machine; nuance sometimes belongs to a person. Context must survive the crossing.

What delay does to confidence

Fast
76.5%
Slow
36.2%
Share reporting high confidence in the sales process. Fast responders replied within 15 minutes; slow responders took more than an hour. Blazeo 2026 benchmark, 573 companies.

The company's 2026 benchmark makes the cost of a bad handoff unusually concrete. It studied 573 businesses across six service industries. Among companies that took more than an hour to respond, 81.2 percent reported losing leads. Among those answering within 15 minutes, the figure was 46.6 percent. More than 40 percent of high-intent inquiries arrived during evenings and weekends. The report even found the grotesque little monument to office hours: a lead submitted Friday night and answered 61 hours later.

“Belief alone doesn't translate into performance.”Aarij Khan on Blazeo's 2026 response-time research

Khan's argument is that response speed has become an infrastructure question. Telling a busy team to care more does not create coverage at midnight or keep five inboxes synchronized. A system can answer, record, schedule, route, and remind; a person can step in when the conversation earns human judgment. The point is not to turn every customer exchange into a machine event. It is to prevent human busyness from becoming organizational silence.

05 · The durable patternA signature made of connections

Seen from a distance, Khan's career can look eclectic: engineering, economics, product, security, marketing, consulting, and conversational AI. Seen from the seams, it is consistent. He works where one system must make itself intelligible to another. Code meets a developer. Security telemetry meets an analyst. A technical product meets a buyer. An interested stranger meets a business. Most failures happen between the boxes on the diagram.

There is also a quiet preference for institutions over moments. A student club outlasts an exchange term. A product workflow outlasts a launch. A unified customer record outlasts the first chat. Even his broad Blazeo remit makes sense in that light: if the experience crosses product, interface, engineering, and language, someone has to watch the crossings.

The young man in the Leuven photograph wanted to leave a signature. The mature version is less like a flourish at the bottom of a page and more like connective tissue - useful, mostly unseen, and tested by whether the next person can move through the system without losing the plot. It is not glamorous work. Good handoffs rarely are. You notice them mainly by the absence of delay, confusion, and repetition. Then the conversation simply continues.