Nizan Shifman

Role

Building harmony inside monday — a self-improving voice agent for call centers. Heavy daily user of saar-arbel’s Brain prototype; runs a growth team within Harmony.

Affiliations

• monday → harmony — leading the product; team is ~16 people as of 2026-05-06.

Notes

• Operates almost entirely through cursor + Brain + a NoteTaker MCP. Quote: “you can’t go back” once you live this way.
• Pitched the two-pillar architecture during the meeting: Operating System (Brain itself, including authorization/personal/team/org spaces) plus “Skins” (NoteTaker, integrations, etc). See context-os-brain.
• Strong proponent that the Brain is already painkiller-grade (rates it 9/10) based on Harmony’s daily use — see vitamin-vs-painkiller-framing. By 2026-05-27 conceded the GTM is stronger if value is led by use case rather than personal-productivity speed-up — supporting the vertical-use-case-led-brain direction without abandoning the personal-productivity claim.
• Concrete daily-Brain example (2026-05-27): produced a heatmap mapping channel × language × inbound/outbound opportunity for harmony’s next growth bet — claimed it would have been infeasible to load that context into a one-shot ChatGPT task.
• Has a younger sister at Monday on the Enablement team who also uses Cursor + NoteTaker daily as evidence the pattern generalizes beyond engineers.
• His growth team (working with someone named “Tom”) all operate via Brain + per-team GitHub auto-commits with each member’s context.
• Owns the team’s relationship with the monday-agents-month catalog; action: send the full ~3,000-entry list to the team for use-case mining.
• Pipeline owner for the construction-domain contact (returned from Lebanon); intro coming this week.
• 2026-06-20: argued that the team should study recent VC/YC investments and trends as an ideation source rather than inventing only from first principles.
• 2026-06-20: recommended user-interviews based on recent positive experience and favored pay-as-you-go recruiting before committing to a larger package.
• 2026-06-21: sharpened the AM/revenue-team opportunity away from generic account prep and toward relationship acts, unusual customer gestures, and AI transformation gaps that salesforce / Slack Bot do not naturally solve.

Mentioned in

• 2026-05-06-brain-os-strategy-brainstorm — pitched two-pillar architecture and pressed for first-to-market positioning while guy-barkat challenged on differentiation.
• 2026-05-27-directions-vertical-pivot-and-prediction-markets — defended personal-productivity Brain value and conceded the use-case-led GTM frame; flagged Brain-shaped agents from monday-agents-month.
• 2026-05-31-directions-connect-businesses-and-brain-scaling — held the Holy-Grail framing for the Brain (alignment + transparency + speed + source-of-truth); reported he has “cracked AI” via the Brain in his daily flow; called Saar + Guy out for not yet having Guy installed on the Brain. Cousin at Amazon presented the Brain there and became “champion of the week” — giving a 40-person internal talk next week.
• 2026-06-02-directions-account-management-vertical — pitched AM/CS as the primary Brain vertical (79% fit, Nir Goldstein framing, Daniela demo); introduced the “70% of AM time is CRM management” value prop; advocated for building an AM-native CRM on top of Brain rather than just integrating with existing CRMs.
• 2026-06-04-directions-matan-construction — co-led expert interview with matan-amram; identified “context is the root of everything” as the unifying construction PM pain point; floated the “OS for Construction” framing and Lemonade analog.
• 2026-06-13-directions-revenue-cycle-and-construction-poc — argued for revenue-cycle / closed-loop GTM as a large strategic direction while keeping account-management-vertical and construction POC validation live.
• 2026-06-14-directions-from-home-strategy-brain-dogfooding — defended AM-native CRM and revenue-cycle-brain as strategic directions, while warning that generic Brain infrastructure may become built into Claude/OpenAI/Google and the startup wedge should be vertical flavor.
• 2026-06-15-directions-ofer-polivoda-am-operator-interview — interviewed ofer-polivoda on current CS tooling, past/present/future account-state framing, and the book-of-business expansion metric.
• 2026-06-16-directions-ran-levy-fiverr-cs-operator-interview — interviewed ran-levy on high-volume B2C seller success at fiverr; noted that Fiverr’s CSMs operate like sophisticated business consultants rather than simple retention reps.
• 2026-06-16-directions-ofri-avivi-renewals-operator-interview — interviewed ofri-avivi on whether automation, technical answers, and stronger CS context could let one renewal manager cover more regions/accounts.
• 2026-06-20-directions-planning-the-week-18-30 — pushed trend/VC investment scanning as ideation input, kept construction live as a parallel research lane, and took the action to schedule sefi plus an ideation session.
• 2026-06-21-directions-roy-keren-salesforce-gtm-ai-interview — framed the interview with roy-keren, compared Slack Bot to the team’s Brain/agent thinking, and took the follow-up to schedule sefi.