Monday

Overview

Workplace / work-management platform. Both saar-arbel and nizan-shifman work here. Described in 2026-05-06-brain-os-strategy-brainstorm as “one of the more AI-adopting companies” but still struggling to integrate AI tools cleanly internally — which is precisely the gap the Brain prototype is trying to close.

Relationships

• Hosts harmony internally (Nizan’s product).
• Internal users of cursor across many teams, including non-engineering (Enablement, growth).
• Direct/indirect competitive overlap with glean (context retrieval), sierra (enterprise agents), wonderful (adjacent space).

Notes

• Has structured OKRs, weekly syncs with the CEOs, and is described as more aligned than typical enterprise orgs.
• Internal AI tool referenced as “Cramer” — named after Monday’s Director of Analytics; an MCP-installed tool that aggregates all Monday data points into one queryable surface. Effectively “replaced the analysts” — anyone can now ask their Cursor any product/data question. (stub — could become its own page on second mention.)
• The “Solutions” group inside Monday (R&D + Product) holds a Thursday focus-list-board meeting where directors review every major project’s status and adjust priorities. Cited as one example of an org’s existing alignment ritual the Brain would interact with.
• Yoni and Tubel are the main internal stakeholders for any Brain pitch — see yoni and tubel.
• Ran monday-agents-month — a company-wide agent-building program that produced ~3,000+ submissions, treated as a use-case mining ground for the Brain.
• Notable Monday agent-builders surfaced in 2026-05-27: inbar-markovich (Engy — employee sentiment), yuval-ovadia (Simona — candidate matching), amit-frishberg (web→mobile feature port), shiran-navi (HR-team agent-week recap publisher).
• 2026-06-13: used as the strongest internal evidence for revenue-cycle-brain. Saar/Nizan described prior Harmony/Monday demos where acquisition, sales-call, product, and customer-lifecycle signals were connected to expose insights campaign owners could not see from local marketing metrics.
• 2026-06-14: used as both evidence and caution for account-management-vertical. Monday has substantial post-sale/fulfillment CRM usage and considered a “Monday Engage” positioning, but the team said Monday still lacks deep native AM features; sales CRM is Salesforce, marketing CRM is HubSpot, and post-sale work often lands in Monday.
• 2026-06-14: Nizan framed Monday’s global-maximum learning as optimizing toward 12-month ARR/retention rather than local team metrics. He also said Monday is addressing this internally through Sales Optimization and Marketing Optimization teams, but has not clearly chosen to sell that optimization as an external product.
• 2026-06-20: Saar reported consulting roughly 15 Monday people about Brain use cases. The pattern was useful but fragmented: each local workflow suggested a different Brain solution, reinforcing the need to find a specific pain before productizing.

Mentioned in

• 2026-05-06-brain-os-strategy-brainstorm — host org for the Brain prototype; reference architecture and pitch target.
• 2026-05-27-directions-vertical-pivot-and-prediction-markets — host of monday-agents-month; the catalog is the team’s near-term use-case mining ground.
• 2026-06-13-directions-revenue-cycle-and-construction-poc — internal reference case for revenue-cycle-brain and the AI-driven reorganization of GTM workflows.
• 2026-06-14-directions-from-home-strategy-brain-dogfooding — evidence for Monday post-sale/AM usage, the Monday Engage positioning idea, and the global-maximum / retention metric debate.
• 2026-06-20-directions-planning-the-week-18-30 — internal source of varied Brain-use-case feedback that pushed the team toward problem-first discovery.