# Client correspondence — digest

Chronological digest (oldest first) of the client email thread "Equinox / PlusROI meeting",
2026-07-09 to 2026-08-27, plus the one platform question answered outside the thread. Written
2026-09-02 from the original messages. This is the in-project record; the originals contain
commercial terms and are kept outside the project (see the last section).

Rules applied to this digest: no amounts of any kind; add-ons and plans by name only; the
client's design decisions of 2026-08-27 are quoted verbatim because they are binding on the
build. Everything else is paraphrase.

## Who is on the thread

| Person | Role | Address on the thread |
|---|---|---|
| Rian Bowden | PlusROI; owns delivery, wrote the proposal | rian@plusroi.com (calendar invites from rianbowden@gmail.com; rian@rian.ca for Cloudflare) |
| Rob Cooper | PlusROI; client relationship, copied on every message | robertecooper@gmail.com (signature: Rob@PlusROI.com) |
| Alicia Wimmer | Equinox, Sales & Marketing Operations Coordinator; day-to-day contact | aliciam@equinoxbusinesslaw.com; phone 425-250-0205 |
| Michelle Bomberger | Equinox, CEO & Managing Attorney; copied throughout, did not write in the thread | michelle@equinoxbusinesslaw.com |

Not on the thread but referenced: Adi (adi@plusroi.com, PlusROI designer/developer, named in the
access request) and AI Smart Ventures (AISV), the client's marketing partner, whom Rian met
separately before writing the proposal.

## Timeline

