OIAR Enterprise is the SaaS for consulting, audit and assessment projects with many stakeholders. Its agents interview the client's stakeholders and write the drafts of blueprints, requirements and assessments. Your team decides, the client signs, and every sentence points to the source it comes from.
For partners, PMOs and practice leads who run ERP implementations, CRM projects and process transformations.
A programme produces dozens of documents, in parallel, written by different consultants, with the same stakeholders and with decisions that travel from one document to another. Today all of this lives in shared folders, Excel sheets, meeting minutes and the senior consultant's memory.
A decision taken in the Finance workstream changes an invoicing process that was already approved. Nobody notices until the client does.
The head of administration gets three invitations from three consultants, for three different documents, and says the same things again.
Three months later, a sentence of the document is challenged. Finding the interview or the file behind it takes hours, when it can be found at all.
Orders and accounting describe the same posting in two ways. The senior consultant checks it by hand, the night before delivery.
The method stays your firm's own. What changes is where the work lives, and who does the repetitive part.
| How it is done today | With OIAR Enterprise | |
|---|---|---|
| Interviews | Calendars to match, minutes written by hand, the same person heard several times | The agent interviews each person when they have time; one session per person, even when it serves several documents |
| Drafts | The consultant rewrites the minutes into the templates, section by section | The agents propose the sections; the team accepts, corrects or rejects every change |
| Sources | "Who said that?" means listening to the recordings again | Every sentence points to the interviews and documents that support it |
| Versions | Files renamed "v3_final_rev2", copies in several folders | Published versions that never change again, with the list of what changed |
| Consistency | The senior consultant rereads the documents side by side before delivery | Checks across documents, and before publishing you see which other documents a change touches |
| Client | Comments by e-mail on attachments, signatures on PDFs | The client comments directly on the sentences and signs the version |
| AI | Everyone uses their own tool, with no record of what it did | The agents work within the rules set by the programme lead, and everything leaves a record |
Every workstream of the programme follows them, with an owner and a status the whole team can see.
The agent interviews each stakeholder from their phone or PC, with questions written for their role. If you prefer, you run the interview in person and the platform tells you what is missing, or you upload the minutes of a meeting.
Interviews and client documents become statements, each with who said it. The agents propose the sections of the document as changes to accept or reject: nothing is rewritten behind your back.
You publish a version: the client sees only that one, comments on the sentences and signs. If another workstream changes something, you see which documents it touches before you publish the next version.
Supplier invoices reach accounting ten days after goods receipt, on average.
The name comes from these steps: Orchestrate (the plan), Interview, Analyze, Report.
A single assessment can be run with a good template. A programme with ten documents and forty stakeholders cannot: that is where OIAR Enterprise earns its place.
Every area has its consultant, its interviews and its documents, and the status of everything is visible at a glance.
If the head of administration is needed for three documents, they answer once.
Checks across documents flag where orders and accounting, or two different areas, do not say the same thing.
An assistant answers the team's questions about the programme, citing the document version and the source.
Or an area managed by the platform. More document systems are added over time.
OIAR works on the documents in the Data Room your firm chooses. If you connect it to Google Drive, SharePoint or Dropbox, the data stays in the storage system you already use and under your control.
The administrator connects the firm's archive, the programme lead assigns it to the programme. Each programme works in its own subfolder, not in the whole archive.
The connection can be turned off or deleted at any time. The documents produced stay in the archive you chose.
Every programme folder always holds the .md version of the documents as well: the folder can be queried at any time, by you or by agents and harnesses such as Claude Code or Codex.
What the agents read is material to analyse, never instructions to follow, and every sentence of the final documents points to the file it comes from.
OIAR Enterprise collects everything that is known about a context, whether a project, a company or a single function, and returns it in two formats: one for people, one for AI. The result is a company second brain, focused on a precise scope.
The stakeholder interviews, the client's documents, the decisions taken in the workstreams. Every piece of information comes in with its source: who said it, which file it is in.
Blueprints, requirements, reports and charts in the format the client reads, comments on and signs.
Every document also exists in .md in the programme folder. An agent reads it with no conversion and answers citing the version and the source.
If the scope is an ERP implementation, you get the brain of the project. If it is a company, a function or a process, you get the brain of that scope. Whoever comes next, a person or an agent, starts from there instead of from zero.
It is not an archive of everything. It is the knowledge collected and verified on a chosen perimeter, and every answer points to the interview or the document it comes from.
Skills are the instructions the agents follow to interview, analyse and write. The Skill Loader is the loader that picks them: it looks at the context of the project and hands each agent the skill it needs at that moment, instead of making it carry the whole catalogue.
The catalogue has four types: methodologies (for example requirements management), products (for example the Odoo modules), general processes (CRM, recruitment, GDPR, technical assessment) and vertical processes (for example meter self-reading and account transfer in a CRM project for a utility). From the configuration you can preselect the families to use, so the method the agents follow is your firm's.
In the Skillblog we publish part of the catalogue: every skill has an article that explains the process in plain language. The skill itself, written for the agents, is used inside OIAR.
If you need a single report or assessment, and not a programme with several workstreams, OIAR is the right fit: it interviews people, analyses the documents and writes the report.
The programme lead chooses, action by action, how much to leave to the agents. Whoever confirms sees exactly what will change.
The agent cannot take the action, and cannot propose it either.
The agent prepares the change, the owner accepts or rejects it. If something has changed in the meantime, the proposal expires.
Only for actions that can be taken back. Every action stays visible, with the button to undo it.
No setting makes them automatic: never an agent, never an automation.
The person rereads the minutes of their own interview and sees their own data. They give consent and can withdraw it.
Never the name or the original text, and nothing comes out until the group has at least five people. We do not promise pure anonymity: we promise what the system guarantees.
You work with your clients' data. These rules are written into the product: they are not settings someone can switch off.
Every consulting firm has its own space, with its own brand, people and permissions.
The client sees only the published versions, the stakeholder only their own interviews. Drafts and the Data Room stay with the team.
The team signs in with a password, Google or Microsoft, but only with an invited account. Guests use a personal link.
What the client or a stakeholder writes, and the files uploaded, are treated by the AI as content to analyse, never as instructions to follow.
Every action records who took it (a person or an agent), on whose behalf and under which rule.
The cost of AI is recorded per programme and per type of agent, and you see the estimate before you start.
It is the SaaS for consulting, audit and assessment firms that run programmes with several workstreams, several consultants and a client who has to review and sign the documents: ERP implementations, CRM projects, process transformations. If your work is a single assessment with a final report, you probably need less than this: look at OIAR, the solution for one report or one assessment.
On the consulting firm's side: the administrator (people and templates), the programme lead (plan, owners, rules for the agents), the workstream owners and the consultants. On the client's side: the reviewer, who sees only the published versions, comments and signs, and the stakeholders, who see only their own interviews. Agents are not users: they work within the rules of the programme.
No. Publishing a version, closing the programme, changing permissions and deleting are always manual. For everything else the programme lead decides, and a workstream owner can only make the rules stricter on their own workstream.
We do not promise pure anonymity, because we cannot guarantee it. An interview is either named or confidential to the team: in that case the team reads only paraphrases aggregated by group, never the name or the original text, and nothing comes out below five people.
Yes, that is the point. You start from a template (ERP Business Blueprint, Process Assessment, Odoo assessment, CRM requirements for a utility) and adapt it: roles to interview, documents, sections, questions, consistency checks. A simulation shows what it produces and what it costs before you use it on a client.
The Skill Loader is OIAR's skill loader: based on the context, it picks the right instructions for each agent, or the ones you preselected in the configuration. The catalogue has four types: methodologies, products, general processes and vertical processes. In the Skillblog we publish part of it, each skill with an article that explains the process. The skills are used inside OIAR.
No. The client's reviewer sees only the published versions of their programme, comments on the sentences and signs. Drafts, the Data Room and the interviews stay with the team.
It depends on the programme: how many workstreams, how many stakeholders, how much work the agents do. There is no public price list: contact our sales team and we will propose the right plan. Every AI call is recorded with its cost, so the proposal starts from real costs, not from a desk estimate.
Interested in OIAR Enterprise, or want to know more? Tell us about your programme: our sales team will get back to you and, if useful, set up a call to show you the platform.
Thank you. Our sales team will get back to you shortly. In the meantime you can have a look at the Skillblog.