Which side of the work are you on? It sets what your screens are called,
and which ones you get.
Oumi
Tell us about your organisation
Oumi reads your client calls against what your company actually sells, so this shapes every scope-creep call it makes.
What do you sell?auto_awesomeImproves AI
Upsell opportunities matches every client requirement against this list, so Oumi can tell you what to pitch and what you have never pitched. You can change it any time in Profile.
How do you plan to use Oumi?
Oumi reads every call and writes everything it finds. That work runs on Claude, either on your own key or on ours. You can change this later in Profile.
Oumi
Session
Record a call
File it under
Co-pilot tone
record_voice_overBoth sides are heard and read on this Mac. Tell everyone on the call first.
One client each. Every call, document and decision with them held in one place, measured against what they agreed to buy.
Q&A sessions
Several projects at once. Put their documents side by side and ask what they add up to: what customers keep asking for, where they disagree, what only one of them wants.
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.
Scope Board
One board per SOW. Once a board is locked, that is the line every later call is measured against.
Co-ordinator
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 briefs
Workflows taken into delivery, one brief each. Everything here is editable: type, stop typing, it is saved.
Overview
Discovery Sessions
Requirement map
Every call, what it asked for, and the workflow that carries it. Hover anything to read it, click a call to trace only that one.
Requirements
What the client needs built, gathered from every call so far
Confirmed or already in scope
New requirement alerts
check_circle
0
00
Pain stories
What hurts in the client's world today, in their own words, straight from the calls
Upsell 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
New message
close
To
Need a separate discussion
Already covered, no action needed
calendar_month
group
Where this came up
Full transcript
Found in your Drive
search
Sync status
Next call homework
AI cost to run this project
How everyone showed up
How much research is this project?
Bought once for this project, never monthly. Pick the size that looks about right: every size is the same price a Unit, adding more later costs the same again, and nothing expires. Build briefs are separate.
Card on file
shieldCard details are typed straight into Stripe, not into Oumi: this build keeps only the brand, the last four digits and the expiry, which is what you need to recognise your own card.
Add research
Oumi or document
Meeting name (optional)
Call date (optional)
Oumi reads the document once and pulls out the meeting title, date, and attendees, scope alerts (New / Assumed / Already covered), and the client asks for the Requirements tab.
Reading the document…
This usually takes under a minute.
search
Enter openEsc closePut "quotes" round a phrase
Oumi: reply detected
This reply relates to
New project
Project name
What are you tracking here?
Where the documents come from
search
Loading…
No research to hand?Start with a real client conversation and see the whole thing work.
Oumi reads the documents in the background: the baseline, the team and the client details come from them. You can add research any time from the project itself.
Profile & settings
U
Full name
Email
Industry
Country
Team size
Branding
What your team sees at the top of every screen, and the colour the whole app is drawn in.
Organisation name
Shown in the top bar and on the sign-in screen in place of "Oumi".
Brand colour
#0b57d0
Applies across Oumi: buttons, tabs, links, chips, charts, and the sign-in screen.
What do you call the person in front of you?
Client, customer, patient, resident, member,
whatever it is where you work. One word, singular. Oumi uses it wherever it names the other
side of the work, starting with who is who on a call. It changes the wording only, never
what anything does.
And what do you call yourself?
Agency, clinic, practice, team, studio. The
other end of the arrow: the Co-ordinator says who owes what to whom, and both ends need a
name. Leave it empty to keep saying "our team".
Products & Servicesauto_awesomeImproves AI
Services we offer
Products & pricing
Knowledge baseauto_awesomeImproves AI
What Oumi should know about your company: what you sell and for how much, how you work, who is on the team, the words you use. The co-pilots and the client overview read it, so "we" in an answer means you. Nobody you share a project with can see it.
A folder brings in up to 25 of its newest documents. Anything read from Drive can be read again from here when it changes.
Google Drive
Nothing is suggested from a document Oumi cannot name a client in, and no file is looked at twice: turning a card down is final. Nothing is read until you press Create, and then the call costs Discovery Units like any other.
Fill in Products & Services if you have not. A call about your own product names that product on every page, and without knowing which names are yours Oumi can mistake one of them for the client.
Look through everything
The sweep above takes a page of files every ten minutes. This reads the lot in one go and puts up a card for every client you have no project for. Reading a name costs about a penny, and no file is ever read twice.
AI engine
Checking what Oumi is running on…
Anthropic API key
Optional. With no key, Oumi reads every call through the Claude Code CLI on this machine, using the account signed in there. A key removes that dependency and runs faster. The key is stored on this machine and never leaves it except to call Anthropic.
Model
Model for setup and baseline
Calls, requirements, commitments and the co-pilot run on the first model. Project setup and baseline reading are structurally simpler, so they can run on a faster one.
Change password
Plans & card
A project is bought once, by how much research goes into it, and never billed monthly. Build briefs are separate, under Build briefs.
Build briefs
Pay as you go, nothing to subscribe to. A brief is charged by the effort it describes, and the charge is raised the moment it is written so what is owed is never a surprise. Settle them one at a time or together.
Hourly rate
Every hours figure in Oumi turns into money with this: scope alerts, the build spec, and confirmed scope. A rate set on a project overrides it.
Cost by project (AI usage, API-equivalent)
Move to Execution
notifications_active
New requirement alert
graphic_eq
Import this call?
People on this project
Artifact
Who is who on this account?auto_awesomeImproves AI
Delete project
What this session reads
New Q&A session
upload_file
Or bring in documents that are in no projectA survey export, release notes, a competitor's release, a pile of support tickets. Drop them here or use one of these.
Name it after the question you are trying to answer. You add the documents it reads once it is open: calls from any project, files, Drive, or pasted text.
Change type
Nothing already read is read again. Requirements found so far are kept either way.
Rename project
Connect Google Drive
Oumi will read the call transcripts and documents you pick, so you never have to paste them in.
folder_open
See the documents you chooseRead-only. Oumi never edits, moves or deletes anything in your Drive.
mail
Send the approval emails you writeOnly when you press send, from your own address.
Get client approval
To
Subject
Message
Import from Google
Watch a Drive folder
Which AI should run your projects?
Oumi reads every call and writes everything it finds. That work runs on Claude,
either on your own key or on ours. You can change this later in Profile.