project-stateby Atomic47 Labs
Pilot programme

Start with one project. Six weeks.

This is for people who answer for outcomes — the CEO, the COO, the CIO or CTO, the person leading the program. If you spend your week chasing answers that already exist somewhere in your company, this is built for you.

Give us one important project. In six weeks, project-state builds a reliable record of it, answers hard questions with sources, and cuts the work of keeping leadership informed. We agree on three success measures before we start. In week six, you review the results.

How the six weeks go
Week 1
We start on your work

We connect your tools and load the project you picked. No migration, no rollout committee. Your team keeps working the way they already work.

Weeks 2–5
You ask it hard questions

One working session a week. You bring the questions you normally chase — the funder question, the allocation question, the what-did-we-decide question — and we make sure it answers them with sources.

Week 6
You review the results

We measure against the three things we agreed on up front. You decide whether it stays.

Three measures, agreed and baselined before we start

One of each kind — never three of the same. We take the baseline in week one, from the cycle you just lived through rather than from memory, and the same three numbers again in week six. That way the review is a fact, not an impression.

Speed

How long it takes to answer a hard question about the work, with sources.

Effort

Hours to produce the thing you owe — your team’s, plus anyone you pay.

Risk

What surfaced that you would otherwise have found late, and how much of it is evidenced with dates.

What you get

Your real project, not a demo

Loaded with your actual work, your people, and your stakeholders from day one.

Answers with sources

Ask anything about the project and get an answer in under a minute, with every source attached.

Reporting without the chase

The weekly update, the board note, the funder answer — drafted from the record, waiting for your approval.

A direct line to us

Weekly sessions with the people who build it. What you need changes what gets built.

Your data, day one

The record and the documents are yours. Full export whenever you want it. No lock-in.

What we need from you

One real project

Something that actually matters this quarter — not a test project set up for us.

About an hour a week

One working session, for six weeks. Your team keeps doing their work.

Straight feedback

What worked, what annoyed you, what you would never use. That is the whole point.

A conversation at week six

Tell us what the results were worth. Write it up together if you are happy — privately if you prefer.

Apply

Apply for a pilot.

Four questions. Two minutes. We read every one ourselves, and we will tell you honestly if it is not a fit.