Level 2: every rule, name and step kept and explained. Examples from code, deployments and incidents.
Notion · Confluence · GitHub · the web
Your documents, told as lectures for every role
Connect where your company keeps its knowledge, choose the documents, say who reads. Each topic becomes a course of narrated, illustrated lectures: one for developers, one for sales, one for new colleagues. When a document changes, the course follows.
Make your team’s page
Sign in, name the organisation, connect a source. The first topic is ready to make in about ten minutes; the lectures take an hour.
Open the consoleFourteen days to try, with the first short topic on us. A subscription afterwards, and the lectures at the price any reader pays.
- Connect the sourcesNotion with an integration token, Confluence with an API token, GitHub with a personal access token, any public page by address. Several at once.
- Choose the documentsBrowse spaces, databases and folders; add a page, a folder or a whole space. Each document is read into chapters at once.
- Say who readsDevelopers, product managers, sales, support, leadership, new colleagues: each gets the depth, the examples and the stress that fit. Add your own.
- Name the topicsSecurity, onboarding, how we deploy, the pricing: a set of documents from any sources, told as one course. Or let the model propose them.
One topic, several readers
The same documents, a different lecture for each profession
A reader profile is a level of depth, the listener’s world for the examples, and what to stress or skip. The security policy for developers keeps every command and exception; for sales it keeps what can be promised to a customer.
Level 3: what each thing does for users and why; implementation in a sentence, not skipped.
Level 4: what the customer gets, what can be promised and what cannot, the wording to use on a call.
Level 3: every internal name explained the first time, who to ask and where things are.
Your page
A page of your own, by category and by role
Members sign in and pick who they are; the page shows every topic for them: Onboarding, Security, Engineering, Product, Sales, Support and more. Each course plays in the browser with the voice and the drawings, or downloads as audio.
- Open to members only, or to anyone with the link.
- Every lecture is checked against the documents by a second model before anyone hears it.
- A document changed at its source shows on the page as soon as the watch finds it; the course can be made again by itself.
Kept current
When a document changes, the course knows
Every hour, day or week the documents’ version marks are compared with their sources: Notion’s last edit, Confluence’s version number, a file’s hash in GitHub, a page’s ETag. What changed is read again; the topics it belongs to are marked, and made again when you say so.
Without the console
Set it up from Claude, Cursor or your own scripts
The console is also an MCP server: with an API key, an agent connects the sources, picks the documents, names the readers and the topics, starts the lectures and sets the watch, the same way it would set up products at Stripe.
claude mcp add --transport http lecturized https://lecturized.com/api/business/mcp --header "Authorization: Bearer lcz_…"
Every tool mirrors a step of the console: connect_source, browse_source, add_documents, add_profile, suggest_topics, create_topic, make_topics, set_auto_update, get_page.
Pricing
A subscription for the page, the lectures at the usual price
The subscription pays for the page, the connections, the watch and the MCP, and brings a monthly allowance for lectures. Lectures beyond it cost what they cost any reader: about 0,36 USD a page of documents with drawings, read by a studio voice. You see every price before anything is made.
Organisations can pay by invoice; write to us. Prices are provisional while the service is new.
Domande
Questions
Where do our documents go?
The text of each chosen document is fetched with your token and kept as a book of your organisation, visible to its members and nobody else. Tokens are stored for the watch and never shown again; remove a source and its documents go with it.
Do we need OAuth?
Not now: Notion internal integrations, Atlassian API tokens and GitHub personal access tokens are made in a minute and pasted into the console. An OAuth app for each service can be added later over the same connectors.
How is the content kept faithful?
Each lecture is written from the documents of its topic and compared with them, part by part, by a second model; what differs is rewritten. Where the documents disagree, the lecture says so.
How long does a topic take?
Reading the documents takes seconds. The lectures of one topic for one kind of reader take from a few minutes to about an hour, depending on the length; you can watch the progress on the console and the page.
Can a reader choose a different depth?
Each edition is made for one profile. A member picks their profile at the top of the page; a topic without an edition for them shows the one for everyone, when there is one.
What does a change cost?
A document that changed is read again for free. Making the course again costs what a new one costs, which is why remaking is off until you switch it on, and why the page tells you what is behind.