Olive

What do they actually do

Olive lets teams create internal dashboards and admin tools by typing what they want in plain English. You connect a database or warehouse, describe the tool, and Olive generates and deploys an interactive UI that runs on your live data (fromolive.com).

Teams across the company use it: executives, analysts, customer success, and operations. A published case study shows users building and sharing dozens of dashboards for sales, pricing experiments, and operational metrics (RTK Tickets case study). The product includes role/access controls, auditable queries, “Ask mode” for non‑destructive questions, code editing and forking, API keys, and an AI query agent to improve accuracy (changelog).

Olive is live with paying customers and enterprise‑readiness features such as SOC 2, VPC/bastion and SSL connections, and fast human support via chat/Slack/email/phone (changelog, RTK Tickets case study). The company recently announced a $2.1M seed round to scale product and go‑to‑market (seed announcement).

Who are their target customer(s)

• Executives and managers making operational and strategic decisions: They need current metrics and drilldowns without waiting weeks for engineering or analyst bandwidth; reporting delays slow decision-making (RTK case study, seed announcement).
• Data analysts and analytics engineers: They are overloaded with ad‑hoc SQL and dashboard requests and spend time building UIs instead of analysis; they want accurate queries and less repetitive dashboard work without creating more maintenance burden (fromolive.com, RTK case study).
• Customer success and operations reps: They need to slice and act on live customer data but lack self‑serve admin tools and must rely on engineers for interfaces or queries (RTK case study, fromolive.com).
• Security, IT, and database administrators: They must prevent data leakage and enforce permissions; new tools often create unmanaged DB access, so they require VPC/bastion connectivity, auditable queries, and compliance before approving adoption (changelog).
• Product and growth teams running experiments: They need quick, repeatable dashboards with good drilldowns to monitor tests and KPIs; slow dashboard delivery makes iteration costly (RTK case study, fromolive.com).

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

• First 10: Hand‑pick pilots from YC/seed networks and early signups; run free, white‑glove implementations where the team connects the data and builds the first dashboards to prove value quickly (RTK case study, seed announcement).
• First 50: Convert pilots into referrals and publish a few case studies plus ready‑to‑use templates; run targeted outbound to heads of ops/product/CS with founder‑led demos and a low‑friction trial backed by fast in‑app support and Ask mode (RTK case study, changelog).
• First 100: Hire a small sales/CS team for account‑based motions and close security‑sensitive accounts by emphasizing SOC 2, VPC/bastion, and auditability; in parallel, grow product‑led inbound via API/embed examples, templates, marketplace listings, and consultancy partnerships (changelog, seed announcement).

What is the rough total addressable market

Top-down context:

The core target is BI/dashboard software: ~$36.6B in 2023, projected to ~$86.7B by 2030, where companies already budget for analytics and reporting tools (Grand View Research). Olive also overlaps with low‑code app platforms: ~$24.8B in 2023, projected to ~$101.7B by 2030 (Grand View Research).

Bottom-up calculation:

As a simple bottom‑up cut: if 25,000 mid‑market and enterprise companies adopt a prompt‑to‑dashboard tool at an average $15,000 annual contract, that implies a ~$375M TAM for Olive’s initial offering. Higher adoption or larger ACVs (e.g., multi‑team orgs) would increase this figure.

Assumptions:

• Targetable mid‑market/enterprise universe of ~25,000 companies with live databases/warehouses and BI spend.
• Average annual contract value of ~$15,000 for an organization‑level Olive deployment.
• Focus on the primary dashboarding/admin‑tool use case; excludes broader low‑code/AI assistant adjacencies.

Who are some of their notable competitors

• Retool: Low‑code internal‑app builder where teams assemble UIs with components, queries, and JavaScript. Powerful for developers and citizen‑devs; less of a prompt‑to‑deploy experience than Olive.
• Looker (Google): Enterprise BI with a governed modeling layer (LookML) and embedded analytics. Optimized for centralized data models and data teams rather than natural‑language generation of admin UIs.
• Metabase: Open‑source, user‑friendly dashboarding focused on creating and sharing charts. Requires manually building questions/dashboards instead of generating full tools from a prompt.
• Mode: Analyst‑first SQL + Python/R + visualization platform for deep analysis and reporting. Geared to analysts who write queries/notebooks, not to non‑technical users generating admin UIs from plain English.
• Appsmith: Open‑source platform for building internal tools by connecting data sources and composing widgets. Builder‑centric (drag/drop + code) rather than Olive’s prompt‑first generation.