Slashy

What do they actually do

Slashy is a hosted AI agent you connect to your work apps (Gmail, Slack, Notion, calendars, CRMs). It can search across those tools, pull the right context, and then take actions like drafting emails, creating calendar events, or opening tickets—either on demand via chat or when triggered by events such as time or new messages (homepage; Launch HN).

Teams can build multi-step automations in a web workflow builder and add optional human-in-the-loop approvals and admin review. For larger customers, Slashy offers enterprise-oriented controls and private connectors to internal APIs so actions can be governed and audited before going live (enterprise).

Public materials show live integrations across a broad set of common tools and published tiers (Free, Pro, Premium, Enterprise), signaling a self-serve path for small teams plus enterprise plans via sales (homepage; pricing). The founders have highlighted early interest and traffic growth, citing a milestone of ~200k+ monthly visits as they scaled awareness (interview).

Who are their target customer(s)

• Startup founders and small-team operators: They juggle ops across Gmail, Slack, Notion, calendars, and CRMs and lose time copy-pasting context for meeting prep, follow-ups, and project updates. They want quick-to-set-up automations without adding headcount.
• Sales reps and SDR teams: They spend time drafting personalized follow-ups and syncing activity with HubSpot/Gmail, which slows outreach and leads to missed follow-ups. They need automation that keeps the CRM current while preserving context.
• Customer support and operations teams: They triage conversations across Slack and email and must reliably convert them into tickets or tasks. Manual handoffs drop context and delay resolution; they want consistent ticket creation and routing.
• Product managers and team leads: Action items and specs get scattered across meeting notes and Slack threads. They need a way to turn discussions into trackable tasks and keep related docs linked across tools to avoid rework.
• IT/security or compliance owners (mid-market/enterprise): They require audit trails, admin controls, and private connectors before allowing automated actions in production. Without governance and approvals, they will block adoption.

How would they acquire their first 10, 50, and 100 customers

• First 10: Founder-led pilots with YC and operator networks: run hands-on onboarding, wire up core apps, and build initial workflows to prove time savings quickly; use freemium/Pro to reduce friction (pricing; product).
• First 50: Lean into product-led growth with ready-made templates (outreach, meeting prep, ticket triage), plus tutorials and community posts in startup channels to drive self-serve signups; host group onboarding and offer short-term credits to accelerate activation (Launch HN; product).
• First 100: Pursue marketplace listings and co-marketing with tools like CRMs and ticketing systems; run targeted outreach to SDR, ops, and support teams with short pilots backed by approvals/security materials and early case studies to ease procurement (enterprise; Launch HN).

What is the rough total addressable market

Top-down context:

Slashy sits at the intersection of no-code automation/iPaaS and AI-powered workplace assistants: moving data and actions across SaaS apps with a conversational agent and governance features. Buyers span SMB teams seeking self-serve automation and larger orgs that require controls and approvals.

Bottom-up calculation:

Initial SMB-focused TAM: assume 100k English-speaking SMB/startup teams using Google Workspace/Slack adopt an ops agent; at 8 paid seats per team and ~$25/user/month, TAM ≈ 100,000 × 8 × $25 × 12 ≈ $240M/year. Enterprise contracts could expand this, but are not included in this initial estimate.

Assumptions:

• Focus on ~100k SMB/startup teams in early-adopter markets (English-speaking).
• Average of 8 paid users per adopting team for core workflows.
• Average price of ~$25 per user per month across paid tiers.

Who are some of their notable competitors

• Zapier: Broad no-code automation connecting hundreds of apps with rule-based triggers and multi-step Zaps; overlaps on moving data/actions but lacks Slashy’s chat/agent UX and cross-app semantic context (features).
• Make (Integromat): Visual workflow builder for complex, conditional automations and data transformations; strong on intricate flows, but not centered on an LLM agent or conversational search across tools (features).
• Workato: Enterprise iPaaS with governance, approvals, and robust connectors; closest on selling to larger orgs needing controls, though its core is integration at scale rather than an agent-first experience (enterprise).
• Glean: Workplace search that indexes knowledge across tools to answer questions; overlaps on finding context, but core product is search and knowledge surfacing rather than executing cross-app actions (product).
• Pipedream: Developer-centric automation that glues APIs together with code-based steps; flexible for engineers and custom connectors, but expects coding and isn’t built around a chat/agent workflow (workflows).