Executive brief

A scheduling agent
that sits above every
calendar tool.

The thesis

Scheduling is becoming an agent-to-agent protocol. The winner is the layer that negotiates meetings on users’ behalf — regardless of which calendar or booking tool either party uses. The long-term asset is the availability graph: a proprietary dataset of when people actually meet, and what works.

The wedge

Gmail + Outlook add-ins plus a universal agent that handles the multi-turn email negotiation that Calendly, MS Bookings, and Cal.com all fall back to. The user keeps their existing tool. Meridian adds the intelligence.

Why now

Frontier LLMs are capable of real agent behavior; their prices are deflating ~40–60% per year. Our marginal cost structure is shifting faster than the incumbents’. The window for establishing the protocol is roughly 18 months after public launch.

Universal

Works with Google, Microsoft 365, Calendly, Cal.com, MS Bookings, and the long tail.

Agentic

Negotiates over email, Slack, Teams, or directly agent-to-agent over the open ASP.

Defensible

Protocol lock-in + preference-learning moat + availability graph that compounds.

$550–650M
SMB TAM, 2026
>$3B
Adjacent TAM w/ agent layer
~20M
Calendly paid users
-25%
Tiers vs. Calendly
-40-60%/yr
Inference cost trend
5+
Target protocol adopters by Y2

What we sell

Starter $1/mo · Pro $9/mo · Team $15/mo · Enterprise custom · Platform $0.05/negotiation. No free tier — the $1 entry filters freeloaders and preserves viral mechanics. All paid tiers sit 25% below Calendly's equivalents, a gap we can sustain because our main variable cost (LLM inference) deflates while theirs doesn't.

The moat

Four interlocking layers:
  1. Data: every meeting we touch — even ones we don’t host — feeds the availability graph + relationship graph. Better predictions → faster time-to-confirmed → more volume.
  2. Network: the Agent Scheduling Protocol (ASP). Once it's the default, switching off is like switching off MX records.
  3. Switching: agent memory, preference learning, deep CRM/ATS sync. User-level stickiness that follows a person across jobs.
  4. Counter-positioning: Calendly can’t ship an open protocol without commoditizing itself. We can — we monetize the agent + graph, not the protocol.

What's built today

Monorepo with 12 packages + 5 apps. Google + Microsoft OAuth live; Calendly, Cal.com, MS Bookings importers written; HubSpot, Attio, Salesforce connectors written; ASP protocol v1.0 implemented (Zod schemas + Ed25519 tokens + HTTP endpoints); meeting intelligence + routing + billing + preferences engines running; Gmail add-in ships. 175+ tests pass. Observability (request-id, rate limit, OpenAPI, readyz). Editorial UI with command palette.

Want the full story?

The investor brief has unit economics, funnel maths, and the 18-month plan.

Open investor brief →