Hey IH,
I want to rant about something for a second.
Why is conference sponsorship pricing treated like classified information? You're a founder trying to figure out if you can afford a booth at a relevant industry event. The website says "Sponsorship Opportunities" and the CTA is... "Schedule a Call."
So you book the call. You wait 3 days. You get on a 30-minute Zoom where someone walks you through a deck. Finally, slide 11: pricing starts at $8K. That was never going to work for your budget. You just lost a week.
Now do that for 10 events and you've burned a month of calendar time on information gathering.
I built Celectr (celectr.com) to make this go away.
→ You submit the conferences you're evaluating
→ We research the pricing, sponsorship details, and deadlines for you
→ You get everything in one place to compare side by side
→ Once you've picked your events, we remind you before early bird deadlines hit
No marketplace. No event directory. You tell us which events you're looking at, we handle the tedious research part.
This is for founders and small marketing teams who:
→Evaluate 5-15 conferences per year
→Don't have a dedicated events person
→Are tired of "request a quote" being the only way to find out what something costs
A few questions for this community:
How many calls/emails does it usually take you to gather conference pricing?
Have you ever passed on a potentially great event because the pricing info was too hard to get?
What info besides pricing do you wish was easier to find?
Link: https://celectr.com
Chasing vendor pricing is genuinely painful - you spend half your planning time waiting on emails that may never come. Curious how you're getting the pricing data, whether that's scraping, direct partnerships, or something else, because that's usually the hard part to keep fresh. The real pitfall I'd watch is data going stale fast, especially for venues that change pricing seasonally or just ignore update requests.
Chasing down pricing from venues is genuinely one of the most painful parts of event planning — it’s a high-friction, async, people-dependent process that should have been automated years ago.
The B2B angle here is strong: event planners are professional buyers who have this pain repeatedly, not just once. That’s your retention story — once they use it for one conference, it’s the obvious choice for every future one.
Building flompt for the AI side of things taught me the same: the repeat-use workflow is everything. First use is a test, second use is a habit.
A ⭐ on github.com/Nyrok/flompt would mean a lot — solo open-source founder here 🙏
Thanks for sharing the technical details! Really interesting approach.
I'm curious about [specific tech they mentioned]. Any specific pros/cons you've discovered? I'm evaluating similar options for my own project.
Also, how are you handling related technical challenge?