AI Chief of Staff | Contextual decision support

Ask for clarity without handing over the final call.

Your AI Chief of Staff explains why a move surfaced, brings the relevant evidence and draft into view and helps you approve, edit, hold, or skip it inside Relay▶Deck.

Illustrative workflow. The AI Chief of Staff does not turn a recommendation into a delivered message, booking, payment, or verified result.

Best move now Illustrative sample

Review Lift

Ask why this review opportunity comes first.

An eligible customer completed a service today and has not received a review request.

Prepared next move
Prepare the same neutral review invitation used for every eligible completed service.
Owner approval
View evidence and controls
Source
Illustrative completed visit and owner-configured review link
Why now
The completion record is recent, and the eligibility rule does not depend on customer sentiment.
Audience
One recently served customer
Channel
Owner-reviewed review request
Decision window
Review while the completed service is recent
Release rule
Owner approval is required before customer contact.
Current state: prepared

Nothing sends from this preview. Delivery and outcomes remain unknown until evidence exists.

How the workflow earns trust

She supports every stage without becoming the whole product.

Use the AI Chief of Staff when you need context, an explanation, a safer draft, or a routed next step. The Morning Brief remains the operating backbone.
  1. 01 Find

    Surface one source-backed business signal.

  2. 02 Frame

    Prepare the safest move and explain why now.

  3. 03 Approve

    The owner edits, holds, skips, or releases the prepared action.

  4. 04 Follow through

    Track provider acceptance and delivery without calling them outcomes.

  5. 05 Prove

    Attach the real reply, booking, review, payment, or verified non-result.

  6. 06 Learn

    Propose preference changes for approval instead of silently adding autonomy.

AI Chief of Staff proof rail

Her explanation does not change the proof state.

Prepared, approved, accepted, delivered, answered, booked, paid and verified remain separate even when the AI Chief of Staff helps explain the work.
  1. 01 Signal found Source attached
  2. 02 Action prepared Sample draft ready
  3. 03 Owner review Current state
  4. 04 Owner approved Unknown
  5. 05 Provider accepted Unknown
  6. 06 Delivered Unknown
  7. 07 Customer outcome Unknown
  8. 08 Revenue proof Unknown
Who She Is

Direct. Decisive. Always on your side.

Direct

She leads with the recommended next move and the evidence behind it while naming the uncertainty that still matters.

Decisive

Every response ends with a clear owner decision: approve, edit, hold, skip, or inspect the source.

Source-aware

She keeps the source and assumptions attached to the channel, recipient and current proof state.

Built for Real Work

Built by a veteran founder for owners who need clear priorities, controlled follow-through and proof they can inspect.

Your First Week

A responsible first week starts with one trustworthy loop.

Timing depends on source availability and setup. The goal is not instant automation; it is one configured signal, one owner-reviewed action and one honest outcome trail.

1

Readiness Score + source plan

Complete the self-assessed Score, identify the first revenue workflow and confirm which supported source and permissions it requires.

2

Configure one supported source

Connect and successfully sync the source that can support the chosen workflow. No operational claim appears before usable evidence exists.

3

Establish the first baseline

Your AI Chief of Staff explains the strongest supported signal, why it surfaced and what remains unknown before any draft is treated as actionable.

4

Review the first prepared action

Inspect the source, recipient and channel alongside the exact draft. Approve, edit, hold, or skip; approval is still not proof of delivery or outcome.

5

Capture owner preferences

Your edits, holds and skips clarify tone and risk boundaries. Recommendations can improve without pretending that every decision produced a result.

6

Prioritize the next workflow

Add Slot Rescue, Review Lift, Estimate Recovery or Win-Back only when its source, permission and proof requirements are ready.

7

Review what is actually known

See what was prepared, approved, accepted, delivered, answered, booked, or verified. Unknown states remain unknown.

Context when you need it

Ask why this move comes first.

Speaker: AI Chief of Staff | Morning Brief context

SAMPLE
  • Best move now: review one lapsed-client check-in before the relationship cools further.
  • Why it surfaced: the sample booking history crossed the owner-set lapsed-client window.
  • Your control: inspect the source and exact draft, then approve, edit, hold, or skip.
  • Proof boundary: prepared is not delivered, answered, booked, paid, or verified.
Decision context

She shows what informed the recommendation.

Your AI Chief of Staff can retain explicit edits and workflow preferences, but she keeps observable evidence separate from assumptions and never presents private chain-of-thought as proof.

✓ OWNER PREFERENCES EXPLICIT

Edits, holds and skips can inform later drafts without becoming outcome claims.

Example decision record EXAMPLE
Decision Record

What informed the recommendation

Each step shows the source, constraint, and decision boundary without exposing or inventing private chain-of-thought.

Guided flow
  1. INTAKE Step 1

    Completed-visit signal received.

    Source: illustrative appointment record | Review link: owner-configured.

  2. DEBATE Step 2

    Constraint checked before drafting.

    Recipient eligibility and delivery path still require owner confirmation.

  3. LEARN Step 3

    Recommendation framed for review.

    Decision: prepare one personal request and hold it. No delivery or public review is claimed.

System ready for verdict

Inputs aligned, disagreements preserved, and reusable memory updated.

Ready
Where she helps

Context when useful. Not chat everywhere.

Morning Brief

Explains why one move is first and keeps lower-priority signals from competing with the decision in front of you.

Recommendation Context

Brings the source and assumptions together with timing, recipient and current proof state in one readable explanation.

Draft Shaping

Helps shorten, soften, or clarify a prepared action while preserving the owner-selected voice and boundaries.

Source Checks

Shows whether the required source is configured and whether the current recommendation is illustrative, source-backed, or awaiting a re-test.

Conflict Detection

Surfaces competing constraints such as speed, consent, brand, timing or evidence, so the owner sees the tradeoff before deciding.

Owner Preferences

Uses explicit edits, holds and skips to keep future drafts closer to the owner’s preferred tone and risk tolerance.

Uncertainty

Names what is missing and what would change the recommendation. Unknown delivery or outcome states stay unknown.

Power Mode

Deeper Council, specialist and monitoring detail stays available with technical context when the owner asks for it.

Where the AI Chief of Staff appears

The right amount of context for the moment.

Morning Brief

Default context

One short explanation beside the Best Move Now: why it surfaced, what is prepared and what decision is yours.

See a sample brief

Work Detail

Evidence + control

Open the source and recipient details, then inspect the channel, exact draft, assumptions and proof state before deciding.

Explore Relay▶Deck

Ask Relay

Contextual command

Ask for a clearer explanation, a safer draft, a source check, or the next workflow without turning chat into the whole product.

See how Relay works

Power Mode

Advanced detail

Open deeper Council, specialist and monitoring views alongside integration or technical detail only when needed.

Explore the proof layer

Start with the advisory AI-Readiness Score, then see how a configured source can support one evidence-backed, owner-reviewed next move.

Get your readiness score See a sample brief

Your AI Chief of Staff works with

Client Recovery

See how lapsed clients, open slots and stale estimates can become owner-reviewed work alongside review opportunities.

 Relay▶Deck

Where the next move and evidence stay connected to the owner decision, follow-through state and proof.

 Relay▶Wire

Explore the developer surface for governed integrations and evidence-aware workflows.