Scripta takes what a meeting produced and files it as things that behave correctly — a record that stays findable, and work that has an owner. Here is what the product actually consists of.
Notes are a record; work moves. Scripta keeps them as separate objects because they behave differently.
The transcript you bring in, record from your own browser (every plan, behind a consent step — no bot of Scripta’s ever joins a call), or type as notes — plus the summary generated from it. Each one keeps its source, date and processing state.
What was agreed, the reasoning behind it, the date, and the excerpt it came from — findable without remembering which meeting produced it. The Follow-Through Matrix then tracks each one to an outcome: delivered, moving, drifting, stale, or nothing linked yet, with a rate counted from real due dates and completions.
Work with an owner, a due date and a status. The assignee can be someone without an account, recorded by email.
Attachments and threaded discussion attached to the meeting that produced them, so a follow-up question keeps its context. The text of a PDF, Word, PowerPoint or text upload is read on arrival, so search finds a document by what it says — and a document can be checked against the meetings that came after it, to see what has since changed.
The place decisions and their work are filed across the meetings that touched them. A project carries a name, a summary, optional owner, date, priority and milestones, and a health chip worked out from its own rows — at risk, stale, nothing linked yet, on track. No status dropdown and no progress bar: nothing here is graded by hand.
Your team, with the profile fields they chose to fill in, and every other person who was in a meeting — an address each. Companies are derived from those addresses’ domains: the people, the meetings, the decisions recorded and the work still owed. Nothing is entered; it is read out of the meetings you already have.
What needs a person: decisions drifting or stale, recordings that failed, projects at risk, and proposals from extraction or the Scripta AI Agent waiting to be accepted or dismissed. Every item is worked out fresh from the record on each load, so it leaves on its own once the thing is fixed.
Scripta doesn’t join your calls. Record from your own browser, upload the audio, or work on the text: copy the transcript out of whatever captured it, upload the file, or paste your own notes, and log which of these it came from. A meeting can also be created from the .ics file your calendar exports for an event — it reads the file; no calendar account is connected.
None of these is a connected integration — there is no account to link and nothing is fetched on your behalf. Pushing action items back out to Slack, Notion, Linear or Jira isn’t built either; when either one is, it will be listed here rather than promised.
Permissions aren’t a UI convention. A request for a workspace you aren’t a member of returns nothing, rather than returning data the interface then hides.
| Role | Can do |
|---|---|
| Viewer | Reads everything in the workspace. |
| Commenter | Reads, and can post comments — but can't change the record. |
| Editor | Creates and edits meetings, decisions, action items and files. |
| Admin | Everything an editor can do, plus managing who's in the workspace. |
External guests get the same four roles, scoped per workspace — a client sees their workspace and nothing else. Somebody with no account can be sent one write-up instead: an unlisted link rather than a public page, protected by a passcode, revocable whenever you like, and kept out of search engines.
Paste a transcript you already have and look at what comes back.