Every block copies as a complete request, ready to forward
Data
access.
Hit Copy, send it to whoever owns that system. Each block is written for you to send as-is: what is needed, what "access" actually means, and the terms — so nobody has to come back with a question.
This board is yours to drive. Hitting Copy marks that block sent with today's date, so you never update anything by hand — copy it, send it, done. Tap any mark to change it.A mark is only made by the side that can actually make the request, so copying from a Kairos account changes nothing on the board — tap a mark to set it by hand.
not sent you have not passed this one to its owner yet.
sent you sent it; we still cannot open the data.
working we tried it and it opens — that one is finished. We set this one, not you: only our side can tell whether a credential actually works.
stuck the owner said no, or it needs a decision from you.
not at MN no such system here, or you would rather not share it.
Anything sent and still not working after four days turns red and gets named at the top. That line is the only thing here worth reading daily.
What "access" means
- An API token or service credential, read-only. Our tooling reads it directly. Nothing gets re-exported by hand and it never goes stale. Ask for this first.
- A read-only seat for a named account we can point our own tooling at.
- One complete, dated export. Good for history; stale the moment it lands.
- A shared dashboard, or a person pasting answers out of a chat bot. This is not access — it breaks on the first follow-up question.
We learned this on the warehouse: a shared analytics link looked like access, but nothing could read it programmatically. A BigQuery read grant took minutes and actually worked. Start at the top — and if the top rung is impossible, any lower rung beats nothing. Just say which one it is.
Where things go
Invites and read-only seats: always both Kairos addresses — me@leematulis.com (Lee) and savickas.sarunas@gmail.com (Šarūnas), the identities we sign into this War Room with. Every invite, code and grant goes to both, so neither of us ever has to come back for it. Files: one folder in your Google Drive, named Kairos data, shared with both addresses (Viewer is enough); every export from every owner goes in there, one sub-folder per system. Every block below carries this, so nobody has to ask.
One source in motion. Three at the absolute maximum. Keep the ranked five, but do not send them as a batch. Start with the Sales AI system and stay on it until the access works or the exact blocker is named. The analysis starts the day a source lands. When that encounter closes, pull the next item from the ranked five. If an owner goes quiet for four days the board turns that item red at the top of this page.
The first five
Keep all five. Work one source at a time, three maximum in flight. The full map follows.
- Sales AI system — credentials. (Rytis; promised on the call)
- Slack — full workspace export. Admin → Import/Export, one file, no API limits. The most context per single action anywhere on this list.
- Marketing ad accounts and analytics — Google Ads, Meta, Search Console, and GA4 for the history from before mid-June this year (the daily GA4 export since then already lands in the warehouse). I have not seen a single marketing spend number.
- Google Drive — the marketing folder. The other half of marketing.
- Stripe — read-only. Refused payments, disputes, dunning.
Sales
Rytis
- The sales AI system — credentials
- The CRM — which one is in use? Deal pipeline, stages, won/lost
- Pricing and discount tables
Marketing
owner?
- Ad accounts: Google Ads, Microsoft Ads, Meta, X, Reddit, TikTok — or simply monthly spend per channel since January 2025, as an export. The warehouse holds no spend figure anywhere (every dataset checked, 16 Aug); it does see which paid click a web purchase carried — Google, Microsoft, Impact, CJ, Meta — so one spend line per channel is enough to put a cost on each door
- Google Analytics 4 — property access for the history from before mid-June this year (the daily export since then already lands in the warehouse) — and Search Console
- The SEO tool — Ahrefs, Semrush or another
- The email platform — which one? Campaign stats, segments, automations
- The affiliate programmes — Impact and CJ, both visible on web purchases — payouts by month, and any others
- Influencer outreach — where the list and the results live
- App Store Connect and Google Play Console
- Google Drive — the marketing folder
Customer support
owner?
- Slack — a full workspace export (Admin → Import/Export). One file, no API rate limits
- The community: Discord, Telegram, Reddit — where it lives and who moderates it
- The support cost line — monthly support payroll and tooling since January 2025 (or headcount with a loaded monthly cost), from finance. The warehouse holds every conversation and every reply — about 3,200 VPN conversations a month on three inbox seats, 58% tagged, billing and cancellation 27.5% of the whole and 39% of agent replies over the last twelve months (16 Aug) — but no cost figure, so what a contact costs, and what a billing question costs the company, needs that one line
- Intercom — the help-centre articles only (an export, or a read-scope token limited to Articles). Conversations, contacts and tags are not asked for: their full replica already lands in the warehouse every day; the articles do not.
Product and network
owner?
- Product analytics — Amplitude, Mixpanel, Firebase or other?
- Error tracking — Sentry or equivalent
- Feature flags and A/B tests, if any exist
- App store reviews and ratings
- Network telemetry: nodes, IP inventory, bandwidth
Payments
owner?
- Stripe — a read-only key or dashboard viewer: charges, refused payments, disputes, dunning
- PayPal and Coingate — charge-level exports or read-only API access: every renewal attempt with its outcome. The warehouse holds Stripe and Adyen at that grain and nothing for these two (about $11k of July renewals). Apple and Google retry inside the stores; there is nothing to ask for there
- Fraud and risk tooling
GoProxies
owner?
- Billing and the customer list
- Margin by SKU
- Supply sources — where the IPs come from
Finance
owner?
- The accounting system — which one?
- P&L by product and by legal entity, plus intercompany flows
- The recurring SaaS spend list, 12 months
Company knowledge
owner?
- ClickUp — an API token covering all Spaces
- Documents — Notion, Confluence, Drive? Where writing actually happens
- All Hands recordings and decks — and the date after which recordings stopped
Warehouse
Ieva
- BigQuery mysterium-bq — a grant to my own account (today we work through Šaras's)
- Table ownership and a metric dictionary. Without it we cannot tell whether a number means what we think it means
Finding what nobody lists
Everything above is what we knew to ask about. These four enumerate the rest of the toolset on their own.
- The recurring SaaS spend list — from accounting or the company card, 12 months. It names every tool the company pays for
- Google Workspace admin → the connected-apps list. This catches everything that costs nothing
- Password vault entry NAMES only (1Password, Bitwarden, whichever) — names, no values. I neither need nor want to see a single password
- The domain and subdomain list, and what runs on each — internal systems often live there and appear on no list at all
- Three questions for each team lead: (1) which tools do you open every morning, (2) where do you write numbers down, (3) what report do you file weekly or monthly, and where do you get its data