Sarvaswa AI Labs
Slack Data Copilot

Plain-English answers to your Airtable & Google Sheets, in Slack.

An internal Slack copilot that lets any team member ask data questions in natural language and get sourced, traceable answers, without bothering the ops person and without learning a new tool.

The problem

Your data is in Airtable and Sheets.Answers shouldn't depend on one person.

Sales asks “which deals are stuck?” Finance asks “what's our AR aging?” Project managers ask “what's due this week and who owns it?” Today, every one of those questions is a Slack thread, a screenshot, and a wait.

The ops person who knows the right view is the bottleneck. The team makes decisions on stale data, or no data. And when a number gets challenged, nobody can show how it was calculated, which is when finance meetings turn awkward.

How it works

From a Slack question to a sourced answer, and into the audit log.

User question#ops in SlackSlack botreceives + plans the queryClaudepicks base, fields, filtersLive readAirtable + Google SheetsSourced answerinline table + deep linkAudit log + admin pageEvery query, every result, response time, daily LLM token spend in dollars.Mark answers correct or wrong; flag unanswered questions for prompt review.

The bot plans the query first, fetches only the records it needs, returns a structured answer with a deep link back to the source view, and writes the whole interaction to an audit log. Read-only by design, every query is a SELECT-equivalent.

What we ship

Four pieces, end-to-end.

01

Plain-English Q&A in Slack

A private channel where any team member types a question in natural language and gets a structured answer; text, an inline table or chart when the data shape calls for one, and a direct link back to the source so every number is traceable.

  • Conversational interface inside an existing Slack workspace
  • Inline tables and charts when the data shape warrants
  • Honest "I don't know" responses instead of hallucinations
02

Live reads from Airtable + Google Sheets

Connects to one Airtable workspace (multiple bases and tables) and a Google Sheets folder. Auto-discovers Airtable schema on first run and infers Sheet structure from column headers, no training, no manual mapping.

  • Auto-discover Airtable bases, tables, and fields
  • Infer Google Sheets structure from headers
  • Read-only by design in phase one, no surprise writes
03

Sourced answers, every time

Every response includes a deep link back to the exact Airtable view or Sheet range used to compute the answer. If a number looks wrong, you can click through and verify the underlying records in seconds.

  • Deep links to Airtable views and Sheet ranges
  • Plain explanation of which fields were summed
  • Confidence flags on fuzzy joins between tables
04

Audit log and admin page

Every query is logged: the original question, the data sources hit, the answer returned, and the response time. A lightweight admin page lets the ops lead review answers, mark correct or incorrect, flag unanswered questions, and watch daily LLM cost.

  • Full query audit log with response time
  • Mark correct / incorrect, flag for prompt review
  • Daily LLM token spend, in dollars, on the same page
Real questions it answers

Eight questions teams ask, answered without a meeting.

SalesPipeline staleness check

Which deals have been stuck in the pipeline for more than 14 days?

The bot filters Airtable deals by stage-change timestamp and returns deal name, current stage, days stuck, and owner, with a direct link to the filtered view.

FinanceAccounts receivable aging

What is the AR aging breakdown by client?

Groups outstanding invoices by client and aging bucket (0–30, 31–60, 60+), returns a clean inline table, and links to the source range in Sheets.

Account managementRetainer hours consumed

How many retainer hours has Acme used this month?

Joins time-tracking with the client table, filters by current calendar month, sums logged hours, and compares against the contracted retainer if that field exists.

Project managementWeekly project ownership

Which projects are due this week and who owns them?

Filters the project status table by due date inside the current ISO week, returns name + owner, and flags overdue items from the previous week separately.

Team leadTime log lookup by project

Who has logged time on Bituin in the last 30 days?

Filters the time tracking table by project and date range, deduplicates by team member, and returns hours logged per person with a link to the underlying records.

ManagerFuzzy join across tables

Who has been on more than five client calls this month?

