Loading video...

Video Failed to Load

Go Home

Today, we're officially introducing the new Vybe. We started as "Lovable for internal apps." We spent the last year building the infrastructure: permissions, integrations, databases, workflows. Everything companies need to actually trust software inside their business. Then, OpenClaw came out and started showing what was possible with agents for...

33,385 views • 27 days ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Here we go again 🚀! Excited to announce that we're building A1Zap (YC W25) with Pennie Li and that we're in the Y Combinator W25 batch in San Francisco! What is A1Base? A1Base gives AI Agents a real world identity for work. We do that by rebuilding Twilio and Okta from the ground up, putting AI Agents first. This means developers can make AI-first agentic applications 10x easier with our API's. ⁉️ Why are we doing this? Because there's a huge torrent of new valuable companies possible with AI agents, but to get their AI Agents to users, they have to chain custom apps, chat interfaces, awkward Slack integrations, browser bots, and wrestle with Twilio’s legacy API (which is built for marketing). We solve this by providing developers with an easy to use API to interface your AI agent with humans/coworkers/users where they are in this case in Whatsapp, Slack, Teams, SMS and more) - with AI Agent features built in. These digital workers are poised to transform how we work and we're the critical infrastructure to help them interact naturally in human workflows. We're not just building another AI tool. We're creating the infrastructure that will enable AI agents to become a natural part of the workforce - handling everything from customer support to sales development to creative work. We're backed by Y Combinator and working with founding teams who share our vision. We believe that in the near future, AI Agents with human coworkers will enable us to pursue more creative and impactful work. Our mission is to help developers build AI Agents that people can partner with and rely on as trusted allies—always with a human-first mindset. If you're thinking about the Agentic future of your company reach out! If you're looking to build your first AI Agentic company - reach out too - we have some amazing open source templates to get you started on the journey. Excited to share more of what we're up to soon 🔜.

Pasha Rayan

53,904 views • 1 year ago

We're only year 3 of a decade (if not multi-decades) long transformation of work. 3 years ago we bet on building an horizontal platform for work with agents, a chance to invent a new operating system for companies, from scratch, with AI as a fundamental premise. Many people considered us crazy for going after that, praising verticalized AI products as the winning strategy. But here's the thing: the time horizon of tasks successfully handled by agents has been predictively increasing form minutes to hours and will in all likelihood reach the equivalent of days and weeks of human work equivalent in the coming quarters. This is were verticalized and/or single-player AI falls short. Single-player tools, one person, one agent, confined to your machine is the wrong architecture for what's coming. We're shifting from using AI to produce things, to managing fleets of agents that do the producing. 3 years ago I wrote[1]: "ChatGPT is the Pong of LLMs. [...] Imagine, one day we'll get the DOOM, Civ, Red Alert, and Counter Strike of LLMs. Let alone multiplayer modes." Weeks long tasks in companies are inherently collaborative and mechanically spanning multiple teams. The new bottleneck in harnessing agents within organizations is coordination: multiple humans and multiple agents need to work together, with shared context, shared tools, shared goals. Agents that can hand work off to other agents or surface decisions to the right person at the right time. Humans who can review, steer, and step in without losing the thread. Teams that can run parallel workstreams and actually stay aligned. This is Multiplayer AI, and that's what we've been building at Dust. Across Datadog, Clay, Persona, 1Password, Doctolib and 3,000+ organizations globally, we've watched teams figure out what this looks like in practice. 300,000+ agents deployed. 70% weekly active. 240%+ NRR. Today we're announcing a $40M Series B with Abstract, Sequoia, Snowflake, and Datadog to accelerate our vision. Designing the right interfaces for multiplayer AI is the next frontier. Join us to redefine work by defining multiplayer AI.

Stanislas Polu

801,584 views • 1 month ago

What does it actually mean to be AI native? There was no clear guide on the internet for how to become AI native so we built the definitive one (60 min masterclass): 1. An AI native org has 3 layers: people for strategy and taste, agents for execution, and a shared context layer that makes the entire company readable to agents. 2. AI eats the middle of your work. You used to spend 80% of your day on execution. Now agents do that. Your job is the bookends: deciding what to do and judging whether it's good enough. 3. Everyone is a manager now. Your output is the output of your agents. If your agents produce garbage, that's on you. You set them up wrong. 4. Using ChatGPT doesn't make you AI native. That's like having a website and calling yourself a tech company lol. 5. No AI native org without AI native people. Most companies skip straight to the tools. That's why it fails. If your people don't understand how to manage agents, the tech doesn't matter. 6. Making your company "readable" to agents is the real work. Every process, every decision, every piece of knowledge needs to exist in a format an agent can consume. Most companies are nowhere close. 7. Speed without signal is just expensive chaos. You need the system to move fast AND know if you're moving in the right direction. 8. The skill chain is how agents get good at your specific workflows. Skills build on skills. The more you invest in them, the more your company compounds. 9. The moat is the system. People managing agents, agents reading from rich context, the whole thing getting smarter every week. That compounds. Your competitor can copy your tools. They can't copy your system. Full episode with Theo Tabah from LCA on The Startup Ideas Podcast (SIP) 🧃. This is the stuff we normally keep internal but all the sauce is yours. Theo Tabah is the brains behind advising the world's biggest companies on AI and building AI products. Your fav CEO's first call for figuring out AI. You are in for a treat Become AI native in under 60 minutes Watch

