The project remembers.
Ask your project a hard question — what did we decide, what did we promise, why did it slip? — and get the answer in seconds, with sources. project-state connects to the tools your team already uses and turns what happens in them into shared intelligence and reporting — in chat, and in a full cloud workspace.
The board wants to know why the launch moved. What happened?
Nobody can ask “where are we, really?” and get an answer with sources.
The decision is in a thread. The risk is in someone’s head. The status is in three places, and they disagree. Every week your team spends a quarter of its time reporting about the work instead of doing it — reassembling, by hand, what the tools already know.
project-state plugs into where your team already works. Then it runs, continuously:
The signals — what was said, sent, decided, and delivered, gathered automatically across your tools and conversations.
Decisions and actions are tracked, risks are re-assessed as new signal lands, drift is caught while it’s still cheap.
The weekly status, the board pack, the client update, the funder claim: generated on cadence, shaped for each audience.
Every outgoing decision, email, and report waits in one queue for a human yes. Nothing sends itself.
Ask the project anything — what changed this week, which risks touch the launch, what did we decide about pricing and why. It answers from the live record, with sources.
A full modern UI: boards, timelines, risks, goals, documents, dashboards — and the queue, where everything outbound waits for your approval.
Ask it like an oracle.
Underneath everything, project-state keeps the foundation: your project’s full history and documents on an auditable timeline. Every signal with its source. Every decision with its reasoning and its date. Append-only — nothing overwritten, ever — so every answer can cite exactly what was known, and when.
That’s what makes the chat an oracle, not a chatbot: what did we decide about pricing, and what did we know at the time? gets a real answer, with the timeline and the sources attached. New teammates inherit the full picture on day one. When someone leaves, nothing leaves with them.
Add whole domains to the same workspace. Tender intelligence today — a governed pursuit pipeline from discovery through bid/no-bid to won. Intel is next. Enable per project, like flipping a switch.
Shape the reporting to your world — your funder’s claim cycle, your board’s pack format, your client’s QBR — configuration, not custom development.
Every email, report, and post stops in the queue for sign-off.
Answers cite where they came from — and the record is append-only, so citations can’t rot.
Full export, any time. Run in the cloud, on your own infrastructure, or fully local. No lock-in, by design.
project-state’s own development runs on project-state — the signals, the decisions, the risks, the reporting, all live at project-state.app. Not a demo dataset. The actual project.
One foundation — the project’s auditable, citable history — and what each role builds on it:
One live picture across every project. Hard questions get sourced answers.
The company’s history collected while you build. Diligence, pre-assembled.
Decisions keep their context. Status becomes a question, not a meeting.
Commitments on the record. The handoff carries everything ever promised.
Sign in at project-state.app. Connected and working the same afternoon.
The same product on your infrastructure. Your custody, end to end.
project-state-plugin for Claude Desktop — the full product, driven from chat, no server at all.