Substring-matches calendar event titles against known client names, applies a confidence threshold, and notes which matches were exact vs fuzzy. Low-confidence rows are surfaced separately.

Ops + FinanceBilling discrepancy investigation

How much have we billed Acme this quarter?

If a number is challenged, the audit log shows exactly which records were summed, the date range used, and the field interpretation, so disagreements (calendar vs fiscal quarter, missing record, wrong field) get resolved in minutes.

Ops leadAdmin monitoring + feedback loop

(opens the admin page, not Slack)

Reviews the past 24 hours of queries, marks answers correct or wrong, flags unanswered questions for prompt review, and watches daily token spend in dollars, no separate Anthropic dashboard needed.

How we ship it

Three milestones, 4 to 8 weeks total.

M1

Spec + first base

Technical specification document and a working live connection to one Airtable base, with schema auto-discovery confirmed end-to-end.

M2

Five canonical questions, in Slack

The bot answering five canonical question types accurately inside Slack, with source links and per-query logging active.

M3

Admin page + handoff

Admin page live with full audit log, daily LLM cost display, and full project handoff with documentation your team owns.

Scope

Honest about what's in,and what's later.

In phase one
  • One Airtable workspace, multiple bases and tables
  • One Google Sheets folder, all active sheets
  • Read-only queries, never any writes in phase one
  • Slack interface in a private channel
  • Per-query audit log with response time
  • Admin page with feedback marks and daily token spend
  • Architecture designed to absorb Notion in phase two without a rebuild
Phase two roadmap
  • Write actions to Airtable or Sheets (planned for phase two)
  • Notion integration (planned for phase two)
  • User-level access control beyond Slack workspace membership
  • Mobile or native app interface
Questions worth answering

Slack data copilot, FAQ.

The Slack data copilot is a read-only Slack bot that lets any team member ask plain-English questions about your Airtable bases and Google Sheets and get sourced, traceable answers, without bothering the ops person and without learning a new tool. It auto-discovers Airtable schema, infers Sheet structure from headers, returns answers with deep links back to the source records, and logs every query for review on a lightweight admin page.
In phase one: one Airtable workspace (multiple bases and tables) and one Google Sheets folder containing the active sheets. The architecture is designed so that Notion integration can be added in phase two without a rebuild. Other connectors (HubSpot, Linear, internal Postgres) follow the same pattern.
Strictly read-only in phase one, by design. Every query that lands in your data source is a SELECT-equivalent. Write actions (creating follow-up records, marking invoices as sent, updating fields) are flagged for phase two so they ship behind explicit approval flows and an extended audit trail.
Most engagements move from kickoff to a production Slack copilot in 4 to 8 weeks. Milestone one (spec and first live Airtable connection) lands inside the first two weeks, milestone two (five canonical question types in Slack) follows, and milestone three (admin page, audit log, token cost display, handoff) closes the build.
The admin page shows daily token spend in dollars on the same screen as the audit log, so the ops team has visibility without opening the Anthropic dashboard. Per-query token usage is captured so you can spot expensive queries and tune them before they become a budget item.
Only the data needed to answer the current question reaches the model. The bot plans the query first, fetches the minimal records, and ships those (not whole tables) to Claude. We deploy via the Anthropic Claude API or AWS Bedrock under your account, your choice, and credentials and audit logs live inside your infrastructure.
It says so clearly and describes what it attempted, which sources it looked at, which fields it tried, and where the ambiguity was. Unanswered questions get surfaced in the admin page so the ops lead can refine the prompt or add a new pattern, instead of being silently swallowed.
When two tables do not share a clean key, e.g. calendar event titles vs client names, the bot uses substring and similarity matching with a confidence threshold. The answer notes which rows matched exactly and which were fuzzy, and lists low-confidence rows separately so you know what may be missing from the count.

Ready to scope your Slack data copilot?

A 15-minute consultation is enough to know if it fits, and to roughly size the build for your Airtable and Sheets footprint.

Book a 15-min consultation