Rosana EPS Access + Rebuild Scope Alignment (Mira, Arseni, Riaan) — March 11, 2026

Participants: Mira, Arseni, Riaan Type: ops_call Approximate duration: 1 hour 30 minutes Date logged: 2026-03-11 Notion: Not created from this environment

Action items

• Riaan — Obtain or coordinate WP Engine access with Rosana / current site owner so the team can inspect the live setup directly | Deadline: Mar 12 | Priority: urgent
• Riaan — Confirm where the current EPS-related data is stored and how the new build would read from it | Deadline: Mar 13 | Priority: urgent
• Mira — Prepare Rosana's current missing-functionality list, especially around subsection filtering and promo selection | Deadline: Mar 12 | Priority: normal
• Ivan — Stay available to explain the older EPS logic and any rebuild implications if Rosana wants a larger solution | Deadline: Mar 13 | Priority: normal

Key quotes

— Arseni, re: solution framing: "It should be the best thing for her business and not the cheapest."

— Riaan, re: the main current request: "We need to get the functionality that she had before."

— Mira, re: the current missing capability: "She doesn't have that possibility to filter people and filter subsections."

Topics covered

1. WP Engine access is the immediate operational blocker

The team cannot safely inspect or change the current implementation without access. Getting into WP Engine was treated as the fastest operational step because email back-and-forth is too slow and fragmented.

2. Rosana's main concern is restoring useful prior behavior

The conversation sharpened around a practical client request: restore the older EPS-style behavior that let Rosana send more targeted promo selections and subsection-based packages, not just broad category blasts.

3. Rebuild discussion depends on the data model