What's going on around you, matched to what you actually asked for.
Local life lives in PDF newsletters, WhatsApp groups and chalkboards, invisible unless someone tells you. Step Out puts it on one board, matches it to a plain sentence about your situation, and notices what people keep asking for that doesn't exist yet.
Three things to see, in order. Each step runs its example for you, and a floating chip carries you to the next.
Open the board and tell it your situation, like a neighbour would: โI've just moved here and barely know anyone, I'd love something regular near me.โ Ranked matches come back, each with a specific reason, and it answers in your language: tested in Bengali and Somali, the languages of the venue's own neighbourhood.
Start at the board โ 2Now ask for โa running group, mornings, before work.โ There isn't one. Instead of a dead end you get a demand card: widen, connect, create, inform. The engine behind it lives on the Demand page.
Fire the demand card โ 3Drop a photo of a noticeboard, or a whole PDF newsletter, onto Snap. Structured entries fall out, with personal contact details stripped to roles and anything date-stale flagged for re-checking.
Snap a flyer โThe pages where the product loop actually runs: browse it, ask it, feed it. Hosted copies open in demo mode with sample responses, and the banner on each page links the live version.
The hackathon's own neighbourhood: real entries pulled from this month's community newsletter, each with a named source, and the live matcher on top of them.
Start here โOne engine, any place. Flip between the saved boards, or sketch a board for your own neighbourhood, loudly labelled until a human verifies it.
Open โDrop a photo of a chalkboard or a PDF newsletter and proposed entries fall out, roles only, stamped for re-verification.
Open โYour matches as a journey instead of a list, the same results ordered and colour-coded by what each step is for.
Open โWhat this could grow into. Real data and real model outputs where labelled, but these are sketches of the product, not the product.
The loop behind the โ4 people askedโฆโ card: unmet asks get logged, cluster by need, and become demand cards with honest counts.
Open โThe freshness loop: the people who run things confirm their own entries, so the board stays true without a central maintainer.
Open โThe pocket form, same product, phone-shaped. The interface is a mock-up; the responses in it are real outputs from the build afternoon.
Open โTheme three of the brief asked how AI could expose opportunities locally instead of centralising them. The walk that led to this answer, the plan going in and what I'd do differently are in the writeup โ.
Exactly what existed at the freeze is kept, never edited: browse the frozen hackathon build โ