CitadelCompany Demo
Northstar is mid-quarter. The thread is already live.
You're joining a company that made a pricing change Tuesday, hit an implementation wall Wednesday, and needs to make a call Friday. Every detail is already here.
Company
Northstar Operations Group
Role
VP Operations — owns pricing, onboarding, and forecast
This week
Pricing changed Tuesday. Implementation flagged risk Wednesday. Board prep starts Monday.
What Citadel holds
The decision, who made it, why, what depends on it, and what's stuck.
Session start. Loaded Northstar context: 4 active outcomes, last update 11 hours ago. Pricing decision (Tuesday) has a downstream blocker.
I have two minutes before a call. What do I need to know?
The 15% pricing increase you approved Tuesday is live, but onboarding flagged a sequencing risk yesterday — two enterprise clients start next week on the old rate. Finance hasn't confirmed the transition plan.
Who owns the transition plan?
Jamie Chen in finance. She has the task but hasn't started. The record shows she's waiting on the final rate table from your Tuesday decision — it's attached, she may not know.
Send her the rate table and mark the blocker as resolved on my authority.
Done. Rate table linked to Jamie's task. Blocker updated. The board prep outcome now shows green on pricing, amber on onboarding timeline.
What Survives
continuity after the session ends
Chat history
Tuesday's context gone by Friday
reset
Email + docs
pieces exist, nothing linked
fragmented
Citadel record
decision → blocker → owner → action, intact
preserved
The problem
In a normal workflow, Tuesday's pricing rationale lives in a Slack thread, Wednesday's blocker is in someone's head, and Friday's AI session starts from zero. The executive has to reconstruct the story every time.
The difference
With Citadel, the pricing decision, the implementation risk, the owner, and the next action are one record. Any session — human or AI — picks it up intact.