Scattered knowledge
Policies live in shared drives, procedures in wikis, and the latest version in someone’s inbox. People spend time hunting instead of working — and aren’t always sure they found the current copy.
In development · Early access open
FolioQuery is being built to let your team ask plain-language questions about approved internal documents — policies, procedures, onboarding guides — and get answers that point back to the exact sources they came from.
Every answer links to its sources, so you can check the original document when accuracy matters.
Product preview
Here’s the kind of interaction FolioQuery is designed for. The content below is a mock-up — not output from a live system.
Sample employee question
How many days of annual leave can I carry over into next year, and who approves it?
Illustrative answer
According to the leave policy, you can carry over up to 5 unused days into the next calendar year [1]. Carry-over requests are approved by your line manager and must be submitted before December 15 [2].
Review the cited sections before acting on this answer.
Sample sources
The problem
Policies live in shared drives, procedures in wikis, and the latest version in someone’s inbox. People spend time hunting instead of working — and aren’t always sure they found the current copy.
HR, operations and support teams answer the same questions again and again. Each one is quick on its own, but together they pull experienced people away from higher-value work.
New hires don’t yet know where things are or who to ask. Ramping up depends on how much time busy colleagues can spare to point them to the right document.
Features
FolioQuery is in active development. Features marked Planned are on the roadmap but not yet built.
Upload approved documents — including scanned files — and FolioQuery prepares their content so it can be searched and cited.
Ask questions the way you’d ask a colleague. No need to guess the right keyword or remember which folder something lives in.
Each answer lists the documents and passages it drew from, so people can open the original and verify it themselves.
Designed so people only get answers drawn from documents they’re authorized to see, based on access rules your organization defines.
Sources show when they were last updated, so it’s obvious when an answer relies on a document that may be out of date.
People can mark whether an answer helped. That signal highlights gaps in your documentation and answers that need attention.
How it works
Your team chooses which documents FolioQuery should use. Only approved content goes in.
Text is extracted — including from scanned pages — and organized so relevant passages can be found quickly.
Employees ask in plain language and receive an answer generated from the matching passages.
Each answer links to its sources. Open them to confirm the details — especially when the decision matters.
Use cases
For growing businesses, operations teams, HR departments, and internal support teams.
Give new hires a place to ask “how do I…?” and “where is…?” without waiting for someone to be free.
Example question“How do I request equipment for my first week?”
Help people find what the handbook actually says about leave, expenses, travel, and working arrangements.
Example question“What’s the daily meal allowance when travelling?”
Surface the right step in a process document when someone needs it, with a link to the full procedure.
Example question“What’s the escalation path for a delayed supplier delivery?”
Help support staff locate internal guidance and product documentation faster while handling tickets.
Example question“What’s our refund process for annual plans?”
Planned architecture
This is our intended design. Details may change as we build and test.
Cognito is planned to handle sign-in: verifying a user’s identity. Deciding what that user can see is a separate job. FolioQuery’s application authorization layer will control access to documents and filter retrieval results, so answers are only drawn from content the user is permitted to view.
Teams evaluating a knowledge tool reasonably want to know where their documents go. We’d rather show the intended design early and take questions than ask for trust without detail. Security and data-handling specifics will be documented as they are finalized.
About
FolioQuery is in development. It is not yet generally available, and we don’t have production customers. We’re building the product and looking for early-access teams willing to share feedback on real use cases.
We have no compliance certifications at this time, and we don’t claim integrations beyond the planned architecture described above. We’ll update this page as that changes.
FAQ
Not yet. FolioQuery is in development. You can request early access and we’ll contact you as we open it to a small number of teams.
No system like this is perfectly accurate. Answers are generated from your documents and can still be incomplete, outdated, or misread. That’s why every answer includes source references — when accuracy matters, review the cited source before acting.
Only documents your team uploads and approves. The plan is to support common text documents and scanned files, with text extracted from scans using Amazon Textract. Supported formats will be confirmed during early access.
Permission-aware retrieval is a planned feature. The design is for FolioQuery’s application authorization to control which documents and retrieval results each user can access. Until that feature ships, you should only upload documents appropriate for everyone who has access.
The planned design stores documents in Amazon S3 within AWS. Specifics such as region, encryption, and retention will be documented before general availability.
Not currently. The initial focus is document upload. If a specific integration matters to you, tell us in the early-access form — it helps us prioritize.
Not at this stage. We won’t claim certifications we don’t hold. We’re happy to discuss our planned approach to security with early-access teams.
Pricing hasn’t been set. We’ll share it with early-access participants before asking anyone to commit.
Early access
We’re looking for teams who field a lot of internal questions and want to try a better way. Early-access participants will get a hands-on look at the product as it develops, and a direct line to the people building it.
Email: [hello@yourdomain.com]
Address: [Business address]