Remember when the loudest thing at a Disrupt stage was a four-minute demo with a countdown clock? A founder would get on stage, show a slick prototype, land a laugh, and walk off with a leaderboard spot. The whole format rewarded the thing that looked most impressive in the shortest window. I loved it. I also watched a lot of those products quietly disappear within two years.
Which is why the lineup note for TechCrunch Disrupt 2026 caught my attention more than most conference announcements. Jas Khaira, global head of Blackstone N1, is taking the Builders Stage for a talk called “Building the Next Generation of AI Giants.” He’s set to cover what Blackstone looks for when it backs category-defining companies, how founders should think about capital as they scale, and what separates lasting businesses from early traction. The event runs October 13-15 at Moscone West in San Francisco, and this year’s theme is building enduring companies in the AI era.
That last phrase in his talk description — lasting businesses versus early traction — is the one I keep circling back to, because it’s the exact problem I deal with every week in this job.
Why a Private Capital Talk Matters to People Who Review Tools
I test AI tools for a living. Most of what crosses my desk has early traction. A waitlist. A viral launch thread. A clever wrapper around a model that genuinely does save you twenty minutes a day. Early traction is cheap to generate right now, and that’s not a dig at founders. The tooling to ship something demo-worthy has never been more accessible.
What’s gotten harder is telling which of those tools will still be maintained when you need it in eighteen months. And that question is not really a product question. It’s a capital question. A tool’s roadmap, pricing stability, support response time, and willingness to fix unglamorous bugs all trace back to how the company is funded and what its backers expect.
So when the global head of a Blackstone unit sits down to explain how he evaluates which AI companies become permanent fixtures, that’s a framework I want to steal. Not to invest. To review.
What I’m Listening For
Khaira’s three stated topics map almost directly onto the questions I wish I could answer before recommending a tool to readers:
- What gets backed. If large pools of capital are screening for specific traits in AI companies, those traits are probably the same ones that predict whether a product survives its first real pricing crisis.
- How founders should think about capital as they scale. Translated for buyers, this is the question of whether a $19/month tool is priced to be sustainable or priced to acquire users before a repricing event.
- Lasting businesses versus early traction. The single most useful filter in this entire category, and the one almost no review methodology — including mine — has fully solved.
I don’t expect him to hand out a checklist. People in his seat rarely do, and the honest answer to “how do you pick winners” usually involves judgment that doesn’t compress into bullet points. But even directional signal is useful. If the money looking at AI has moved from “how fast is your growth curve” to “what happens to your margins at scale,” that reframes how I should be weighing the tools I test.
Skepticism, Offered Freely
A fair pushback: private capital evaluating AI companies and an individual developer picking a note-taking agent are not the same exercise. Blackstone is looking at outcomes measured in years and billions. You’re looking at whether your workflow breaks next quarter. The frameworks don’t transfer cleanly.
There’s also the obvious thing about conference stages. They reward tidy narratives. The investor who explains their selection criteria on stage is describing a process that, in practice, involves a lot of pattern-matching and a fair amount of luck. I’ll take the talk as input, not gospel.
Still, the choice of speaker tells you something about where the conversation has landed. TechCrunch built this year’s theme around enduring companies and then put a large-scale capital allocator on the Builders Stage to talk about it. That’s a different signal than booking the founder with the best demo.
What This Means for Your Stack
Practical takeaway, since that’s what you come here for: start treating funding posture as a product spec. Before you commit a team workflow to an AI tool, ask who’s paying for it, what they expect back, and what happens to your pricing when that expectation arrives. Check whether the company ships boring maintenance releases or only feature announcements. Check whether support answers questions that don’t lead to upsells.
None of that shows up in a feature comparison table. It shows up when you need the tool to still work. If Khaira’s talk gives us better language for that distinction, it’ll be the most useful forty minutes of the week for anyone who buys software rather than builds it.
🕒 Published: