Strawberry

#### Direct competitors and differentiators - Strawberry vs Comet: Strawberry emphasizes companions that execute data work (research, prospecting, extraction) with a credit system. Comet has focused on a broader consumer-facing AI browser and has recently adjusted its availability and pricing in public coverage. - Strawberry vs Dia: Dia’s enterprise-focused materials reference completed or in-progress security attestations relevant to procurement. Strawberry states it is pursuing SOC 2/ISO 27001 but does not publish attestations in public documentation. - Strawberry vs Opera Neon: Opera Neon is positioned as a subscription-based agentic AI browser; Opera’s established brand may reduce some unknown-vendor concerns relative to newer entrants, but brand alone does not substitute for enterprise controls. #### Feature comparison: where Strawberry may excel and where it may lag Potential strengths (based on vendor positioning and user signals): - Focus on workflow automation for specific vertical tasks (sales, recruiting, research). - Context-aware companions that operate on active pages to reduce manual copy/paste work. Potential gaps: - Enterprise-grade identity and provisioning features (SAML SSO, SCIM), published SOC 2/ISO certificates, and exportable audit logs are not clearly documented publicly. - Real-world execution reliability remains a common challenge for agentic solutions operating across diverse web properties. #### Pricing comparison: considerations vs alternatives - Strawberry’s published entry-tier pricing is accessible for individual users, but intermittent heavy usage can result in additional usage-based charges. Competitors shifting to free/no-cost tiers may exert pricing pressure on paid, credit-based models. #### Adoption trends and agentic browser market risk The category is early and evolving. Procurement should expect rapid feature and pricing changes, evolving security risks (such as prompt injection and data exfiltration vectors), and possible vendor strategic shifts. A cautious pilot approach — using non-sensitive workflows and requiring clear controls before scaling — is advisable.