The Activity tab#
The Activity tab records what happened during a test and the studio's time, in one place. Its top bar switches between two forms — Log event and Log hours — and below them is one timeline of everything logged, newest first. On the right, Hours by stage totals the time.
Logging an event#
Choose Log event, fill in the fields and click Add. You return to the tab with the toast "Event added".
| Field | What to enter |
|---|---|
| Type | Conversation (a qualified conversation or a Cal.com booking), Objection (a reason a buyer gave for not buying), Pilot commitment (a signed pilot), Deposit (a paid Stripe deposit), Revenue (money received) |
| Amount (USD) | Optional; for deposits and revenue. A number with up to 2 decimals |
| Date | When it happened; defaults to today |
| Note | Who and what, briefly |
Cal.com bookings and Stripe deposits are not received automatically: log each one here. Events feed the evidence (conversations, commitments, deposits).
Page change is not in the list: the platform writes it automatically, with your reason, when you republish.
Logging hours#
Choose Log hours, fill in the fields and click Add. Toast: "Hours added".
| Field | What to enter |
|---|---|
| Stage | intake (assessing the application), test (running the offer test — the default), demo (building a demo), pilot (running a pilot) |
| Hours | A positive number, up to 2 decimals (1.5) |
| Worked on | The day; defaults to today |
| Note | What the time was for |
Under the form, a line tells you whether demo and pilot hours are accepted:
- Amber: "Demo and pilot hours are refused while N risks are open: …", naming them. Clear or accept each (below), then log the hours again. A continue verdict does not lift this gate.
- Aqua: "All risks resolved. Any stage is accepted."
Hours are recorded against the admin operator. Intake and test hours count against the offer-test cap. The platform tracks hours but never computes a payout or balance: the hourly rate lives in the collaboration agreement.
Experiment 000 has no risks, so recruitment hours of any stage are accepted there.
The timeline#
One list of events and hours together, newest first. Each line shows the date, a coloured square and the kind, the note, and the amount or hours:
| Square | Kind |
|---|---|
| Blue | Conversation |
| Red | Objection |
| Aqua | Pilot commitment, Deposit, Revenue |
| Amber | Page change (from a republish) |
| Grey | Hours · intake / test / demo / pilot |
Hours by stage#
Totals for intake and test ("Counts to cap") and demo and pilot ("Gated by risks").
The Risks tab#
An offer test proves demand, not that the product can be built legally and reliably. The Risks tab lists each feasibility risk from the brief as a card, with its check, its status and any note. A banner at the top says whether the gate is closed ("N open · demo and pilot hours are gated") or clear.
To resolve an open risk:
- Run the check it names.
- In its card, write a note (required — what you found, or why you accept the risk).
- Click Mark cleared (the check passed) or Accept risk (you will proceed despite it). Toast: "Risk cleared" or "Risk accepted".
A resolved risk shows its status and note and cannot be reopened here; edit it in the brief if needed. Open risks never block publishing, and they never appear on the page. To add risks, use the Feasibility risks fold in the Brief editor.