Linked, not filed away
Pages link straight to features, capabilities, processes and custom developments. Conversely every capability and feature carries its own wiki page — business context exactly where the data is.
Knowledge base & specs
Functional specs built on real data
Documentation goes stale because it lives beside the system. In Conjola it lives inside it: your functional specs, system documentation and decision papers sit right next to processes, features and custom developments — and link into them. An AI assistant that knows the same data helps you write.
The knowledge base
A wiki that doesn't sit next to your SAP analysis but inside it — linked to the same objects.
Versioned and traceable
Every state is a version with inline diff and restore — including every change the AI makes. Nothing disappears quietly.
Structured work
Page tree, per-page sharing, full-text search, comments, data tables and templates — system templates for recurring document types, your own templates per tenant.
The assistant writes along
Not a prose chat beside the document — a writing aid that works inside it.
It writes into the page
Where the assistant is confident, it applies the change directly — and highlights the affected passage in the editor. No working through a list of suggestions.
Uncertain things stay untouched
What it cannot support it does not apply; it flags it separately instead. Better an open question than an invented statement.
Every change individually revertible
The panel lists what it changed — each entry with “undo”. On top of that, every state is restorable from the version history.
Anchored in your data
For content it draws on the same basis as the system chat: feature map, SAP dictionary, your Z-object source code and the detected processes. Chapters come from your system, not from general knowledge.
The assistant extends and revises text at specific places — it does not write whole chapters at the push of a button. The professional judgment stays with you; the groundwork is on it.
What you write with it
The document types that cost weeks of groundwork today.
Functional specs
As-is description, affected processes, affected custom developments — with links to the very objects you are writing about.
System documentation
What a feature means in your house, which special logic hangs off it, which company codes use it — captured on the object itself.
Decision papers
Cloud-fit assessments, decommissioning candidates, migration recommendations — argued with the numbers sitting right next to them.
Revise & review
Have selected text shortened, rephrased or translated; in review mode let it read the whole page for gaps and contradictions.
Why this makes the difference
The work after the analysis is the work nobody plans for.
Insight becomes document
The analysis isn't the deliverable — the deliverable is the spec somebody writes from it. That step happens on the same platform, with the same data.
Documentation that keeps up
Every new extract carries the technical layer forward. Your business text stays anchored to it instead of quietly going stale.
Ready to understand your SAP landscape?
In a short demo we'll show you how Conjola turns your document data into a basis for decisions.
Book a demo