Zendavox
Log In/Register

Your next session already knows.

Zendavox keeps the context of a project as you work — what was decided, why, and what has already been tried — so the next session carries on instead of starting over.

The problem

You work on something with Claude, ChatGPT, Perplexity, or whichever AI assistant you use. You explain the project, the constraints, the decisions you already made and the approaches you already ruled out. You get somewhere.

Then the session ends. And the next one knows none of it.

So you explain it again. And again. Decisions get reopened because nothing recorded that they were settled. Work gets redone because nothing recorded that it was done. The longer a project runs, the more of each session is spent catching up rather than getting on.

What Zendavox does

Attach it to a project. As each session runs, Zendavox records the substance — not the transcript, but what matters: the decisions taken and the reasoning behind them, the facts that hold true, what was built or changed, and the documents that came with it.

The next session opens with that in hand.

Each session writes into one shared project context, and the next session reads it Session 1 Session 2 Session 3 Project context decisions · facts activity · documents Session 4 opens already knowing

Decisions, with the reasoning

Not just what was chosen — why, and what was rejected. A settled question stays settled.

Facts that stay true

The things you should never have to say twice: what it is called, where it lives, what it must never do.

What actually happened

What was built, fixed or changed, in order, so progress is visible across weeks rather than within an hour.

What a new session sees

This is the whole idea, and it is worth seeing literally. A fresh session on a project opens with something like this, before you type a word:

Example brief

Sessions so far: 14

Facts
deadline: filing due 14 March · constraint: no customer data leaves our servers · stack: Postgres, no ORM

Decisions already made
Q: Do we build our own billing?
A: No — use an existing provider. Rebuilt twice before and it was never the differentiator.

Recent activity
Migrated the reporting queries · Fixed the duplicate-invoice bug · Added the March filing documents

No re-explaining. No reopening the billing question for the third time.

Documents are part of it

A project is not only conversation. Things arrive — a contract, a records release, a batch of scans — and they belong to the same context as the decisions made around them.

Zendavox reads what arrives, works out what each item is, files it against the matter it belongs to, and makes people, organisations and addresses searchable across everything. Duplicates are caught before they are filed twice. An item referring to a record you do not hold is flagged.

And it counts. When you are owed documents by someone in no hurry to send them, the hard part is not reading what came — it is noticing what never did.

I have 7 of 43 — 36 still missing.

From a live public-records request. Zendavox took the total of 43 from the agency’s own document portal rather than anyone’s say-so. A folder can tell you it holds seven files. Only something that knows what was promised can tell you thirty-six are outstanding.

Start with the project you already have

You do not have to begin the day you install it. Point Zendavox at a project that already exists — sessions already run, files already accumulated, in sub-folders named inconsistently — and it works through the whole thing, filing what it recognises and setting aside what it does not.

Anything it cannot place, it holds and asks about rather than guessing. Answer once, and it remembers the words that set that document apart, so the next one like it is filed without being asked about. Your vocabulary becomes its vocabulary.

Who can see what

In a business, access is decided by document type rather than document by document. Management sets the rule once — procedures readable by all staff, personnel files by HR only — and whoever files an incoming document only answers what it is.

Managing access can be handed to an office manager or records clerk without handing over anything else. It never has to reach the person running the company, and every change is recorded.

Modules

Context is the foundation. On top of it sit modules you add to a basic subscription when you need them, each bringing the records and rules for a particular kind of work.

Work orders

Jobs, assignments and the paperwork around them.

Invoicing & accounting

Billing, invoices, and books that consume them.

Service & repair

Repair tickets, building on work orders.

Business ethics

Rule content for organisations that must demonstrate a standard.

Modules are planned, not yet available. The context layer and document handling are what exist today.

Three ways to use it

PlanWho it suitsWhat changes
Individual One person, working alone No job titles, no permissions, no access screens. Everything you put in is yours.
Small Business A team where not everyone should see everything Four job titles to start — Owner, Records Administrator, Supervisor, Staff — and one named person managing access.
Enterprise Larger organisations As many job titles as you need, and more than one administrator, because at that size a single one is a bottleneck.

How it decides

You tell Zendavox a little about a project when you start it. From there, it learns as you go — what comes up as you write in a session, what gets decided, what gets built. The whole time, it is recording that context, without being asked and without waiting for the session to end.

Files work the same way. When you upload something to a session, Zendavox reads it and works out how it relates to the project. Where it is not confident, it stops and shows you the file and asks what it is. Answer once, and that type of document is recognised from then on — the next one like it is filed without being asked about again.

You can move between sessions as the work demands it — back to one from weeks ago, on to a new one, and back again — and every entry, in any session, updates the same project. So the picture you get back is never just the last conversation; it is everything that has happened so far.

All of it is judged by Zendavox’s own rules, in code. No outside service reads your material, and nothing about it is sent anywhere to be interpreted. Anything touching money, legal exposure or safety is held for a person to review regardless of how confident it is.

Get started

Create an account, or log in.

Log in

Forgot password?

Create account

Use a real email address - sign-up verifies the domain.

Enterprise

Setting up Zendavox for a larger organization? Enterprise accounts are configured by our team, not signed up online. Tell us about your organization and we'll be in touch to get you set up.