Nexus logo

Nexus

We help non-technical teams build AI agent no-code

Fall 2025active2021Website
Artificial IntelligenceNo-codeEnterprise Software
Sponsored
Documenso logo

Documenso

Open source e-signing

The open source DocuSign alternative. Beautiful, modern, and built for developers.

Learn more →
?

Your Company Here

Sponsor slot available

Want to be listed as a sponsor? Reach thousands of founders and developers.

Report from 27 days ago

What do they actually do

Nexus is a no‑code platform that lets non‑technical business teams build, test, and deploy task‑specific AI agents. Users design agents in a visual builder, connect company knowledge sources and integrations, test them in a built‑in chat view, and embed or integrate them into other applications (homepage, docs).

The product is live with documentation and published pricing, and it offers enterprise options like SSO/SAML, SLAs, and flexible hosting to meet security and compliance needs. The company is early and focused on enterprise use cases rather than being a mature, widely deployed platform yet (pricing, homepage, YC profile).

Who are their target customer(s)

  • Head of Customer Support at a large telco: Needs faster, consistent answers for front‑line agents and has scattered knowledge across tools, but can’t wait for engineering to build helpers (docs, LinkedIn).
  • Consulting team lead: Consultants waste time searching and reformatting firm knowledge per engagement and need repeatable workflows they can deploy without product/engineering support (homepage, YC profile).
  • Legal operations / paralegal manager: Must surface precise clauses and precedents quickly while meeting strict security/compliance requirements, but new tools typically require IT approvals and engineering work (pricing).
  • Private equity / deal‑team analyst: Spends too much time on manual review of deal documents and waiting on bespoke tools; needs reliable extraction and summarization tied to firm knowledge sources (LinkedIn, docs).
  • Marketing or operations owner at a mid‑sized company: Wants simple automations for routine workflows (lead routing, content Q&A, SOPs) but lacks developers to build and iterate assistant experiences (docs, homepage).

How would they acquire their first 10, 50, and 100 customers

  • First 10: Run hands‑on pilots in target verticals where the founders co‑build one production agent with the team and measure time saved and error reduction; use YC network and existing marketing claims to secure warm introductions (docs, YC profile, LinkedIn).
  • First 50: Convert pilot results into short vertical case studies and ship packaged templates/connectors (e.g., support KB assistant, deal‑doc summarizer, clause finder) to speed onboarding; pair targeted outbound with a small channel program (select SIs and Zendesk/Confluence‑type partners) (docs, pricing).
  • First 100: Open a self‑serve tier with templates, an integrations marketplace, and in‑app onboarding for mid‑market buyers while running an enterprise sales/CS motion to upsell SLAs, SSO, and hosting; use reference customers and measured ROI to shorten sales cycles (pricing, docs).

What is the rough total addressable market

Top-down context:

Nexus fits at the overlap of conversational AI, knowledge‑management, and no‑/low‑code AI. A conservative primary TAM framing is the no‑code AI platform segment, which is multi‑billion today with projections into the low‑tens of billions by 2030; broader conversational AI and knowledge‑management markets represent upside (Grand View, MarketsandMarkets, IDC, Mordor Intelligence).

Bottom-up calculation:

Estimate practical SAM by counting target mid‑market and enterprise accounts in support, consulting, legal, and PE; multiply by the number of teams likely to adopt agents per company and an assumed mid‑five‑figure annual contract per deployment. This yields a tractable SAM in the hundreds of millions to low single‑digit billions, depending on adoption per account and depth of enterprise features required.

Assumptions:

  • Focus on knowledge‑intensive teams within mid‑market and enterprise firms (not SMB long tail).
  • Average contract value in the mid‑five‑figures annually per deployed agent suite, increasing with SSO/SLA/hosting needs.
  • Multiple teams per enterprise (e.g., support, ops, legal) can adopt independently, but adoption ramps gradually.

Who are some of their notable competitors

  • Microsoft Power Virtual Agents (Copilot Studio): Microsoft’s no‑code chatbot/agent builder integrated with Azure and Microsoft 365, with enterprise SSO, Teams, and web embedding—strong when IT wants control inside an existing Microsoft stack (docs, SSO guide).
  • IBM watsonx Assistant: Enterprise conversational platform with a visual builder and options for managed cloud or self‑hosted deployments, emphasizing compliance and data isolation (overview, docs).
  • Cognigy (Cognigy.AI): Contact‑center automation platform with a low‑code studio, multi‑channel voice/chat, and deep CCaaS integrations—chosen for heavy telephony and large‑scale contact centers (platform, telco use cases).
  • Ada: Enterprise CX agent platform with no‑code playbooks, omnichannel deployment, and analytics/coaching—appeals to support teams wanting a packaged CX model over self‑service building (overview, platform pages).
  • Intercom: Customer‑messaging platform with KB integration and AI bots (Fin) that automate support inside broader messaging/CRM workflows, often preferred over a separate agent studio (overview).