Knowledge Base & Wiki

The Operations Lead v1.0

Head of operations at a 180-person machine builder in Baden-Württemberg, where onboarding, travel rules and the service hotline's answers live in a shared drive, three OneNote books and two colleagues' heads. Wants one place the whole company actually uses: an editor office staff manage without training, a search that finds the answer rather than the file, pages that name who keeps them current, and a price that does not double when the workshop gets read access.

The IT Administrator v1.0

Runs IT for a public utility with 900 staff whose Confluence Server held twelve years of pages until Atlassian ended its support. Was offered the cloud, read the subprocessor list and went looking instead. Needs a migration that keeps page trees, permissions and attachments, single sign-on against Entra ID with groups synced, an audit log the auditor accepts, and an edition they can run in the utility's own data centre if the works council or the regulator asks.

The Support Knowledge Manager v1.0

Owns the knowledge base of a Dutch SaaS company with customers in six languages and a support team of twenty-five. Writes once for agents and customers, publishes the public part as a help center on the company's own domain, and watches which searches find nothing. Wants review dates that nag the right expert, translations kept in step with the source, a widget inside the product, and articles that show up in the help desk next to the ticket.

The Engineering Lead v1.0

Leads a forty-person engineering team at a Berlin fintech that writes runbooks, architecture decisions and on-call guides. Writes in Markdown, links pages to Jira tickets and Slack threads, and has moved the team's docs twice. Wants fast search, code blocks and diagrams that render, an API and webhooks to generate pages from the pipeline, AI answers that cite their pages, and a full export the next tool can read.

The Quality Manager v1.0

Quality manager at a medical device supplier certified to ISO 9001 and ISO 13485, where every work instruction must be approved, versioned and read by the people it applies to. Today that means Word files, a sign-off sheet and an audit every spring. Wants approval workflows with named reviewers, read confirmations, review dates that expire pages, an audit trail they can export for the certifier, and permissions that keep drafts out of sight.

The Skeptic v1.0

Has migrated a wiki whose "export" turned out to be one PDF per page, watched a self-hosted edition announced as retired with two years' notice, and read "your data is never used for training" above a subprocessor list naming two AI providers. Asks what a full export contains, which model reads the pages and where, whether readers are billed like editors — and what leaving would cost.