Fortune

About Fortune

Fortune is a private travel calendar for iGaming professionals. Mark which conferences you're attending. See who from your network overlaps with each trip. Plan real catchups, not guesswork. Closed beta, opening Q3 2026.

Hi — I'm Pavlo. You know the routine: a week before every show your LinkedIn is a wall of "Meet me at SBC"graphics, your WhatsApp lights up with intros and pitches, and half of it goes nowhere. Your calendar fills anyway — in iGaming it always does. The problem isn't finding meetings. It's knowing which of your actual friends is even in town before everyone's overbooked.

Because the meetings that matter aren't the cold ones. They're the dinner with someone you've already done a deal with. The coffee with a friend who introduces you to the right person. The catch-up that turns into the next deal.

Fortune doesn't replace your conference calendar. It's a side-layer for the people who matter — your real friends, on top of everything else. They mark the trips they're taking. So do you. Where you overlap, you see it before the week is sold to pitches.

One missed coffee can cost you a Fortune.

That's not a metaphor — it's why the thing is called what it's called.

Same trick works for the side-events. Every season half a dozen vendors host their own dinners, parties, lunches around the main show — and everyone's asking everyone "are you going to the BetConstruct dinner? what about the SoftSwiss yacht?" Tedious. Drop it into your RSVP note once — "hitting BetConstruct Tue, skipping the rest" — and any friend going to the same conference sees it. The "are you going?" round of WhatsApps just stops.

One thing to be honest about: there's no autofill here. The first day, you'll send 10–20 invite links to the people you actually want to see at the next show. That part is manual — and intentionally so. No address-book scraping, no "people you may know", no spam. It's a one-time effort. After that, every season just gets richer: new trips show up, overlaps appear, side-events get visibility, you start planning around them instead of guessing.

One more thing. Fortune isn't really a calendar app — it's a calendar that lives inside your Claude. Connect it once, then stop opening tabs. "Who's at SBC Lisbon? Who's at the BetConstruct dinner? Mark me Going to ICE. Draft Elena a coffee message." All in chat. The web UI is the dashboard for when you want it; the Claude side is the daily driver.

That's why "AI" is in the name. Fortune is built for the moment software stopped being screens and started being tools your AI calls on your behalf. iGaming friends are just the first cohort.

Coffees, not check-ins

Every season ends the same way: you flew to four cities, shook a hundred hands, can't remember who you actually spent real time with. Fortune lets you confirm the meetings that happened — one tap on the past event, or a magic-link in the day-after email. Those add up to a personal coffee log and a year heatmap on your settings page. It's yours; friends only see it if you leave the switch on. No badges, no leaderboards, no streaks.

A profile your friends can act on

Three optional fields — bio, looking for, offering— visible only to direct friends. The use case is the warm intro: your friend opens your page, spots that you're looking for a DACH regulator contact, and remembers they know one. Or your Claude does that sweep across your friend graph and surfaces the match. Either way the intro happens through a mutual — Fortune never recommends strangers.

Side-events, not just main floors

Conference week isn't one event. NEXT Summit Valletta has a golf tournament, two networking dinners, an affiliate focus track. ICE has the EGR awards, the Eurogamer roundup, the Fire & Ice party. Fortune catalogs them as side-events nested under the parent — you see the whole week in one place. A friend RSVP'd to the golf still counts as a coffee opportunity on the main summit.

What Fortune doesn't do

Sends nothing on your behalf to anyone else. Every message to a friend is a client-side intent (wa.me, t.me, mailto, Google Calendar, .ics) — you press send in your own app. Fortune itself only emails you transactionally — the weekly “On the road” digest, T-7 reminders, and a post-event “did you meet anyone?” recap. All gated by Settings → Notifications; one switch turns them off.
Doesn't auto-import contacts. No Gmail, Google Contacts, or LinkedIn pull. Every friendship is created by an explicit invite link the other party clicks.
Doesn't train on your data. Fortune ships no in-app AI of its own. The intelligence comes from the LLM you connect via MCP — your Claude account, your ChatGPT, your Cursor.
Doesn't sell or share data. No advertisers, no brokers, no affiliates. See /privacy for the full list.
No public profiles, no search. You can't look people up. Friends are added by link only.

MCP server

One endpoint, OAuth 2.1 + Dynamic Client Registration. Authorised clients get a 90-day Fortune-signed JWT; revoke from Settings → AI any time.

https://www.getfortune.ai/api/mcp

Claude

Every tier
  1. Open Settings → Connectors
  2. Click Add custom connector
  3. Paste the URL above

ChatGPT

All tiers
  1. Settings → Apps → Advanced settings
  2. Toggle Developer mode on
  3. Add more → Add custom app, paste URL

Tools the LLM can call

  • list_eventsCatalog of upcoming iGaming conferences with the user's RSVP status. Side-events are nested under their parent by default.
  • search_eventsSearch the catalog by name or city.
  • get_eventFull event detail — venue, organiser, friends going, parent event and side-events.
  • my_attendancesEvents the user has marked Going / Maybe / Declined.
  • set_attendanceSet or update an RSVP, with optional free-text note.
  • delete_attendanceWithdraw an RSVP.
  • list_friendsThe user's connections, with last-met and next-overlap context.
  • find_overlapFriends going to the same event(s) as the user. Includes side-event inheritance — a friend on the conference dinner shows up as overlap on the main summit.
  • upcoming_catchupsNext events where at least one friend will be.
  • confirm_meetingLog that the user actually met a friend at a past event. Feeds the coffee counter and heatmap.
  • unconfirm_meetingReverse a confirm_meeting call.
  • list_my_coffeesAll (event, friend) pairs the user has logged as a meeting. Filterable by year.
  • get_my_intentRead the user's friend-visible profile fields: bio, lookingFor, offering.
  • set_my_intentUpdate bio / lookingFor / offering. These broadcast inside the user's direct-friend graph so friends can spot warm intros.
  • get_my_invite_linkUser's permanent invite URL plus pre-built share links.
  • get_my_preferred_contactRead the user's preferred-contact handle.
  • set_my_preferred_contactUpdate the user's preferred-contact handle.
  • clear_my_preferred_contactRemove the user's preferred-contact handle.
  • get_notification_preferencesRead the user's email cadence — off / weekly / daily.
  • set_notification_preferencesChange the email cadence — 'mute Fortune for two weeks' style asks.
  • draft_messageBuilds a share-intent payload (WhatsApp / Telegram / mailto) for messaging a friend. The LLM drafts the text; the user sends it.
  • add_event_to_calendarReturns a Google Calendar template URL for a specific event.
  • draft_followup_emailReturns a mailto: URL builder for a friend, used after events.

Constraints we ship under

Single-user accounts — no teams, orgs, or shared inboxes.
Friends-only visibility — there is no public mode in v1.
RSVP notes are visible to the user, to the LLM they've connected via MCP, and to friends who RSVP'd Going to the same event — so a friend can plan around the practical stuff ("Tue–Wed only, NH Centro", "Free Wed evening for dinner"). Anyone outside that overlap never sees them.
Two-degree connections aren't modelled. We'll never recommend friends-of-friends. If they're not connected to you, they're not in your view.

Stack

Next.js + Supabase (Postgres) + Clerk for auth + Resend for email + Vercel for hosting (eu-central). MCP server uses @modelcontextprotocol/sdk. Built almost entirely with Claude Code — pair-programmed end-to-end. More detail in /llms.txt.

Contact

hello@getfortune.ai. One inbox, real replies.

Pavlo Agoshkov
Pavlo Agoshkov
CEO, Playtagon
Fortune Builder