A tool we built for ourselves.

Transcript hears everyone at the same time. It can ask one person about something others described, without ever naming them, keeps the contradictions, and asks the question nobody has asked yet.

• Talks with everyone, in private.

  Everyone at once, each conversation as long as the person wants. Not a survey with fixed questions.

• Keeps asking.

  Follow-ups until the real process is on the table: the phone call, the spreadsheet, the workaround nobody wrote down.

• Checks back with each person.

  Nothing counts until the person who said it has approved it.

Thousands of things people said, each checked back with the person who said it, become one living picture of the company. What it hands back is a list: every problem the company described, ranked by what it costs today.

• Every problem, priced in hours.

  What each one costs in the time your people spend on it, so the largest return comes first.

• Every process, as it really runs.

  How the work actually gets done, not how the process document says it does.

• How your teams use AI today.

  Where it has taken hold, where it has not, and where to point it next.

• Who everything depends on.

  The handoffs that run through one person, the report only one person can produce.

Nobody can read one person's conversation. Not a manager, not the management team, not us. That is built into how the product stores data, not promised in a policy.

• Managers see the model, never a conversation.

  How much of the company has been heard and what it knows as a whole. Never a quote, and never a summary of one person.

• Your data never trains AI models.

  Conversations stay in your organisation's own space. Transcript records nothing outside the chat.

• Built for the GDPR and the EU AI Act.

  It describes how the organisation works, not how an individual performs, so it cannot be used to assess people.

⁰¹Who can see what I say?

Nobody. Your manager and the management team never see what you say. The product stores conversations so that no one can open them; that is built in, not a policy. Managers see how much of the company has been heard and what the company as a whole knows, never a conversation, a quote or a summary of one person.

⁰²Does Transcript capture tribal knowledge before someone leaves?

Yes. That is most of what the model is made of: the way work actually gets done, which lives with the people doing it and rarely reaches a system. Transcript hears everyone, so the knowledge of the quiet expert everyone asks is in the model before they hand in their notice.

⁰³How is this different from process mining or an employee survey?

Process mining reads system logs, so it sees the steps that touched a system and misses the phone call, the spreadsheet and the workaround. A survey asks everyone the same questions once. Transcript has an ongoing conversation with each person about their own work, asks again where accounts disagree, and keeps the contradictions, because that is where the cost sits.

⁰⁴Can it tell me who my single points of failure are?

Yes. The model shows who everything depends on: the handoffs that run through one person, the report only one person can produce, the approval that waits for someone who is rarely in. You see the dependency, never the conversation.

⁰⁵Is Transcript a hiring or assessment tool?

No. Transcript talks with the people already in the company about how the work runs. No manager can read what any one person said, so it cannot be used to assess individuals.

⁰⁶Does it connect to our systems?

It starts with your people, because that is where the real process lives, then your systems come in on top. Calendars first, so the model also sees how people work together, and more as the model grows.

⁰⁷Is my data used to train AI models?

No. Conversations are processed to extract learnings and stay within your organisation's own review. Your data never trains models, and Transcript records nothing outside the chat.

⁰⁸What does our team have to do?

A short note from the top saying this matters and that answers will not be used against anyone, and one named person who owns the rollout with us. Everyone is asked by default, on their own schedule, and managers can see participation across their own teams in real time.

⁰⁹Does every engagement start with Transcript?

No. Most start with a problem and a prototype in week one. We bring Transcript in when the problem depends on how the work really runs and nobody has written that down, and we tell you why before we suggest it.

¹⁰How long do you keep the conversations, and can we delete them?

Conversations stay in your organisation's own space while we work together. You can delete them, or ask us to, at any time; the picture and the exports you keep are yours. Transcript describes how the organisation works, not how an individual performs, and is built for the GDPR and the EU AI Act.