Engine
Knowledge Engine
A private chat that answers your team's “how do we do X” questions from your own SOPs, docs and past work — so new hires stop interrupting senior staff.
Replaces
Price band
scoped in the Control Centre
Typical timeline
Stack tier
A private chat that answers your team's "how do we do X" questions from your own SOPs, docs and past work — so new hires stop interrupting senior staff.
The work it retires
The senior-staff-as-Slack-help-desk pattern: where the same six questions get asked weekly because the docs exist but no one can find them, or the docs are stale, or the answer is buried in last year's project folder.
Inputs
- Your internal knowledge: Notion, Confluence, Google Drive, SharePoint, a folder of PDFs, a wiki, past project handovers, SOPs.
- The questions your team actually asks (we'll pull these from your support inbox or run a workshop).
- Who's allowed to see what (access control is mandatory, not optional).
Outputs
- A private chat interface for your team (Slack-native, Teams-native, or a simple web app).
- Cited answers — every reply links back to the source doc, so trust is verifiable.
- A weekly "knowledge gap" report: questions asked that the docs couldn't answer.
Typical integrations
Notion, Confluence, Google Drive, SharePoint, Dropbox, Slab, Guru, Slack, Microsoft Teams, Linear (for engineering knowledge), GitHub (for code/runbook context).
What's included
- Ingestion of up to 2 doc sources.
- RAG pipeline with citations.
- Chat interface (Slack/Teams/web).
- Access controls aligned to your existing source-of-truth permissions.
- Weekly knowledge gap report.
- Setup notes, ingestion run-book, handover.
What's not included
- Doc cleanup or rewriting (we'll tell you what's broken; fixing it is your team's call or a separate engagement).
- Public-facing chatbots (this is internal-only by default — public deployment is a separate scope with different risk).
- Real-time sync to source docs (re-ingestion is scheduled, not live, unless explicitly scoped).
- Replacement of your existing wiki or doc tool.
Human review
The Knowledge Engine cites every answer. Users can verify against the source. For any answer that would lead to a customer-facing action, a financial action or a policy decision, the system surfaces a "verify before acting" prompt and requires the user to click through to the source.
Price detail
- Basic (from A$650 AUD): one doc source, web chat, no integrations.
- Standard (from A$1,800 AUD): two doc sources, Slack/Teams integration, citations, weekly gap report.
- Premium (from A$4,500 AUD): multi-source, access controls, custom chat UI, full reporting.
Price band: from A$650 → A$4,500 (AUD), scoped in the Control Centre.
Typical timeline
2–4 weeks depending on doc volume and access control complexity.
Related Engines
Support Engine
Customer ServiceRead every ticket, draft the reply, queue it for your one-click send.
Ops Engine
OperationsRun the recurring admin a chief-of-staff would otherwise do.
Insight Engine
ReportingA dashboard and a weekly written summary that prepares your Monday meeting for you.
Suggested for
Verticals where this Engine carries most of the weight in the recommended stack.
For small marketing & creative agencies
Built for“Half my senior team's week is status reports, approvals and “where's that file?””
For recruiters & staffing
Built for“Actual recruiting is 20% of my week. The rest is admin.”
For coaches, consultants & course creators
Built for“Enquiry to onboarded is all me, all manual.”
Get started
Configure this in the Control Centre.
Two to four minutes. A draft scope and a starting price band — no call required.