Your team’s experience.
Ready for everyone.
Turn everyday answers, written guides and experienced people’s know-how into help your whole team can use.
From what your team knows
to what to do next.
Capture what matters
Save a common answer, add a guide, or use a few questions to capture someone’s experience.
Review and share
A manager checks the draft and approves what the team should be able to use.
Put it to work
Ask in plain words. Company answers show their sources. General help is clearly labeled.
Keep the useful answers. Refine them as the work changes.
New teammate. Shared know-how.
Alex just joined a tech company. Pick an employee’s question and see how Crux uses the manager’s saved guidance.
What does Alex need help with?
The team’s experience,
ready for Alex’s first question.
Alex Morgan New employee
How do I report a problem with a work tool?
Crux From your team’s knowledge
Use the team’s problem report template:
- What happenedDescribe the problem and what you expected.
- How to repeat itList the steps that led to the problem.
- What helps us checkAdd a screenshot, device, and browser.
Send the report to the IT help channel.
Problem report formatAlex Morgan New employee
I can’t sign in to a work tool. What do I do?
Crux From your team’s knowledge
Try “Forgot password” with your work email.
- Still stuck?Note the tool’s name, the error message, and when it happened.
- Send those details to ITThey can help you get back in.
Never share your password.
Signing in to work toolsAlex Morgan New employee
What goes in my weekly team update?
Crux From your team’s knowledge
Use three short sections:
- DoneWhat you finished.
- NextWhat you plan to do.
- BlockedWhere you need help.
Post it in the Team updates channel by Friday at 3 pm.
Weekly team updatesMaya writes it down once. Alex gets the answer, the next step, and the source.
Illustrative conversations with a fictional team and sample manager entries.
For the questions that usually mean interrupting someone.
Help someone find the team’s way of doing things, get started on a simple task, or understand which decision needs a person.
- Company knowledge
Who approves a rush request?
Crux answers from the team’s approved knowledge and links to the relevant passage.
- General guidance
How can I write a clearer team update?
Crux can suggest a structure: what changed, what happens next, and who owns it. Clearly labeled as general help, not your company’s policy.
- Needs confirmation
Can I buy a $500 work tool?
If the company’s rules don’t cover it, Crux asks for confirmation. It should not invent your spending limits or permissions.
Choose open-source models, or use your own API account for Claude or OpenAI. Paid usage is billed directly by your provider.
When something changes.
Flag it
Anyone who spots a wrong or out-of-date answer can flag it.
Someone owns it
A manager reviews the flag and can give the fix an owner and a due date.
Save the better answer
A manager can turn a correction into a reusable answer with “Save as team guidance.”
Review and approve
Once approved, the new guidance is available for future answers. The original answer and correction stay visible.
Missing company knowledge can become an assigned task. Answer it once, review it, and make it useful to the next person who asks.
The people behind Crux.
Building a simpler way for teams to share what they know.
Olaf Wrzesinski
Founder & CEO
LinkedIn: Olaf Wrzesinski
Sandor Alberti
Before you begin.
Do we need recordings or existing documents?
No. Start with a question and a short answer, or capture a teammate’s experience in a guided interview. Crux also supports PDFs, Word documents, meeting transcripts, and imports from Google Drive and Slack. We’ll help connect your sources and keep expanding support around your team’s needs.
How does a guided interview work?
Choose a topic, then capture what someone would do, why, what changes the approach, common mistakes and when to ask for help. A manager can fill in the answers or copy the questions for a teammate to answer in their own time. You can save a partial draft. Interviews do not require a live call; scheduling and invitations are not built in.
Does every question need a company document?
With a working AI connection, Crux can offer general help with routine writing, explanations and planning when approved knowledge does not cover the question. It labels that help as general guidance. Company-specific rules, spending limits and approvals still need company evidence or confirmation. The hosted demo uses offline answers and does not demonstrate open-ended AI guidance.
Who can see the knowledge and questions?
A 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?
Anyone 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 the evidence easier to check; they do not guarantee an answer is correct.
How should we handle sensitive material?
Only add information your company is allowed 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.
Start with the question
that keeps coming back.
Bring a question people keep asking, someone who knows the answer, and the teammates who need it.
Start with one team and a useful slice of its knowledge: onboarding, daily decisions, or a task that always needs an experienced person. Capture what matters, agree on the questions to test, and see whether people get useful answers with fewer interruptions.