First week on the team
A new designer learns the process by asking.
Instead of searching shared folders, Jonas asks Squaria how a brand workshop runs at Northfold. The answer comes from the delivery playbook the team added to the knowledge base.
Knowledge base
Checking availabilityComing soonAnswers that follow the way your team works.
Add your PDFs, Word documents and text files, plus a short “how we work” note. Squaria searches them when it answers, so replies come from your knowledge.
Your know-how, where Squaria can find it
Most teams keep their methods in documents few people open: a delivery playbook, a pricing guide, an onboarding checklist. Add them to the knowledge base and Squaria searches them when it answers, alongside your records. A short note tells it how your team works.
Add the documents your team already relies on
Upload PDF, DOCX and text files: playbooks, pricing guides, onboarding notes, past proposals. Squario splits each one into passages and indexes it, so Squaria can find the right paragraph when a question needs it.
PDF, DOCX and plain text
Upload documents in the format they already exist in, without converting them first.
Split into passages, indexed
Each document is split into passages and indexed, so answers draw on the part that matters.
Meaning and exact words
Search combines meaning and keywords, so a reworded question still finds the right passage.
Sized to your plan
Knowledge sources and storage are counted per workspace, with more room on larger plans.
Answers in your words, by your rules
Write a short “how we work” note once: your tone, your review steps, the terms your team uses. Squaria takes it into account when it answers, and draws on your documents and your records together.
A “how we work” note
One note per workspace with your tone, your steps and the words your team uses.
Answers from your knowledge
Ask how your team handles something and the answer comes from your own documents.
Your playbook on live work
One question can weigh a live project budget against the threshold your playbook sets.
The same permissions as before
Squaria still runs as you: the knowledge base adds context, not access to more records.
When the answer is in a document
The questions that used to wait for the one colleague who knew, answered from what your team already wrote down.
Before a scope goes outPricing questions, answered the house way.
Léa asks which extras the studio usually prices separately on a website project. Squaria answers from the pricing guide, in the tone the “how we work” note describes.
Between two site visitsThe handover checklist, from a phone.
On the way to Oudry Architects, Max dictates a question about the handover checklist. Squaria answers from the checklist in the knowledge base, step by step.
An assistant that knows your playbook.
In a 30-minute demo, bring one document your team relies on and see Squaria answer from it. Or start free and add your first sources today.
Questions about the knowledge base
Which files can I add?
PDF, DOCX and plain text files. Each one is split into passages and indexed so Squaria can search it. The number of sources and the storage depend on your plan.
Does Squaria read everything in our Drive?
No. Squaria sees file names in Drive but never reads their contents. It only searches the documents you add to the knowledge base.
Does indexing use AI credits?
Yes. Indexing a document uses AI credits, depending on its size. After that, each message to Squaria uses 1 credit as usual.
How is the text of our documents processed?
Your workspace is hosted in Europe, in Switzerland. To make documents searchable, their text is sent from Squario’s servers to OpenAI for processing. Squaria still only works with data your role is allowed to see.