Ask your knowledge engine — and let it do the work
Everything your company knows, one question away.
The Floral assistant sits inside your workspace with access to the whole knowledge engine: meetings, summaries, briefings, transcripts, your own documents and data sources, plus companies, contacts, deals, tasks and notes. It finds, it analyses, and it finishes the job — with your permissions, and never without your approval.
Find, analyse, act
Most AI tools stop at retrieval. The assistant reasons across everything your company knows, then reaches for the same tools your team uses to actually change something.
Find across everything
Ask in plain language. Floral searches by keyword and by meaning across meetings, summaries, briefings, transcripts and every source you have uploaded.
Analyse, not just retrieve
Compare accounts, pull the pattern out of a quarter of conversations, summarise what changed since the last meeting. It reasons across the workspace, not one document at a time.
Get the work done
Create the task, write the note, update the record, draft the follow-up — and chain several steps together until the job is finished.
Grounded in your own material
Every answer shows the meeting, summary or source behind it, so you can open the evidence and check the work.
Works as you, not above you
It acts on behalf of the person using it with exactly their permissions. Membership and access are re-checked on every request, and every action is logged.
Approval before every write
Reading is free. Anything that changes a record stops and asks first, so the assistant can be useful without being risky.
Connect it to any AI model, through MCP
Floral runs its own MCP server. Any MCP-capable AI client — ChatGPT and others — can reach the same knowledge and the same tools, under the same permissions as the person using it. The model you prefer today does not have to be the model you are stuck with next year.
That is the whole point of building on an open protocol rather than a single vendor's assistant: your knowledge stays in your workspace, your data stays yours, and the AI layer on top stays replaceable. MCP access is enabled per workspace.
Floral suggests the next step on its own
You should not have to know the right question. When a meeting summary is approved, Floral works out what follows from it and brings that to the person it belongs to.
Tasks from what was agreed
Every to-do captured in an approved summary becomes a proposed task, with the deadline and priority it was given in the conversation.
Insight for the individual
Suggestions are personal, not a team firehose. Each person gets a short review inbox with what is relevant to their own accounts and work.
Records that should move
When a conversation implies a company detail changed or a deal moved on, Floral proposes the update — with the exact quote it is based on.
Pairs well with
AI meeting summaries
Approved summaries are what the assistant reasons over and what suggestions are built from.
Workspace AI context
Teach the assistant your vocabulary, your industry, and what to ignore.
Per-user feature access
The permissions the assistant inherits are the ones you set here.
Frequently asked
Anything your company has recorded. It searches by keyword and by meaning across meetings, summaries, briefings, transcripts and the documents and data sources you have uploaded, plus companies, contacts, deals, tasks and notes. Ask what a customer said about pricing last quarter, what changed since the last meeting, or which accounts have gone quiet.
It can do things. The assistant reaches the same tools your team uses — create a task, write a note, update a record, move a deal — and chains them to finish a job. Every write asks you for approval before it happens.
No. The assistant acts on behalf of the person using it with exactly their permissions, and never more. Feature access, record access and workspace membership are re-checked on every single request, and every action it takes is logged.
Yes. Floral runs its own MCP server, so any MCP-capable AI client can reach the same knowledge and the same tools. That is the point of building on an open protocol: you are never locked to one vendor’s model. MCP access is enabled per workspace and is currently in early access.
Yes. After a meeting summary is approved, Floral proposes the next step to the person it belongs to — follow-up tasks from the to-dos that were agreed, records that look out of date, and insight worth knowing. Suggestions land in a personal review inbox where you edit, apply or dismiss them. Nothing is written without a person deciding.
From your own material. Answers show the meeting, summary or source they are built on, so you can open the evidence and check the work rather than trusting it blindly.
Put your company’s knowledge one question away
Sign up, connect a calendar, and ask the assistant something only your company would know.