Guy Barkat

Role

Senior at etoro; business owner for the APIs domain (API Trading, Agent Portfolio, App Store) and involved in M&A discussions. In 2026-05-06-brain-os-strategy-brainstorm played the explicit “red team” role challenging the Brain’s value proposition. By 2026-05-27-directions-vertical-pivot-and-prediction-markets had moved from red-team-only into authoring the dominant strategic frame (vertical-use-case-led-brain).

Affiliations

• etoro — current employer; business-owner over API Trading, Agent Portfolio, and App Store. Recent compliance incident blocking two key markets is the canonical “Brain would have caught this” example.
• brm — family VC; father is owner/MP, uncle Eran is the SaaS/hi-tech partner. Potential intro pipeline.

Notes

• Personally knows Sierra’s VP Product (ex-Mixpanel VP Product, who joined Sierra as an IC engineer for ~$7M signing). Used this as a data point for Sierra’s seriousness — see sierra.
• Met Wonderful’s VP Product (Norm Mahabi/Rakhabi — uncertain spelling) once when trying to bring him in to discuss product methodology at eToro.
• Frames the central strategic question as “vitamin vs. painkiller” — see vitamin-vs-painkiller-framing.
• Believes etoro is more chaotic than monday and that most companies are closer to eToro-style chaos than Monday-style alignment, which strengthens the market opportunity.
• Convinced any pitch must convince a CEO buyer that they cannot build this themselves and that the alternatives in 6 months will not be good enough.
• New (2026-05-27) strategic frame: build vertical, use-case-led products with the Brain as the moat underneath — see vertical-use-case-led-brain. Pricing intuition: ride agent-token usage like Cursor (≈20% margin) rather than seat-based wiki licensing.
• New (2026-06-13) red-team frame: the product cannot be “better context” alone; it must expose a concrete output buyers can pay for, whether in revenue-cycle-brain, account-management-vertical, or construction exec visibility.
• Surfaced the prediction-markets-regulatory-play thesis after a conversation with tomer-shalom; has a follow-up scheduled with the chairman of winner-toto early next week.
• Meeting axonius’s CTO Wednesday evening for directions input. Connection routed through pagaya’s founder.
• Personal: child-on-the-way; available cadence-wise “until the birth, then a few days off”; partner of a Maccabi Tel Aviv basketball fanbase (the football opener of the meeting).
• 2026-06-20: articulated the strongest human-in-the-loop-accountability thesis so far: company brains cannot be accountable without human approval because real organizational truth includes politics, status theater, and context not captured in text.
• 2026-06-20: pushed the group toward a denser interview cadence and agreed to source at least two construction-management interviews plus evaluate user-interviews.
• 2026-06-21: used roy-keren’s salesforce workflow as a red-team benchmark for the AM wedge: Slack Bot makes account prep look close to solved in advanced GTM orgs, so the team needs a sharper secret sauce.

Mentioned in

• 2026-05-06-brain-os-strategy-brainstorm — designated red-team challenger; pushed for sharper vision beyond “we are an Operating System.”
• 2026-05-19-saar-leshno-glaucoma-data-tracking — joined saar-arbel for the ari-leshno pitch; pushed Ari hardest on whether the visual-field-tracking pain generalizes beyond ophthalmology.
• 2026-05-27-directions-vertical-pivot-and-prediction-markets — author of the vertical-use-case-led-brain reframe and the prediction-markets-regulatory-play tangent.
• 2026-05-31-directions-connect-businesses-and-brain-scaling — author of the new connect-businesses-multi-vertical-api thesis (third open exploratory direction, non-Brain). Also surfaced the strongest Brain-scaling-difficulty argument yet — and reframed the difficulty itself as the moat.
• 2026-06-02-directions-account-management-vertical — interrogated the AM vertical pitch; pushed for bigger ambition (“be the next Monday for AMs, not just a tool on the side”); raised the integrate-vs.-build-CRM architecture question; offered to connect AM practitioners ofer-polivoda and Gal (Dave-AI startup) for feedback. Noted his personal experience: managing relationships beyond ~10 customers without a system causes loss of context.
• 2026-06-04-directions-matan-construction — co-led expert interview with matan-amram; raised the subcontractor/labor-deployment layer as an under-examined segment; noted the lack of any real enforcement mechanism on lagging subcontractors as a structural market flaw; suggested following up with “Moshiko” (construction contact) for the subcontractor perspective.
• 2026-06-13-directions-revenue-cycle-and-construction-poc — hosted the in-person directions session; pressure-tested revenue-cycle-brain, account-management-vertical, and construction POC paths; contributed wonderful / discount-bank and meitav / brm market anecdotes.
• 2026-06-14-directions-from-home-strategy-brain-dogfooding — argued for aggressive AM/operator interviews before demos, challenged the revenue-cycle thesis as possibly just data engineering, and proposed proactive Brain dogfooding around missing context, stale cleanup, and action-item follow-up.
• 2026-06-15-directions-ofer-polivoda-am-operator-interview — brought ofer-polivoda into the AM validation loop and guided the interview toward existing-tool gaps, prep workflow, and relationship-memory pain.
• 2026-06-16-directions-ran-levy-fiverr-cs-operator-interview — interviewed ran-levy on Fiverr’s seller-success operating model; pushed on CSM portfolio size, reactive load, tooling, attribution, and why Fiverr does not proactively cover more high-value sellers.
• 2026-06-16-directions-ofri-avivi-renewals-operator-interview — brought ofri-avivi into the AM/CS validation loop and probed renewals workflow, current tools, regional differences, and customer-health visibility.
• 2026-06-20-directions-planning-the-week-18-30 — framed human approval as the Brain trust layer; supported 2026-06-20-vertical-product-over-generic-brain; pushed the interview sprint and construction sourcing plan.
• 2026-06-21-directions-roy-keren-salesforce-gtm-ai-interview — interviewed roy-keren on Salesforce AE workflow, Slack Bot, and whether the AM wedge has enough unsolved surface beyond incumbent account-prep automation.