On Friday, the project manager gathers the week’s minutes, tickets and emails to write Monday’s status report. The agent your provider or your team sets up does that reading instead and calls a language model to write. That model, Agent Libre serves in Canada for a fixed monthly amount, whatever the number of projects.
Talk about your project managementA mid-sized project builds up more text than its team can re-read.
A deadline is set in an email, moved in a meeting and confirmed in a ticket. At the steering meeting, the status report gives three versions of it, and the discussion is about the date rather than the project.
The register is filled in at kickoff, then updated once a risk has already happened. The supplier who announces a two-week delay in the March minutes enters the register in May, when the delivery slips.
Notes are taken during Monday’s meeting and written up on Thursday, when the person finds an hour. Two of the actions were due Wednesday, and nobody had seen them in writing.
Your tool stays the same. What changes is the model that answers it.
Your teams, your data and your rules. You decide what the tool does, and with which data.
The tool that reads your minutes, tickets and emails, then writes the day’s minutes, the risk register update and the status report. Your provider or your team connects it to your project platform and tells it what it may write on its own.
Every time the tool needs an answer, it calls a language model. That model can come from different providers. This is where Agent Libre comes in.
Your provider’s or your team’s tool reads your tickets and writes. It calls a language model to do so. What Agent Libre’s model changes comes down to four points.
The tool reads your tickets, minutes and emails from your platform (Jira, Asana, Microsoft Project or others) or a home-built one. Your provider or your team sets up that link and chooses the model that answers behind it. Switching to Agent Libre means changing the model’s address in the tool’s settings.
The tool re-reads the last six months of minutes before writing a line, and does it again on every request. With Agent Libre behind it, that re-reading is included in the plan, under fair use: an eighteen-month project is read in full, at the same price as a three-month one.
You reserve a processing speed for yourself, and all your projects share it. The month’s amount is written in the contract and follows that speed. A free 24-hour to one-week audit first measures what your tools consume today, to choose that speed.
The emails, minutes and reports the tool sends to the model are processed on servers hosted and operated in Canada. Nothing is kept after processing and nothing is used to train a model.
From the transcript or the notes, the tool writes the minutes, lists decisions and actions, then matches them to existing tickets.
The tool re-reads the week’s minutes and emails, spots new or changed risks and proposes a register update the manager approves.
The tool compares ticket status against the plan, notes moved deadlines and drafts the status report. Each statement points to the ticket or the minutes it came from.
Four decisions to make before changing the model behind your project management tool. None of them belongs to Agent Libre.
Decide what the tool writes on its own and what it submits to you: minutes can go to the team as they are, but a risk register update or a deadline moved in the plan should wait for your approval. Set that split in the tool before changing the model behind it. The model does not make that call for you.
Pick two or three current projects and have the minutes and the status report produced, for two weeks, by the current model and by Agent Libre’s, from the same meetings. Compare missed decisions and cited sources before extending the change to every project.
Check that the tool connected to Jira, Asana or Microsoft Project lets you choose the model’s address: it is the only setting to change, in three lines of configuration. Also note when it calls the model (on every changed ticket, at the end of each meeting, every night). That rhythm is what sets the speed to reserve.
Minutes name employees and clients, and tickets sometimes mention hourly rates or contract amounts. List what Agent Libre’s gateway must mask before sending to the model and what must get through for the summary to keep its meaning: the project name, yes; the name of a person on sick leave, no.
No. The agent is set up by your provider or your team, with your platform or a home-built tool. Agent Libre serves the language model that reads and writes behind it, and nothing else.
It reads the full transcript and draws out the decisions, actions and deadlines. The result depends mostly on the quality of the transcript and on the instructions the tool gives it, both of which stay in your provider’s hands. Compare it on your own meetings, for two weeks, before switching.
Requests share the reserved speed. If they all arrive at once, they wait their turn: the minutes come out a few minutes later, with no cut-off and no charge. Sprint end and the month-end report go the same way.
Only what the tool sends it for each request: the selected minutes, tickets and emails, minus what Agent Libre’s gateway masks in passing (names, amounts) if you asked for it. Processing happens on servers hosted and operated in Canada, and nothing is kept after processing.
No. The contract amount does not change during the year, whatever the number of projects or minutes. If the reserved speed is saturated every day, requests wait longer; at renewal, the speed and the amount are revised from measured consumption, up or down.
What each team decides before putting a model served in Canada behind the assistant that answers from your policies, procedures and contracts.
What a law, accounting or consulting engineering firm decides before putting a model served in Canada behind its contract review and file search tools.
Why the history re-read on every call weighs more than the summary produced in an agent’s bill.
The first one you already know. Materials come in, they are transported, stored, transformed, delivered. Every step has a supplier, a lead time, a unit cost. When the margin tightens, you walk down that chain step by step, and you generally know where to look.
The second one moves information instead of materials. A price request comes in and becomes a quote. An order comes in and becomes a production order, an invoice, a confirmed delivery. A site report becomes a change order, or it does not. This chain runs through every one of your departments and it employs a large share of your people.
We measure your actual consumption at your current provider: who calls what, what it costs, and what is leaving your walls. Free, no commitment, and the report is yours even if you go no further.