Vybe

Onboarding trackers, launch calendars, status bots, reconciliation queues, internal CRMs that diverged from Salesforce three quarters ago. The founders' own framing of the problem they lived inside Plato and Wealthfront: "each steals engineering time, rots when its owner leaves, and derails sprints."^[12]

Today's options all break in different ways. Rigid SaaS doesn't bend to the workflow. Spreadsheets break the second the row count goes past 10k. Engineering builds it — and then quietly stops maintaining it. Retool and Airtable demand a builder with technical chops; the function head still files a ticket and waits. And the new wave of vibe-coders — Lovable, v0, Bolt — were built for consumer and indie apps. They don't ship SSO, they don't speak to Salesforce, and you can't point them at production Postgres.

Airplane.dev — well-funded, internal-tools-first — was acquired and sunset by Airtable in January 2024.^[5] The cautionary tale is the same one Vybe is solving against: the category needed the AI authoring unlock to clear the value bar. That unlock arrived in 2025.

Code-gen became the killer LLM app. Cursor cleared $100M ARR in twelve months;^[4] Lovable shipped to $17M ARR in three;^[6] Bolt is at $40M ARR;^[7] Windsurf was acquired by OpenAI in a $3B deal.^[9] One-shot React from a prompt is now table stakes — the playbook works. The next move is choosing the surface where the AI authoring layer wins the next $100M.

Connector ecosystems matured. 3,000+ pre-built integrations are now a starting line, not a five-year roadmap. The connector matrix that took Zapier a decade to build is now an off-the-shelf platform primitive — which means Vybe's first day of development starts after the boring undifferentiated work that broke previous attempts.

Function heads control internal-tools budgets. Engineering's queue is full of revenue work. Ops, finance, and support buy directly when the AI authoring story is convincing enough — the same buyer pattern that took Notion, Linear, and Figma from individual seats to enterprise. Vybe is the first AI-native platform pointed at that exact buyer.

Model-agnostic and open-output. Vybe scaffolds standard NextJS — React on the front, NodeJS on the back. The generated app is real code, not a black-box template, which means engineering teams can read, fork, and audit what shipped. Deploy to Vercel, Cloudflare, your own infra, or BYO-VPC for the regulated cohort.

Schema-aware connectors. Vybe doesn't just pipe data — it tracks schema drift. When a Snowflake field renames or a Jira workflow changes, queries and UI regenerate automatically. The 80% of internal-tools maintenance cost ("the schema changed, the dashboard broke") becomes a background process, not a sprint.

Agents as a first-class citizen. Slack pings, reconciliations, status follow-ups, on-call escalations — the apps Vybe builds run autonomously between human reviews. The internal-app surface and the agent surface are the same product, not two separate purchases.^[12]

The dead-letter demand. Excel sheets and Notion docs are the body count of internal-tools projects that engineering couldn't get to. The function head's path of least resistance has been to roll their own and live with the rot. Vybe gives them a real app, with the data plugged in, that their team can use tomorrow.

The bottom-up enterprise motion. Same buyer pattern that took Notion, Linear, and Figma from individual seats to enterprise. The function head ships one tool; the team adopts it; the SSO/RBAC/audit conversation happens with IT after the value is in production. Engineering doesn't fight it because Vybe takes work off their plate, not off their roadmap.

The pricing landing zone. Vybe's beta plan is $49/builder/mo + $9/end-user/mo with usage-based agent actions — aligned with Retool's seat bands^[14] and well inside the function head's discretionary budget. The expansion path is the same one Retool walked: builder seats grow first; end-user seats follow; agents become the consumption SKU.

Low-code and no-code platforms are the closest TAM proxy: $37.4B in 2025 to $264.4B by 2032 at ~32% CAGR.^[1] Gartner has long forecast 70% of new apps will be low-code by 2025.^[2] Both numbers were calibrated before the AI authoring layer arrived and likely understate the pull-forward.

Vybe's near-term ICP is the 50-to-5,000-FTE band: tech-savvy enough to have mature data infra, large enough to feel the internal-tools backlog, small enough to have a function-head buyer with budget authority. Roughly 120k orgs × ~$20k ACV ≈ $2.4B addressable inside that band alone — and Retool's $1.4M average ACV^[3] hints at the upside as customers grow.