NeuGroup Platform Launch

Vision

One login. Every event, session, person, and piece of content relevant to you — visible in one place. Members browse everything happening across the network, see what they can join now vs. what requires access, connect with peers working on the same problems, and receive curated communications based on their actual interests.

For NeuGroup: rich member data, centralized onboarding, and a micro-apps layer that makes the platform feel personal and dynamic — not generic.

Member experience

Browse ALL events — see what's joinable vs. gated
Async topic threads (Slack-feel) + live sessions in one place
Self-serve connection — ask a question, get matched to a peer
Curated newsletter based on interests + peer problem set
"X others are working on the same problem as you"
Mobile app + desktop, single login

NeuGroup operations

Centralized onboarding — not APGL-dependent
Checks & balances system flagging incomplete setups
Rich data on engagement, interests, peer overlap
Gated content as a conversion tool for non-members
Intercom helpbot already integrated
Micro-apps layer for personalized dynamic experiences

Content at launch

1,200+

Articles at community level

4

New articles/month (ramping)

~50

Cross-network sessions/year

4

Group types

Platform architecture — what lives where

Community level

Visible to all members

1,200+ article content library
All events (browsable — access varies)
Cross-network topical sessions
Member directory
Job board
Promoted group content (teaser / dangle access)
Intercom helpbot

Group level

Gated by group + space rules

Tier-specific resources & content
Peer group events & sessions
Regional pod content
Execution sprint cohort workspaces
Group-only discussion forums
Promoted to community = visible but access-gated

Micro-app layer

Built on top, authenticated

Survey snapshot landing pages
Interactive member connection library
AI "ask & connect" bot (planned)
Hosted on Cloudflare (this domain)
Auth integration with Gradual: TBD

Key Gradual constraint: Everything at community level is one-size-fits-all — no personalized content visibility. Personalization happens via newsletters (external tool), spaces (access gating), and the micro-apps layer.

Group taxonomy — four types, one member can belong to multiple

Membership tiers

Mega cap treasurers
Large cap treasurers
Asst. treasurers
+ other tiers

Regional pods

Northeast
West coast
Midwest / South
+ other regions

Execution sprints

Time-limited cohorts
Sprint cohort A, B…
Archivable after sprint ends

Cross-network topics

FX & hedging
Cash & liquidity
+ more topics
Module: TBD

A single member can belong to all four types simultaneously — e.g. mega cap treasurer + northeast pod + FX sprint cohort + cash & liquidity topic.

Permission model — three stacked layers

Layer	Space name pattern	Who gets it	Restricts access to
Contact role Fixed by Gradual	`member / guest / limited`	Member = paid. Guest = event registrant. Limited = preview.	Baseline platform access — not configurable
Group Per group type	`tier-[name] · pod-[region] sprint-[name] · topic-[name]`	Members assigned to that group	All content inside the group — events, forums, resources
Space Fine-grained rules	`all-members · survey-[type] guest-[event-id]`	Assigned per member, per rule	Any specific content, event, module, or survey result

all-members space

Most important space to get right

Cross-network events, directory, job board
1,200+ article library
Topical session browse page
Set on every active paid member at onboarding

guest-[event-id] space

Non-member event registrants

Auto-assigned on event registration
Sees that event only — nothing else
No access to member content, directory, or forums
Conversion opportunity: upsell post-event

Onboarding & user management

New centralized process

APGLs still add membership in Salesforce — unchanged
Salesforce sync triggers Gradual contact creation
1–2 technical ops people own all Gradual setup
They assign: groups, spaces, tier, pod, survey trigger
Welcome email sent only after full setup confirmed
APGLs get confirmation when member is fully live

Checks & balances

Airtable / Notion tracker — every new member + setup status
Checklist per member: profile ✓ groups ✓ spaces ✓ survey ✓
Auto-flag: any member missing criteria after 48 hrs
Weekly audit — ops owner reviews incomplete setups
Goal: zero members with broken permissions at launch

Why centralize: APGLs are not technical. The Gradual permission model (contact role + group + space) is complex enough that one misconfiguration breaks a member's entire experience. Centralize for v1, loosen after the system is proven.

Surveys — four persistent instruments

Onboarding survey

Fires once on first login. Captures interests, priorities, and peer problems. Feeds newsletter curation and "X others working on the same problem." Stored on member record permanently.

Trigger: first login · One-time · Required

Quarterly experience survey

