Skip to lesson
Exit
Capstone: Mock Loop1 / 2

2 min lesson

The four-beat pitch

Rebuild the sequence in "The four-beat pitch" from memory, ending with the check that proves the outcome.

Step 1 of 2

The four-beat pitchStructure

  1. 1Problem. Name the toil with a number. “Roughly 30% of tickets are the same five setup issues and each one costs an agent ten minutes of copy-paste triage.”
  2. 2Design. Describe the flow in one breath. “A bot reads the incoming ticket, classifies it against the top issue signatures and either drafts a grounded reply or routes a likely-novel one to a human.”
  3. 3Toolkit. Be concrete. The ticketing API for ingest, a small Python or TS service, an LLM call for classification and drafting, the KB as the grounding source, posted back via the Slack workflow.
  4. 4Impact. Tie it to a metric. “Cuts first-response time on the common 30%, frees agent hours for the hard tickets and the drafts get better as the KB grows.”
Say it like this

Run the four beats together and the whole three minutes sound like one breath: “Roughly 30% of our tickets are the same five setup issues, and each one costs an agent about ten minutes of copy-paste triage. So I'd build a bot that reads the incoming ticket, classifies it against the top issue signatures, and either drafts a grounded reply or routes a likely-novel one to a human. The toolkit is deliberately boring: the ticketing API for ingest, a small Python or TS service, one LLM call for classification and drafting, the KB as the grounding source, and the reply posted back through the Slack workflow. The impact is where I'd land it - first-response time drops on the common 30%, agent hours free up for the hard tickets, and the drafts get better as the KB grows.”

Interview move

Name your failure modes before they ask. “The risk is a confidently wrong auto-draft, so a human edits and sends every reply - the bot drafts, it never fires. And I'd watch the misclassification rate weekly; if novel tickets get auto-labeled as common ones, I'd lower the confidence threshold for routing.” Naming the downside is what separates an engineer's pitch from a demo.