Skip to content

Day-zero checklist

Sent to the incoming FA 1–2 weeks before start. Day one = ready to run. This is the provisioning list; the full do-and-confirm version (with the briefing, language, and ground-rule gates) lives at the top of the FA onboarding guide.

Every tool below should be provisioned before day one. Anything under scailetech (GitHub, Vercel, Supabase) that is missing must be requested on day 1, before any code is written. The "who grants" column points to who-grants-what.md; route requests through Niccolo unless noted.

Done Tool Purpose Who grants
Google Workspace (@scaile) Company email + login for Vercel/Supabase/most tools Niccolo (confirm)
Bitwarden Password manager — system of record for all credentials Niccolo (confirm)
Slack Internal comms Niccolo (confirm)
Claude plan (Team) Paid plan that includes Claude Code — company account, not personal Simon / Niccolo (confirm)
Claude Code Primary execution surface — installed + authenticated Self-install (steps)
MCPs (Notion, Gmail, Drive, Slack, Granola) Connect tools to Claude Self-configure
Granola Meeting transcription Niccolo (confirm)
Fireflies Secondary meeting capture Niccolo (confirm)
Notion Venture builds, knowledge base Niccolo (confirm)
GitHub — scailetech org Code, client DB, ventures August (org owner), via Niccolo
Vercel — scailetech team Front-end deploys August / Simon (confirm)
Supabase — scailetech org Database, auth, storage August / Simon (confirm)
Linear Engineering task context Niccolo (confirm)
Twenty CRM Client + contact database Niccolo (confirm)
Render Back-end hosting (read context only) Engineering, via Niccolo

The "who grants" entries marked (confirm) are best-effort defaults pending the authoritative list from Simon — see the open question below.

Before your first task — not just access

Provisioning is only half of day 0. The onboarding guide's Day 0 checklist also requires you to have, before opening Claude Code:

  • confirmed the core task in your own words with your guide;
  • confirmed the venture name (the brief's name is a codename — don't ship it as-is);
  • confirmed the target market + language, and flagged any language gap;
  • confirmed first-MVP scope and your operating line;
  • an explicit "go build."

Open questions

Question Owner Urgency
Full day-zero access checklist — every tool + who grants it (confirm the (confirm) rows) Simon Medium

Owner: Current FA Last reviewed: 2026-06-14