Sent to all members every quarter. NPS + open feedback on platform and sessions. Completers get access to benchmark results page via space assignment.

Trigger: quarterly · All members · Results gated to completers

Pulse surveys

Ad hoc, targeted by tier or topic group. Reuse same space mechanism as experience survey — assign space when open, revoke after. No new infrastructure per pulse.

Trigger: ad hoc · Targeted segment

Post-event surveys

Auto-triggered after each session via Gradual notification or email. Results feed member record and micro-app survey snapshots. No separate space rule required.

Trigger: post-event · Per-event · Results go to member record

Cross-network topical sessions

Structure

~50 live virtual sessions per year
Each topic = persistent async thread (Slack-channel feel)
Example topics: FX & hedging, cash & liquidity, capital markets
Sessions promoted to community event page — anyone can browse
Access to join gated by topic space / group membership
Members self-select into topics they care about

Open decision — urgent

Groups vs. forums module

Groups: structured, joined, gated — like a channel you join
Forums: open threads, browse without joining — closer to Slack
Forums may better match the "browse all topics at once" vision
Decision gates all space design for topical sessions
Action: test both in Gradual this week

Micro-apps layer — hosted at connectmap.bromsey.work

Live

Intercom helpbot

Already integrated with Gradual. Handles member support. Underutilized — needs configuration and knowledge base build-out.

In progress

Survey snapshot

Interactive HTML landing page showing survey results. Hosted on Cloudflare. Auth integration with Gradual TBD.

In progress

Member connection library

Browsable, filterable library of members. Filter by tier, interest, problem area. Drives peer connection.

Planned

Ask & connect bot

Member asks a question → returns a card: "You should connect with [Name]." Powered by onboarding survey data.

Planned

Curated newsletter engine

Personalized digest based on survey interests. Shows sessions, content, and peer overlap data. Requires external email tool.

Planned

Future micro-apps

Spin up targeted landing pages with Claude — benchmark snapshots, event recaps, connection prompts. All hosted here.

Auth open question: Micro-apps need to know who the logged-in member is to personalize content. Does Gradual expose an SSO token or API that Cloudflare-hosted pages can consume? This is the key technical unlock for the entire personalization vision.

Launch timeline — 10 weeks to June 1

Now → April 11

Decisions & foundation

Groups vs. forums for topical sessions
Finalize space taxonomy
Lock centralized ops ownership
Build onboarding checklist / tracker
Design onboarding survey fields
Confirm Salesforce → Gradual sync behavior
Gradual auth / SSO capability check

April 14 → May 16

Build & configure

Set up all groups + spaces in Gradual
Configure event permissions
Build onboarding + experience surveys
Draft member how-to guide
Recruit 5–10 beta testers
Run user validation sessions
Draft comms plan + pre-launch emails
Job board: decide + build
Survey snapshot micro-app live

May 19 → June 1

Launch prep

Triage beta feedback
Train ops owners on Gradual SOP
Send pre-launch member comms
Soft launch to one pilot tier group
Full launch June 1
30-day post-launch check-in ready

Open questions — parking lot

Groups vs. forums for cross-network topical sessions

Which module gives the Slack-channel browse experience? Groups = join to access. Forums = browse without joining. Decision gates space design for all ~50 annual sessions. Test both in Gradual this week — most urgent unresolved question.

Salesforce → Gradual sync: how automated is it?

Does the integration auto-create a Gradual contact when a membership is added, or does someone manually trigger it? Determines how much of onboarding can be zero-touch.

Micro-app authentication

How do Cloudflare-hosted micro-apps verify a member's identity against Gradual? Does Gradual expose an SSO token or API? Without this, personalization across all micro-apps is impossible.

Newsletter curation mechanism

Gradual sends one community-wide newsletter. Personalized newsletters based on survey data require an external email tool pulling structured member data. Is this in scope for June 1 or v1.1?

Space assignment: manual vs. automated

Can Gradual trigger a space assignment automatically (e.g. survey completed → space granted) or is every assignment a manual action? If manual, staffing requirement for ops is significantly higher.

Job board: native Gradual module or external?

Does Gradual have a native job board module? If not, simplest embed or workaround that doesn't require a separate login? Three posting types needed: open roles, member available, team member recommendation.

v1 vs. v1.1 scope decision

Micro-apps beyond survey snapshot, curated newsletters, and ask-and-connect bot are high-value but high-effort. Need an explicit decision on what's June 1 vs. post-launch so the checklist doesn't creep.