Hour 0 reads your documents, sits in your meetings, and keeps every decision, requirement and promise connected — so the next question, the next meeting and the next project all start from what you already know.
14 days, no card. Add a document and ask your first question.
What it reads
Documents, transcripts, decisions, notes
What it says
Every claim traceable, gaps named
Where it runs
EU, Amsterdam
What it costs
€29 / month
Different titles, same job: you were in the meeting, you remember what was agreed, and everyone comes to you when the document doesn’t say. Hour 0 takes that weight off you and puts it somewhere it can be checked.
Compounding memory
Six months ago you connected the first booking channel. You worked out which system owned the reservation ID, where the status had to land, what broke in UAT and why the first approach was abandoned.
Now the same work starts again with a different channel. The knowledge exists — in a transcript, in a document, in a decision someone recorded on a Tuesday.
Ask Hour 0.
Ask this project
How did we handle the reservation ID last time, and what would you do differently for this one?
The reservation ID was owned by the channel integration service, not the property system — that was decided after the first approach put it on the room record and broke the nightly audit in UAT.
Status updates landed on the reservation record on a five-minute sync. Live push was considered and dropped on cost.
Left unresolved: who owns retries when the channel feed fails. Raised on 12 Jun, never decided.
It answers from the project record, points you to the document or meeting each part came from, and tells you what was left unresolved — which is usually the part that bites twice.
Project A
Channel one. Decisions, transcripts, the approach that failed UAT and why.
The project record
Searchable, cited, and honest about what it never settled.
Project B
Channel two. Starts from what channel one already taught you.
Every project you run makes the next one faster. That is not a summary of your meetings. That is an organisation’s memory, held by one person’s tool.
In the meeting
Ask anything, mid-meeting
Type a question and get an answer without asking the room.
“What’s a channel manager, and why would we sync on a schedule instead of live?” “What did we agree about the cancellation window?” “Is this in scope?” You stay in the conversation; you just stop having to bluff.
Ask now
“Which system owns the room-status list?”
Because a decision is about to be made without it.
Capture
“Billing starts at check-in, not at booking.”
Someone said it in passing and nobody wrote it down.
Watch
“This contradicts the refund rule agreed on 12 June.”
From a transcript three weeks old that nobody in the room remembers.
A note-taker records the meeting. You still find the problem at seven in the evening, reading a transcript, after the decision was made.
Hour 0 reads what is being said against everything the project already knows — every document, every earlier call, every saved decision — and speaks up while there is still time.
In one real meeting, Hour 0 caught two requirements that could not both be true. Nobody had noticed. The conflict was not in anyone’s memory — it was in a call from three weeks earlier. The difference is not that it was listening. It is that it had read everything else first.
Ask anything, mid-meeting
Type a question and get an answer without asking the room.
“What’s a channel manager, and why would we sync on a schedule instead of live?” “What did we agree about the cancellation window?” “Is this in scope?” You stay in the conversation; you just stop having to bluff.
Ask now
“Which system owns the room-status list?”
Because a decision is about to be made without it.
Capture
“Billing starts at check-in, not at booking.”
Someone said it in passing and nobody wrote it down.
Watch
“This contradicts the refund rule agreed on 12 June.”
From a transcript three weeks old that nobody in the room remembers.
Meeting prep
Before the meeting
Not a summary of everything. The four things you need in the next hour: what was decided, what is still open, where the conflict is, and what to ask.
Morning digest
Hour 0 looks across your projects and gives you the things worth knowing today — what happened, what you’re waiting on, and what to follow up. You pick the hour it’s written for.
No feed to clear. No notification pile. Just the things that still matter.
What happened
Channel integration spec landed Thursday, with two questions open on it.
Waiting on
Refund rule sign-off from Finance — asked 12 Jun, no reply yet.
Waiting on
Channel integration spec from the vendor — promised Tuesday, due today.
Follow up
Confirm which rate plans late checkout applies to.
Tuesday · in the meeting
“I’ll send the channel integration spec over by Friday.”
Captured — nobody typed anything.
Friday · waiting on
Channel integration spec — still waiting, promised Tuesday.
Follow-ups
Someone says they’ll send the integration spec by Friday. Hour 0 hears it in the meeting and turns it into a dated follow-up — reading “by Friday” as an actual date.
Friday morning, it’s in your digest: still waiting, promised on Tuesday.
This is project memory, not a task manager. The promise gets caught inside the conversation, where it was made — rather than waiting for you to remember it, open a list, and type it in.
Numbered requirements, each traced back to the document or meeting it came from, and a section listing exactly what is still missing. Export to Word. Send it.
| ID | Requirement | Source |
|---|---|---|
| FR-04 | A booking made through a partner channel shall not be editable at the front desk after check-in. | Whisper session, 12 Jun |
| FR-05 | Guests on a corporate rate shall be excluded from automatic room upgrades. | Channel integration spec.docx |
Missing: maximum group size for a single reservation not defined.
Stakeholders don’t read a forty-page requirements document. Hour 0 turns the same project record into slides — what changed, why, who it affects, what happens next — with a version for the people who need training and a shorter one for the people who only need to know. Export to PowerPoint.
Who’s affected, and from when
Not covered by the project record: rollout order across properties.
That’s the overview — if you only needed to know what’s changing, you can stop here.
Neither invents anything to look finished. If the record does not cover it, the document says so — which is the part your stakeholders should be reading.
A confident wrong requirement does not get caught in review. It gets built.
Hour 0 shows the source behind every claim, separates what your documents say from what it infers, and when your project record does not answer the question, it says so instead of filling the gap.
“Not in this project’s record. I’d rather tell you that than guess.”
Today Hour 0 is one person’s working memory, and it is deliberately good at that. But a project record that is traceable, searchable and honest about its gaps is exactly what a team needs when the analyst is on holiday, when the project changes hands, or when someone new joins and asks why.
Shared projects are what comes next. Everything you put in now carries over.
Pricing
Fourteen days to try it, with no card. Then one plan, everything included — no per-seat tiers, no feature gates, no sales call.
€29per month
14 days, no card. Add a document and ask your first question.
Buying for a team, or need paperwork before you can start? Say what you need and you will get a straight answer from the person who builds it.
Cancel whenever you like — it takes effect at the end of the month you have already paid for.
Security
The answers, in the same words as the privacy page — which is the longer version, with nothing held back.
Hour 0 stops you having to hold all of it in your head.
Start 14-day trial — no card14 days free, no card. €29 a month after that. No sales call.