Booking the stand on a feeling
Nobody checked whether one person worth meeting is in the room. The invoice arrives anyway, and the debrief is about the coffee.
Marketevents
Events
Judge attending, exhibiting and speaking separately, before you book.
An event record holds the title, the start date, the location, the attendee list, the stated cost and your participation. Planning reads six signals from our own records and judges the three ways of showing up on their own terms, because a stand is paid for before anybody walks past it. Afterwards you write what happened and compare it to what you expected.
- 3 ways of showing up, judged separately
- 6 signals read from our own records
- 4 figures you type, none of them measured for you
4 of 5 in Market
In the workspace
The pages this covers
The problem this solves
What goes wrong when this work lives in spreadsheets, documents and one person's memory.
An empty form read as a bad result
Nothing modelled yet is a different answer from not worth it. The page lists the figures it is missing instead of scoring you zero.
Numbers mined out of a paragraph
Nothing reads figures out of your outcome prose. You type the observed figures yourself, next to the ones you expected.
In the app
What it looks like
Captures of Growth-OS itself, rendered with sample data rather than our own records.
How it works
From an empty record to something you can act on, in the order you do it.
- 1
Create the record
Title, start date and participation set to considering. Everything else can follow.
- 2
Write what you know
Location as your records name it, attendees one per line, and the cost the event itself states.
- 3
Open planning
Filter by participation, pick an ICP revision, read the three verdicts, and expand the signals behind each one.
- 4
Model it, then close the loop
Cost, expected qualified conversations, conversation to deal rate, value of a won deal, and a currency. After the event, write the outcome and type what actually happened.
Highlights
Why it matters
Attendees are matched line by line
One name per line, each matched on its own against company titles and domains. Lines that match nothing are listed rather than dropped.
Six signals with the counts behind them
ICP density among recorded attendees, accounts we already track, competitors we hold a card for, partners, whether records name the location, and whether an objective or bet exists.
The retrospective compares like for like
Once you write the outcome, expected and observed appear in the same four terms, with two lists: what it lets you change, and what it does not let you say.
Honest limits
What this does and does not promise
Growth-OS has measured none of those four figures. There is no attendance data, no conversion rate and no deal value behind them, and the numbers live on the page rather than on the event record.
Partners reads unknown permanently, because no record kind stores a partner relationship. It is excluded from every verdict rather than counted as a miss.
Questions
Frequently asked questions
Used alongside this
These pages share records with this one, so what you write here shows up there.
Do this work in Events
The page opens on this project's records. The in-app guide describes every field.