---
name: client-decisions-2026-08-27
description: The seven binding onboarding decisions from Alicia Wimmer's 2026-08-27 email, verbatim with implications, plus the hosting (PlusROI) and Cloudflare DNS decisions.
metadata:
  type: project
---

# Client decisions of 2026-08-27 (binding)

Source: Alicia Wimmer's email of 2026-08-27, sent after the kickoff/onboarding call the same
day (full digest in `notes/client-correspondence.md`). These override anything the proposal
(2026-07-30) offered as an option. The seven bullets are quoted verbatim, typos included.

| # | Verbatim | Implication for the build |
|---|---|---|
| 1 | "Remove all mentions of Twitter and Facebook" | Drop twitter.com/equinoxlaw and facebook.com/Equinoxbusinesslaw from header, footer, social icon blocks, share buttons, and from `Organization.sameAs`. Keep LinkedIn (linkedin.com/company/equinox-business-law-group-pllc) and YouTube (youtube.com/channel/UCTEE4EFZH16GE-1zkiEvFUg). Whether the Meta pixel (connect.facebook.net) counts as a "mention" is to be confirmed with Alicia Wimmer before launch (Rian asks); until answered, keep it in the GTM preservation checklist but do not add a Facebook icon, link, or share button anywhere. |
| 2 | "Remove inks [sic] to EO Portland and Women in Finance" | The live footer "Community Involvement" list has seven entries; the rebuilt list keeps five: EO Seattle, Women's Presidents Organization, Seattle U Family Business Exchange, Bellevue LifeSpring, CFO Leadership Council. |
| 3 | "Remove any mention of serving businesses in DC and VA" | States become Washington first, Oregon secondary, Colorado retained. The firm's own email signature had changed from "WA, OR, CO, DC, and VA" to "WA, OR and CO" by 2026-08-27 (ground truth), so Colorado stays. The proposal had offered to drop Colorado too — that offer is dead. Do not write any licensing sentence until the Idaho/Colorado discrepancy is resolved (see `.memory/naming-conflicts.md`). |
| 4 | "Replace Equinox logo, it is no longer our 20th anniversary" | Use the logo from the SharePoint Brand Kit folder (link in the 2026-08-27 email; a human with SharePoint access pulls it into `notes/` and the media library). Never reuse the anniversary mark from the live site's media library — header, footer, favicon, and schema `logo` all use the new one. |
| 5 | "Team webpage - remove Mandy Bowen, add Nicole Farahdel, Corporate Paralegal, no headshot or bio yet, can a placeholder be used?" | Roster is 9 bios: the 8 live plus Nicole Farahdel (see `.memory/live-site-numbers.md`). Mandy Bowen is already absent from the live sitemap. Nicole gets drafted placeholder text and a non-person placeholder image (decision 7 forbids stock people); her Person schema waits until real details arrive. The launch checklist must not ship her placeholder unknowingly. |
| 6 | "Overall, we find our current website visually busy and somewhat dated. We're looking for a more elevated, simplified look and feel." | This is the brief for the Design Mockup and Review Round: less section density, tighter hierarchy, more whitespace, fewer competing elements per screen. Detail in `.logs/planning/design-direction.md`. |
| 7 | "Regarding images, we'd like to remove the team photos from our homepage, if that works from a design standpoint. We're comfortable keeping one or two team photos overall across the entire website, however keeping them current is cumbersome, we'd like to remove them from other pages as well wherever it makes design sense. Stock images are fine, just please no stock photos of people" | No team photography on the homepage. At most one or two team/group photos site-wide (likely About Us and one other), sourced from the "2026 Brand Photo Shoot" SharePoint folder. Individual headshots on bio pages are the bio, not "team photos" — confirm at mockup review. Stock imagery limited to objects, places, abstracts, textures; the mockup's placeholder imagery must obey this too. |

## Hosting decision

The 2026-08-27 email's Hosting line reads "Move to PlusROI" (the plan named in the same line is
the Hosting add-on; its price is omitted by the project's pricing rule). Alicia had already
named the Hosting add-on in the acceptance of 2026-08-13. Consequence: the staging project
`equinoxbusinesslaw` on this server becomes production at launch; launch is a DNS cutover, not
a file transfer to the client's host. The post-launch choice between the Hosting add-on alone
and the Hosting and Support plan is deferred ("no need to decide now", Rian, 2026-08-24).

## Cloudflare decision

- 2026-08-13: Rian recommended Cloudflare for DNS.
- 2026-08-18: Alicia agreed ("We're open to making the move to Cloudflare") and asked whether
  email would go offline. Rian's answer the same day: no downtime — Cloudflare imports the
  existing DNS records; invite rian@rian.ca as super administrator under Manage account >
  Members; either add the domain themselves or give Rian registrar access (GoDaddy delegate at
  rian@rian.ca, or equivalent) and he moves it. The entry tier suffices; a higher tier with
  bot controls, which AISV sometimes prefers, can be added later.
- 2026-08-27: "waiting on a response from our current website/email management" vendor.
  Blocked on that vendor as of 2026-09-02.

How to apply: before nameservers change, compare the imported zone against a fresh `dig` of
every record type at the current provider — MX, SPF, DKIM, DMARC, Microsoft 365 autodiscover —
and change nameservers outside business hours. A law firm losing mail is the worst outcome of
this project.