Projects
1
Client
2
Baseline
3
Calendar
4
Domains
What's the client called?
This becomes the project name.
Client name
Describe your baseline requirementsauto_awesomeImproves AI
This is what every new requirement gets compared against. Paste your SOW/PRD, or a one-liner works just as well.
Or pull it from Google Drive
+ Pick transcript files from Drive
Which meetings should Oumi watch?
Pick specific recurring meetings: safer than watching everything with this client's domain on it. (Prototype: type the series names; the live Calendar picker ships with Google ingestion.)
+ Add a meeting series
+ Pick meetings from Drive transcripts (imports them as calls)
Which domains should Oumi track?
This powers email reading, and it's the safety net for step 3: anything from these domains outside your watched meetings gets suggested, not silently missed or silently included.
+ Add another domain
auto_awesomeCo-pilot
Co-pilot reads the whole project: baseline, board, calls, and tasks.
rocket_launchDone with discovery?
Once discovery is complete, everything gathered so far becomes the agreed baseline and execution begins: from then on, new asks on calls count as scope change and raise an alert.
Boards
One board per SOW. Once a board is locked, that is the line every later call is measured against.
Tasks
What each call left someone to do. Follow ups, documents and decisions, never project requirements.
Workflows
The project cut into things you could click through in front of the client, in the order worth showing them. Each one becomes a brief and a build prompt.
Build brief
One workflow taken into delivery. Everything here is editable: type, stop typing, it is saved.
Overview
Conversations
Requirements
What the client needs built, gathered from every call so far
Confirmed or already in scope
New requirement alerts
check_circle
0
0
0
Pain stories
What hurts in the client's world today, in their own words, straight from the calls
Opportunities
Openings to add value beyond what was asked, matched against what your organisation sells
Scope tickets
The whole agreed scope as a backlog: epics in build order, each holding the stories that deliver it