GREG ISENBERG

82,822 views • 21 days ago

Today we’re launching Vybe to the world and announcing our $10M Seed round to make vibe-coding actually work inside companies. This is why, how and our vision: Over the last few decades, every fast-growing company has quietly built the same mess behind the scenes: internal ops glued together with rigid SaaS, fragile spreadsheets or custom-coded tools nobody wants to maintain. Meanwhile, eng teams are stretched thin. Internal tools never make it to the top of the backlog. Vibe-coding is changing the game but it’s mostly been good for prototypes, landing pages, and side projects disconnected to production data. Our belief is simple: in the next few years, most internal software will be vibe-coded by teams working with AI, engineers and business teams together. Vybe is built for that collaboration: 1/ Business teams own the surface area: Business teams (Ops, CX, PMs etc.) can build and iterate on apps themselves: flows, UI, fields, and logic; without waiting weeks for eng to pick up another “internal tools” ticket. 2/ Engineers own the foundation: Integrate production data (Postgres, Salesforce, Jira, and 3,000 integrations), define SQL definitions once, set up SSO auth, access control, and keep everything in Git to help when needed (from their favorite IDE!) 3/ Secure by design: Our security and permissioning layer is not vibe-coded and can’t be modified by AI. Everyone can sleep at night. 4/ Team-ready out of the box: SSO, Auth, environments, deployments, and review flows are built in. Over the last few months, we’ve been in closed waitlist mode and have hand-onboarded teams to pressure-test Vybe on real production workflows: - A YC Founder runs his entire CS operation on Vybe and saves ~2 days per week. - Another company ingested millions of rows from their warehouse to build BI-like internal views that would break typical AI builders. - One team fully replaced Metabase/Looker by plugging Redshift into Vybe and just… prompting their way to MAU, DAU, funnels… Remix apps from world-class operators To make it even easier to get started, we’re launching templates co-created with operators who’ve already solved these problems at scale: - Mathilde Collin (CEO @ Front) – how she runs 1:1s - Lenny Rachitsky (yeah, that Lenny!) - how to manage up, do perf reviews and write PRDs - Sushma Nallapeta (CTO @ 23andMe) - her 7Cs Framework for Build vs. Buy Decisions - and many more from the best Tech leaders Backed by people who’ve lived this pain We’ve raised $10M in Seed funding, led by First Round with participation from Y Combinator and an incredible group of operators and founders, including: The CEO Datadog, CEO Grammarly, CEO Reforge, CTO Intercom, Head of Product at OpenAI, Head of Product Anthropic, and 50 more incredible operators who believed in our vision! Huge thank you to our early customers, team, and investors for believing in us this early. 🙏 We’re now in GA: no more waitlist!

Quang HOANG

108,346 views • 6 months ago

We've built 40+ AI agents and internal tools. The hardest part is Context Creation. AI runs playbooks and makes judgment calls for you. But without your company's context, you get slop. Context Creation means extracting the subject matter expertise and playbooks that live in people's heads, not in LLM training data, or even your tools. As forward deployed engineers (FDEs), we create context and turn it into code. We evaluate the business impact, how it aligns with the dev roadmap, and come up with creative solutions. We built The FDE Factory to replace ourselves. It drives AI adoption inside our clients' companies by running discovery sessions using prototypes to create context. Here's how it works: We put a prototype in front of a stakeholder. The stakeholder gives feedback via voice while they're using or reviewing it. Then our FDE Factory Agents builds in their expertise in minutes: > Context Agent reviews the codebase and feedback, extracts the requirements, and creates a spec > Scope Agent checks the spec against the development roadmap, validates it, and hands it off > Engineering Agent builds a new feature and wires the integration > QA Agent runs tests to prove to itself it works > PR merges, feature goes live, product updates itself in real time It's like the nontechnical stakeholder wrote the code without even knowing it. Coding agents are great at turning good development plans into code, and they're getting better at turning context into good development plans in collaboration with professional engineers. But nontechnical people are capped on what they can build without product people and engineers. The bridge that takes nontechnical people from vibe coding basic apps to building production AI tools that run on first party context is FDEs. Our new FDE Factory gives you the system to go from idea to production. Context Creation is the first and most important step in our FDE lifecycle, and we just automated it. Now clients get the right agents and tools built for them, customized to their unique business and encoded with their expertise. PS: If you're building AI agents within your company, reply "Playbook" and I'll DM you the entire FDE playbook we've run with 30+ companies. It covers finding high-impact AI use cases, building them, and deploying them across the org.

Mike Fishbein

10,054 views • 25 days ago