Alkemi: Put a Data Analyst in Your Slack Chat for Free

2026-02-28 | Product Hunt | Official Site

30-Second Quick Judgment

What is this?: Ask data questions in plain English within Slack ("How much did the pipeline grow last week?" "Which product is trending?") and get charts and answers instantly. It connects to your company's Snowflake, BigQuery, HubSpot, and other data sources.

Is it worth watching?: Yes. This direction (Conversational BI + Slack Native) is a clear trend in the 2026 BI space, and it's currently completely free. The team consists of Seattle-based serial entrepreneur brothers with successful exit experience. However, the product was just released a week ago, so maturity is still a question.

Comparison:

• Slack AI's native features only search internal Slack data, not external sources.
• Tableau/Metabase/Mode are traditional BI tools requiring a switch to a separate interface.
• Alkemi's edge: Query external data via chat right where you already work—in Slack.

Three Key Questions

Is it relevant to me?

Target Users:

• Sales/Marketing/Ops teams who frequently discuss business metrics in Slack but have to switch tools to check data.
• Small companies without dedicated data analysts where everyone needs to pull their own data.
• RevOps teams discussing pipelines and conversions daily in Slack.

Is that you?: You are the target user if:

• You often say "Wait, let me check the data" during Slack discussions.
• Your data is in Snowflake/BigQuery/HubSpot, but you don't know SQL.
• You often want to ask an analyst a "small question" but feel bad bothering them.

Use Cases:

• Before a weekly meeting: Quickly pull a chart of last week's pipeline changes in Slack.
• During a discussion: Someone asks "Which channel has the highest ROI?", @ Alkemi for the answer.
• Not for you if: Your data isn't in the supported sources or you don't use Slack.

Is it useful for me?

ROI Judgment: If your team has more than 5 people, discusses business metrics in Slack daily, and your data is in Snowflake/BigQuery—it's absolutely worth 30 minutes to try it out since it's free.

Is it a "wow" experience?

The Highlights:

• Zero Switching Cost: Ask directly in the Slack window you already have open; no need to open Metabase or Looker.
• Natural Language Querying: No SQL required; just speak like a human.
• Instant Charts: Get a chart immediately after asking; no waiting for an analyst to draw it.

The "Wow" Moment:

"This hits. If teams live in Slack but their data lives everywhere else, that's pure friction. Bringing real answers into the exact moment decisions happen? That's leverage." — @Faazsh (Twitter)

Team Attitude:

"We want blunt feedback. Let us know what would make this essential for you. We're shipping fast." — Connor Folley, Founder

To be honest, the product is so new (released just over a week ago) that large-scale user feedback isn't out yet. What we see now are mostly early reactions from the PH launch day.

For Independent Developers

Tech Stack

• Data Connection Layer: Snowflake, BigQuery, Databricks, HubSpot, Looker, CSV
• Core Mechanism: Converts data sources into structured "agent-usable functions"—essentially wrapping table structures and query logic into tool functions that the AI agent calls to generate queries.
• Protocol Support: MCP (Model Context Protocol) compatible; open-sourced an MCP Server.
• Platform: Slack Bot + Web-based DataLab.
• Architectural Philosophy: API-first, compatible with RAG frameworks like LangChain/LlamaIndex.

Core Implementation

Alkemi's core isn't just simple text-to-SQL. It encapsulates the schema and business semantics of each data source into "structured functions." When the AI calls these functions, the generated queries are constrained and validated—this is what they mean by "responses are reliable, not just convenient." It's like giving the LLM a type-safe toolbox instead of letting it write SQL freely.

This approach is similar to how Cursor uses AST to understand code—they even describe themselves as "Like Cursor for Business Teams."

Open Source Status

• GitHub: alkemi-ai/alkemi-mcp — The MCP Server is open-sourced, allowing any MCP client to query databases using natural language.
• The core Slack Agent product is not open-sourced.
• Build-it-yourself Difficulty: Medium-High. The MCP Server part provides a reference, but the core schema → function mapping + natural language understanding is the key barrier. Expect 2-3 person-months for an MVP.

Business Model

• Currently Free (Growth phase strategy).
• Dual-Engine Model:
  1. Slack Agent / DataLab — For enterprise users, self-service querying.
  2. DataLab for Data Providers — For data providers to safely sell data to AI developers ($4.4T AI data economy).
• Future likely involves usage-based or per-seat subscriptions.

Giant Risk

High Risk. Slack is building its own AI agent ecosystem (Agentforce + Slack AI), and Salesforce is Slack's parent company. Once Slack's native AI supports connecting to external data sources (BigQuery, Snowflake), Alkemi's core differentiator could be erased. However, in the short term, Slack AI only searches internal Slack data ($10-15/user/month), giving Alkemi a window of opportunity.

Another threat comes from Google (BigQuery + Gemini) and Snowflake (built-in AI features) attacking from the data side.

For Product Managers

Pain Point Analysis

• Problem Solved: Solves the friction business users face when they need data to support decisions in Slack but the data is in another system, requiring them to wait for an analyst or switch tools.
• Severity: High frequency (multiple times daily), medium necessity. Founder Connor says that in every company he's worked at, Slack is where revenue conversations happen, but people hesitate to bother an analyst for a "small question."

User Persona

• Primary Users: Non-technical staff in Sales/Marketing/Ops teams.
• Decision Makers: VP of Sales, Head of Revenue Ops, CMO.
• Usage Scenarios: Checking metrics before daily/weekly meetings, real-time hypothesis testing during discussions, pulling trend charts for monthly reviews.

Feature Breakdown

