§ 01 · project-state

Hard questions. Instant answers. Every source attached.

Ask anything about your organization. Get a real, sourced answer in under a minute — without bugging your staff.

You

The board wants to know why the launch moved. What happened?

The launch moved twice. Mar 14 — held for the security review decided by Sara · Slack #launch. Apr 2 — vendor delivery slipped three weeks email · Acme. Both on the timeline, with sources.

§ 02 · Who this is for

Built for people who are accountable for outcomes.

CEOs & executives
You answer to a board, funders, or shareholders.
COOs & operations
Multiple projects, one view — without chasing anyone.
CIOs & CTOs
Delivery across teams and tools, recorded as it happens.
Program & project leads
You build the thing and report on the thing. Keep building.
§ 03 · The problem
Your funder comes back with questions. You spend two days digging for answers you know exist.
“Can you free someone up for this?” — “I'll have to get back to you.”
Every status update means interrupting the people doing the work.
A key person leaves, and what they knew leaves with them.
§ 04 · What it costs
19%
of payroll goes to reporting and status, not the work
2.5hrs
per person per day searching for information that already exists
42%
of what people know walks out the door when they do

The answer already exists inside your company. It just doesn’t live anywhere you can ask.

§ 05 · What it is

Operational memory for your organization.

It connects to the tools your team already uses and builds the record automatically: decisions, milestones, risks, documents, commitments.

Nobody on your team fills anything in.

Microsoft 365 Google Workspace GitHub Slack Jira

A dashboard shows what someone typed in.

project-state remembers what actually happened — and can prove it.

§ 06 · The proof
FROM THE LIVE DEMO

A hard question, answered — with the receipts.

01
The question
“Why are we only learning this now?”
02
The answer
Three stakeholder reports overdue against their cadence.
03
The sources
Each one named, with when it was expected and when it last went out.

project-state.app/dash/demo/showcase

The live demo showing a flagged blind spot: three stakeholder reports overdue, each source named with its cadence
LIVE — click to explore
§ 07 · What changes for you

You stop assembling the answer. You just have it.

◆
Answer board and funder questions the same day, with sources.
◆
Do the reporting you owe without interrupting your team.
◆
See where the organization is losing time before it costs you.
◆
Keep what people know inside the company, even when they leave.
§ 08 · How it starts

Start with one project. Six weeks.

Week 1
We start on your work
Your tools connected, your real project loaded. No migration.
Weeks 2–5
You ask it hard questions
One working session a week. Bring the questions you normally chase.
Week 6
You review the results
Measured against the three things we agreed up front.
Speed
How fast a hard question gets a sourced answer.
Effort
Hours to produce the thing you owe.
Risk
What surfaced that you’d have found late.

One of each kind — baselined in week one, measured again in week six.

§ 09 · Next step

A 20-minute diagnostic

How do you build a project update today?

Walk us through who touches it and how long it takes. We’ll tell you honestly whether a pilot makes sense.

project-state.com klo@atomic47.co
1 / 9 Mobile ↗

Speaker notes