NextLevel Website Call — Launch Planning & User Flow Review

Date: 2026-01-19
Client: ^[1]
Attendees:
- Karly Oykhman (Asymmetric)
- Melissa Cusumano (Asymmetric)
- Mark Hope (Asymmetric)
- Peter Tourville, NLP Wealth Management (external)
- John Jonas, NLP Wealth Management (external)

Overview

Working session to walk through the new FWDR website's user registration flow on the staging environment, confirm the February 2nd soft launch target, finalize branding decisions, and define reporting and Salesforce integration requirements. The meeting covered a live demo of the signup-to-event-registration flow, email delivery concerns, domain and logo selection, resource library planning, ongoing maintenance scope, and the need for automated signup reporting.

Key Decisions

Action Items

Karly Oykhman (Asymmetric)

• [ ] Fix signup page layout/styling issues observed during demo
• [ ] Schedule 10-minute GoDaddy 2FA session with John to switch domain to finwellu.com
• [ ] Send staging site link and draft copy to Peter and John; implement approved copy once received
• [ ] Draft RetireU vs. ThriveU resource mapping; send to John and Peter for approval
• [ ] Replace site logo with approved Logo D variant
• [ ] Design and implement reporting for name, email, and in-person/virtual status; build automated roster delivery
• [ ] Implement in-person event capacity counters to prevent overbooking
• [ ] Confirm ongoing maintenance scope and pricing; send proposal to Peter and John
• [ ] Investigate automated reporting solutions for launch and long-term Salesforce integration path
• [ ] Send next meeting date options to Peter and John; schedule full site sweep before launch

John Jonas (NLP Wealth Management)

• [ ] Compile and send resource links (calculators, SSA, Medicare) to Karly
• [ ] Send top 10 company list (including Eric/Jacob/Paul schedules, with URLs) to Karly
• [ ] Coordinate with Paul on email reply-to strategy (centralized vs. rep-specific)

Peter Tourville (NLP Wealth Management)

• [ ] Review and approve website copy once staging link is received
• [ ] Consult Paul re: reply-to address; then finalize event-created notification email

Topic Notes

User Registration & Workshop Signup Flow

A live demo was conducted on the staging site. The flow is:

1. User visits the site and navigates to the registration page
2. User enters username, first/last name, email, company website URL, and password
3. System matches the company URL to an existing company profile
4. Confirmation email is sent with login link and password reset option
5. User logs in and lands on their company-specific page showing available events
6. User clicks an event, reviews details, and registers — form auto-fills from their profile
7. Event-specific confirmation email is sent

Individual logins vs. shared login: The team had previously discussed a single company-wide login. After WordPress troubleshooting, individual logins were determined to be the better approach — they enable personalized tracking and pre-filled registration forms.

Email delivery concern: A test email to Peter's LPL address was delayed due to LPL's corporate firewall and Microsoft quarantine system. Melissa flagged that proper SMTP configuration will be needed at launch to maximize deliverability through corporate email environments.

Branding & Content

Rebrand: The site is moving from the internal "Next Level" project name to the public-facing brand "Financial Wellness Done Right" (FWDR). Peter emphasized that all references to "Next Level" must be removed from the site, emails, and confirmations before launch.

Naming convention: "Financial Wellness Done Right" is the full brand name; "FinWellU" / "finwellu.com" is the shorthand used for the domain and casual reference. Both will coexist — the shorthand is easier to say in HR conversations.

Email templates — required overhaul:
- Add FWDR logo and branding
- Replace generic "success" message with a hype/welcome message and clear CTA to register for a workshop
- Include language encouraging users to save the email as their master login reference
- Event-specific confirmation emails must support dynamic content:
- Virtual events: include join link
- In-person events: include location/room details (e.g., "Conference Room C, 3rd Floor" or a street address)

Resource library: Will be split into two buckets — RetireU (retirement-focused) and ThriveU (younger professionals). Content will include workshop listings plus external links (calculators, SSA, Medicare, company benefits pages where permitted). Karly will draft the initial mapping for client approval. John will compile specific resource links. Peter noted this is lower priority for launch.

Company pages: NLP Wealth Management has 114 companies in their system. For launch, John will provide a prioritized top 10 list (coordinated with reps Eric, Jacob, and Paul to include companies with already-scheduled events). Company pages require the company name and website URL.

Reporting & Data Management

Current problem: John manually fields requests from advisors asking for signup counts on specific events — not scalable as the program grows.

Critical data fields identified by Peter:
- Name
- Email address
- In-person or virtual

Immediate solution (for launch): Some form of automated report — email delivery, spreadsheet, or similar — that gives reps visibility into event rosters without requiring WordPress admin access.

Options discussed:
- Automated scheduled email reports (e.g., weekly, then 7 days out, then 1 day out from event)
- Company-level admin accounts with read access to their own roster
- Zapier integration to a shared Google Sheet

Long-term solution: Salesforce integration
- Platform: GVA's Salesforce instance (not NLP's)
- GVA's CEO James has deep Salesforce/coding expertise and will finalize the integration once Asymmetric gets it close
- Desired behavior:
- New signup → check Salesforce for existing record by email
- Match found → log event attendance on existing record
- No match → create new Lead record under the relevant Company
- Purpose of data: Re-engagement for future workshops at the same company ("Hey, we're back — come see us again"). Peter and John explicitly noted they are not actively soliciting attendees; data use is limited to workshop-related communications.

In-person capacity counters: Peter flagged the need for a signup counter on in-person events to prevent overbooking. When capacity is reached, the event can be offered as virtual-only for additional registrants.

Launch Plan & Ongoing Maintenance

Launch philosophy (Peter): "Get the freeway built — we can paint the lines the last week." The Feb 2nd soft launch prioritizes getting the public-facing experience in front of key stakeholders. Backend reporting can be refined post-launch.

Ongoing maintenance scope (Asymmetric):
- In scope: adding new events, updating copy, minor changes
- Out of scope: structural changes such as adding new company pages (quoted separately)
- Volume context: NLP does ~300–400 presentations/year internally; GVA expansion could add another 20–25%

Notification routing (open question): Peter and John need to decide whether event reply-to emails come from a centralized finwellu.com address or from individual reps. Peter leaned toward rep-level replies to keep it clean; John will coordinate with Paul.

Related

• ^[2]
• ^[3] (if created)
• ^[4] (if created)