A first brief, already drafted
After the first useful capture, Knowvaulty drafts a project brief from its takeaways. Read it in the app or download the Markdown.
Private beta
Decisions happen in Slack threads, emails and meetings. Knowvaulty captures the ones you choose, proposes updates to the documents they change, and answers anyone in the company with the quote behind every claim.
Already have access? Sign in
Captures from
Timeline
Onboarding opens to the first five customers once the help center is live.
Proposed update
The pilot starts on October 14 October 21, after accessibility testing.
#launch-planning · Daniel · Thu 14:02
“Let’s move the pilot to October 21 so testing can finish first.”
Launch review follows two weeks after the pilot.
Why it matters
Nobody is careless. Writing it down is a separate job that comes after the moment has passed, and three things follow.
A stale brief doesn’t announce itself. It keeps being read, and the team builds against it.
Retention policies and busy channels bury the only record of why a call was made.
Whoever joins mid-project inherits a confident document and no thread back to the discussion behind it.
How it works
Knowvaulty works from the places your team already talks, and every step leaves a trail back to the source.
01Capture
Nothing is recorded by default. Someone on the project sends a conversation in.
02Understand
Each capture is read for what it settles. Every takeaway keeps the quote it came from, and snapshots show how a topic changed.
03ProposeComing soon
When a decision changes a document, Knowvaulty proposes the edit block by block, with the conversation behind it. Nothing changes until you accept.
04Ask
Ask about a decision, a requirement or an open question. Open any citation to read the original words.
Always cited
Every takeaway keeps the words it came from, and every answer cites them. Open a citation and the original line is waiting in the thread, email or meeting it came from.
Point at the citation to see the line it rests on.
#launch-planningThu 14:02
The pilot moves to October 21, after accessibility testing.
Why did the pilot move?
To let accessibility testing finish before the client sees it. 1
1 · Slack · #launch-planning · Daniel, 14:02
One vault for the whole company
Every team’s decisions in one vault, so the context behind a project outlives the people and channels it started in.
Access is granted project by project. Nothing from a project you can’t see ever reaches an answer you get.
Knowvaulty doesn’t listen to every channel or join every call. A conversation is captured only when someone sends it.
The notetaker introduces itself in the meeting chat as it joins, so everyone knows it’s there.
For whoever joins next
New to the project or back from leave, start from what the team already settled.
After the first useful capture, Knowvaulty drafts a project brief from its takeaways. Read it in the app or download the Markdown.
Write project documents in Markdown. Every save keeps a version you can open again.
Questions
Something else? Write to support@knowvaulty.com.
Knowvaulty is in private beta, and we’re onboarding a few teams at a time. Email support@knowvaulty.com and tell us a little about your team. If you already have access, sign in with your work Google account.
A company-wide knowledge vault. It captures the Slack threads, emails and meetings your team chooses, organizes what they settle by project and topic, and keeps every answer traceable to the original words.
Mention the bot in a connected Slack workspace, forward an email to your personal project address, or send a meeting bot to Google Meet, Zoom or Microsoft Teams. You can also upload an existing transcript in VTT, SRT, TXT or DOCX format. Capturing information requires project edit access.
Not on its own. When a captured decision affects a document, Knowvaulty proposes the edit along with the conversation behind it, and nothing changes until someone on the project accepts it. Proposed edits are coming soon; today, your team writes and edits project documents, with every version kept.
Yes. Answers cite project context and source evidence. Open a cited topic snapshot, inspect its takeaways and follow the supporting quotes to the captured conversation, email or meeting.
Projects are shared with specific organization members as viewers or editors. Organization owners and admins can access every project in their organization. Joining an organization alone does not give an ordinary member access to its projects.
Yes. Create projects within an organization and switch between them from the sidebar. Project creation is available when your organization permissions allow it.
Private beta
We’re opening Knowvaulty to a few teams at a time. Tell us about yours, and we’ll be in touch.
Already have access? Sign in