← Selected work

AI operations / Interactive example

A useful summary knows what’s missing.

A handoff should tell the next person what they need to know, what still needs checking, and who owns the next step.

This is an illustrative walkthrough with fictional records and preset outputs. It does not call an AI model, connect to a CRM, or save your selections.

Source notes

Example Co. Deal: onboarding package. Sales owner: Alex. Onboarding owner: Sam. Signed scope: standard onboarding. Customer confirmed a kickoff on October 8. Next step: Sam sends the kickoff agenda.

Ready for human review

Draft handoff

Example Co. has signed for standard onboarding. Sam owns onboarding and should send the agenda for the customer-confirmed October 8 kickoff.

Checks before taking action

  • Verify the signed scope matches the CRM record.
  • Sam reviews the summary and confirms the next step.

Suggested next step: create a task after the owner approves. Nothing is sent automatically.

How I would turn this into a real workflow

  1. 01 / Define the sourceChoose the records and notes the workflow is allowed to use.
  2. 02 / Draft & checkReturn a structured summary and explicit missing fields.
  3. 03 / Review & actRoute the draft to a person before changing a record or sending a message.

Before deployment, test incomplete records, conflicting notes, permissions, and failed model requests. Compare the output with a human-written handoff and track corrections as well as time saved.

Why start here?

It is a bounded task with a visible output and a clear owner. You can decide whether the result is useful before giving the workflow more responsibility.

Read my note on the foundations AI agents need ↗

Working through something similar?

Tell me about the process, the tools, and the part that keeps getting in the way.

Talk Through Your Setup