---
title: Next Level / FinWellU Project Status — 2026-01-08
type: article
created: '2026-01-08'
updated: '2026-01-08'
source_docs:
- raw/2026-01-08-sprint-planning-meeting-112798607.md
tags:
- next-level
- finwellu
- project-status
- blockers
- godaddy
- domain-access
- client-delays
layer: 2
client_source: FinWellU
industry_context: b2b-services
transferable: false
---

# Next Level / FinWellU Project Status — 2026-01-08

## Overview

As of the [[wiki/meetings/2026-01-08-sprint-planning|2026-01-08 Sprint Planning Meeting]], the Next Level / FinWellU project is **stalled** due to a combination of client-side delays and an unresolved infrastructure access issue. Karly is the primary AM on this account.

---

## Current Status

**Overall: Blocked — awaiting client deliverables and domain access**

The project cannot meaningfully advance until the client provides the required company list for portal creation and approves the new "Finwell U" branding. A planned February launch is at risk if momentum is not established soon.

---

## Active Blockers

### 1. Client Has Not Provided Company List
The client (contact: John) committed on a Monday call to sending a list of all companies that need portals built. As of this meeting, that list has not arrived. No portals can be created until it is received.

### 2. "Finwell U" Logo Pending Approval
The team submitted a logo for the new "Finwell U" brand. The client has not responded with approval or feedback. No copy or design work tied to this brand identity can be finalized until approval is received.

### 3. GoDaddy Domain Access — 2FA Complication
The new domain (`finwellu` — purchased by the client on their GoDaddy account) is needed for the site launch. The client believes access was previously granted, but the team cannot confirm active access. GoDaddy's two-factor authentication makes ad-hoc access attempts impractical.

**Decision:** Karly will wait until GoDaddy access is actually needed before requesting it again, to avoid 2FA friction and expired sessions.

---

## Key Decisions

- **GoDaddy access:** Do not request until actively needed; reach out to client at that time and ask them to remove or redirect 2FA to a team-accessible channel.
- **Portal creation:** Fully blocked until client company list is received from John.
- **Logo/branding:** No downstream design or copy work should proceed until "Finwell U" logo is approved.

---

## Action Items

| Owner | Action | Status |
|-------|--------|--------|
| Karly | Follow up with client on company list for portals | Pending |
| Karly | Follow up with client on "Finwell U" logo approval | Pending |
| Karly | Request GoDaddy access when domain work is imminent | Deferred |

---

## Background Context

- The client (Next Level) is also associated with a separate Masons project starting this month, adding complexity to the relationship.
- The client has been described as difficult to manage — they have changed domain/branding direction multiple times.
- There is an ongoing internal question about the developer workflow: Karly and Jeff (developer) have had disagreements about implementation approach for the portal structure. This remains unresolved but is secondary to the client-side blockers.
- The project was originally scoped with a February launch target. That timeline is increasingly uncertain.

---

## Related

- [[wiki/meetings/2026-01-08-sprint-planning|Sprint Planning Meeting — 2026-01-08]]
- [[wiki/clients/current/finwellu/_index|FinWellU Client Index]]