Competitive Differentiation

Key Takeaways

1. "Deliver value where the user already is"—Don't make users come to your dashboard; bring the answers to the Slack conversation.
2. Free + MCP Open Source growth strategy—Secure an ecosystem position first, then consider monetization.
3. "Like Cursor for Business Teams" positioning—Leverage existing mental models to reduce cognitive load.

For Tech Bloggers

Founder Story

• Connor Folley: Former Amazon Marketing Manager → Founded Downstream (Amazon ad analytics) in 2018 → Acquired by Jungle Scout in 2021 → Stayed at Jungle Scout for two years → Founded Alkemi.
• Maxwell Folley: Connor’s brother, previously founded Caravel (conversational intelligence), acquired by Commsor.
• Brother Duo + Double Exits: This story writes itself. Two Seattle brothers, separate startups, separate acquisitions, now partnering on a new project.
• Ryan Breen: Co-CEO (a rare dual-CEO structure), details to be explored.

Motivation Quote:

"At every company I worked at, Slack was where revenue conversations actually happened. Teams would be in the middle of a pipeline discussion and need a data point, but then hesitate to ask an analyst." — Connor Folley

Controversies / Discussion Angles

• Will Slack do it themselves? Salesforce just announced the Slack AI agent ecosystem; how long can Alkemi survive?
• Is "Conversational BI" a real need? Will people actually query data in Slack, or are they more comfortable opening a Dashboard?
• Data Accuracy: Are AI-generated queries reliable? Who is responsible if they're wrong?
• How long can "Free" last? 7-person team, $1.65M pre-seed—how long can the free strategy be sustained?

Hype Data

• PH Votes: 94 votes (moderate, not a viral hit).
• Twitter Discussion: Mostly self-promotion by the team; very little organic discussion.
• GeekWire Interview: Gained attention from Seattle's tech media.
• RevGenius Community: Actively seeking feedback in RevOps communities.

Content Suggestions

• Angle: "When Slack Becomes the New BI Entry Point—Will Conversational Analytics Replace Dashboards?"
• Trend Opportunity: The Slack AI agent ecosystem is just starting; Alkemi is among the first to dive in.

For Early Adopters

Pricing Analysis

Hidden Costs: Initial setup requires IT help to connect data sources (Snowflake/BigQuery), which might take some coordination time.

Getting Started Guide

• Setup Time: 15-30 minutes (if IT has the data source connection ready).
• Learning Curve: Low (if you can type, you can use it).
• Steps:
  1. Visit alkemi.ai/slack-agent, add the Slack App.
  2. Connect data sources (Snowflake/BigQuery/HubSpot/CSV) or use a dummy dataset to explore.
  3. @ Alkemi in Slack and ask a question in plain English.
  4. Get answers, charts, and suggestions.

Pitfalls and Gripes

1. Product is very new: Released Feb 18, 2026; stability and feature completeness haven't been verified at scale.
2. Data Source Limits: Currently supports Snowflake, BigQuery, Databricks, HubSpot, CSV—if you use direct MySQL/PostgreSQL, it might not be supported yet.
3. AI Accuracy: Accuracy in conversational queries is a common industry challenge; complex queries might fail. They claim to use structured functions for reliability, but no public benchmarks are available.

Security and Privacy

• Data Storage: Data does not leave your infrastructure; the AI model performs read-only inference.
• Privacy Policy: Official Privacy Policy
• No Training: Explicit promise that queries and results are not used to train external models.
• Auditability: All sessions are auditable and governed by existing security policies.
• Security Audit: No third-party security audit reports yet (too new).

Alternatives

For Investors

Market Analysis

• Conversational AI Market: $17.97B in 2026 → $82.46B by 2034, 21% CAGR (Fortune Business Insights).
• BI Market: Conversational BI listed as a top 10 BI trend for 2026 by ThoughtSpot.
• Slack Ecosystem: 47.2M DAU, ~79M MAU, $1.3B estimated annual revenue (DemandSage).
• AI Data Economy: $4.4T (Morningstar/PR Newswire).

Competitive Landscape

Timing Analysis

• Why now:
  1. Slack just opened its AI agent ecosystem (Agentforce), allowing third-party agents to embed natively.
  2. The rise of the MCP protocol creates a need for AI-native interfaces for data tools.
  3. 81% of business users already use ChatGPT for decision-making (NBER study) but lack trusted data sources.
• Tech Maturity: LLM natural language understanding is now sufficient for conversational queries, though accuracy remains a challenge.
• Market Readiness: High—"AI for data" is one of the hottest tracks in 2026.

Team Background

• Connor Folley (Co-founder & CEO): Former Amazon Marketing Manager, Founder of Downstream (acquired by Jungle Scout in 2021).
• Maxwell Folley (Co-founder): Founder of Caravel (acquired by Commsor).
• Ryan Breen (Co-founder & Co-CEO).
• Aristotle Andrulakis (Co-founder & CIO).
• Team Size: 7 people.

Both founders have startup + successful exit experience, and original investors have returned to support them—a strong signal of trust.

Funding Status

• Raised: $1.65M pre-seed.
• Lead Investor: Tuesday Capital.
• Follow-on: DNX, MGV, Angel investors (all previous Downstream investors).
• Valuation: Not disclosed.

Conclusion

Bottom Line: Alkemi has identified a real pain point (querying data in Slack) but is operating in a space where giants are watching closely. Their free + open-source MCP strategy is a smart growth move. The key question is whether they can build a moat before Slack's native AI consumes the market.

Resource Links

2026-02-28 | Trend-Tracker v7.3