Your positioning, docs and calls go into the Knowledge Base and stay current. Every LinkedIn post idea and draft builds on them, and every quote shows you where it came from.
Positioning 2026Pricing decisionProduct pagesRelease notesWeekly customer syncVoice note from LeaWebinar recordingPost history
More than 1,200 companies run LinkedIn on Scripe, from solo founders to teams of 20 and more.
Picked by you. Kept current. Cited where it's used.
How the Knowledge Base in Scripe works, in three steps.
01
Pick what matters
Choose the exact sources, like files in Google Drive, pages in Notion, a repository in GitHub and calls from Granola, and connect them.
02
It stays current
When a file changes, the Knowledge Base changes with it, so nobody re-uploads anything.
03
Every draft draws on it
When Scripe suggests an idea or writes a draft, it builds on your material. Every passage it quotes links to the source.
Evidence
Outlier · Lea Brandt, 6.4× her average
Knowledge base · the 14 Sep call, Granola
Positioning · marketing leads, 11-50-person B2B
Puts your expertise into every draft.
The opinion stays yours. Scripe learns from every post you publish.
Company documentsWorkspace
Positioning 2026
Product handbook
Pricing decision
Lea Brandt
Onboarding call
Priya Desai
Customer interview
Set a base. Everyone posts from it.
Positioning, product handbooks or pricing decisions live in the workspace, and every profile draws on them. A profile's own files stay with that profile.
Knowledge base
Positioning 2026Synced
Pricing decisionSynced
Release notesSynced
Cited, not summarised
When a draft uses your material, it quotes the passage and links the file. Whoever signs off can check every quote against its source.
Scripeonline
Today
Eva, what was the pushback when we decided to publish prices?9:14
0:429:16
Added to your idea board.9:16
Gets it out of your experts' heads
Scripe sends one question over WhatsApp. The spoken answer lands on the idea, no login needed.
“I tell the AI what I did this week. It always has time. And in doing that, I also remind myself of what I actually have to talk about.”
Dominik Galler · Director IT Excellence, esentri
Teaching earns saves. Launches earn clicks.Against the author's own other posts, posts filed as hands-on guides earn 1.73× the saves per view, launch posts 5.76× the link clicks per view. Both start with material you already have.
Plugs into the tools you already use.
Integrations with Google Drive, Notion, GitHub, Granola, Slack, WhatsApp, Claude, ChatGPT and more.
Pick the documents that matter, such as your positioning deck, messaging doc, or case-study PDF, and Scripe reads each into the Knowledge Base and refreshes it when the file changes. Google Docs, Slides, and PDFs; you choose files, not whole folders.
Choose the Notion pages that hold your positioning and playbooks and Scripe reads them into the Knowledge Base, cited wherever a draft uses them. A changed page updates its document; a removed one removes it.
Connect a repository and pick the paths that matter (docs, changelogs, READMEs), and Scripe keeps them current with the tree. A new release note becomes source material for a post, while code stays code.
Pick the meeting notes that matter, and Scripe reads them into the Knowledge Base, cited wherever a draft uses them. A changed note updates its document.
WhatsApp
Knowledge from experts who never log in. Scripe sends a content question as a WhatsApp message; the person answers by voice or text, with no login and no account, and the answer lands on the idea as material for the draft.
Voice notes and calls become knowledge too, and the workflow around them reaches your team where it already works: review requests and updates come through Slack, so drafts built on your material keep moving.
Read and update the Knowledge Base straight from Claude, ChatGPT, or Grok with one OAuth connection, or from your own code on the public API: add, read, and delete documents, and read and update your positioning, with the same permissions you have in the app.
esentri, an IT and strategy consultancy, could never stay consistent while ten specialists ran at full capacity. Now a short weekly voice note becomes posts that fit each person's positioning, and monthly reach grew from 20,000 to 300,000 impressions.
ColdIQ: 20+ people posting, from documenting the work
ColdIQ, a B2B growth and GTM agency, scaled from one person coaching each teammate to 20 to 30 people posting consistently, by turning what happens inside the company into content instead of inventing ideas from scratch.
“You don't need to reinvent the wheel. Just documenting what happens inside the company already gives you a lot of content ideas.”
Smovement: 25 to 30 social sellers, each from the client's own material
Smovement, a B2B marketing agency, produces content from each client's own material, running 25 to 30 social sellers and cutting content-operations time by 60% with no drop in quality.
“We started testing it on my profile. Then Torben's. After 4-6 weeks of testing, we onboarded our first client. Today, 25–30 of our social sellers are using Scripe with us.”
Every personal profile you plan for is a seat, with its own settings, knowledge and post history. Add seats as more people start posting. Approval workflows start in the Advanced plan, roles and permissions in the Business plan. A marketer prepares, each person reviews and publishes their own post, and nobody shares a login.
Every paid plan has a Knowledge Base with all connectors. The workspace-wide Knowledge Base starts in the Advanced plan.
Connect your sources. Every draft builds on your own material, and every quote is one click from its source.
Frequently asked questions
It is the store of your company's own material (documents, calls, code, and answers from your experts) that Scripe reads and draws on when it suggests ideas and writes drafts, so your content is grounded in what your company actually knows rather than a generic take.
The opinion comes from you. Everything before and after it runs on the system. Scripe learns from the posts you publish, and your knowledge and topics are there from day one.
Google Drive files (Docs, Slides, PDFs), Notion pages, GitHub paths (docs, changelogs, READMEs), and Granola meeting notes, plus answers your experts send back over WhatsApp, voice notes, and calls. You choose the files and paths; code stays code.
Both. Company documents live at the workspace level and every profile draws on them, while a profile's own files stay private to that profile, and each profile keeps its own settings.
A chat can hold your docs, but it can't see which topic is working right now, for you or for your field. Scripe keeps your material in sync and quotes the passage wherever a draft uses it. Every profile in your workspace draws on the same knowledge, and ChatGPT and Claude connect to Scripe too, so you keep both.
Yes. Each source stays in sync with the original: a changed file updates its document and a removed one removes it, so your knowledge never goes stale.
Content is stored in Frankfurt with a DPA included. Scripe connects to LinkedIn through its official interface, without shared logins or a forced extension, and never has access to your session.
Yes. Through the MCP server and the public API you can add, read, and delete documents and read and update your positioning, from Claude, ChatGPT, or your own code.
Lea Brandt
Priya Desai
EsentriRead the full story
ColdIQ
Smovement
