Knowledge Assistants
AI Company Memory
Captures decisions, context and lessons from meetings and threads into searchable memory.
Knowledge Assistants
AI Company Knowledge Hub for Google Workspace
Answers from your Drive files, Docs, Gmail and Calendar data, cited and permission-checked, with Google Workspace staying your source of truth.
If your company runs on Google Workspace, the answer to most questions is already in a Drive file, a Doc or a Gmail thread. Finding it is the hard part. This hub connects natively to Google Workspace and answers in plain language with a link to the source file, inside the scopes your admin approves. Google stays your source of truth, and nothing is copied out of your control.
- Answers link straight back to the Drive file or Doc
- Admin-approved scopes decide exactly what the hub can read
- Gmail and Calendar context within reach when you allow it
$11,900
20–30 working days
Optional maintenance $595/mo
What it is
AI Company Knowledge Hub for Google Workspace is a cited Q&A assistant connected natively to Google Workspace, reading and updating Drive files, Docs, Gmail and Calendar data within the scopes your admin approves. Staff ask in plain language and every answer links back to its file. Google sharing rules are respected.
Why businesses buy it
Shared drives grow faster than anyone can organize them, so people message colleagues instead of searching, and the same questions get answered again and again. Each interruption costs focus, and outdated copies spread. This hub turns your Google Workspace into something you can ask, with every answer pointing to the file behind it, so staff find the current version themselves. The Scope Card sets the Google scopes, the one extra system, the document volume and testing before you order, so your admin approves a known, limited connection.
Problems this solves
Company knowledge is spread across Drive, Docs, Gmail and Calendar
The hub connects natively to Google Workspace. It answers from Drive files, Docs, Gmail and Calendar data within the scopes your admin approves. Every answer links back to its file.
Keeping shared documents up to date is easy to forget
Within approved scopes, the hub can update Workspace data as well as read it. The field mapping is agreed and documented, so updates land in the right place.
An assistant could ignore the sharing settings you rely on
Google sharing rules are respected, and up to three permission groups add another layer of control. Access uses keys you control, and testing runs on sandbox or test records.
A good fit if
Your company's knowledge lives mostly in Google Drive and Docs, and people message colleagues instead of searching shared drives.
Decisions and answers also sit in Gmail threads and Calendar invites, and you want those within reach, inside scopes an admin controls.
A Google Workspace admin can grant OAuth consent and give a 30-minute setup call to agree the mapping.
Beside Google Workspace you need at most one more system connected, such as a CRM or a wiki.
Not the right fit if
Your files live in SharePoint, OneDrive and Teams rather than Google Drive. See AI Company Knowledge Hub for Microsoft 365.
Your knowledge is split across three different tools with no main platform. See AI Company Knowledge Hub, which connects up to 3 content sources of any kind.
Your team works in Notion pages and databases rather than Google Docs. See AI Company Knowledge Hub for Notion.
You only want a search bar that ranks results across your tools. See AI Internal Search.
How it works
- An admin grants Google Workspace OAuth consent, and on a 30-minute setup call we agree which shared drives, mailboxes and calendars fall within approved scopes.
- The field mapping is written down: which Drive files, Docs, Gmail and Calendar data the hub reads, what it may update, and which permission group each maps to.
- Up to 2,000 documents from Google Workspace, plus up to 1 more system such as a CRM, are indexed for cited retrieval.
- Staff ask in a web app, Slack or Microsoft Teams, and each answer cites the Doc, Drive file or email thread it came from.
- Up to 3 permission groups, configured for your Google Workspace setup, decide whose questions may draw on which files.
- We test on live sandbox or test records with 60 benchmark questions, and a monthly refresh re-indexes new and edited Google Workspace content.
What you provide within 72 hours
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
- OAuth consent for Google Workspace, granted by one of your admins.
- A Google Workspace admin for a 30-minute setup call to confirm scopes and the field mapping.
- The shared drives, mailboxes and calendars to include, and any that must stay out.
- Your user list and the permission group each person belongs to.
- 30 sample questions with the answers you expect, drawn from real Drive, Docs and Gmail content.
- Access to the one additional system, if you are connecting one, and one decision-maker for approvals.
- An API key for your own AI model account (for example OpenAI or Google Gemini), created for this build with a spending limit.
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.
Timeline
Start
OAuth consent granted, setup call held, scopes and field mapping agreed.
Weeks 1–2
Drive files, Docs, Gmail and Calendar data in scope indexed and mapped to groups.
Week 3
Second system connected, citations and the chosen interface wired up.
Weeks 3–4
60 benchmark questions run on sandbox or test records, accuracy report shared.
Week 4
Your review and two rounds of changes.
Go-live
Live, recorded handoff, documented field mapping delivered, 30 days of support.
| Option | Delivery time | Price |
|---|---|---|
| Standard | 20–30 working days | $11,900 |
| Express | 15–25 working days | $13,100 |
| Rush | 10–20 working days | $14,300 |
What you receive at handover
- The AI company knowledge hub for Google Workspace, live in a web app, Slack or Microsoft Teams
- A two-way Google Workspace connection with documented field mapping, plus up to one more system
- Cited Q&A over up to two thousand documents, with three permission groups and a monthly refresh
- A test report on sandbox or test records, with sixty benchmark questions and an accuracy report
- An admin guide and the recorded 60-minute handoff session
- 30 days of post-launch support
Expected benefits and how to measure them
- Can bring company knowledge in Google Workspace into one place to ask
- Helps admins keep control through scopes and sharing rules
- Makes it easier to keep shared records current
- Time to find company information
- Time a set of real questions answered by searching Workspace before launch. Repeat the same set with the hub.
- Weekly hub questions
- Track question volume by team from the hub's usage records.
- Benchmark accuracy
- Re-run the sixty benchmark questions after a few months and compare with the launch report.
Before you start: List the Workspace areas in scope and time a set of real questions. Note how often staff ask colleagues for information instead.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
You pay for the build once. Running the hub costs roughly $50 to $300 a month in your own accounts for AI model usage, the vector database and hosting. Your Google Workspace subscription is separate and unchanged; licenses and plan upgrades are not part of this build.
AI usage during build and testing is billed to your accounts too.
Ask about running costsCustom requirements
If you need Google Workspace objects beyond the agreed mapping, a second additional system, or more than 2,000 documents, add a note at checkout. A written Change Quote arrives, and that work starts only after you accept it. Larger or bespoke projects go through the Custom AI request form.
Request a custom versionKeep it running
Monthly maintenance covers monitoring, fixes, model and platform updates, a monthly health report and monthly hours for changes, such as adding a shared drive to scope or adjusting the field mapping. It starts after the 30 days of support.
$595/mo (5% of the build price a month, includes 5 change hours)
Optional. Starts after the post-launch support period. Cancel any month.
How maintenance worksHow this compares
| Do it yourself with a SaaS tool | Hire a custom agency | Upmark Labs | |
|---|---|---|---|
| Price | A workspace search add-on bills per user, every month | An integrator quotes the Google Workspace connection separately | Ours is one fixed price, shown before you buy |
| Access control | Relies on sharing settings staying tidy | Depends on the design agreed | Ours applies approved OAuth scopes plus up to 3 permission groups |
| Documentation | Settings live in an admin console | Documentation varies by project | Ours hands over a documented field mapping |
| Delivery | Installs quickly, tuning is on you | Usually several weeks | Ours has a fixed delivery time shown before you buy, with faster options |
Questions about this product
Which Google Workspace data can the knowledge hub read?
Drive files, Docs, Gmail and Calendar data, limited to the scopes your admin approves through OAuth consent. On the setup call you choose which shared drives, mailboxes and calendars are in scope, and the field mapping records it. Anything outside those scopes is never read, and custom objects beyond the agreed mapping are excluded.
Will the hub change anything inside our Google Workspace?
Only within the agreed field mapping. The connection is two-way, but every update is limited to the scopes and fields documented at intake, and you approve that mapping before anything is built. Its main job is answering questions, with a citation to the Doc, Drive file or email thread behind each answer.
What admin access does the Google Workspace edition need?
OAuth consent granted by a Google Workspace admin, plus that admin's time for a 30-minute setup call to confirm scopes and the field mapping. Consent and any keys are handled through the intake process, never shared by email. Without admin consent the connection cannot start, so arrange it within the 72-hour intake window.
Can we connect a CRM or wiki alongside Google Workspace?
Yes, one more system is included on the Scope Card, for example a CRM or a wiki your team also uses. Its content is indexed beside your Google Workspace data and cited the same way. A third system comes through the Knowledge Base Expansion add-on, or a Change Quote.
Can staff ask from Microsoft Teams while our files stay in Google?
Yes. The interface is chosen separately from the content source: a web app, Slack or Microsoft Teams, for up to 50 users. Your Google Workspace files stay where they are and answers cite them, wherever the question is asked. Pick the interface your team already has open all day.
When can staff start asking the Google Workspace hub questions?
Delivery runs on a fixed schedule from a verified intake, and the delivery panel shows the date plus express and rush options, each priced, before you order. The clock starts after OAuth consent, the setup call and your sample questions are complete, so book your Google Workspace admin's time early.
What does it cost to run on top of Google Workspace?
Roughly $50 to $300 a month in your own accounts for AI model usage, the vector database and hosting. Google Workspace licenses are billed by Google as they are now and are not part of this build. Monthly maintenance is optional.
Ask Google Workspace a question and get the file back.
Order AI Company Knowledge Hub for Google Workspace and staff get cited answers from Drive, Docs, Gmail and Calendar within approved scopes, on a fixed delivery date.
Works well with
Knowledge Assistants
AI Internal Search
Searches across your internal tools from one place with AI-ranked results.
