Type: One-off project · Closed — client took changes in-house
Tools: Klaviyo · Asana · Figma
Status: All 9 flows delivered · All payments collected
The situation
The Bon Charge project arrived via an incomplete sales handover. Scope was based on a standard email design and build template — no dedicated scoping call, no technical discovery. The actual deliverable was 9 complex Klaviyo flows with multi-variant show/hide logic, regional product display rules (AU/US/EU), Shopify feed dependencies, a Judge Me review feed integration, and a Back in Stock JS snippet removed from the site 3 years prior. A 2-week timeline had already been communicated to the client before the delivery team had any visibility.
The real problems
- Incomplete sales handover — scope based on standard template, complexity never surfaced or priced
- Hidden technical complexity: show/hide logic for 3 regional markets, Shopify product feed disconnected from Klaviyo, Back in Stock snippet missing for 3 years, Judge Me feed not pulling
- Client feedback fragmented across multiple Figma comment threads
- Client expectations around technical feasibility had never been set before build began
What I did
- Conducted full technical audit across all 9 flows — documented every flag, dependency, and blocker in a consolidated QA document shared transparently with the client
- Escalated hidden complexity honestly — framed as professional obligation to surface what would have caused problems post-launch
- Renegotiated the timeline balancing Flowstate's commercial position with client constraints and the true scope of work
- Introduced consolidated feedback process — all new comments directed to a single reference page
- Held firm on client-side blockers with clear technical requirements
Outcome
All 9 email flows fully delivered. Timeline renegotiated and agreed by both parties. Client chose to take all further changes and monitoring in-house — not a relationship failure. All outstanding payments and overflows collected in full before project closure. Consolidated QA documentation became a Flowstate template for future builds.