Day.ai

What it is

Day.ai is an AI-native CRM that assembles the customer record instead of asking reps to type it in. It ingests Gmail, Google Calendar, Slack, and recorded meetings, then compiles them into what the company calls Customer Memory — an indexed context graph of customer interactions that carries its own sources and the reasoning chain behind each conclusion. Agents read that pre-processed memory rather than re-reading raw transcripts and inboxes on every request, which is the company’s stated reason its agents burn fewer tokens per task than a live-connector fan-out.

Day.ai was founded in spring 2023 by former HubSpot chief product officer Christopher O’Donnell and Michael Pici, another HubSpot product and sales veteran. It spent roughly 18 months in closed early access with about 120 customers, then went generally available on 2 February 2026 alongside a $20M Series A led by Sequoia — Pat Grady joined the board — with Greenoaks, Conviction, Sound Ventures, and Permanent Capital participating on top of an earlier $4M Sequoia seed. Headcount was 38 as of April 2026. The company sells the category as CRMx: context, not records, as the primary interface for both humans and agents.

Why it shows up in RevOps stacks

• You buy agents, not seats. Every paid tier prices one agent per month. A workspace with at least one Professional agent adds human colleagues at no charge, so the bill tracks how much autonomous work you run rather than how many people log in. That inverts the seat-count math every incumbent CRM runs on.
• It replaces the system of record rather than sitting on top of it. Rox, Agentforce, and Breeze all assume you keep paying for the CRM underneath. Day.ai is the pole that argues the record itself should be rebuilt around agents — one bill, one data model, no sync layer to maintain.
• The MCP server is a first-class surface, not a checkbox. Day.ai ships an OAuth-authenticated MCP server at https://day.ai/api/mcp with 20-plus tools covering object search, record creation, meeting transcripts, email drafts, and notifications. It is listed in the Claude directory and works from Claude Code and Cursor. The Operations Harness goes further: you administer the workspace from Claude Code instead of clicking through settings. A paid agent tier is required for MCP access.

Pricing reality

Published, per agent, per month, with no usage overages:

• Free — $0. Gmail and Calendar ingestion, meeting recording and context, search, share, contact creation.
• Turbo — $25. Adds task management, email drafts, web search, 2 automated skill slots.
• Professional — $60. Adds pipeline and opportunity management, custom properties and views, workspace creation, 5 automated skill slots.
• Executive — $200. Adds prospecting, workspace-wide custom instructions, administrative control, 10 automated skill slots.

Annual billing runs 20% off. A realistic five-person GTM team — one Executive agent, two Professional, two Turbo — lands at $370/month, about $4,440/year, or roughly $3,550/year annualized. The number that matters in the business case is agent count, not headcount: adding five non-agent users to that workspace costs nothing, while the same five people on a per-seat CRM are five more line items. Model your spend on how many scheduled skills you actually want running, because that is the variable the tiers meter.

Best for

RevOps leaders and founder-led GTM teams at seed-to-Series-B companies who are still early enough to move their system of record, and whose real bottleneck is that nobody logs anything — pipeline that lives in inboxes and call recordings rather than in the CRM. It is the right call specifically when you would rather pay for scheduled autonomous work (a morning pipeline brief, a nightly target list) than for more seats.

Skip it if your CRM is load-bearing for billing, support, or a warehouse contract; if you need certified partner-built apps and a deep integration catalog; or if procurement will not approve a 38-person vendor as the system of record.

Versus the alternatives

The incumbents are Salesforce with Agentforce and HubSpot with Breeze — pick either when consolidating agents inside a platform you already pay for beats a migration, or when you need the integration catalog and admin tooling a decade of ISVs produced. Rox is the layer-on-top pole: choose Rox when the CRM stays and you want agents working over it. Attio is the fastest-growing entrant in the AI-native CRM segment and the closer substitute — take Attio when you want a modern, data-model-flexible CRM your team drives, and Day.ai when you want the agents driving and the humans reviewing.

Watch-outs

• This is a system-of-record migration, not an add-on. Ripping out a CRM breaks reporting continuity, integrations, and any downstream contract that reads from it. Guard: run Day.ai in parallel on one segment or one rep pod for a full quarter, keep the incumbent as the reporting source until you have matched pipeline totals, and confirm an export path before you cut over.
• The vendor is young and small. 38 employees, about 120 customers, five months past general availability, and no published ARR. Guard: negotiate a data-export clause and a term shorter than a year, and keep meeting recordings and email in their source systems so your context graph is reconstructible from Google and Slack if the vendor status changes.
• Agent autonomy is a new failure surface on your customer record. Day.ai’s own reference agents are constrained to drafting and flagging — one “flags deals, never changes a stage or forecast on its own,” another “drafts only, never emails a prospect.” Guard: keep those constraints on your own agents for the first quarter, review agent-written fields weekly, and add write permissions one skill slot at a time rather than enabling all 10 on the Executive tier at once.
• The integration surface is narrow. Confirmed connectors are Google Workspace, Slack, Zoom, Gong, and Zapier, plus MCP clients. Guard: list every system that reads from your CRM today, and check each one against that list or against a Zapier path before signing — the gaps are where migration cost hides.