---
title: Website Launch to Production (2026-02-17)
type: article
created: '2026-02-17'
updated: '2026-02-17'
source_docs:
- raw/2026-02-17-nextlevel-website-launch-123006456.md
tags:
- finwellu
- website-launch
- production
- gtm
- google-analytics
- legal
- accessibility
layer: 2
client_source: FinWellU
industry_context: b2b-services
transferable: false
---

# Website Launch to Production (2026-02-17)

## Overview

During an internal sync on 2026-02-17, Mark and Karly finalized the plan to push the Finwell U website from staging to production. The decision was made to launch immediately and allow the client (Jeff) to complete remaining minor edits directly on the live site, rather than delay for staging work to finish. Mark executed the domain switch and production push during the call.

**Meeting:** [[wiki/meetings/2026-02-17-asymmetric-internal-sync|Asymmetric Internal Sync — Fenwell Launch & Doodla Account Review (2026-02-17)]]
**Client:** [[wiki/clients/current/finwellu/_index|Finwell U]]

---

## Key Decisions

- **Launch now, edit in production.** Remaining site edits (buttons, footer links) are low-risk and can be completed by Jeff directly on the live site without degrading user experience. No need to hold the launch.
- **Mark to own the push.** Mark will handle the staging-to-production push, domain switch, redirects, and post-launch audit rather than delegating to Jeff.
- **GTM and GA4 accounts needed.** Neither had been created prior to launch; Mark will set both up under the name "Finwell U."

---

## Launch Process

1. **Domain switch** — Mark switched the primary domain to `finwellu.com`. All internal links that previously pointed to `nextlevelproduction` are automatically rewritten to `finwellu.com` during the push.
2. **Staging freeze** — Karly notified Jeff to pause all staging work for ~1 hour during the push. Any work done in staging after this point will not carry over.
3. **Production push** — Mark pushed the site from staging to production (~1-hour process).
4. **Post-launch audit** — Mark verified settings, tags, and redirects on the live site.

---

## Legal Policies

All required legal documents were prepared and ready at launch:

| Document | Status |
|---|---|
| Privacy Policy | ✅ Ready |
| Cookie Policy | ✅ Ready |
| Terms & Conditions | ✅ Ready |
| Disclaimer | ✅ Ready |
| Accessibility Statement | ⚠️ Pending (see below) |

---

## Accessibility Compliance

Because Finwell U operates in the financial services space, accessibility compliance carries heightened regulatory importance. Two items were outstanding at launch:

- **Accessibility plugin** — Jeff to add the standard accessibility plugin to the live site (Jeff knows which plugin the team uses).
- **Accessibility Statement** — To be generated after the plugin is installed.

---

## Analytics & Tracking Setup

Neither GTM nor GA4 had been configured prior to launch.

- **Action (Mark):** Create Google Tag Manager account for "Finwell U."
- **Action (Mark):** Create Google Analytics 4 property for "Finwell U."
- Both to be verified during the post-launch audit.

---

## Client Email Requirement

The legal policies reference `info@finwellu.com` as the contact address. This inbox does not yet exist.

- **Action (Karly):** Inform the Finwell U client that they must create `info@finwellu.com`. A catch-all address on the `@finwellu.com` domain is acceptable.

---

## Action Items

| # | Task | Owner | Status |
|---|---|---|---|
| 1 | Push Finwell U to production; set redirects; verify settings/tags; run audit; notify Karly | Mark | ⬜ |
| 2 | Set up GTM + GA4 for Finwell U | Mark | ⬜ |
| 3 | Notify Jeff: pause staging ~1 hour; all future work in production | Karly | ⬜ |
| 4 | Ask Finwell U to set up `info@finwellu.com` + catch-all | Karly | ⬜ |
| 5 | Add accessibility plugin to Finwell U site | Jeff | ⬜ |
| 6 | Generate Accessibility Statement after plugin is installed | Jeff / Karly | ⬜ |

---

## Related

- [[wiki/clients/current/finwellu/_index|Finwell U Client Index]]
- [[wiki/meetings/2026-02-17-asymmetric-internal-sync|Internal Sync — 2026-02-17 (full meeting notes)]]