For organisations
The reason an organisation switches off the assistant in its office suite is rarely that the assistant is bad. It is that nobody can answer the question of where the document went. This suite is built so that question has a short answer: the model runs on hardware you own, at an address you set, and out of the box that address is the machine the document is already on.
That claim has one limit and we print it rather than bury it — the endpoint is a setting you can change, and changing it changes where your documents go. It is one destination that you choose, not a wall that stops the application talking to anything.
Pricing on enquiry. No published number, because the deployment work differs enough between organisations that a headline figure would be wrong for most of them.
Where you stand
Free for individuals, always — donations welcome, never required.
Organisations pay a subscription; for organisations over 100 people it is required.
The software itself is licensed under Apache-2.0. These terms govern the service and support relationship — they are not a restriction on your right to the code.
There is no licence key, no activation and no seat check anywhere in the software. Nothing phones home to count you, because nothing phones home at all.
Which is worth being blunt about, because it is unusual: nothing in the software checks whether you have paid. The subscription is a commercial relationship you enter into, not a lock we have put on the product — and below 100 people it is a decision rather than a requirement.
What you get
The application an organisation runs is the same one anybody can download from this site. What a subscription buys is the work around it — getting it deployed, keeping it working, and being able to show someone why it is allowed.
The bundle is the whole working set, assembled together and checksummed: the installer, a pinned version of Ollama, a quantized model chosen against the hardware you actually have, and a manifest of hashes for every part so your own people can verify what they are installing. Handing someone an installer and telling them to go and find a model is not a deployment; this is the version of it that survives a machine with the network unplugged.
We do the rollout with you, or for you — sizing the model against the hardware, standardising the settings, and working out what the first week looks like for the people who have to use it. This is our own consultancy work rather than a download, and it is the part that decides whether the software is still being used in month three.
A named way to reach us when something is wrong, and a defect from your organisation goes on the public limitations page like any other. We will agree what support looks like with you in writing rather than print a promise here that we have not sized. There is no service level on this page because there is not yet one to state.
A short, plain document you can hand to whoever asks — the data-protection assessment, the security questionnaire, the person in the next chair — setting out which addresses the application contacts and which it does not, and what changes if you point it somewhere else. It restates what is already public on this site rather than making a stronger claim in private, which is the only version of that document worth having.
What we are not promising
We are a small company selling to organisations that are, in most cases, larger than we are. The way that goes wrong is a promise made to win the meeting and discovered in month two. So these are stated here, before the meeting.
No response time, no uptime figure, no support window. We have not sized any of them, so printing one would be a guess dressed as a commitment. What we will do is agree the terms with you before you pay anything.
It is not a product sitting on a shelf waiting to be downloaded. The pieces all exist and the work of putting them together for your hardware and your model choice happens once you ask. We would rather say that than imply a warehouse we do not have.
This applies to you exactly as it applies to everyone else, and it matters more at scale: unsigned software has to be got past your operating systems deliberately, on every machine. Signing and notarisation are next on the bench. Ask us where that has got to when you write.
There is no better build behind a paywall. An organisation gets the same software as an individual, with the same defects, which are published in full.
The full defect list is on the known limitations page, and it is the same page we would send you during a procurement review. Reading it before you write to us is not a bad use of ten minutes.
How to ask
Write to hello@consultancyinaction.com. There is no form, no qualification sequence and nobody will chase you.
Four things make the first reply a useful one rather than a request for more information:
If it would help to see the assistant reading a real workbook before you commit anyone's time, say so and we will show you that. It is the demonstration that tends to settle the question, and it works precisely because the file never has to leave the machine it is on.
Consultancy in Action Ltd
Registered in England and Wales, company number 17388810.
Registered office: 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ.
Invoicing is in pounds sterling against a written order. Terms are agreed before anything is payable.
