The answers below describe what Calliops does today, in preview. Where something is not connected yet, it says so.
Calliops reads a team’s meetings, extracts what clients asked for, decided, flagged or were promised, and files all of it into a shared register where a request heard by four people is a single line. Every line cites its meetings, to the second.
It is not a note-taker: minutes belong to one meeting and close with it. The register belongs to the team and grows with every meeting after it.
No, and not merely as editorial caution: the system has nowhere to write a product decision. The pass that files sealed items into needs has no field for “and so here is what we should do”, and its instructions forbid proposing one.
One step requires a person — review — and nothing goes round it. What has not been sealed does not enter the register.
One line, with two quotes. Every sealed item is checked against the needs that already exist, and the instruction is to prefer what exists over creating something new: the second mention joins the first instead of producing a duplicate.
That holds between two people, between two meetings and between two client accounts. The need then keeps the list of accounts that raised it, which is the difference between “one client keeps asking” and “three clients want the same thing”.
Everyone sees the same register inside a product space. That is the point: client knowledge stops being split across the memories of whoever was in the room.
Partitioning is by product space, not by person. Two spaces share no meetings, no accounts and no needs, and a meeting imported into one cannot produce anything in the other.
It enters the register, becomes citable and attaches to a theme. From there it feeds four readings: the pre-meeting brief, the register itself, the map of themes, and a question asked in plain language.
It stays open until somebody closes it. A closed need stays readable and stops surfacing as a live subject.
Meeting transcripts brought in by the calendar, transcripts caught by the extension when the calendar cannot see the meeting, and written feedback you add by hand.
A meeting with no transcript is not processed: the product does not guess what was said in a room it did not hear.
Google Calendar and Google Meet on the way in, a Chrome extension for meetings the calendar cannot see, Notion on the way out, and MCP access for your agents. Nothing else is connected yet.
No. The register lives in Calliops; Notion is an optional destination for what has been sealed. Without Notion, everything stays readable in the product and exports to Markdown.
A sealed perimeter: its meetings, its client accounts, its needs, its seals, its members. A team working on two distinct products takes two spaces.
Three tiers, per contributor per month on a one-year commitment: Pro at €10, Organisation at €24, Entreprise at €55. Without a commitment, €13, €30 and €69.
Pro covers one product space and a single contributor, with unlimited meetings; Organisation opens three spaces, as many contributors as you need, the map of themes and spec generation; Entreprise opens unlimited spaces, roles and the audit log.
Only the people whose meetings feed the register. Reading the register, reviewing an extraction and sealing are billed to nobody, and a client invited to read their own account costs no licence.
That is deliberate: pricing that counts every seat pushes teams to leave people out of the register, and a register missing a whole team is not worth much.
Nothing enters the register. Items stay as drafts in the queue, dashed, and keep being deduplicated against later meetings. The first seal files all of them at once.
The screen says so with the time and offers to resume. The blocked item is stamped in ink, not in red.
Notion sync interrupted at 09:41. Resume.
Yes, to Markdown, quotes and seals included. What Calliops writes is yours and does not depend on your subscription to stay readable.
No. From the Organisation plan up, a sealed need becomes a specification — user stories, UX constraints, technical scope, definition of done — carrying the same quotes as the need. An engineer reads it and writes the code.
The register stays useful to a team that ships no software at all; the specification is what a team that does gets out of it next.
Every seal carries the person’s name and the time, and stays attached to the item. On Entreprise, an audit log collects every seal in a space.
Calliops is in preview and opens in waves, one product space at a time, to keep extraction quality honest. The next wave is planned for September 2026, and people on the list get a reply within 24 hours, dated.