Call Analyst — Build Docs

Everything a new collaborator needs to understand the build, run it, and start advising. Written so you can ramp without me in the room. Nothing secret is printed here; this page itself sits behind the Daxos password gate.

Live product: callanalyst.app  ·  Repo: cus-commits/call-analyst (private)  ·  Owner: Mark / Daxos Capital

1. What it is

Call Analyst is an AI meeting notetaker aimed at investors and dealmakers. A notetaker bot joins your Zoom/Meet/Teams call, transcribes it live, and an AI analyzes the conversation in real time and afterward. The killer surface beyond "notes" is the Projects Hub (a.k.a. Data Room): every call about a given deal/company accumulates into a persistent memory you can ask questions across.

It ships as two products from one codebase:

2. Tech stack (deliberately boring)

• Frontend: one ~20,000-line vanilla-JS single-file PWA — call-analyst-pwa/index.html — plus tour.js and a service worker sw.js. No framework. No bundler. No build step. The HTML file is served as-is.
• Backend: Netlify serverless — Node functions (netlify/functions/*.mjs) for Stripe / credits / calendar / email, and Deno edge functions (netlify/edge-functions/*.mjs) for Recall, Projects, and storage.
• Data & services: Supabase (Postgres + Auth), Stripe (billing), Recall.ai (the notetaker bot), Fireflies/Otter/Fathom (transcript sources), Google Calendar (auto-join), Cloudflare R2 (file storage), Resend (email). Anthropic + OpenAI are the AI.
• Hosting: Netlify. DNS on Cloudflare.

3. The one big idea: the build flavor flag

At the top of index.html (~line 5206) the app reads the hostname and sets flags:

window.IS_CONSUMER  // true on consumer-analyst / consumer-testing hosts
window.IS_DAXOS     // true on the internal daxos-analyst host
window.BUILD_FLAVOR = {            // ~line 5223 — the single source of truth
  tours, demoCall, accountChrome,  // consumer-only capabilities
  passwordGate, modelQuickSelector,// internal-only capabilities
  projectsHub, aiRouting: 'proxy'|'direct', ...
}

Every behavioral difference between the two products reads a capability flag, never a bare hostname check. Consumer says "Ask AI"; internal says "Ask Claude". Consumer routes the AI through the /api/ask proxy (server keys, billing, credits); internal calls Anthropic/OpenAI directly with Mark's keys. When you add a feature, you gate it on a flag.

4. Repo & branches

cus-commits/call-analyst — one private repo. Single-file PWA + netlify/ functions.

Gitignored: .backups/, .netlify/, node_modules/, .env*, *.bak. No secrets and no customer/founder content ever land in git.

5. Deploy topology

Deploy command for every site (memorize the dir flag):

netlify deploy --dir=call-analyst-pwa --site=<site-id>   # add --prod to publish
# NEVER --dir=.  → that publishes the repo root and breaks the site.

Consumer sites (IS_CONSUMER=true)

Internal sites (IS_CONSUMER=false)

6. The app — index.html (~20.5k lines)

All markup, CSS, and JS inline. You navigate by these anchors (approximate lines — search the nearby function name to be exact):

Key globals: store (localStorage wrapper, ca_* keys) · getKeys()/getEnabledKeys() (notetaker API keys) · getSessions() (the canonical call+transcript records every renderer and poller consumes).

tour.js — interactive product tour, consumer-only (hard if(!BUILD_FLAVOR.tours)return). Two flows (call / hub) × three styles. Also defines caStartDemoCall(), which seeds a real sample session (Northbeam Robotics seed pitch, 25 turns) through the actual machinery, so transcript, analyses, and Ask AI genuinely work on the demo.

7. Serverless functions

netlify.toml: publish dir call-analyst-pwa; Node functions in netlify/functions, Deno edge in netlify/edge-functions (each self-registers its route via config.path). Scheduled jobs: calendar-poll + credit-autorefill every 2 min, cost-alarm hourly.

Node functions — netlify/functions/

Edge functions — netlify/edge-functions/

8. How data flows

A live call (via the Recall notetaker bot)

1. User pastes a meeting link or has calendar auto-join on → app POSTs /api/recall/bot.
2. recall-bot-create tier-gates, brands the bot (org name + logo), tells Recall to join with streaming transcript + webhook, inserts a recall_bots row.
3. Recall joins the meeting. As people speak it POSTs transcript.data events to /api/webhook/recall.
4. recall-webhook Svix-verifies, dedupes, updates bot status, inserts recall_transcript_chunks (bumping bot-hours).
5. The app polls /api/recall/chunks and renders the growing transcript into the live call card via getSessions() + renderContent().

Ask AI

1. User types in the composer → sendChat() builds {system, messages, model}.
2. Consumer POSTs /api/ask: authenticate (Supabase JWT) → enforce paywall/tier.
3. Look up the model → pick provider (Anthropic vs OpenAI) → pick key (server env key, or the user's BYOK).
4. Check/deduct AI credits (monthly allotment, then the purchased wallet).
5. Call the provider, stream the answer back, log tokens + cost. (Internal builds skip the proxy and stream directly.)

9. Integrations

10. Env & secrets

Secrets live only as Netlify environment variables on each site — never in the repo, never in this doc. The key names (so you know what exists):

SUPABASE_URL / ANON_KEY / SERVICE_KEY STRIPE_SECRET_KEY / WEBHOOK_SECRET STRIPE_PRICE_* (lite/standard/pro × mo/yr × byok) FOUNDING_COUPON_ID / TEAMDAXOS_COUPON_ID RECALL_API_KEY / WEBHOOK_SECRET / REGION_BASE ANTHROPIC_KEY OPENAI_KEY GOOGLE_OAUTH_CLIENT_ID / SECRET / CALENDAR_STATE_SECRET R2_ACCOUNT_ID / ACCESS_KEY_ID / SECRET_ACCESS_KEY / BUCKET STORAGE_PROVIDER BYOK_ENC_KEY ANALYTICS_KEY RESEND_API_KEY

11. Get it running locally

# clone (Mark will add you to the private repo)
git clone https://github.com/cus-commits/call-analyst.git
cd call-analyst

# the app is a static file — open it directly or serve it
npx serve call-analyst-pwa        # or: python3 -m http.server -d call-analyst-pwa

# for the functions + a prod-like env, use the Netlify CLI
npm i -g netlify-cli
netlify link        # link to a preview site, NOT prod
netlify dev         # runs functions + edge locally

On localhost IS_CONSUMER is false by default (it's hostname-based), so you'll see the internal flavor unless you force the flag. To preview the consumer build, deploy a feature branch and open its Netlify deploy-preview URL — that's the realistic path.

Shipping a change safely:

1. Branch off main (git checkout -b feat/whatever).
2. Edit, commit, push the branch → open the Netlify deploy-preview URL to test.
3. Get Mark's sign-off. Only then merge to main (which publishes to prod).
4. Backend changes that the internal build shares get cherry-picked/merged into internal too.

12. Where you can help / advise

Highest-leverage places for a second brain:

13. Roadmap — the 7 features

Ranked, approved, mockups built. See the visual examples →

Full spec + constraints: memory file project_callanalyst_7features_build.md. Build target: consumer testing/preview only until approved, never prod, never the internal build.

14. Gotchas & glossary

• main = prod. Pushing main publishes to callanalyst.app. Use feature branches + deploy-previews to test.
• Always --dir=call-analyst-pwa on deploy. --dir=. breaks the site.
• Gate consumer/internal on BUILD_FLAVOR, never a raw hostname check.
• Netlify env writes via CLI --site silently fail — use the API; DELETE+POST to update a key.
• No secret literals in code; no founder content in git.
• callanalyst.app ≠ DRA. "Data Room Analyst" (dra.daxos.us) is a separate product in a separate repo. The "Projects Hub" inside Call Analyst is a different thing despite the similar "data room" language. Don't cross them.

Glossary: PWA installable web app · Projects Hub / Data Room per-deal persistent memory inside Call Analyst · aap2 ask-across-projects · BYOK bring-your-own-key · notetaker bot the Recall.ai participant · Founding 50 first-50-users 20%-off coupon · flavor consumer vs internal build.