Harmony

**Product and the concrete problem it solves.** Harmony addresses a mundane but strategically consequential failure in modern organizations: employees need access, equipment, policy answers, account changes, and operational help, but the answer is scattered across ticketing systems, identity providers, HRIS platforms, knowledge bases, device-management tools, and departmental workflows. The employee experiences a maze of portals and forms; the support organization experiences the same request repeated across thousands of people. Harmony's product is an AI-native enterprise service management platform intended to provide one conversational front door while also executing the underlying work. An employee can ask for an application, recover a device, reset a password, check a policy, report a problem, or begin onboarding from a familiar collaboration surface. Harmony then aims to answer the question, request approval where necessary, call the appropriate system, update records, and return a result without forcing the employee to understand the company's back-office topology. This matters beyond convenience: unresolved access and device requests slow productivity, stale inventories create security blind spots, and manual offboarding or certificate-renewal processes can leave operational exposure in place.

**Core technology and how it works.** The public product surface is a connected agent system rather than a single chatbot. Harmony says it provides more than 100 production-ready agents, customized to the customer's tools, policies, and workflows, with multi-desk coverage across IT, HR, legal, finance, operations, and security. The agents can be invoked from Slack, Microsoft Teams, Zoom, and other employee-facing tools, while a broad integration layer connects to identity providers such as Okta and Microsoft Entra ID, endpoint and mobile-device systems such as Intune, Jamf, Kandji, and ManageEngine, HR systems such as HiBob, BambooHR, and Rippling, knowledge systems such as Confluence, Notion, SharePoint, and Google Workspace, and common IT service platforms. Harmony also describes a continuously generated knowledge base that learns from tickets, user interactions, and organizational context, alongside a system of record for automated asset and software inventory. That combination is the technical load-bearing point: a useful service agent needs current organizational facts, a permission-aware action path, and a durable record of what happened. The company publishes examples including application-access requests with approvals and automatic provisioning, identity-group assignment, device recovery with identity verification, license-expiration discovery, certificate-expiration detection, and EDR-misconfiguration detection. The public material does not disclose the foundation models, orchestration architecture, model-evaluation methodology, or exact authorization implementation, so the platform should be understood as an integration-heavy agent and workflow system whose production reliability depends on those undisclosed details.

**Market, customers, and go-to-market.** Harmony sells into the overlap between IT service management, employee experience, identity and asset administration, and the emerging market for enterprise agents that can take action. The initial buyer is likely a CIO, IT operations leader, or service-desk owner seeking measurable ticket deflection and faster employee resolution, but the expansion path is deliberately cross-functional: HR onboarding and offboarding, procurement approvals, finance requests, legal workflows, compliance and policy questions, DevOps support, and security operations. The company's stated deployment model is additive rather than a rip-and-replace transformation. It can sit inside collaboration tools and connect to an existing stack, while prebuilt agents and no-code customization are intended to reduce implementation time. Harmony claims more than 100 integrations and markets agents that can be deployed in days rather than months. Calcalist reported that the company was in sales discussions with approximately 60 customers in the United States, Europe, and Israel, including Coralogix, eToro, HoneyBook, and other technology companies; the same article names n8n, Cyera, and KITH among customers. Those are meaningful reference signals, but the public record does not establish which customers are paying, contract values, renewal rates, or the proportion using only IT versus multiple desks. The commercial challenge is to convert a compelling employee interface into a durable system-of-action budget line without becoming a thin front end over ServiceNow, an identity platform, or a customer's own agent stack.

**Traction, funding, and third-party validation.** Harmony announced its public launch on July 28, 2026 with a $34 million Seed round led by Lightspeed Venture Partners and participation from Hitachi Ventures, Fin Capital, Mercer Ventures, Operator Partners, and technology-industry angels including Wiz co-founder Assaf Rappaport and Eon.io co-founder Ofir Ehrlich. The round is a strong financing and network signal for a company founded in 2025, although funding should not be mistaken for product-market proof. Public performance data is primarily company-reported: Harmony says roughly 48% of support requests can be resolved within two weeks of implementation, more than 75% without human intervention within three months in some deployments, and employee adoption can exceed 80% in selected organizations. Citybiz reproduces further company-reported deflection figures of up to 68% in HR, 58% in procurement, 47% in DevOps, 42% in cybersecurity, and 36% in finance. Harmony's website also displays 4.8-star G2 and 4.9-star Capterra ratings and lists recognition such as G2 Leader and High Performer, while its homepage shows customer or ecosystem logos including Cyera, eToro, Cribl, Coralogix, KITH, n8n, AppsFlyer, Exodigo, Fireblocks, HoneyBook, and Eon. These signals indicate a live product and customer-facing distribution motion, but independent validation is limited: no audited automation study, revenue disclosure, retention cohort, security-assurance report, or customer case study with baseline and counterfactual is public in the reviewed sources. Diligence should reconcile the different public headcount and scale descriptions before treating the launch metrics as comparable.

