Meetings
The meeting ends with its record already written
Names are recognised as they are said, decisions and tasks go to the right pages, and each person sees only the part they are entitled to.
How it works
From the meeting room to the client's page, with nobody typing
Capture, name recognition, the record, publication. Every step can be seen in the product.
Live capture, or a recorded file
Audio is transcribed every half minute and every participant in the workspace watches progress live. Upload a file recorded elsewhere; it is split at the silences and reaches the same transcript.
Persian, with the names right
Each meeting's glossary is built from the meeting itself — participants, organisation, engagement. “Kavir Steel” is transcribed as Kavir Steel, not something like it.
Names recognised the moment they are said
As each transcript page arrives, the meeting knows which of your contacts, organisations, opportunities, engagements or services it named — with no model call, and with the reader's own access.
When it's ambiguous, Pulse asks
A card in that part of the meeting: this one, someone else, or skip? Anyone with access to the meeting answers, and answering costs no credits.
The record reads like a document
The same cards used across the product. A decision says who decided and who was part of it; a deadline the meeting spoke — “Saturday”, “end of Shahrivar” — becomes a real date with the words kept beside it.
Records leave the meeting
For every decision, task and blocker Pulse suggests destinations — an organisation, an engagement, an opportunity or a contact, often several. On the organiser's approval the record lands on those pages and shows in the team's work stream. Anywhere the organiser may read is a possible destination.
Each person, their own record
Everyone sees the same proceedings, and each person's records are built only from what they may see. A personal reading is asked for by the reader, who sees its price before flipping the switch.
Pulse's trail, and its cost
Above everything Pulse adds to the record, one line says how it got there: pages read, names recognised, what the model was asked and what it cost in credits. A credit is exactly one cent.
Confidentiality
To everyone else, this meeting does not exist
Our rule is not “access denied”; it is “not found”. To anyone outside its list a restricted meeting appears in no list, in no search result, and the assistant does not know it exists.
Access is a disclosure ledger: every grant is recorded with who gave it, and leaving the meeting does not take the history back. Someone spoken about but not in the room is recorded as mentioned and gains no access.
- Outsiders get “not found”; even confirming the meeting exists is a leak
- Search and the assistant see only what the asker sees
- Platform staff cannot see restricted content either
- A workspace admin can always read; hiding from the admin is not a feature
What did we agree on Alborz's working capital adjustment?
The normalised working capital peg was set at 364.9 B T, based on the twelve-month average and excluding the related-party receivable of 41.2 B T.
it asked first — and the yes stays a person's
An honest transcript
The record says what it did not hear
When part of a recording is unreadable, or the model returns text the audio does not support, that part does not become minutes: a gap is recorded instead, and the set-aside text is kept for the organiser to read and restore if they choose.
The record says how much of the recording it was built from and which pages were never heard. A long meeting is read in windows so its later hours reach the record too; and when a phone locks and a piece is lost, the progress bar marks the point in red and carries on.
- A decision is only a decision if it was made or confirmed in the meeting
- The executive summary ends with one sentence per open commitment: who, what, by when
- A figure the platform cannot count, such as a vote share, is never written
- ## Statement of financial position
- | Account | 1403 | 1402 |
- | Cash and equivalents | 84,120 | 61,540 |
- | Trade receivables | 402,880 | 366,210 |
every figure can point back to its page
Page 12 validated by Sara
Sending it
Once the file leaves it does not come back, and the product says so
The same record goes out as a designed PDF or as Markdown, from the same builder that renders the page. On a phone, through the device's own share sheet: the executive summary becomes the message and the PDF its attachment.
Before that happens, one line says what is about to: the file leaves PulseUp, whoever receives it reads the whole record, it cannot be recalled, and the export itself is logged.
- Every served file writes one row: workspace, meeting, user, format, time
- An organiser's correction is frozen against later machine passes; the machine does not rewrite a person
- The PDF is Persian throughout, and nothing internal to the system appears on the page
Contract draft review
- The price-adjustment clause reverts to the July formula, with the cap reviewed annually.
- The technical annex arrives from the client next week.
- On the payment schedule, the proposal is…
56 of 120 minutes
nobody in the room is taking notes
Filing and reopening
A meeting knows which engagement it belongs to, and is never finished
A meeting attaches to one or more engagements and organisations, when it is created or later, and announces itself on each one's feed. Attaching grants nobody access; filing is data, not disclosure.
Anything the record should reflect — a participant added later, a recording that resumed — returns the meeting to in progress until the next summary. The meeting's settings say what each part cost in credits: transcription, the shared record, personal readings, questions.
- One meeting, several engagements; the badge keeps the set
- Resume a finished meeting; the next summary re-reads everything said
- Cost is credits and never a price; a credit is a cent
Honestly
What it does not have yet, or ships switched off
Being built, or off by your choice — not a sales promise. Each one leaves this list when it lands.
- Speaker detection is built but ships OFF: roughly an hour of processing per hour of audio, so each workspace flips its own switch — and a voice's name is always given by a person, never by the machine
- Notifications and a meeting calendar
- Revoking meeting access; the disclosure ledger only ever grows
About meetings
How long is the audio kept?
90 days by default, configurable per workspace; the organiser can delete it at once. The transcript is separate and stays.Can a guest without an account be a participant?
Yes. “Participant” means who was in the room and comes from the contacts directory, not the user list. What needs an account is watching progress live and reading the transcript in the platform.Who can grant access to someone else?
Anyone already on the meeting's access list, and the workspace admin. Access is always granted to one named person; nobody, not even the admin, can open a meeting to the whole workspace.What about a long meeting?
Every meeting has a duration ceiling and the meter beside the recording shows it live. A long meeting is read in windows, so its later hours reach the record too.What does it cost?
Credits, and a credit is exactly one cent — the cost the model provider reports, with no per-line rounding up. The meeting's settings show what each part cost, and a personal reading shows its price before you flip the switch.Does it work self-hosted?
Yes. Transcription goes through the model gateway you configured; on an on-premises deployment it can stay inside your own network with nothing leaving.
Record your next meeting
One real meeting is enough: record it and see where its decisions land on the client's page.