Conpass, an event radar for founders deciding which events are worth a day
Early access. Being built now. Request early access on the Conpass site.
Conpass is designed to watch registered event sources near a founder's home base, rank what it finds, and explain each pick in one sentence.
Last reviewed
What works today and what is not there yet
Works today
- A private deployment that Verne uses itself.
- A capture playground that reads a pasted post with rules only, using fictional events, and stores nothing.
- A browser extension, built and loaded unpacked, that has not been tried against the live system.
Not there yet
- Quality is unmeasured. The test set is empty, so there is no miss rate, lead time or precision figure to quote.
- Digests and alerts, which do not deliver yet.
- The learned ranking model, which is not active. Ticket-drop timing is untested.
- Multi-user hosting, which is not scheduled.
What Conpass is built to do
- You miss the moment tickets go live.
- Built to watch a ticket page every five minutes, from two hours before release to six hours after.
- You hear about a meetup after it has happened.
- Designed to sweep registered sources on a schedule and send a daily digest.
- The ticket price is not the real price.
- Designed to add travel, lodging and the workdays lost at your own day rate.
For your engineers
- Structured data first and AI last, with a daily and a monthly spending cap.
- Nothing unchecked becomes an event, and every pick carries its reason.
- Its crawler, ConpassBot, follows robots.txt and says who it is.
- Facebook and LinkedIn arrive only through your own capture. Meetup, Eventbrite, Reddit, X and Telegram are not sources.
- Sites behind Cloudflare challenges give degraded results, and travel costs are static estimates.
- Precision beats recall, so it will miss events.
Ask for a Conpass walkthrough
We show a ranked list built from fictional events and explain how the scoring is designed to work.