| Date | From | What happened |
|---|---|---|
| 2026-07-09 | Rian Bowden | Calendar invitation "Equinox / PlusROI meeting" on Google Meet, originally 2026-07-14 12:00-12:50 PT, moved to 2026-07-21 same time. Guests: Michelle Bomberger, Alicia Wimmer, Rob Cooper (optional). |
| 2026-07-21 | Alicia Wimmer, Rob Cooper | Initial discovery meeting (the pre-proposal call). Alicia asked at 12:05 whether the time still held; Rob wrote at 12:06 that he was on the call and would try again. The meeting went ahead: Rian's strategy notes of 2026-07-27 cite "notes from the Equinox meeting" as an input to the proposal. |
| 2026-07-27 | Alicia Wimmer | Asked for an estimated delivery date for the proposal. |
| 2026-07-28 | Rob Cooper | Replied that Rian had gone fairly deep into planning and was travelling with his daughter; something would come shortly. Alicia acknowledged the same day. |
| 2026-07-29 | Rian Bowden | Apologised for the delay. Reported a deep look at the site and at AISV's plans, a recommended approach already outlined, and a good meeting held with AISV to go over their plans and requests for the site. Promised a detailed proposal with optional items the next day. Alicia acknowledged. |
| 2026-07-30 | Rian Bowden | Sent the detailed proposal as an attachment, "with some optional items for your consideration". Its scope checklists are the contracted deliverables; see `.logs/planning/scope.md`. |
| after 2026-07-30 (date not in the thread) | Rian Bowden | Answered a client question, raised outside this thread, about building on Vercel/Next.js instead of WordPress. See "The platform question" below. |
| 2026-08-13 | Alicia Wimmer | Acceptance. "This is exactly the kind of thinking we were hoping for, and the audit findings align closely with what we suspected was negatively affecting the Equinox website." The client moves forward with the base scope plus the Hosting add-on and the Design Mockup and Review Round. On the Fractional General Counsel Landing Page with Tiered Pricing add-on: interested, but "we'd like to discuss further before making a decision". The Practice Area and Topic Hub Architecture add-on was not mentioned (treated as not taken). Wants to start as soon as the team has availability. |
| 2026-08-13 | Rian Bowden | Confirmed a start for 2026-08-17. Asked for access to the current hosting account and domain registrar (or the client's help moving hosting at some point). Recommended Cloudflare for DNS management (many benefits over registrar-only DNS) and offered to move the domain over once given domain access. |
| 2026-08-18 | Alicia Wimmer | Working on providing access to the Equinox hosting account and domain registrar. Open to moving to Cloudflare; asked for a walkthrough of what it involves and whether anything such as email would go offline, even briefly. |
| 2026-08-18 | Rian Bowden | Cloudflare walkthrough, see below. |
| 2026-08-24 | Rian Bowden | Onboarding questions, see below. |
| 2026-08-27 | Alicia Wimmer | Kickoff/onboarding call held that day ("Thanks for chatting today!"), followed by the written onboarding answers, see below. Her email signature now reads "Strategic Legal Counsel for Businesses in WA, OR and CO" (her earlier messages in the thread carried "WA, OR, CO, DC, and VA"; the thread does not date the change precisely, and the stacked signature blocks suggest it was already in place by her 2026-08-18 message). |

## The platform question (Vercel or WordPress)

The client asked whether the site should be built on Vercel (Next.js) rather than WordPress.
The question is not in the email thread; the reply was drafted in the original planning
session in two lengths, and the short version (five paragraphs, about 300 words) is the one
sent. The position sent to the client:

- Vercel is a hosting and deployment platform for custom-built front ends, usually Next.js; it
  does not store content or give the team somewhere to edit it. The real comparison is a custom
  Next.js application versus block-based WordPress; both are legitimate.
- Recommendation: block-based WordPress, because the deciding factor is who can change the
  site. On a custom build a new landing page or a restructured section routes through a
  developer every time; on block-based WordPress the client's team and AISV do it themselves.
  AISV's plan runs on a weekly publishing cadence with execution resting largely on one person,
  and their Phase 01 drafts posts directly into WordPress, so the client should confirm the
  platform question with AISV too.
- Conceded openly: Vercel is not slower and not worse for SEO or AI search; it solves problems
  the client does not have yet. Where it would genuinely fit is the interactive Smart Assessment
  AISV wants to build later, which is an application, not a web page, and can be added without
  redoing the site.
- Capability answer: WordPress is PlusROI's core competency and what it builds on with AISV.
  PlusROI can work with Vercel, but that would be a different project requiring a new quote.
- Closing ask: if a specific Vercel proposal is on the table, send it over.

The longer draft (kept outside the project) additionally discloses that Kadence Blocks creates
its own lock-in for pages (posts stay standard content) and corrects the proposal on FAQ rich
results: Google stopped showing them on 2026-05-07, so FAQ content is built for buyers and AI
answer engines, not for rich snippets. Neither point was in the short version sent.

## 2026-08-18 — Cloudflare walkthrough (Rian)

- Create a Cloudflare account, then Manage account > Members > Invite members: add rian@rian.ca
  with super administrator access.
- Then either add the domain themselves (Domains home > "Add domain"; the wizard imports the
  current DNS records, so no downtime is expected) or give Rian access to the current domain
  registrar and he moves it. Most clients prefer the latter. For GoDaddy, add rian@rian.ca as a
  delegate; other registrars have similar delegate/team invitations. (Rian's 2026-08-18 email
  also mentioned a password as an alternative; do not take that route. Registrar access is by
  delegate invitation only, never a shared password, and no credential is ever sent by email or
  pasted in chat, per /srv/CLAUDE.md.)
- A basic Cloudflare account is all that is needed. Cloudflare also offers additional controls
  over which bots may access the domain, which AISV often likes its customers to have; those can
  be added later and are not a concern now.

## 2026-08-24 — onboarding questions (Rian)

Access. Share admin access with rian@plusroi.com, adi@plusroi.com and plusroi@gmail.com for
Google Analytics, Google Tag Manager, and Google Search Console (if set up). Google Ads is not in
scope, but if the client has an account and wants it connected properly, PlusROI needs the
10-digit Google Ads account ID and will request access through its client centre. Once
Cloudflare is set up, share access with rian@rian.ca; or share registrar access and Rian sets it
up.

Billing. Billing contacts requested.

Design. A mockup of the proposed design will be sent before anything is built. Before the mockup,
the client should send: a brand guide (or, failing that, notes on colours, fonts and other brand
considerations, including any logo package); and a couple or few links to sites they like, with
what they like about each.

Hosting. Stay on the current host (then provide access to it) or move to a PlusROI hosting plan?
If PlusROI, the post-launch choice between the Hosting add-on alone (maintenance handled as
needed) and the Hosting and Support plan does not need to be made now.

Timing. Once the above arrives, an initial mockup within a week, then a call to discuss the
mockup and any other issues relevant to the build.

## 2026-08-27 — onboarding answers (Alicia), binding

Access:

| Tool | Status 2026-08-27 |
|---|---|
| Google Analytics | Access given that morning. |
| Google Tag Manager | Blocked. Alicia got the message "This tag's users are controlled by Google Analytics" (screenshot in the original email). Cause: the Google tag on the site is governed by the GA4 property whose stream is "Equinox Website" (measurement ID G-PTGQ1K61M6), so user access for that tag is managed from the Google Analytics admin, not from the Tag page. GTM container access itself is still to be confirmed by Alicia Wimmer. |
| Google Search Console | Access given that morning. |
| Cloudflare | Waiting on a response from the client's current website/email management vendor. |

Billing: billing contacts provided — ap@equinoxbusinesslaw.com and matt@equinoxbusinesslaw.com.

Design inputs: two SharePoint folders on the client's MarketingSales site were shared, "Brand
Kit" and "2026 Brand Photo Shoot". The links are in the original email; a person with SharePoint
access pulls the contents into `notes/source/brand-kit/` and `notes/source/photos/` (or the
media library). Not done as of 2026-09-02.

The seven design decisions, verbatim from the email:

1. "Remove all mentions of Twitter and Facebook"
2. "Remove inks [sic] to EO Portland and Women in Finance"
3. "Remove any mention of serving businesses in DC and VA"
4. "Replace Equinox logo, it is no longer our 20th anniversary"
5. "Team webpage - remove Mandy Bowen, add Nicole Farahdel, Corporate Paralegal, no headshot or
   bio yet, can a placeholder be used?"
6. "Overall, we find our current website visually busy and somewhat dated. We're looking for a
   more elevated, simplified look and feel."
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"

How to read decision 3 with the signature change: the firm's signature moved from "WA, OR, CO,
DC, and VA" to "WA, OR and CO", so Colorado stays. The proposal had offered to drop Colorado as
well; the client's answer overrides it. States for the build: Washington first, Oregon secondary,
Colorado retained; DC and VA removed. Do not write licensing language until the Idaho/Colorado
discrepancy on the live assessment page is settled with the client (see
`notes/site-audit-2026-07.md`).

Hosting: the client chose PlusROI hosting. Launch target is therefore PlusROI-managed hosting on
this server, not the client's current host.

Closing: "Please let me know if I can answer any questions or provide clarifications."

## What is still owed by whom, as of 2026-09-02

| Item | Who |
|---|---|
| Google Tag Manager access for the three PlusROI addresses (managed via the GA4 admin) | Alicia Wimmer |
| Cloudflare account created and rian@rian.ca invited as super administrator; or registrar access | Alicia Wimmer (waiting on the client's web/email vendor) |
| Brand Kit and 2026 Brand Photo Shoot pulled from SharePoint into the project | Rian or Adi (needs SharePoint access) |
| Links to liked sites, with reasons (requested 2026-08-24, not answered 2026-08-27) | Alicia Wimmer |
| Initial design mockup within a week of the inputs, then a review call | Rian / Adi |
| Decision on the Fractional General Counsel Landing Page with Tiered Pricing add-on | Client, after discussion with Rian |
| Post-launch plan choice (Hosting add-on alone vs Hosting and Support) | Client, after launch |

## Where the originals are

The original messages (.eml) and the proposal itself are kept outside the project (location:
Rian to confirm) because they contain pricing and payment terms. This digest is the in-project record of the
thread. New material from the client goes into `notes/inbox/` and is digested the same way (see
`notes/inbox/README.md`); do not copy an original email into the project if it carries any
amount.