The questions you stop chasing.
Every role below asks the project a different hard question. They all get answered the same way — from one record of what actually happened, with the sources attached.
Every document, decision, and update lands on the timeline as it happens, and the source is saved with it. Nothing is ever written over — a correction is a new entry, so you can always see what changed and when. That way the project can answer the three questions that settle arguments, audits, and handoffs: what happened, what did we know at the time, and where’s the source?
“Where are we, really?”
One live picture across every project — assembled from the tools and conversations your teams already work in, not from what people remember to roll up. Board packs and exec reports generate on cadence; hard questions get answers with sources; and the company’s intelligence stops living in individual heads.
The recognition: the board asks a hard question, and you ask the project, and it answers with sources.
“How do I keep the story straight while building the company?”
You’re wearing every hat — the investor update, the grant claim, the diligence binder all compete with the actual work. project-state collects the company’s history as it happens: decisions with reasoning, milestones with evidence, every claim traceable to its source and its date. Updates and claims generate themselves; you approve and send.
The recognition: diligence arrives, and the history is already there — timestamped, sourced, nothing to reconstruct.
“Why did we build it this way?”
Decisions keep their context — who, why, what it depended on. Risks are re-assessed as new signal lands; drift between plan and reality surfaces early; status becomes a question you ask instead of a meeting you hold. New teammates onboard by asking.
The recognition: “why is it like this?” gets an answer with a date and a source — six months later, from someone who wasn’t there.
“What did we promise, and to whom?”
Everything said to a customer or partner — on calls, in email, in Slack — is collected against the pursuit as it happens, and every promise made goes on the record. Outbound messages wait for a person to approve them. Pursuit teams can add the tender plugin: qualification backed by evidence, bid or no-bid recorded as a decision with the reasoning kept, six stages from first sighting to closed. Win, and delivery starts knowing the full history of what was said.
The recognition: the handoff carries every promise ever made to the customer — nothing lives only in one person’s head.
Whatever the role, the reports come out in your format — funder claims, board packs, client updates. Set up once, not custom-built.
Start with one project. In six weeks you’ll know whether it holds up on your real work.