Track every client call promise until it is actually done

Build me an app that answers one question for my client services team: did we actually do what we said we would on the call. I run an agency, so everything groups by client account, not by deal stage and not by meeting.

The main surface is a commitment ledger grouped by client account. Each row is a single commitment someone made on a Grain call, showing the verbatim quote pulled straight from the transcript, who owes it, the date it was promised, the due date, and the live status of the linked Asana task. Within an account, anything overdue pins to the top of the list with a day counter such as "14 days late", and the accounts themselves sort so the ones with broken promises appear first. Each account header shows counts for open, overdue, and delivered.

Give each account a "Pull commitments" button that kicks off a background agent. The agent uses Grain List Recordings to find recent calls for that account, Get Recording for the details of each candidate call, and Get Transcript to read what was actually said. It extracts commitments with the exact quote, the speaker who made it, and the promised date, resolving relative language like "by end of next week" against the call date. It writes them back into the app as freshly extracted rows marked pending review. Show progress while the agent runs, and dedupe against commitments already in the ledger by recording id plus quote so repeat pulls never create doubles.

Only client-facing calls should count. Detect them by an external participant domain: each account stores one or more client email domains, and a call qualifies when at least one participant sits outside our own company domain. Grain only returns participant and AI summary enrichment on the Business and Enterprise plans, so degrade gracefully. If participants come back empty, fall back to matching speaker names and the account name inside the transcript, and show in the UI which detection method was used for that pull so I know how much to trust it.

Separate firm commitments from soft ones. A firm commitment has a clear action, an owner, and a date or a phrase that can be resolved to a date. Soft statements like "we will take a look" or "let me circle back on that" belong in a separate maybe column so they never mix into the dated ledger. Let me promote a maybe into a firm commitment by adding an owner and a due date.

Every approved commitment links to an Asana task. From a row, an Approve action calls Asana Create a Task in that account's Asana project, using the commitment as the task name, the verbatim quote plus the call title, call date and Grain link in the notes, the owner as assignee, and the promised date as the due date. Store the returned task id on the commitment row so the two stay linked.

The board shows live status by reading Asana. The default read path is Get Multiple Tasks scoped by project, because Asana's workspace search requires a premium plan. Use Search Tasks in a Workspace only as an optional fallback when a commitment's task is not in a known project, and when Asana responds that the plan does not allow search, surface a small note rather than breaking the board. Refresh status when the ledger loads and from an explicit refresh button.

From a row I can also change the owner or the due date, which calls Asana Update a Task and updates the row in place, and nudge the owner, which uses Slack Bot Look Up User by Email to find them, Open a Conversation to open a direct message, and Send a Message containing the verbatim quote, the client account, the due date, and a link to the Asana task. Record when the last nudge was sent so the row can show "nudged 2 days ago" and I do not badger the same person twice in one day.

Persist client accounts (display name, client email domains, Asana project id, Asana workspace id), commitments (account, source recording id, call title, call date, verbatim quote, speaker, owner, promised date, firm or maybe classification, review state, Asana task id, last nudge time), and the last pull time per account. Include a settings page where I add and edit accounts, set our own company domain, and map each account to its Asana project.

Keep the ledger and the overdue sorting front and center. The extraction is plumbing; the value is opening one screen and seeing, per client, exactly what we promised and what we have not delivered.