Skip to main content

​
Tutorial: Meeting notes intelligence

Outcome: messy meeting input becomes searchable structured notes with action items and a people directory. Domain swap: use the same brief for field notes, interviews, or any capture → structure → act loop. Change the nouns; keep the roles and rules.

​
Step 1 | Prompt in Build mode

Stay in Build mode and send:
Build a meeting notes app. Roles: member and optional admin. Members upload an audio recording or paste rough notes. When needed, the app transcribes, then produces structured notes: headline, summary, action items, agreements, and key quotes. Meetings are listed and searchable. Each meeting has a detail view with checkable action items. Maintain a participants directory and link people to meetings. Members create and edit their own meetings. Admins can see everything. Long transcription or summary work must not hang the chat; the user should be able to check progress afterward. Action items must be real trackable items (not only prose inside a summary blob). No public unauthenticated API.

​
Step 2 | Review the plan by journeys

Approve when these journeys look right:
  1. Capture: member uploads or pastes → processing starts without freezing chat → structured meeting appears.
  2. Act: member opens a meeting, checks off action items, and finds linked people.
  3. Admin (if used): sees across members without giving every member that power.
Adjust the brief if a journey is missing, then approve. Glance at App Blueprint only as a map of the result, not as a shopping list you were supposed to request.

​
Step 3 | Preview, Access, and Executions

Select a project so Preview uses real project data.
  1. App Blueprint → Access: members should not delete other people’s meetings unless you intend that.
  2. Preview as member: upload or paste a short sample, wait for structured notes, check an action item.
  3. If you used audio/transcription, confirm progress under project Executions.
  4. Optional: ask Build for a notification when an action item is created with someone’s name, then re-Preview.

​
Step 4 | Soft launch

Invite a small team under End-Users with the right roles. Confirm they land in the portal, not Build mode. Then follow Launch checklist.

​
How to verify (checklist)

  • Preview as member: upload or paste a short sample; structured notes appear
  • Action items are editable and scoped as you intended in Access
  • Long audio/transcription (if used) shows progress under Executions
  • Soft-launch invites land in the portal, not Build mode