Discussion Doc · GBX Global

Ideas for What's Next

Phase 1 is done and stable — messaging, the directory, events, benefits, all live. This is a working list of where the app could go next, to talk through and prioritise together.

Prepared for  GBX Global Prepared by  MazeSpace Studios LTD Last updated  22 September 2026

Nothing Here Is Built Yet

Everything below is a proposal, not a commitment — the point of this page is to give us a shared list to prioritise from on our next call, not to lock anything in.

The Headline Idea

Biggest opportunity

"Who should I talk to?" — a real search over the whole directory

Instead of browsing or filtering, a member types a plain question — "who's raising a seed round in fintech," "who can help with a US visa" — and gets back real people, ranked by relevance, not just a keyword match.

Why this is the natural next step, not a new direction: the database was deliberately built on Postgres with a feature called pgvector from day one, specifically to leave room for this. And the "About," "Looking for help with," and "Happy to help GBxers with" fields already added to every profile exist for exactly this reason — they're the raw material a search like this reads from.

In plain terms: most of the groundwork is already sitting there, unused. This isn't starting from zero.

It could also start chipping away at the WhatsApp group's role as the default place people ask "does anyone know someone who...?" — the group works, but it's ephemeral and nothing in it is searchable later. A "who should I talk to" box in the app is the same instinct, done in a way that's discoverable and doesn't rely on the right person happening to see the message at the right moment.

Events, Extended

Confirmed feasible

See who's going, before you go

Right now an event page shows the event itself — date, location, a link to register on Luma. The idea: also show which GBx members are already attending, with a way to message them directly, before the event even happens.

ASDPJQ
12 GBx members are also going to this event

Decided so far, from talking it through:

Checked, not assumed

Luma's API already has an endpoint for exactly this — the list of approved guests for an event, with name and email — on the same access level already used for the existing event sync. No new agreement with Luma needed to build this.

Also On The Table

Other directions worth weighing up

Less developed than the two above — flagged here so nothing discussed gets lost, not fully scoped yet.

Next Step

Talk through this list together, pick what matters most, and turn the winners into a real scoped plan — the same way every phase of this project has worked so far.

See Project Progress for everything already built.