Intellodocs is an AI-native document vault. It captures files wherever they land, reads the content rather than the filename, and answers questions about your archive in plain language — pointing at the exact sentence each answer came from.
Example — WhatsApp capture
The chase starts where it always does — the client group.
Three movements, in order. A document is taken in wherever it appeared, read for what it actually is, and handed back with the source line attached when somebody asks. Nobody is trained, and nobody downloads, renames or re-files anything.
Documents are absorbed where they already land — a WhatsApp group, a forwarded email, a scan from the office printer.
Not the filename. Kind of record, parties, dates and amounts are extracted, indexed, and routed to the right client and matter.
A question in plain language returns an answer bound to its source passage — not a list of ten PDFs to open one by one.
A document enters the vault from wherever it already appeared. A client drops it into a WhatsApp thread. A vendor emails it as an attachment. Reception scans a stack of paper. Someone drags a folder straight into the DMS. Intellodocs listens on all four, pulls the file in with its origin, sender and timestamp intact — and nobody forwards, renames or re-uploads anything.
No portal to teach a client, no login for them to remember. They keep sending documents exactly the way they do today, and your team keeps working in the DMS.
Skewed, blurry, badly lit phone photographs go through OCR tuned for exactly that. Where a field genuinely cannot be read it is flagged for review rather than guessed.
Which channel it arrived on, who sent it and when are recorded against the document itself — so months later you can still show exactly where it came from.
Low bandwidth, entry-level Android, patchy connectivity. Capture still works, because the heavy lifting happens on our side rather than theirs.
Every arrival is classified and indexed within seconds, then routed to the right client and matter.
Tags typed by the user: none
The vault restates what it understood — the topic and the period — before it answers. Intent is visible and correctable, so search never becomes a guessing game.
The answer opens the source document and highlights the exact line. No invented facts, no confident guesses — a professional can verify in one glance and put their name on it.
Asked — what are the termination terms in the vendor contract?
Either party may terminate on 90 days' written notice. Termination for material breach takes effect after a 30-day cure period.
Master Service Agreement · clause 11.2 · page 711.1 This Agreement shall commence on the Effective Date and continue for an initial term of twenty-four (24) months. 11.2 Either party may terminate this Agreement for convenience upon ninety (90) days' prior written notice to the other party. 11.3 In the event of a material breach, the non-breaching party may terminate following a cure period of thirty (30) days.
Chartered accountants, lawyers and company secretaries get document types and extracted fields tuned to their work — that is where Phase 1 goes deepest. It is not a limit: the same vault handles whatever your documents turn out to be.
Tax filings, audits, GST compliance and client financials
Contracts, court filings, client mandates and legal matters
Board records, statutory registers and regulatory filings
If you receive documents from people you do not control, and you are accountable for producing them again later, the vault does the same job — it just learns your record types instead.
Phase 1 does four things properly — capture, classification, retrieval and control — rather than a dozen things adequately.
Attach a firm WhatsApp number, a mailbox or the office scanner, and every document sent to it is captured, named, classified and filed — without anyone forwarding, downloading or uploading anything. This is where your client documents already arrive.
ITRs, consent letters, NDAs, court orders, expense sheets and balance sheets are recognised on arrival — no manual tagging.
Names, dates, amounts, obligations and identifiers are pulled into structured fields you can filter and sort the whole archive by.
A question in plain language — “which client agreements expire this quarter?” — returns an answer with the source passage attached.
Send a document back out over WhatsApp, email or a time-limited link — and keep a record of exactly what went where.
Clients send documents from wherever they are. Your team works in a full workspace — numbered engagements, the folder structure a practice already uses, and permissions down to the individual file.
Every client and matter gets its own numbered workspace, marked internal, external or under audit — so nothing is ever filed against the wrong entity.
Automatic filing is worthless without governance underneath it. These are the foundation the capture layer sits on, not roadmap items.
An exclusive lock while a document is in use, so two people can never quietly overwrite each other. Every checkout records who holds it and since when, and an administrator can force a release.
Every revision retained with its author and timestamp. Roll any document back to an earlier version in one click — history is never rewritten, only added to.
Compare any two versions side by side and see exactly what changed — which clause moved, which figure was edited — without opening both files and reading them line by line.
Every open, download, edit, share and deletion written to a tamper-proof record — who, what, when, from where. Exportable the day an auditor, regulator or opposing counsel asks.
Inherit from the folder or override on a single document. View, update or delete, per person or group. External parties see only what you scope them to.
Retention rules per client or record type, with legal hold. Share externally by time-limited, password-protected link — revoke at any moment, and see when it was opened.
Confidentiality, retention and chain of custody were architecture decisions, made before the first screen was designed — and the whole thing runs on channels and infrastructure we already operate.
Managed cloud in the region you choose, a single-tenant dedicated instance with its own database and encryption keys, or a full on-premise install inside your own data centre — behind your firewall, air-gapped if required. Same codebase, three deployment models, so data residency is a decision you make rather than one we make for you.
TLS in transit and AES-256 at rest as standard. On dedicated and on-premise deployments the keys are held by you, not by us.
Our staff cannot browse your vault. Support access is time-boxed, requires your explicit approval, and is written into your own audit log where you can see it.
SAML and OIDC, with SCIM provisioning and role mapping from the directory you already run. People join and leave through your existing process.
Export original files, folder structure, extracted metadata and the complete access log in open formats. No exit fee, no lock-in period, no held hostage data.
We're a new product asking you to trust us with privileged client files. The least we can do is be exact about where we are.
Early access includes white-glove setup — we migrate your existing folders and configure your client and matter structure with you.
Phase 1 firms shape what gets built next, and keep their early-access pricing when it ships.
Yes. On-premise deployment installs inside your data centre or private cloud, behind your firewall, and can be air-gapped. You hold the encryption keys, control the backups and decide when to upgrade. The AI components can run against a model endpoint you nominate, including one inside your own network.
The vault only answers from your own documents, and every answer is bound to the passage it came from — you see the source line before you rely on it. When there isn't a document that supports an answer, it tells you that rather than filling the gap.
We migrate them during setup. Point us at your existing folder structure, shared drive or server and we ingest it, classify what's there, and map it onto your client and matter structure before you go live. You review the mapping before anything is committed.
It runs on the Meta WhatsApp Business API against a separate firm number, not anyone's personal account. Documents sent to that number are captured; ordinary conversation is not stored. Clients keep messaging exactly the way they already do.
No. A connected mailbox is watched for attachments only, and you choose the scope — a shared firm address, specific labels or folders, or particular senders. Documents are captured and filed; correspondence is not stored, indexed or used for anything else.
No. Intellodocs proposes the record type, filename and destination, and someone confirms with one tap — you can see that in the capture sequence above. Anything it isn't confident about is flagged for review rather than filed silently.
That's the normal case, not the edge case. Skewed, blurry and badly lit scans go through OCR tuned for exactly this input. Where a field genuinely can't be read, it's flagged rather than guessed.
Phase 1 pricing is set per firm based on size and volume, and is locked in for early-access firms when we move to general pricing. We'll quote you on the setup call, before you commit to anything.
You export everything — original files, folder structure, extracted metadata and the full audit log — in a standard format. No exit fee and no lock-in period during Phase 1.
Knowledge workers lose close to 1.8 hours a day hunting for information that was already sent to them. Documents stop disappearing, answers come with proof, and nobody has to be a librarian. We're onboarding a limited first cohort with white-glove setup, migration of your existing archive, and pricing locked in for good.
