Evidence, not self-reported status.
Existing tools track what people say is happening. Izella continuously reads the evidence underneath — meetings, contracts, plans, decks — and builds the system of record for what was decided, where reality diverged, and who must act next. That record is what everything below is built from.
A $30M program produces a green slide every month — right up until the quarter it turns red for good.
The Friday steering deck, already built.
Real product views, rendered from the seeded program record — click through the surfaces the record powers.
- 1
When the vendor says “that was never agreed” — tap the quote.
- 2
One click makes it official. No minutes, no memo, no archaeology.
- 3
Six months later: who agreed, when, on what basis. Still there.
Watch one sentence become a decision.
Week two, someone says it out loud. Here's how Izella keeps it from becoming month six's write-off.
- Steering call · Week 2 · Transcript
- Program director: “We're already three weeks behind on data migration.”
- Sponsor: “Fine — we'll skip the pilot and go straight to rollout.”
- Vendor lead: “Works for us. Next item — cutover dates…”
1 · Said
Nobody writes it down.
Week two, steering meeting: “Fine — we'll skip the pilot and go straight to rollout.” Everyone nods. Nobody writes it down.
- Review queue · Same day
This sounds like a decision — confirm it?
“Fine — we'll skip the pilot and go straight to rollout.” — Sponsor, steering call, week 2
2 · Caught
Izella asks: is this a decision?
Izella read the transcript, pinned the quote, and asked the program lead: is this a decision? One click — official, with an owner.
- New document · Week 5
Contradiction
“Workstream plan v3” still schedules the pilot — superseded by the week-2 decision to skip it.
Nudged · Same day
Sent to the workstream owner, with both quotes attached.
3 · Defended
The contradiction gets flagged the day it lands.
Week five: a workstream plan arrives still assuming the pilot. Izella flags the contradiction and nudges the owner the same day — not at the quarterly review.
- Decision record · Month 6
Skip the pilot, go straight to rolloutOfficial
- Found in steering transcript — week 2
- Confirmed by the program lead — week 2
- Defended against workstream plan v3 — week 5
- Still standing — who agreed, when, on what basis
4 · Saved
Month six never happens.
No half-built pilot, no archaeology. One sentence — caught, confirmed, defended.
An illustration, not a screenshot — this is the product's job, one decision at a time.
Under every answer: a knowledge graph of your program.
Izella doesn't store documents — it builds an ontology of the program from them: decisions, owners, commitments, workstreams, evidence, all linked.
Every node is backed by a verbatim quote. Every edge was confirmed by your people. So when a decision stalls, Izella can tell you what it's blocking; when a plan contradicts the record, it knows exactly which decision it contradicts — and who has to care.
That's why “was that decided?” is a lookup, not an argument.
Six views of the same graph
Your people spend ten minutes a week. The agents never stop.
Izella isn't a tool your PMO operates — it's staff the program office didn't have to hire. Here's the division of labor.
Your part
01Drop the documents in.
The SOW, meeting transcripts, decks, circulated recaps — the paper trail your program already produces. No integrations required to start.
02Confirm what's real.
Everything Izella finds arrives as a proposal with its quote attached. Your people ratify, defer, or dismiss — ten minutes in the queue and the record is official.
Izella's part
03It watches for drift.
Every new document is read against the official record: decisions contradicted in later meetings, owners absent where they're accountable, topics discussed for months without a decision, commitments sliding toward their dates.
04It chases the stragglers.
Stuck decisions get nudged to their owners with the evidence attached; the steering readout assembles itself from confirmed facts. The chasing is automated. The deciding stays human.
Why you can bet the program on the record
Four guarantees — by construction, not by policy.
Evidence or it didn't happen.
Every statement traces to a verbatim quote at an exact position in a source document. Claims that can't be located are discarded before they reach the record.
Replace, never erase.
Decisions get superseded, not deleted. The history of every record — who confirmed it, who challenged it, when it changed — is append-only.
Invited, never watching.
Izella reads the documents you give it. It does not join meetings, watch inboxes, or observe anyone.
You decide what's official.
The software never promotes its own guesses. A human's one click makes fact, and the steering readout is built only from what your people ratified or deliberately deferred.
And the record stays yours — institutional knowledge compounds with your employees, not with expensive consultants.
Is it in Izella? If not, it didn't happen.
You find out in week three, not month nine — while it's a decision, not a write-off.