**Founders and team background.** Harmony was founded by Nitzan Shapira and Ran Ribenzaft, who previously co-founded Epsagon, a cloud-native observability company acquired by Cisco in 2021 in a transaction publicly described at approximately $500 million. That prior experience is unusually relevant to Harmony's enterprise thesis. Epsagon required the founders to understand distributed systems, production telemetry, developer workflows, and the operational cost of software sprawl; Harmony applies a similar systems perspective to the internal services layer rather than to application observability. Shapira is identified as co-founder and CEO, and Ribenzaft as co-founder and CTO. The official About page also names Menni Alashvili as VP R&D, Omer Zucker as VP Product, Gadi BenMark as CMO, Bob Laskey as CRO, and Edy Glozman as General Counsel. Calcalist reported approximately 50 employees at launch, with 35 in Israel and 15 in New York, while other public databases place the company in a broader 51-100 employee range; the exact current number is therefore not treated as settled. The team has a credible repeat-founder and enterprise-technology base, and the named commercial and revenue leadership suggests an ambition beyond a founder-led product experiment. The open question is whether an experienced observability founding pair can build the security engineering, customer-success, policy, and enterprise-sales depth required when the product is authorized to change identities, software access, devices, and records across many systems.

**Competitive dynamics and prospective edge.** Harmony competes with established platforms and several different replacement approaches. ServiceNow and Atlassian Jira Service Management own installed ITSM workflows and can add AI agents to existing tickets and knowledge bases. Freshworks and Ivanti compete with lower-friction service-management and endpoint-management suites, while Moveworks and Glean attack employee support through enterprise search, conversational assistance, and agentic workflow execution. Okta, Microsoft Entra, Microsoft Intune, Rippling, and device-management vendors control important identity, lifecycle, and asset primitives that Harmony must integrate with and may eventually extend themselves. Harmony's prospective edge is the breadth of its action layer: one employee-facing experience, prebuilt agents across multiple departments, continuously refreshed knowledge, asset and software records, proactive signal-triggered agents, and the ability to operate alongside rather than replace the incumbent stack. Its best wedge may be a measurable service-desk outcome followed by expansion into onboarding, offboarding, access governance, and security hygiene. The moat is not yet proven. Integrations can be copied, foundation-model capabilities are broadly available, and incumbents own distribution, authoritative system data, procurement relationships, and the right to make changes in their own control planes. Harmony must show that its cross-system context, workflow coverage, implementation speed, and demonstrated automation quality create enough value to survive bundled competition and reduce rather than add enterprise tool sprawl.

**Defense, security, and resilience dual-use relevance.** Harmony's dual-use case is enabling and operational rather than defense-native. The same functions that reduce friction for a commercial employee can support continuity in a defense contractor, hospital, utility, emergency-management body, or public-sector organization: controlled application access, identity-group changes, device recovery, accurate asset inventories, certificate-expiration warnings, employee onboarding and offboarding, knowledge retrieval, and detection of endpoints where EDR protections are disabled or misconfigured. During a cyber incident or infrastructure disruption, a governed service layer that can route requests, preserve approved procedures, surface current system state, and execute repeatable low-risk actions may reduce the human queue that otherwise becomes a bottleneck. The security relevance is strengthened by Harmony's explicit product examples around EDR misconfiguration, identity verification, access approvals, compliance and policies, and software governance. It is also plausible that a large industrial or defense organization would value a single operational interface across many internal teams and geographically distributed sites. However, this record does not claim military capability. No public source reviewed here identifies an Israeli Ministry of Defense, military, intelligence, defense-prime, classified, or critical-infrastructure deployment; the company has not published disconnected-network operation, sovereign hosting, government accreditation, or mission-specific evaluation evidence. The appropriate conclusion is credible resilience and security adjacency with a short commercial deployment path, not fielded defense traction.

**Growth stage, trajectory, and key diligence risks.** Harmony is classified as early even though its capital, customer list, leadership bench, and launch metrics are stronger than those of a typical seed company. It was founded in 2025, publicly launched in July 2026, and reported approximately 50 employees and about 60 customer sales conversations or relationships at launch, with company-reported deployments already producing material automation in selected organizations. The trajectory is to move from an AI service desk into a broader agentic enterprise service-management control layer spanning employee requests, assets, identities, applications, compliance, security, and departmental workflows. The upside depends on expansion: if customers reuse Harmony agents across several desks and keep the platform connected to authoritative systems, accumulated workflow context and operational data could improve retention and make the platform difficult to remove. The key diligence risks are specific. (1) Permission and action risk: a wrong identity change, access grant, offboarding step, or device-recovery instruction can become a security incident rather than a bad answer. (2) Automation-quality risk: the public deflection percentages are not independently audited and may vary sharply by request mix, integration quality, and human-review policy. (3) Incumbent risk: ServiceNow, Microsoft, Okta, Atlassian, Freshworks, and endpoint vendors can bundle adjacent agents into contracts customers already own. (4) Integration risk: 100-plus connectors create maintenance, API-change, data-freshness, and least-privilege burdens that grow with every customer. (5) Model and privacy risk: the company has not publicly detailed model providers, data retention, tenant isolation, or evaluation controls. (6) Commercial-risk concentration: a large early customer pipeline still needs conversion, expansion, and renewal proof. (7) Strategic-maturity risk: resilience adjacency will remain optional until Harmony demonstrates secure deployment in regulated, restricted, or critical operating environments.