governance-first Company AI
AI that does not assert anything a person has not approved.
Favel gives you the full conversational assistant you expect, plus the layer no assistant has on its own: your company's decisions, approved by a person and kept current, named on every answer.
Current phase: closed access, handpicked design partners.
The product / what it does
One product, three aspects.
Three parts, and each needs the other two: a draft is worthless until a person approves it, an approval is worthless until the assistant reads from it, and the assistant is only trustworthy because it starts from approved material. That is one system, not three features.
- 01
From input to a draft
source material.pdf- p.01
- p.02
- p.03
- p.04
- p.05
Favel scans the source material, from meeting transcripts to the latest budget table, and forwards essences that matter to your company.
- 02
A person approves
awaiting approvalchoicePick the Q4 launch scope
E1E2E5Option AOption BadditionName the missing owner
E3E4AcceptRejectThe decision surfaces the contradictions and gaps: you choose a direction, or add what is missing. Only what a person approves reaches the assistant.
- 03
The assistant answers
from approved materialIt answers from what was approved, and can say where it came from. Results produced in the assistant go back for a person to approve.
Show the technical functionalityHide the technical functionality
How it works / the chain of custody
Every answer traces back to a person who signed.
Traceability
Five links, from the answer back to the source it came from.
- 01
Assistant output
A claim, as a sentence you can read.
- 02
Company knowledge
The approved entry the answer was drawn from.
- 03
Decision
A person decided it holds, with the date.
- 04
Extracted Essence
What was pulled out of the source.
- 05
Source
Origin, date, and owner.
The decision / what the act produces
The decision is prepared, and a person approves it.
Favel sets what is new against what already holds. Nothing the company relies on gets there without approval. The bottleneck is the decision, not the reading. A document does not record whether a decision still holds, and only a person can decide. That is why the gate is part of the product.
- 01A source arrives
Read for what it could add, with the passage.
- 02A decision is prepared
What it adds, set against what already holds.
- 03A person approves it
Approve, or say what is missing. Someone answers for it.
The assistant / why it is inside
Tuned to Canon and to the record.
The assistant knows your Canon, the knowledge your team approved, and the record every answer carries. No write access, and what it proposes goes back through the gate.
What holds for the quarterly plan?
Scope and owners are settled, and the budget envelope is set.
Read from Canon, with its record on the answer.
Decisions come from where the work happens.
Not only from a document someone uploads. A finding, a resolution, or a conclusion reached with the assistant can be submitted as a decision: it is prepared like any other, it goes to the person who owns it, and nothing the assistant reads changes until they approve it.
The alternative / what makes Favel different
Why not just use what you already have?
The source
What you have
The document is where the answer comes from.
With Favel
The document is input. The answer comes from a decision.
The evidence
What you have
The answer quotes the first passage it finds.
With Favel
The answer comes from what a person explicitly approved.
What holds
What you have
A document cannot say whether it is still true. Nothing supersedes it, so an outdated answer looks exactly like a current one.
With Favel
A set records what still holds, entry by entry, with what each one replaced.
The timing
What you have
The decision comes later, if it comes at all.
With Favel
The decision happens before the answer.
The context
What you have
You rebuild the context in every new chat.
With Favel
The context is set before you ask.
A document records what was. Canon records the essentials that still hold.
Documents do not disappear. They stop being what you work from and become the record of what was. What Canon keeps instead, entry by entry, is what a document cannot record.
Who this is for / the fit
Favel is for the company that decides, not for the one that wants to hand the decision over.
Fits you
- A leadership team that owns what the company has written down and runs a formal strategy layer: a plan, OKRs, an offsite cycle.
- AI already in use: a company-wide AI search, or a chatbot you use ad hoc.
- You want a centrally governed, company-wide AI system.
Does not fit you
- A company with no written state. If nothing has been decided, there is nothing to approve.
- A team that wants the assistant to take the decision off its hands. That is the one thing Favel will not do.
- Anyone shopping for document search, a meeting notetaker, or a wiki. Those answer a different question.
FAQ / what you still wanted to ask
Frequently Asked
How do I know the assistant does not invent something?
It answers from the decisions a person approved, not from a search over your documents. Every answer carries its record with it: the approved statement, the passage that statement came from, and the person who signed it. The assistant has no write access, so it cannot add anything to what holds. It can write a clumsy sentence; it cannot answer from a decision nobody approved.
Why do I still have to decide?
Because removing the decision is what every other assistant promises, and it is what produced the problem you probably have today: an answer nobody can stand behind. Favel prepares the decision instead. It arrives with the material already extracted and a title, so it starts from something readable rather than a transcript, and the decision type says what is being asked: choose a direction, or add what is missing. Making the decision visible is the product. Taking it off your hands is the one thing it will not do.
What happens when something changes?
A change is a source, and a source goes through the same approval as everything else. Favel sets what it adds against what already holds and prepares a decision for the person it belongs to. Nothing changes in what the assistant reads until a person approves it, and the earlier version stays in the record. What holds is not a snapshot that ages quietly; it is a set a person keeps current.
Why not just store documents?
A document fixes a decision at the moment it is written. Whether it still stands, what replaced it, and what depends on it change afterwards, and the document does not change with them. Favel keeps Canon as one maintained set instead. Each entry points back to who approved it and what it came from, so a replacement has to hold its own against the rest of the set. Your documents do not disappear: they stop being what you work from and become the record of what was, while AI and agents take on more of the work.
What happens after I join the waitlist?
Your entry is stored right away, and you get a welcome email. There is no confirmation click, and that is the only mail you receive until launch. We build with selected design partners, and we review the entries and hand-pick who fits best. Entry order does not decide, you cannot apply to become one, and we do not promise a release date.
Where is the data processed?
We keep the processing chain short. This site collects nothing until you say yes. After that we measure, and the privacy notice names the services behind it and what happens to your data. If you come on as a design partner, we agree what the product does with your data before you start.
The waitlist / what happens next
Join the waitlist.
The product is built and in use with selected design partners. We hand-pick partners in stages rather than all at once. Entry order does not decide who we pick, there is no way to apply, and we promise neither a release date nor a limit on the list.