hi! fleet · Claire · handoff

Three decisions only Stacy can make.

Prepared by Claire

Drafted by Claire 2026-08-30, her first run through her own drafts-only gate · reviewed and approved by Elizabeth 2026-08-31 · commits 112cbb6 + f35ddab

Built: the four engines — intake, scheduling, follow-up, back office — fully generic and fleet-safe, with no hi! specifics inside. Deliberately not decided for you: every business-specific binding, and the open calls below. Nothing here commits hi! to anything; it is all blank until you fill it.

Sources: skills/claire/SKILL.md · skills/claire/references/ (four files) · docs/claire-spec.md · docs/fleet-charter.md §0 and open questions. Quoted, not guessed.

Answers here are shared — whatever you pick, the other founder sees, from any device. There is no login on this site, so this is a self-declared name, not authentication.

1 · Three decisions only Stacy can make

Q1 — Does Claire face clients directly, or only you two?

AClient-facing. She drafts and, once approved, sends first responses straight to leads, with a disclosure line on every message.
BFounders-only. She preps every draft for you or Elizabeth to send yourselves — nothing reaches a client with her name on it.

Q2 — Voice-guide-first, or internal-only to start?

AVoice-guide-first. She can't touch a client-facing word until hi-voice's open item closes — the founder-byline question, already waiting on your confirm, separate from this.
BInternal-only. She starts now, drafting admin work for you and Elizabeth. Client-facing waits.

Q3 — Which calendar is authoritative, and does her queue get write access?

AName a calendar, no write access. Scheduling goes live in propose-only mode — she drafts times and invites, a human applies them.
BName a calendar, grant write access. She can also apply approved bookings herself, reviewed as a batch.
CLeave it unnamed. The engine stays inert — she can only summarise what has been asked, nothing more.

2 · One you share with Elizabeth

Who is Claire's named approver of record?

For back office — invoices, contracts — and generally. Needs a name, not a rota. Charter open question #3.

3 · Fill-in slots, by engine

Each answer goes in that engine's own file, in the "hi! binding" section at the bottom. These live in the repo, not on this page.

Intake

skills/claire/references/intake.md

  1. Response template copy
  2. Decline template copy
  3. Asana board wiring — fields, stages, who watches what
  4. First-response SLA number you'll stand behind

Floors, ladder, capacity and Asana-as-system-of-record are already settled by charter §0 — cited there, nothing to fill.

Scheduling

skills/claire/references/scheduling.md

  1. The authoritative calendar — Q3 above
  2. Write access, yes or no — Q3 above
  3. Bookable windows
  4. Buffers
  5. Daily call ceilings

Follow-up

skills/claire/references/follow-up.md

  1. Template copy for each touch
  2. Cadence numbers — touch count and spacing. The engine default is three touches with widening gaps unless you override it
  3. Queue review rhythm — how often you look at the batch

Back office

skills/claire/references/back-office.md

  1. Invoice template
  2. Contract template
  3. Filing structure inside Asana and Drive
  4. Payment rails and terms boilerplate
  5. Named approver of record — §2 above

Intake — per skill

Scheduling — per skill

Follow-up — per skill

Back office — per skill

← Roundup