AI Engineer World's Fair 2026
Hiring Employable Agents + Startup Battlefield Finals — Howie Liu, HyperAgent
Read the talk
Hiring Employable Agents + Startup Battlefield Finals
Howie Liu explains the product mechanics behind agents that keep working, hand off tasks and ask for approval. Three startup pitches then test where those capabilities create a business—and where domain knowledge, shared context and audience limits still matter.
From a talk by Howie Liu, Shawn "swyx" Wang and Joshua Xu
At a glance
Ideas worth remembering
Tool-result turns keep an agent working within a run; a heartbeat gives it another run after it stops. Neither mechanism alone ensures useful progress.
The landscaping example separates qualification, survey and proposal preparation from the owner's approval of a customer-facing quote.
Useful supervision requires remembered corrections and visibility into current work, blockers and handoffs.
The commodity pitch places specialized agents behind evidence gates and leaves money movement to the bank.
Comment.io targets the manual relay of ideas between separate agent conversations by putting people and agents in a shared document.
A creator's distribution can help launch a product, but sustained value depends on recurring audience needs and the limits of repeated promotion.
From completing text to choosing what happens next
Airtable began with an ambition investors considered implausibly broad: let people build many kinds of applications on one horizontal platform. Howie Liu, founder of Airtable and its HyperAgent product, brings that same ambition to agents. The product question is how to give many different businesses useful autonomous work without requiring each business to assemble all the underlying machinery.
His starting point is a progression in what the interface lets a user delegate. A completion model receives tokens and emits more tokens until it stops. Instruction tuning and conversational behavior make a different product possible: a chatbot that can respond to requests through a back-and-forth exchange. The underlying capability matters because it changes how people can express work, from supplying a pattern to having a conversation.
An agent adds a consequential choice: it can decide its next reasoning step or tool call as the task unfolds. Liu uses a definition aligned with Anthropic’s distinction between agents and workflows. A prescribed workflow determines the path in advance; an agent repeatedly uses the model to choose among possible actions. That freedom is what lets it handle an open-ended request, and what makes keeping it on task a product problem of its own.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
A heartbeat restarts work; orchestration divides it
A reactive agent can work for twenty minutes or an hour and still have the same basic lifecycle as a chat request: the user starts it, it does the task, and it finishes. Liu calls the next form factor a “claw,” borrowing from OpenClaw: an agent that can wake up again and continue pursuing a longer-running goal.
The always-on behavior comes from two mechanisms operating at different timescales:
- Within a wake-up: the model chooses actions, calls tools and receives their results. Each tool response invokes the model again, continuing the agent’s turns until it reaches a stopping point.
- Between wake-ups: a heartbeat invokes the agent again after that run has stopped. The agent gets another opportunity to pursue its goal or find a way around a blocker.
A heartbeat therefore supplies repeated opportunities to act; the model still has to choose useful actions. Liu recalls BabyAGI and AutoGPT as experiments that could run for hours while drifting into unproductive rabbit holes. His assessment is that stronger models now sustain enough coherence to make longer jobs more useful. This is a capability judgment, rather than a claim that restarting an agent guarantees progress.
Agent orchestration adds a separate capability. One agent can distribute work to other agents, including parallel work of the kind Liu describes using in Claude Code. Breaking a large problem into differently scoped tasks gives each agent a more manageable task and context window. The organizational work then includes handing off results and coordinating the pieces. Longer runtime and more workers solve different problems: one extends opportunities to act; the other divides what each worker must understand.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
A backyard inquiry becomes a survey and proposal
The concrete example is a landscaping business, presented as a realistic scenario based on HyperAgent customer usage. Its ambition extends across prospecting, quoting, pitching and managing the work. Agents coordinate the business processes surrounding a physical service; the example does not suggest that software performs the garden work itself. The surprising customer is a traditionally offline business applying a fleet of agents to its operating model.
The workflow starts with an inbound inquiry: a prospective customer supplies information about a messy backyard and asks for a quote and a proposal. A triage agent researches whether the person is legitimate, whether the lead is worthwhile and whether the project fits the business. It then hands the project to a surveyor agent, whose job is to inspect the landscape and develop a proposed redesign. The division separates a commercial qualification decision from the work of understanding and presenting the project.
What can the surveyor extract from the customer’s original images or video? Each HyperAgent thread has a sandbox virtual machine where it can write code and manipulate files. For video, the agent can use FFmpeg to extract individual frames and then analyze them. That gives the proposal process a way to inspect supplied material and assemble relevant information, rather than relying only on the customer’s written description. The resulting work includes proposed imagery and a client pitch deck.
The economic change is the amount of attention a small project can receive. Liu compares the bespoke presentation one might expect for a client spending more than $5 million with a small backyard job. Generating the survey, imagery and pitch makes that level of presentation more accessible to a small business. The example establishes the intended output and workflow, but supplies no measured proposal cost, survey accuracy or customer conversion rate.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Prepare the commitment, then ask the person who owns it
Producing a proposal does not give the agent permission to commit the business. A binding quote or agreement to perform work is a high-impact action, and the owner still controls the relevant policies and decisions. The useful intervention comes after the agent has prepared the work: the human receives something concrete to assess and can unblock the next action.
What does the owner review? The agent returns with a qualified lead, a surveyed project, a pitch deck, a proposal and a quote based on the project factors it considered. It asks for approval to send that package to the customer. Liu describes the proposal itself as an interactive webpage, including for a landscaping job around $10,000. The owner can review the prepared commercial offer before the business exposes it to the customer.
Where does information move, and where does permission enter? The handoff below separates the agents’ preparation from the owner’s authorization. The customer submission starts the work; the customer-facing offer remains behind a human decision.
Information prepares the offer; approval permits sending it
Read the diagram as text
- Customer inquiry. Preparation — Backyard information and supplied imagery or video.
- Triage agent. Preparation — Research legitimacy, lead quality and project fit.
- Surveyor agent. Preparation — Inspect supplied material and prepare the project proposal.
- Business owner. Authorization — Review the prepared proposal and quote; decide whether to approve sending.
- Send offer to customer. Authorization — A proposed next action requiring the owner's approval.
- Customer inquiry → Triage agent: Information: inbound submission.
- Triage agent → Surveyor agent: Work handoff: survey the project.
- Surveyor agent → Business owner: Information: prepared proposal and quote.
- Business owner → Send offer to customer: Control: only if approved.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Remember corrections and make blockers visible
Approval is also an opportunity to teach the agent something useful for its next job. Through Slack, email or another invocation method, the owner can correct the proposal’s format, ask for a different approach or point out a missed cost factor. A correction about an omitted cost matters beyond the current document: remembering it should change what the agent considers when preparing a later quote.
Liu’s proposed mechanism is accumulating memories and updating skills as interactions happen, without waiting for a subsequent model fine-tuning run. Here, “learning” includes changing the context and instructions available to the agent. The recording does not detail how those updates are stored, selected or checked, so it does not establish that every remembered correction reliably improves future work. The product requirement is clear: useful feedback should survive the conversation that produced it.
The interface for supervising this work must change too. Coding provides Liu’s comparison: manual editing gives way to Copilot-style completions, then conversational changes, then oversight of multiple agents working independently. Once several jobs can run at once—including overnight—the limiting human activity increasingly becomes resolving the decisions that stop those jobs.
An orchestration control plane should therefore show three kinds of information together: what agents are working on, what blocks them and where they are handing work to one another. Liu’s analogy is zooming out over SimCity. The operator needs enough of the whole landscape to intervene where it matters, without opening every task individually. That is the practical interface consequence of employing a fleet.
Liu closes by forecasting that this way of operating will become necessary across industries, and invites the audience to try HyperAgent. The offer announced at the event was $1,000 in inference credit. His larger claim remains a forecast: humans will increasingly orchestrate agents that can also orchestrate one another, and companies will compete on how effectively they put that capacity to work.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Three finalists put the agent business thesis on stage
The Startup Battlefield turns that product thesis into three business proposals. HyperAgent’s Founding Five Hundred program backs companies trying to operate with unusually high agent leverage. Twenty companies were preselected from the five hundred founders, and three reached this final. Howie, Theo and Joshua judge the pitches and questions.
The contest offers $100,000 in prizes: $50,000 for the winner, $30,000 for the runner-up and $20,000 for the second runner-up. Its stated emphasis is an impressive, meaningful use of the technology and a founder worth knowing. That framing leaves room for very different products: a specialized transaction system, a broad collaboration tool and an agent team that builds businesses for creators.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Commodity trades need evidence before they can advance
The commodity-trading finalist starts with a coordination problem: transactions cross countries, currencies, banking laws and commodity-specific procedures, while evidence travels through fragmented documents and communication channels. Its proposed agentic execution layer uses a proprietary CFC state machine to govern specialized agents. The founders identify fraud and verification as central obstacles, and describe a first customer operating a Dubai-based trading company.
The pitch describes several pieces of the transaction machinery:
- Counterparty and document checks: agents screen both sides for identity, know-your-customer requirements and sanctions, while document forensics looks for fraud.
- Deal coordination: a private deal room brings in shipping and logistics partners with live pricing.
- Parallel specialist work: agents structure compliance, legal, currency, banking, shipping and settlement aspects of the deal concurrently.
The CFC state machine constrains that parallel work. Agents may advance only after clearing every applicable deny condition; the pitch describes evidence as a prerequisite for progression. Settlement has a further separation of responsibility: the system emits a settlement-eligibility signal, and the bank moves the money. It does not itself hold or transfer the funds. The promotional claim that thirty days can close in minutes is not accompanied by a transaction trace or timing protocol, so it should not be read as an established result for arbitrary trades.
The live presentation has a complication of its own: the judges cannot see the video on their confidence monitor, and an initial question goes to the wrong project. Once the Q&A gets back to commodity trading, the useful challenge is whether a sufficiently capable general model could absorb the product. The founders’ answer rests on access and procedure: agents pull from real databases, operate behind explicit gates and use sensitive industry information that is not simply available on the open internet.
That depth creates an implementation burden: each customer may need specialized information and integration. The proposed economics rely on large deals and per-deal charges. The founders cite transactions of $200 million or more and refinery activity of $9–12 billion a month. Asked how many customers would support a very large business, they estimate about 100, although the question combines a billion-dollar valuation with $100 million ARR, so the answer is not a precise revenue model.
Traders and banks are the intended entry point. The founders argue that stronger audit trails and immutable trade records could help restore bank participation and liquidity in a fraud-prone market. The judges push beyond whether the business is attractive today: what must change as models and competitors improve? The response combines creativity, aggressive shipping, product quality and distribution. The final roadmap answer—“Becoming the bank”—is an ambition beyond the current design in which an external bank moves the money.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Comment.io removes the human context relay
The next team compensates for the same monitor problem by describing its product aloud. Liu jokes, “Pretend like we’re a non-multimodal model.” Comment.io is a multiplayer Markdown editor where people and agents join a familiar document interface, notify one another and call other participants into the work.
Its motivating example is a Friday-afternoon outage. One person asks Claude what is happening, waits for ideas and relays them to colleagues. Those colleagues paste the ideas into their own conversations, get other suggestions and send them back for someone else to paste again. The people who own the incident become the transport layer between separate agent contexts. Each useful idea requires another manual handoff before another agent can use it.
Comment’s proposed change is a shared document where people and agents work with context in real time. Openness and pluggability are explicit product requirements, alongside an interface familiar to people who already work in documents. The presenter’s experience spans collaboration features in Microsoft Word and enterprise AI writing deployments at Textio. The intended users extend beyond developers to teams whose daily work already lives in documents.
Liu identifies the commercial contrast with the previous finalist. Commodity trading goes deep into one domain and seeks substantial value per customer. Comment aims to be a cheap, fast, broadly useful place that many agents touch. His suggestion that a product touching even 1–2% of agent token activity could become valuable is a hypothetical scale argument, not a reported usage figure.
Why build a new editor instead of using Google Docs or a GitHub repository of Markdown files? The team distinguishes moving a document through an integration from collaborating inside it. In its account, sending or reading a Google Doc through MCP does not supply the real-time collaboration it wants. The recording does not explain synchronization, concurrent-edit handling or agent permissions; the supported distinction is the interaction requirement, rather than a demonstrated comparison of collaboration engines.
The closing observation is practical: conference attendees repeatedly described building their own visual Markdown editor, then giving up and sharing an HTML document instead. That is the product gap Comment wants to own. A shared artifact must remain usable by agents while giving people a comfortable place to inspect and contribute to the work.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Built by Foundry turns audience knowledge into a product
Built by Foundry proposes an agent team in place of an agency for content creators. Its input is a creator’s handle. Agents watch the creator’s videos and read comments to identify a problem the audience would pay to solve, then build the business around that opportunity. The creator launches it, and Foundry continues working on revenue growth. The pitch reports that more than half a million people use products its agents built.
Founder Weston Bell-Geddes frames the business around two assets creators already possess: expertise that can shape a product and distribution that can help solve its cold start. The target is a recurring problem behind the content, rather than simply putting the content behind a paywall. In his account, creators limited to brand deals, affiliate links or $20 PDFs can use an agent team to build a recurring-revenue product while they keep producing content.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Distribution has a saturation point
Theo challenges the assumption that an existing audience can keep driving a creator-owned product. His Vercel example separates the audience into people who already use it and people who will not. Repeating the same pitch becomes less useful to both groups. Distribution can help a product start, yet repeated exposure to one offer can exhaust what that audience will do.
His own response was to move from four sponsors to 80. The value came from variety: different products could reach different parts of the audience, even when most offers were irrelevant to any one person. He accepts Foundry’s premise that creators bring taste, distribution and audience knowledge. His objection is that owning a company can add work and audience fatigue without solving the need for a broader range of useful things to discuss.
That leads to a different customer for the same research machinery. Businesses could use it to find creators whose problems match their target customer, study those creators’ streams and videos, and show how an existing product solves an observed problem. The agent’s ability to understand a creator would then improve product development and partnerships, while the creator could work with multiple businesses.
Bell-Geddes answers with a narrower example: Brandon, a homesteading creator with two million followers, loses track of the best settings on his freeze dryer. Foundry treats that recurring operational problem as a subscription opportunity, and the founder says users now pay monthly or yearly to solve it. The example makes the proposed product concrete: preserve useful knowledge for an activity the audience repeatedly performs.
The disagreement turns on the niche and the persistence of the problem. Theo’s technology audience faces many competing products and benefits from variety; Foundry’s answer is a specific recurring need within a different audience. Bell-Geddes says technology and perhaps comedy are harder categories, and reports that no creator has left Foundry because its creators remain profitable. Without the cohort size or observation period, that retention claim cannot settle the broader debate. The freeze-dryer example does, however, explain why a creator product can have continuing utility beyond the next promotional post.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Comment.io wins the final
After a backstage deliberation and an event recap video, the judges return to announce the results:
- Grand prize — Comment.io: $50,000.
- Runner-up — Built by Foundry: $30,000.
- Second runner-up — the commodity-trading finalist: $20,000.
The winning team closes by thanking the audience for its feedback and inviting people to try Comment.io, described at the event as free. The final leaves three distinct product bets in view: evidence-gated execution for expensive transactions, shared context for people working with agents, and agent-built products shaped by an existing audience’s needs.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Resources
Related talks
- Beating RL With Reflection: GEPA and Optimize Anything
Develops a concrete mechanism for turning execution traces and feedback into improved prompts, agent programs and repository skills—the learning machinery left high-level in Liu's discussion.
Read the complete timestamped transcript
- 0:12
Please join me in welcoming the chief executive officer at HyperAgent, Howie Liu.
- 0:31
All right. Hello. Um, who's excited about the end of this event? This, this has been an amazing few days, amazing talks, amazing, uh, Gary talk right there. And, uh, by the way, I've never been introduced with so much bass. I am very, very pumped in this moment. Um, so I consider myself a product thinker at heart, meaning, you know, as much as I like to spend time on the technical side of building and, you know, I, I love to think about architecture and algorithms and so on, you know, really, I'm a product form factor thinker at heart.
- 1:02
And, you know, what I wanna end today off with is a brief and kind of high-level overview of how I see the world going with agents as it relates to product form factors. So I'm calling this hiring employable agents, and it's really a reflection on as these models have gotten better and better, and we've heard from some really, really great speakers about, you know, the latest, uh, frontier models, whether GLM 5.2, uh, or others, and how to coax the most, um, performance out of them. And really, this is not about the technical deep
- 1:31
dive, but how do we think about these from a product-building standpoint? So who am I? I'm the founder and CEO of Airtable, and also now HyperAgent, which is a product within Airtable. And as many of you already know, Airtable is basically a almost laughably horizontal platform. Uh, when we in-in fact set out to build the company almost twelve years ago, we got, you know, basically this negative feedback from virtually every investor we talked to early on, which was, you know, "You can't possibly go out with a horizontal platform approach and try to build something that is
- 2:01
everything for everyone, like any type of app that people wanna build. You know, you can't solve all of those use cases." And, you know, I think we ended up doing a pretty good job of solving for many of them at least and solving for a large builder community, and we're basically applying a very, very similar philosophy to agents now, and I'm gonna break down how we're doing it. So, um, when I zoom out and think about the progression of models and therefore the product form factors they enable, I really see it as this spectrum, right? So we
- 2:31
went from basically completions, which is, you know, you give a model, one of these LLMs, a, you know, string of tokens, and it just, you know, continues emitting more tokens until it gets to a stop token. And more or less, it would just kinda complete your thought, right? Or complete, um, the pattern. And, you know, un-until InstructGPT happened and enabled a chat form factor, it was, like, arguably powerful but more narrowly applicable. Once we got to a higher level of model intelligence and then also the kind of innovation of
- 3:00
InstructGPT and kind of tuning these models to actually have more of a conversational back-and-forth behavior with users, then we enabled the chatbot, right? And of course, we all know ChatGPT was an awesome breakout product. We're now all very, very intimately familiar with that form factor of AI. The next level I call an agent, right? And, you know, I think agent has been very overloaded. Um, we've probably talked about that a ton over the past few days. But my definition of agent really is the same as the Anthropic definition, which is distinct from workflows. And an agent
- 3:30
is really a model that recurses upon itself, right? And has, you know, the, the open-ended set of tools that it could call, of reasoning steps it can make, of decisions it can make. So it's not prescripted to a linear workflow, but it can kind of make an open-ended set of choices. Um, still, you know, I like to think of agents as being a little bit distinct from the next level of agents, which I'm using the term claw here because OpenClaw obviously has, has popularized, uh, this concept. But, you know, there's a market shift that I see from
- 4:01
agents that were still mostly reactive, um, you know, to user input. So you would have an agent go and perform a task. It might spend twenty minutes, maybe up to an hour to perform the task, and then it completes. Claws, um, as I call them, are really, you know, about agents that go and perform work for much longer, right? They can even have a mechanism like the heartbeat mechanism within OpenClaw, um, and now in other products like HyperAgent, that enable them to wake up on their own and almost like, um, exhibit this always-on behavior. I mean, underneath the hood,
- 4:31
what's happening is, you know, each wake-up basically results in many different turns, so the agent loops upon itself. It's performing tool calls. Each tool call response then invokes the, the LLM again until it reaches a stopping point. But then that stopping point gets reinvoked or, or kind of restarted with a heartbeat mechanism where you can wake up the agent again and again, right? And so this idea of this always-on agent that's actually constantly moving towards its goal and kinda figure out creatively how to unblock itself, where maybe prior agents would
- 5:00
get stuck, I think that's a really, really important kind of next form factor, uh, leap that we're seeing. And then finally, as you think about models that are now capable of, you know, really, really intelligent orchestration of complex tasks, right? Um, so I've personally been using the, uh, workflows capability in, uh, Claude Code quite a bit, uh, where it can fan out a lot of work to a massively parallel set of, uh, of agents. Um, but this concept of, you know, this agent that can go and orchestrate with other agents, right? An agent-to-agent interaction,
- 5:30
um, to perform even more advanced tasks, uh, right, longer running jobs, is, I think, the next leap yet. All of this is enabled because the models are getting smarter and smarter to the point where they can achieve coherence even on longer and more open-ended scoped problems, right? Um, if you recall back to the days of, um- Uh, BabyAGI and AutoGPT, those were really kind of fun, cool science experiments, but ultimately, you know, as much as they were really interesting to watch and, you know, see them work for hours and hours on a
- 6:00
problem, they would all inevitably, you know, kinda end up drifting off to something not super useful, right? It would go off into a rabbit hole and kinda get stuck. And I think now the models are actually smart enough to enable not only longer running jobs, but actually enable us to start applying these kind of organizational principles to break down problems into differently scoped tasks that different agents can hand off to each other, all of which is about managing each agent's task, uh, or context window and ability
- 6:30
to coordinate work with each other. So all this is kind of abstract. I wanna make it very, very tangible and show you how we've applied some of that design thinking of building a horizontal product and distilling a lot of the complexity of agents like we did for building a database or a database-powered app with Airtable for agents in HyperAgent. So this is a, um, a very realistic use case based on some of our actual customer usage. One of the interesting things we found from launching HyperAgent is, you know, the, the, uh,
- 7:01
prototypical users for HyperAgent are not who you would think they are, right? I mean, we definitely get our fair share of, like, the super AI forward, you know, kind of pure software companies, like AI companies themselves, but we also get really interesting other companies that are, you know, sometimes like traditionally offline businesses. And in this case, we're depicting a very realistic scenario, which is, um, a customer, uh, that is in a landscaping business and actually uses agents to run virtually end to end every part of their business, which is finding
- 7:30
clients to propose landscaping projects to, like physically going and, like redoing their garden or their backyard and end to end managing everything from the prospecting to building a quote and a pitch to managing the work itself. And I think this is a huge, huge, um, interesting, um, insight that, you know, I've just kind of stumbled on from working on HyperAgent, which is ingenuity of agent builders is not contained to just AI companies or software companies. Um, and I was really inspired by Gary's talk just a second ago. I think the, the, uh,
- 8:00
the motive behind that applies to every industry, every sector. And there are really, really creative people, many of whom are in this room, who can go out and disrupt your own industry, whatever it be. You know, it doesn't have to be a pure software business. Um, but I think all it takes is the ability to imagine what work could look like when you do go and become fully, not just an AI native company, but I like to use the term, you know, a fully fleet of agents native company, where you're actually going above and beyond and not just thinking about small kind of narrow steps to automate with
- 8:30
AI, but actually how to employ a whole fleet of agents that have governed behavior and have the right context and the right tools to be able to do really useful and very end-to-end autonomous work. So let's walk through what this looks like. Um, this is a realistic example of, you know, in this business, this, uh, this landscaper wants to go and pitch clients, right? So, you know, they get all these inbound, uh, submissions of clients who are interested. Somebody submits this inquiry saying, "Hey, here's my current backyard. You know, it's a little
- 9:00
messy. Here's my info. Like, can you give me a quote and show me a proposal of what you could do?" This basically gets routed into a, um, in, into one agent that is the triager agent, right? And so this agent is basically taking in this intake and saying, "Hey, like, what is the, um, the scope of the project? You know, like, is this something we wanna take on? And is this a quality lead? Is this a legit person?" And so it does some research, but ultimately it hands off then the work to another agent, a surveyor
- 9:30
agent, to actually go and then look at the, um, the physical landscape of this person's backyard and come up with a proposal of what a re-landscaped version of that could look like. So here, um, the surveyor agent is going and looking at the original imagery, uh, or even video that the, um, submitter gave them. Um, HyperAgent, uh, in our case, uh, works with a fully, um, capable sandbox VM. So every agent, in fact, every thread with an agent is able to fully write
- 10:00
code, it can manipulate files, it can actually use things like FFmpeg to like, you know, clip out individual screenshots from a video file and then analyze those, um, and actually go through and, like find all the relevant information to create a fairly high quality, um, and high touch, uh, proposal that would've been unfathomable for a small business like this before, right? If you think about like a really high-end interior designer or maybe like a very high-end landscaper, maybe they could do a very bespoke proposal like this for like a
- 10:30
five million dollar plus, uh, client, you know, if they're working for a big hotel or something. But it would've been unheard of to do something this high touch and actually mock up real imagery and a real client pitch deck for, you know, just a small backyard landscaping proposal. But this person has done it because they've, they've figured out how to use agents in an extremely capable and autonomous way to do the job that otherwise would've been undoable by humans. And so what happens next is, you know, the surveyor agent, it, it went and created this proposal and
- 10:59
pitch, and now the intervention has to go back to the human. Like, there is a step where humans still need to unblock the agents, right? Sarah Guo put out a great post, uh, a few weeks ago about, you know, just describing like where the value is going to accrue in this AI landscape as things evolve and models get smarter, and I firmly agree with her take, which was, you know, the ultimate blocker to still be able to deploy useful agents, there's still a human element to that. You know, as much as models are getting smarter, the ability for agents to get unblocked by humans that still
- 11:29
own policies and decisions and really importantly, just kind of gate, you know, really critical, um, high impact actions, like in this case, actually making a pitch to a customer that has a binding quote, um, or perhaps like agreeing to do the work, that becomes something that the human then intervenes at, just like a great manager who's getting upwards, uh, reports or, you know, upwards work updates from their team to then unblock. So here we have Sage who has come back to, uh, the real human, uh, owner of this business and
- 11:59
saying, "Hey, here's a lead. I already surveyed the, the project. Here's a beautiful pitch deck and a, um, proposal, and have come up with a realistic quote based on all the factors I've already surveyed in this, uh, particular project to give to, uh, to you to now approve sending to the client and see if they accept it," right? And you can see like even the, um, the proposal itself is this really beautiful kind of interactive, uh, webpage that again, would've been unfathomable for a business like this to be able to send to every single client, even for
- 12:29
small tasks, uh, or jobs like a ten thousand dollar landscaping proposal, right? Um- You know, better yet, as you interact with these agents, you know, as, as Gary talked about with gBrain and, and just kind of like creating this very, um, sticky context layer that learns with every interaction, I completely agree. I think that is a, you know, kind of a universal principle and kind of a form factor for useful agents going forward is agents should not be static. They should not just be, you know, either static LLM calls or static even agents that
- 12:59
just have a prompt and, you know, some static skills. They really need to learn with every interaction, right? And you can't wait for the next, you know, kind of fine-tuning run of your own models where you have, you know, a bunch of collected data or rubrics to, to retrain the model. It should learn in real time, right? It should accumulate the memories and skill updates and just take user feedback and actually learn from real-world performance to constantly adjust and get better just like humans do. And so in this case, you can see, you know, within Slack or, you know, in our case within, uh,
- 13:29
either Slack or email or other, um, invocation methods, you can basically go back and forth with the agent just like a real human and say, "Hey, like, you know, remember to take this into account next time." You kind of, you know, here's something differently, uh, formatted or a different way to think about the proposal, or you missed kind of, um, this additional cost lever in this particular project. So, you know, remember that for next time. And I think it's critical that in this next generation of agents, agents need to remember these things, right? Um, they should feel fluid and, and,
- 13:59
um, evolving just like humans are in order for them to fully realize the potential that the latest frontier model capabilities enable them to, to actually go and do in terms of autonomy.
- 14:13
Um, and then finally, I think what ends up happening at the end of all of this is with all of these agents that are each individually capable and even interacting with each other, I think the job of the human becomes increasingly about unblocking agents to be able to do work effectively. And so, you know, I, I compare this to the development workflows that, uh, have evolved from, you know, originally before any, um, you know, kind of AI en-enabled coding, obviously, we just sat in front of a computer. We as humans are pretty single-threaded, right? You'd stare at one code file, you think about a problem, you'd kind
- 14:43
of bang out some code, maybe take a break, come back to it. To then we had, um, augmented coding with the first generation of GitHub Copilot and similar tools where, I mean, I think of that as really just a completions form factor on coding. You type some code, it can auto-complete a few extra lines. To then we had things like Cursor Composer 1.0, like the original, uh, experience, not the, the composer model, um, but the chat experience where you could talk to this agent, it would do more complex changes, and that was even more leverage, right? But we're now moving to this point where, you know,
- 15:13
the best frontier agentic developers I know, and many of you are sitting in this room, are, are really just kind of overseeing a fleet of agents, right? Like, in fact, going to sleep without setting off your agents to perform useful work overnight feels like you're, you're taking this huge loss, like your, your team is not working because you're not unblocking them. And so the UX of how you oversee these agents, whether it's in development workflows or general purpose work, like this landscaping example, needs to shift as well. And so the way we've thought about that is you need to see
- 15:43
this kind of orchestration control plane where you can see at a glance what all of your agents are working on, what they're blocked on, who's handing off work to each other. And your job becomes almost like, you know, zooming out to see the entire Sim City landscape and orchestrating across everything going on at a macro level between your different agents rather than going and having to play micro and zoom into each individual project or each individual task. Um, and so I think this is a really, really exciting moment as we have shifted
- 16:13
from, you know, not just completions and kind of the slight augmentation of existing human, uh, work, but really a radical now leap into humans as orchestrators of agents that also can orchestrate themselves. And finding the right way for us to interact with those agents as they become more and more capable is gonna become not just the opportunity to boil the o-ocean, but in my opinion, table stakes for survival for every company in every industry. This is gonna be the way to get ahead and thrive in your
- 16:43
industry. And if you don't, you know, as Jensen put it, you know, it's not gonna be AI taking your job, it's gonna be, you know, somebody using AI who takes your job or takes your business. So really, really excited both for the opportunity and for everyone in this room to be part of this, um, transformation and this really kind of bold leap into the next form factor of AI. Um, all that being said, we'd love to see you try HyperAgent, so hyperagent.com/aie and you get $1,000 of inference credit, um, you know, that can be spent on all of our different model offerings, including, uh, you know, the
- 17:12
latest, uh, Opus 4.8, Fable 5. You can use it on GLM 5.2, uh, on GBD 5.5, et cetera. And we'd love to see what you do with, uh, with agents on HyperAgent or elsewhere. Thank you all for being here.
- 17:57
We love Howie in here.
- 17:58
Well.
- 18:00
Thank you for joining us.
- 18:01
Awesome. Thank you.
- 18:02
Um, so w- for the close of our events, uh, a few w- months ago, I saw that HyperAgent was launching this startup competition. And at AIE, we've always wanted to feature some kind of battlefield for like a com-competition and a contest for people. Uh, and we didn't really have any sort of mechanism by which to judge or to fund it or anything like that. And HyperAgent came along, and they had this, uh, 500 Founders thing.
- 18:28
Yep.
- 18:29
Right? W- what was the inspiration for that?
- 18:31
You know, I think, um- As I think about the multiple layers of disruption stacking, you know, there-- we, we're going, as I said, from, you know, just humans doing the same work they were augmented a little bit by AI to now humans overseeing fleets of agents doing work that wasn't before possible, like this landscaper running his business in a fundamentally different way, to now this entirely new economy of agent-native companies being built. And so, you know, really the Founding Five Hundred is about betting on the most frontier part of that economy as possible, right? It's the most agentically leveraged companies that are not only out disrupting their
- 19:01
space, but kind of defining an entirely new playbook for how companies in this new era will be run. And I think the leverage we're already seeing from some of these, uh, these companies that are running in this way, like Gary said, like, it's profound. I mean, it's far more than even being like an early software leveraged or internet leveraged company. So really, really, you know, kind of big believer that this subset of the economy is going to have explosive growth far higher than any other sector, and it's gonna cut across not just, you know, the tech industry, software industry, but every industry.
- 19:29
Yeah. Uh, in my London keynote, I always-- I often talk, talk about how, uh, work, uh, agents are eating the rest of work-
- 19:36
Yeah
- 19:36
... and being accessible to non-technical teams. In fact, my team is right there back now because AIE runs on Airtable, uh, and they're so excited to meet you and so excited to-
- 19:44
Oh
- 19:44
... to work with HyperAgents. Um, so from five hundred founders, we-- you guys preselected twenty. They competed today in the Startup Battlefields. Uh, three have emerged as finalists. Let's introduce them. Um, so I don't know if I'm supposed to, to click this. Uh, but, uh, first of all, I'm just gonna go to introduce, uh, our dear judges. I think, uh, we're gonna have, uh, Howie, Theo, and Joshua. Um, thank you from Agent. Um, and, uh, we'll-- I think we'll, we'll, we'll sort of,
- 20:14
uh, have them, uh, judging there. Uh, but also we're gonna, uh, go into the format and the background as well. Uh, so basically what we're gonna do, uh, it, we, um, the HyperAgent team has kindly put up a hundred thousand dollars in prizes and basically what this is, is a competition for whoever is gonna be the most impressive, uh, winner. So, uh, fifty K to the winners, um, thirty K to runner-up, twenty, twenty K to second runner-up. Uh, we're gonna have a hype video that is, uh, h-thankfully,
- 20:44
um, created by Hyperframes and Agent. Uh, we have founder pitches and Q&A with the judges, and then we'll also get to the next, uh, s-- uh, pitch as well. So just three quick pitches back to back. Um, and basically we decided that we really wanted some kind of judging in terms of like what is impressive and usage of this technology and like why it matters. Um, it's not an investment pitch so much as like, like, you know, it's not like a VC pitch so much as like, well, why should you
- 21:14
care? Why is this an interesting use of technology? And, and why, um, you know, why are you like an, uh, interesting founder that people should know? Um, and so I'm very excited to announce like the winning teams. Uh, so I think first of all, we're gonna introduce, um, Commod. Spiro, come on stage. All right. Thank you.
- 21:38
Um, I think you guys are gonna take over and present, yeah? Good to see you.
- 21:42
Good to see you.
- 21:43
Hey. All right. Do you have your clickers or y-you got, you got your...
- 21:47
I don't know.
- 21:48
You're gonna just kick it off? Okay. All right.
- 21:50
Hey, everyone. I'm Spiro Nanacos, one of the founders of Commod. This is Dom. And I'm Nick Nanacos. We are the founders of Commod. Commod has agentified physical commodity trade. From the rice you eat, to the gold chain you're wearing, to the chip in your smartphone, to the gas you're putting in your car, to every single copper pipe running through our data centers, physical commodities power the world. But the global trade system is broken.
- 22:20
Trillions move annually, yet hundreds of billions are lost annually due to fraud, fragmentation, and the sheer complexity of coordinating global trade. Commod has taken that complexity and transformed it into an agentic execution layer. Our proprietary CFC state machine governs specialized agents that verify, execute, and settle trades entirely. And then, you know, people ask, "Why is this so complicated?" And if you think
- 22:50
about it, it's like, well, it's every country in the world, every resource-
- 22:53
We should-
- 22:54
... all of their different currencies and all of their different banking laws.
- 22:56
We should end the video.
- 22:57
So of course, it's inevitably going to be a disaster, right? But with AI, it's finally solvable.
- 23:04
Okay.
- 23:05
So we're very excited to have you here. We also have our, our first customer in the crowd out of the UAE, um, trading company based in Dubai, and he moves several hundreds of millions of volume in, in trade every single year and, uh, he's proved the product. So we're excited to be here today, and thank you for the opportunity.
- 23:21
Talk to the judges.
- 23:25
Seventeen trillion dollars in physical commodities move every year. The world runs on them, yet it still moves on paper, email, and a handshake.
- 23:33
Okay, so we'll do the next one.
- 23:33
No one knows who is real or if the documents are.
- 23:35
Got this one.
- 23:35
The result, billions lost.
- 23:37
Which max? Okay, max.
- 23:38
Commod plugs into the stack you already run.
- 23:40
Interesting. Okay, yeah, yeah.
- 23:40
Gmail, Slack, Stripe-
- 23:42
It says founder one down there
- 23:42
... Salesforce, WhatsApp, and more. A deal begins. Agents screen both sides. KYC, identity-
- 23:48
Max
- 23:48
... sanctions in seconds.
- 23:49
Max. Okay.
- 23:50
Forensics catch document fraud instantly. A private deal room spins up. Shipping and logistics partners link in with live pricing. Then an agent swarm structures the deal in parallel. Compliance, legal, currency, banking, shipping, settlement.
- 24:03
I think max is next.
- 24:03
Weeks of work in minutes.
- 24:04
It's max.
- 24:05
The swarm obeys one protocol, the CFC, our patent-filed state machine. Agents advance only by clearing every deny condition. It cannot move until the evidence is real. Settlement eligible. It never touches the funds. It emits the signal. Your bank moves the money. Thirty days closed in minutes.
- 24:22
Guys-
- 24:22
Commod, where commodities meet trust
- 24:23
... the judges can't see the video on the confidence monitor.
- 24:36
What happens now?
- 24:37
I don't know. Is it on me?
- 24:40
Yes. Um, I, I, I realized that we didn't get you a mic, so, uh, are you... You're still mic'd up, but the other two-
- 24:45
Yeah, yeah, yeah.
- 24:46
We're all mic'd, yeah.
- 24:46
Oh, you're all mic'd up. Okay, great.
- 24:47
Yeah.
- 24:47
Um, so I think we have a little bit of a Q&A session.
- 24:50
Yeah.
- 24:53
So are we supposed to ask questions or what?
- 24:55
Exactly.
- 24:57
My team agreed to this, not me.
- 25:01
Wait, why are you guys playing this?
- 25:03
Joshua, you wanna go?
- 25:05
Uh, sure. I, I'm very interested in the, um, the second project, Comment.io. And, you know, certainly we need a shared space for agent to collaborate together. Just curious, have you thought about having that format to be HTML versus like Markdown file? How you been thinking about it?
- 25:22
What is this music?
- 25:24
Uh, sorry.
- 25:26
Yeah.
- 25:26
All right, sure.
- 25:28
Yeah, don't-
- 25:28
Yeah. I was just saying that, you know, um, um, the second project-
- 25:31
It's true
- 25:31
... Comment.io i- is about-
- 25:34
Yeah.
- 25:34
That's the next one, yeah.
- 25:35
Oh, the next one.
- 25:35
Yeah. We're asking them about the first one. Uh, so I'll ask a question. This is one of those types of products that's really hard to build, 'cause it requires so much domain-specific knowledge, as well as, like, the building out of all of these pieces to collect the information needed for the product. A lot of the concern I have with modern startups is the thing that they're building is eventually going to be a, a feature of a sufficiently intelligent model. Do you see a future where the models get capable enough and the tools they're given by Anthropic and OpenAI could compete with you guys if they were
- 26:05
to get smart enough and build in the right directions?
- 26:09
You want me to take it?
- 26:09
Yeah.
- 26:11
So in commodities trade, it's very specific as to what data's being pulled, and what we've done with our orchestration layer is set the gates for each agent. So they're pulling from real databases and have that context themselves. Whereas you're talking about gold, oil, grain, whatever it may be, there's certain procedures that only industry experts really know and have the documents and the information to pull that in, which is why we've partnered with Connor and a few other partners to bring in all that data, and I have domain experience as well, to know what's real, what's not, and to
- 26:41
train the agents based upon that. So to your question, could that happen? They could learn more for sure on the open internet, but this is a private industry with a lot of sensitive information, and they have to learn upon and train upon certain data in order to progress and become experts in that domain.
- 26:57
So it sounds, like, relatively bespoke in the sense that, like, every company's a bit different. You need to get everything for them. How many customers would it take for this to become a billion-dollar company or to hit, like, I don't know, 100 mil ARR? Like, how many customers do you think it would take to get there?
- 27:12
It's about 100 com- uh, 100 customers total.
- 27:15
Huge.
- 27:17
It's also important to mention as well, like the tickets in this industry are massive-
- 27:21
Mm-hmm
- 27:21
... on, on deal sizes. It's not like a Stripe, for example, processing micro transactions. One transaction might be, you know, $200 million or north of that.
- 27:31
And one partner such as a refinery, many of them transact $9 to $12 billion a month. So getting in at that level, charging per deal on that changes the whole landscape of what we're able to earn and what we're able to be valued at.
- 27:44
Yeah, just wanna add one more piece as well. Our solution is end to end, so you know, the solution serves the entire supply chain, but the wedge ultimately into the industry is the traders and the banks.
- 27:55
Hmm.
- 27:55
Banks pulled out of physical commodities trading years ago after the fraud became so rampant. So this unlocks a tremendous amount of liquidity as well by the audit trails and the immutability that we give, uh, into the commodity and the trade itself, so.
- 28:09
There's a lot to love about this business. I think, like, in many ways it's, like, check, checks all the boxes on, like, the classic, like, here is the ideal vertical agent business to build. Like, if you look at the w- the YC kinda, like, RFS for vertical agents, like, this is, like, the perfect application in the right, the right kinda sector. Like, there's lots of money up for grabs, and there's a lot of, like, domain-specific stuff that you have to do that creates, I think, a good defensible moat. Um, I think my perspective is more like, you know, what do you do to keep up with the changing competitive landscape and just, you know, as
- 28:39
models progress, how do you need to evolve your product to stay competitive, right? So it's less about is this a relevant and great business today, and more about what changes over the next two, three years or even, like, next year that impacts you in a way that... You know, it doesn't necessarily mean, like, Anthropic and OpenAI eats your lunch, but what do you need to do to stay, you know, kind of at the frontier and be a better product?
- 29:00
Yeah. I think, like, the only thing that's actually defensible is being the most creative in your category, regardless of which product you're creating, right? Like, truly nothing's defensible other than being the most creative, right?
- 29:09
Yeah.
- 29:09
Anybody these days has a product.
- 29:11
Yeah.
- 29:11
But we actually do like the Anthropic eat your lunch model. Like, we like the ship extinction model where we ship and then 10 companies go extinct the next day. So, um, yeah, it's aggressive shipping and product superiority, but then ultimately we're gonna win on distribution.
- 29:24
What are you most excited about on your, uh, upcoming roadmap, if you can share?
- 29:30
Becoming the bank.
- 29:32
Yeah. It's exciting.
- 29:36
Thank you so much.
- 29:37
Awesome. Thank you.
- 29:37
Awesome.
- 29:38
Give it up for Commod. Uh, we're gonna invite the next team on now, uh, if you wanna come back here.
- 29:43
No worries.
- 29:43
Thanks.
- 29:43
Thank you.
- 29:44
Yeah.
- 29:44
Appreciate it.
- 29:44
Great job.
- 29:45
Yeah. It's awesome.
- 29:46
Thanks.
- 29:46
Yeah.
- 29:47
Um, and up next we have Max Winderbaum and the team from Comment.io. Come on, Max. Woo. Oh, you're gonna play the video? All right. Come on in.
- 30:00
All right. We'll play the video.
- 30:04
That was- That's the music.
- 30:06
Oh. That's all right though.
- 31:03
All right, welcome in. Come on, guys. Oh, thank you.
- 31:09
Um, if you could, uh, so we have a little bit of a technical snafu where the judges couldn't see the video.
- 31:14
Okay.
- 31:15
Uh, we have to describe a little bit just to, just to prompt things off.
- 31:18
Before.
- 31:18
If you sort of, if you sort of re- before you get into the whole pitch, yeah.
- 31:21
Oh, okay. Um-
- 31:22
Pretend like we're a non-multimodal model, and we just, we, we only accept text.
- 31:25
Just giving you, giving you all the context here.
- 31:26
LM5 too.
- 31:26
Yeah, yeah.
- 31:27
So, uh, yeah, Textio, um, um, uh, Comment.io is a, uh, it's um, a multiplayer markdown editor. It's, uh, focused on making the best documents, um, for the modern work, which is, uh, people and agents. But what you would have seen on the video is a familiar document editor interface, but people and agents are popping in, they're notifying each other. Everyone can call anyone in, um, and that's, that's basically the gist.
- 31:54
Awesome.
- 31:55
All right. So, um,
- 31:58
it's Friday afternoon, ready to go home, packing up your laptop, and all of a sudden you're hearing dings around the office. Server's down, big outage. So you put down your bag, you head into the conference room, and you're pulling out your laptop. There's one question on your mind. What is going on, Claude? And you're entering that in, you're waiting a few minutes. Give me some ideas. It's culminating or whatever. And then it gives you some ideas, and the first thing you do is you tell everyone else in the room
- 32:28
the ideas, so they can put it into their Claudes. And then someone else has a different idea, and then they let you know, and then you put it into your Claude. And you real-- How did we get here? How is this the job? There has to be a better way, and there is. It's agents and the pe- who are doing the work, and people who own the problem sharing context in real time. But how? Think of the productivity software that you all use, the collaboration software. Can you just, like, drop your coding agents into them and have them working with each other?
- 32:58
No, you can't because they were built for people, not for agents, and that's why we're making Comment. It is the multiplayer markdown editor. It is-- we're laser-focused on making it the best document platform for modern work for people and for agents. It's open, it's pluggable. That's key for enterprises. It's key for y- it's key for developers, and it's wrapped in a user experience that is super familiar. I started my career in productivity, bringing collaboration features into
- 33:28
Microsoft Word. Max and I worked together, um, at Textio, the first AI-native writing software six years before ChatGPT. We were deploying company-wide rollouts of AI writing software to the Fortune 500. We've been doing this a long time. The market for Comment is expanding with agents. As more and more people use agents, more people are going to need the ability for agents to share context in a product that is built for agents, but designed for people
- 33:58
working together, even in the highest-stakes circumstances.
- 34:03
Awesome. I love the shape of this business because it's like the inverse of what we just heard from the, um, the Commod guys, right? Like, they went super vertically deep. They're trying to extract a lot of value out of a very deep, um, you know, domain. And you guys are going super broad and arguably maybe a little thinner, but by intention, right? And I don't say that as a, as a detriment at all. Like, I think, you know, one way to think about the landscape here is, like, the agent economy is gonna be so large. There's just so much money flowing through agents, like literally the token spend, right? And if you can be
- 34:33
a product that like even a one to, you know, two percent, uh, amount of those tokens touches-
- 34:38
Mm-hmm
- 34:38
... like you could be a very valuable-- even if like the per, uh, per call or per usage, um, you know, kind of, uh, metric, uh, you know, kind of margin extraction or revenue is, is relatively low, you can be a very cheap, very fast, very, um, broad product and still gain a lot of scale, right? So I think it's a really, really interesting shape of product. Um, what have you found is like the most surprising learnings from like a product design or product affordances standpoint to make this product better for agents than like the human-designed equivalents, right? Like, why not just have agents collaborate on a Google
- 35:08
Doc, right? Or even try to use like GitHub as the, uh, you know, kind of repo, not just for code, but for markdown.
- 35:14
All writing software today is horrible for agents to use. Software like Google Docs has a really terrible format. It has an MCP. You can send a document there. You can have your agent read a document from there, but you can't have them collaborate in real time, and that's critical for all kinds of real work that needs to happen. And as more agents join the wor-workforce, they need to be in there with your documents. And as we've talked to
- 35:44
our users, people who love working in documents, who rely on documents for their day-to-day, need to bring their agents because they're starting to use agents too.
- 35:55
Yeah.
- 35:55
It's not just developers anymore.
- 35:58
Okay. I think-
- 35:59
I'll mention it-
- 36:00
Oh, final closing words.
- 36:01
I was just gonna say, the other thing I'll mention is that I've been super surprised about, um, talking to people at this conference when we've talked to them, is how many people have said, "I've rolled my own like visual markdown editor that other people can look at," so people can look and then you're like, "Oh, but I gave up. I just ran an HTML document instead." Like, it's a hard problem, and you need dedicated, like, focus on making it great, and that's kind of what we're doing.
- 36:25
Awesome.
- 36:26
All right. Nice job, guys. Thank you so much.
- 36:31
Uh, next we're, and last team to compete, we're gonna play the video by Foundry.
- 36:52
Content creators don't have time to build a business, so they have to hire an agency. It's expensive, slow, and risky. Built By Foundry replaces the agency and lets creators launch their own products faster and cheaper. Our AI agents build the business end to end. The creator launches it. We keep growing the revenue. Type in any creator's handle, and our agents become their biggest fans, watching their videos, reading their comments, and
- 37:22
finding a painkiller their audience would actually pay for. We've done this for creators of every size, and over half a million people use products our agents built. The cost of building software is approaching zero. What's left is trust and taste, and no one has more of it than creators. We're building the agentic product team that is going to turn every creator into a founder.
- 37:45
Woo! Foundry team, come on up.
- 37:51
Thank you. Thanks, Max.
- 37:52
Hello, AIE. I am Weston Bell-Geddes. I'm the founder and CEO of Built By Foundry. We're gonna turn every content creator into a founder of their very own company. And I have great news today. I think we found the formula for a winning business. You take your unique expertise and turn it into a product, and you solve cold start with your built-in distribution. Theo, you, you did this with T3 Chat.
- 38:18
Yeah. It sucked. It doesn't work.
- 38:20
It works great for our, our, our, our, uh, users, but, uh, Gary did it with, with G s- uh, G Stack and G Brain. And, uh, what, what we, uh, find is that if we help, uh, creators to take a step back and solve a real pain point that their users have, so we're not just making another Patreon for that, paywalling this content. We're helping them solve a real pain point behind that, and that's what our agents are experts in, is finding the pain point within the user's problems.
- 38:50
And our companies have, uh, b- built over, uh, many different niches and, uh, different sizes of sha- and shapes of creators, and really what we're building is we want to give the power back to the content creator. They're stuck in these... I worked at TikTok for two years and, and I met with hundreds of creators who are stuck just doing brand deals or affiliate links or selling $20 PDFs in their link in bio, and they are one step away from building their own
- 39:20
business. They just need someone to help them, and that's what our agents do. At Built By Foundry, we deploy teams of agents to build recurring revenue businesses for content creators so that they can focus on posting and posting and posting, and we can keep growing their revenue.
- 39:36
I have a lot of thoughts on this one.
- 39:37
Okay.
- 39:37
So the problem I find as a creator, even with the brands I work with-
- 39:42
Mm-hmm
- 39:42
... is that there is a saturation point where it stops being useful to talk about a given product with my audience.
- 39:47
Mm-hmm.
- 39:48
Like with me for Vercel, for example, there was quickly a point where everybody in my audience either was a Vercel user and doesn't want me to shill it to them anymore, or they won't be a Vercel user and they don't want me to talk about it anymore.
- 39:58
Mm-hmm.
- 39:58
It is very easy to hit the saturation point, and the best solution is to have a much broader set of things to show your audience.
- 40:05
Mm-hmm.
- 40:05
One of the best things I ever did for myself, the single moment that has had the most positive impact on myself, my career, my businesses, and my income, has been going from having four sponsors to 80. Because now there's a wider variety of things to bring my audience, and even if 80% of them aren't relevant to them, the 20% that is is now conversion I'm getting that I wouldn't have otherwise. The variety of what I bring to my audience is where I find the most value by far, and every creator I've worked with ultimately has come to a similar conclusion. That said, you're touching on really important
- 40:35
pieces here. Creators do have more taste than most founders. Creators do have better distribution than most companies. Creators know their audience better than most businesses. And you've built a machine that identifies that, but it doesn't provide the solution to that other problem, which is you have to bring variety to your audience. Where I could see this working really well is as a tool that businesses use when they identify a creator as a- overlapping with the archetype of customer they're looking for to help that business build better things for Theo. And I've told
- 41:05
this to so many businesses that want to work with me, "Watch my streams, watch my videos, find the problems I have, and then show me how your product solves them." That's a way better pitch than going to try and start your own company as a YouTuber. As the YouTuber who has started the second most companies, as far as I'm aware, it doesn't work. It just burns you out, and it burns your audience out too. The best thing you can do is work with companies to teach them what your audience wants and for them to come to you with money to show it to those audience, or those audience members.
- 41:32
I understand. And I will say your niche as a tech creator is one that is very challenging because there's a lot of options. Um, and what we have found is that for all of our creators, I'll just f- a few examples. Um, one, one creator's name is Brandon, and he does homesteading content, and he always loses track of, uh, the best settings on his freeze dryer, which sounds ridiculous to us, but to his two million followers, that's a real pain point. And now they pay him a recurring revenue monthly, or monthly or yearly
- 42:01
subscription to solve that specific pain point. So I think unfortunately, Theo, you've picked a bad niche. I'm sorry. But, um, if you want to pivot to homesteading or gardening- ... may- maybe, uh, we could, we could work together. But I, I'd say primarily whatever the user's niche is, apart from tech and maybe com- comedians, we've been able to take a step back. Our agents find a pain point that s- they're willing to pay for, and zero creators across our entire company history have ever left our, our company because
- 42:31
they always are profitable.
- 42:34
You're very convincing.
- 42:36
Okay, excellent. Thank... Give it up for Foundry.
- 42:39
Thank you, man.
- 42:40
Yeah. Thank you. Um, so we're gonna have a little bit of a de- deliberation moment. Uh, the judges are gonna go backstage for a couple minutes. In the meantime- Sorry? Okay. In the meantime, we've, uh, prepared this little video recapping the World's Fair. So take your time, judges.
- 43:28
Now, this is our biggest AI engineers event ever.
- 43:40
There are constantly AI new techniques for you to
- 43:42
try.
- 45:08
Thank you so much. All right. Um, I think we're inviting everyone back on stage. Give it up for the Startup Battlefield.
- 45:20
Um, congrats, guys. Yes. Okay. So, uh, we have some prizes that we're gonna hand out. I think, um, the folks back there are doing some checks. Um, in second runner-up place we have Commod.
- 45:40
Uh, Theo, I think you're presenting. Uh, Theo, yes. We can, we can- Okay. We'll take some- Okay ... pictures as well for the team. Awesome.
- 45:53
All right. Spoilers. Uh, next- Oh, no ... and, uh, I guess this also reveals the order. Uh, we have Foundry as runner-ups. Great pitch. All right. Max, great pitch.
- 46:09
All right, congrats. Awesome. All right. No secrets now for the grand prize, Comment IO. Welcome. Great video as well.
- 46:17
Congratulations. Well deserved.
- 46:24
Do you wanna also do the group photo? I think we're doing-
- 46:27
With all of us?
- 46:28
Um,
- 46:31
yes. Okay.
- 46:32
All right.
- 46:33
Let it be just them. They're the founders.
- 46:35
Winners.
- 46:35
We're just here to comment.
- 46:36
Just the winners.
- 46:36
Thank you, everyone.
- 46:37
Oh, fine. We'll sneak in our faces in. Get them.
- 46:41
Joshua.
- 46:41
Come on in.
- 46:42
Yes.
- 46:42
All right.
- 46:46
Thank you so much, guys.
- 46:47
Awesome.
- 46:48
You're welcome.
- 46:48
You had some building with HyperAgent and-
- 46:50
Yeah, of course.
- 46:50
Yeah.
- 46:51
Yeah.
- 46:51
And patient. Um, any last words that you wanted to-
- 46:55
We should talk about it later
- 46:55
... comment on? I think you guys, uh-
- 46:57
Yeah
- 46:57
... briefed a little bit. Yeah.
- 46:58
Yeah. I just wanna thank, uh-
- 47:00
Sorry about the-
- 47:00
Thank everyone here at AIE. We got amazing feedback-
- 47:03
Yeah
- 47:03
... um, through the whole, um, time. And, uh, HyperAgent, um, for inviting us to this. And, uh, HyperFrance-
- 47:09
Of course
- 47:09
... for helping us with the video.
- 47:10
Um, great standing by you
- 47:11
And, uh, overall, like-
- 47:12
Okay. So if you want-
- 47:13
Thank you so much. Check us out. It's free. Comment.io.