Knowledge Hub Overview

Product details, competitive guidance, and support policies change faster than the training built on them. In this 46-second demo, we open a Knowledge Hub stocked with Notion-synced pages, ask Exec for good discovery questions, click the citation back to the page the answer came from, and pull that same page into a roleplay scenario.

A hub holds pages your team writes and sources you connect. Files come in by upload, and documents import from Notion and Google Drive. The workspace in the demo carries hubs for cold call training, new seller onboarding, and call scoring, each holding the pages and files that work depends on. One page can sit in the onboarding hub and the competitive hub at the same time, so nobody keeps two copies in step.

We ask what good discovery questions look like, and Ask Exec answers out of our own pages, ending with a citation to the Discovery Question Bank page it drew from. Clicking the citation opens that page, so anyone can read the source instead of taking the answer on faith. Answers respect permissions, and each person hears only from material they're allowed to see. Somebody who joined last week gets the current answer without knowing which document held it and without interrupting whoever wrote it.

A connected source stays connected. When the Notion page or Drive file changes, the hub reads the new version instead of holding a copy from the day somebody imported it. Sources resync every 15 minutes on their own, and a resync button pulls a change in immediately. Nobody asks a knowledge base that's out of date, so the syncing is what keeps the questions coming.

Any page or source can feed a roleplay. In Scenario Studio, we pick hub content as the scenario's context, so the character your reps practice against raises the objections your material describes and knows your pricing, rather than playing a generic buyer. Courses draw on the same content, so training starts from pages you already maintain instead of a blank prompt.

Does this replace our existing knowledge tool? Not immediately. Exec connects to Notion and Google Drive and reads from them, so a hub can sit on top of what you already maintain. Teams consolidate later, once the hub is where people go to ask.

Who can see what? Every page and source carries its own visibility, either just you, everyone in your workspace, or every workspace in your organization. New content starts private to whoever created it, and workspace admins can always see and edit what's in their own workspace.

Can the agent write pages for us? It drafts pages from source material you point it at, and it writes only into the draft. A person reviews and publishes, and the version history records which edits came from the agent.

Does Ask Exec search the whole internet? No. It answers from your hubs, your connected sources, and Exec's own documentation, and it cites where each answer came from.

Do we need the rest of Exec for this to be useful? No. A team with no knowledge tool in place gets the full value of hubs, sources, and Ask Exec on its own. Generating roleplays and courses from the same pages is what it grows into.