1 comments

  • Squissy 5 hours ago ago

    Hi Hn,

    I am Kevin, I built this tool after noticing a pattern across enigneering teams and client projects.

    When somone ist leaving a company, knowledge isn't lost because of documentation is missing.. I'ts lost in the last working days, when there is not time to capture the context behind decisions, workaround and project history.

    I know that companies have offboarding and documentation. But neither helps when you have 5 days left and need to extract what is inside someone's head.

    So I built a tool for that. I don't say it's solving the problem 100%, but it's a nice help for the successor.

    Based on the profession and position it generates role-specific questions, guides the leaving employee through the context, risks, decisions and dependencies to turn the answers into a structured handover report for wohever takes over later.

    What it does:

    - Asks guided and role-specific questions (no setup, just a link)

    - Works asynchronously, no meetings

    - Produces a structured handover report from answers

    Why this was interesting to build (in 6 months...) I originally thourht this was a documetnation problem, but while building it, I realized it's actually a timing problem.

    This moment simply ins't covered by any existing tool. What makes hard to sell it to be honest...

    Tech side: - Web app, no accounts required fot the employee, just set you password

    - Dynamic question flows with LLM - LLM-assisted structuring of the answers into report - TypeScript/Node/Postgres backend

    What suprised me People don't recognize this as a seperate problem. They assume "we have onboarding" or "we have docs".

    But both fail in this specific time window.

    Would love to hear your thoughts, criticism, or experiences.