What your team knows.
Ready for whoever’s next.
Turn everyday documents and conversations into clear answers your whole team can use.
From what your team knows
to what to do next.
- 1
Share what you know
Add guides, meeting notes, or useful tips. A manager checks them before sharing.
- 2
Ask a question
Ask how something is done. Crux looks through your team’s approved knowledge.
- 3
See where it came from
Read the answer and the original source. Flag anything that needs fixing.
When the work changes, a manager updates the guide. Everyone learns from it.
What one person knows
can help the whole team.
Keep useful knowledge moving across role handoffs, written processes, and everyday decisions. The next person can find an answer and see exactly where it came from.
Explore a team’s six-month demoFictional company. Authored example.
Client handoff walkthrough
Meeting transcript · Mira Chen, delivery manager
Before you take time off, make sure the next person has more than a list of links.
Document the next deliverable, deadline, and anything waiting on the client.
Have your backup confirm ownership and the requirements, then get the delivery lead’s approval before the handoff is complete.
Passage cited in the answer
The goal is for the next person to know what happens next, and who is responsible.
How do I hand off a client
before taking time off?
CruxGive your backup a clear picture of the work, then get the handoff confirmed and approved.
- Document the next deliverable, deadline, and client dependencies.
- Have the backup confirm ownership and requirements.
- Get the delivery lead’s approval to complete the handoff.
Covering a teammate
Written instructions · Covering time off
A shared procedure for handing an active project to a new owner or covering planned time off.
Delivery handoff / Ownership and approvalOwnership and approval
Assign a named backup and record the next deliverable, its deadline, and unresolved client dependencies in the handoff notes.
The backup must confirm ownership and requirements. The delivery lead approves the completed handoff before responsibility changes.
Written passage cited in the answer
Keep the handoff notes with the project so the next owner can find the context behind the work.
What needs to be confirmed
before a handoff is complete?
CruxThe work guide calls for a clear handoff record, confirmation from the backup, and delivery lead approval.
- Name the backup and record the next deliverable, deadline, and unresolved client dependencies.
- Have the backup confirm ownership and requirements.
- Get delivery lead approval before responsibility changes.
A clear path from
“someone knows this”
to “here’s how.”
Your team decides what belongs in its knowledge. Crux makes it available in the moment someone needs it.
Captured
Add a work guide, handbook, instructions for covering a teammate, or notes about a decision. Conversation transcripts can join the same knowledge library.
TXT, VTT, SRT, MarkdownApproved
A manager reviews the text, redactions, and audience. Only approved sources become available to the company workspace.
A deliberate step before sharingAnswered
Teammates ask in their own words, read the supporting passages, and flag anything that needs a closer look.
An answer with its evidenceImproved
A missing or outdated answer gets an owner. A manager revises the source, and the next person works from better guidance.
Current knowledge, preserved history
A correction remains beside the original answer. Approve an updated source to improve what Crux can use in future answers.
The people behind Crux.
Building a simpler way for teams to share what they know.
Olaf
Founder & CEO
Alex
CTO
Start with the question
that keeps coming back.
Bring a real onboarding or handoff workflow, its written processes and notes, and the teammates who need to learn it.
A pilot starts with one invited company, a manager who knows the work, and a small set of approved documents, notes, or transcripts. Agree on the questions to test, then look at answer quality, repeat interruptions, and the effort it takes to keep the knowledge useful.
Talk to your company’s pilot organizer to agree on the scope and get an invitation.
Sign in to your workspaceHave an invitation? Follow your personal link to join.Before you begin.
What do we need to connect?
Start with written knowledge or conversation transcripts you can upload or paste. Markdown and TXT work for step-by-step instructions, handbooks, decision notes, and role handoffs; VTT and SRT preserve transcript timestamps. Files are added manually. PDF, DOCX, and connected Drive or Slack imports are not supported.
Who can see the knowledge and questions?
The workspace serves one company and its invited members. Approved sources are available to everyone in that workspace; drafts are visible to managers. Managers can review employee questions and answers, so the chat is not private from your company.
What if an answer is wrong?
Employees can flag an answer. A manager can review it or add a correction beside the original. An updated, approved source makes the correction available to future answers. Citations make evidence easier to check; they do not guarantee an answer is correct.
How should we handle sensitive material?
Only add information your company is authorized to share with everyone in the workspace. Basic automated redaction can miss personal and confidential details, so a manager must review the content. Agree on hosting, retention, and model-provider requirements before using sensitive material.