March 13 feedback: convert threshold from flat $500 to a configurable percentage of job budget (starting at 5%), show below-threshold items in a gray section instead of hiding them, and fix the inflated variance math (3,000%+ values caused by zero-revenue edge cases).
All requested changes implemented and deployed. The enhanced email has been running daily since March 11:
Bob/Jonathan: You’ve been receiving the enhanced daily emails this week. Please confirm the 5% threshold feels right, or suggest an adjustment. The percentage is configurable and easy to change.
March 13 feedback: add two tabs (current/future vs past events), sort by most recent date first, fix the row grouping collapse/expand buttons, and add a companion email with a link to the report.
All requested changes implemented and live:
Jonathan: Schedule time with Amanda to review the report and begin distributing to her team (carry forward from March 13).
Decision: Needs Changes
Bob wants conditional formatting on rows based on % of approved hours used: ~33% light green, ~50% orange, ~75% pink, 80-90% red. Also add a percentage column for filtering. “I’d rather have more options than less.” Keep colors light. Amanda still NOT added — waiting for Jonathan’s green light.
Michael Metiva reported that leads entered in Nutshell were not being converted to events in Direct. He confirmed this happened on multiple occasions, with the event date open and all required fields present.
Root cause identified as two bugs in the event creation Lambda. Both fixed and deployed:
Decision: Approved
Bob acknowledged the monitoring and bug fixes. No additional changes requested.
March 13 feedback: fix the inflated variance percentages (e.g., 3,318% when estimate was zero), and add a trended view showing department performance over time so managers can see whether adherence to estimated hours is improving or worsening.
All changes implemented and a test email was sent on March 18 for review:
Bob/Jonathan: Review the test email sent March 18 and confirm it’s ready for production (enable for regular recipients and disable test mode).
Decision: Needs Changes
Bob wants 6-month rolling window (not 3). Monthly detail section below the heatmap is not needed — “I don’t think we need this breakdown below anymore.” The real missing piece is scheduled hours from Direct. Bob identified Tony (Installation & Strike) as the model dept — he’s been using the Direct scheduler for 8-10 years. Next step: find where scheduled data lives in Redshift, reach out to Jacques.
Automated reminder sequence for leads stuck in the Nutshell “Inquiry” stage. Approved by Mal and Bob. Schedule: Day 10 first reminder, Day 21 second reminder, Day 30 final warning, Day 35 auto-move to Dead.
Lambda is fully built, tested, and deployed. Currently in disabled state awaiting confirmation to enable. Once enabled, all existing leads that have been in Inquiry for 10+ days will begin receiving reminders. Emails will be sent from analytics@hmrdesigns.com.
Bob: Confirm go-live. Once enabled, designers will start receiving reminders for leads that have been in Inquiry 10+ days. Recommend notifying designers before first production run.
Decision: Deferred
Not discussed in detail. Diego needs to follow up with Mel (who has been out of town, now back) before enabling. Carry forward.
March 13: Bob confirmed “for sure we want to get rid of Tableau subscription.” Diego proposed creating one example report first in a custom AWS-hosted portal to evaluate the approach before migrating all reports.
The first Tableau report has been successfully converted — the Event Margin dashboard is now running on AWS infrastructure, fully independent of Tableau. This is the proof-of-concept we discussed on March 13. Ready for live demo today.
Bob/Jonathan: Review the converted Event Margin dashboard demo. If acceptable, we proceed with converting the remaining Tableau reports and canceling the Tableau subscription.
Decision: Approved
Bob approved enthusiastically: “100%. Let’s get it cancelled right away.” Proceed with migrating remaining 2 reports, cancel Tableau subscription, and build HMR-branded portal. Bob also requested natural language data querying as a priority — wants to ask questions like “What’s the average install hours at Four Seasons in July?”
Nutshell is deprecating their current API protocol. All existing HMR Nutshell integrations (sync-events, event creation, inquiry automation) must be migrated. Some newer functions already use the REST API, but older ones still need migration.
Bob/Jonathan: We need to verify the source of the April API deprecation deadline — our research could not find confirmation of a specific cutoff date. Can you confirm where this deadline originated? In the meantime, we’re planning a V2 architecture redesign to modernize and modularize the Nutshell integration rather than just swapping API calls.
Decision: Approved (prioritize)
Diego clarified April is not a hard deadline. Bob: “Can you make that a priority when you get back? I’d like to just take that off our list — it’s been there for a while.”
From March 13 meeting: Bob requested an automated monitoring system that detects when Direct dropdowns (e.g., event templates) change and sends an alert so Nutshell can be manually updated to match. This replaces the need to remember to notify Diego of changes.
No action needed from client — queued for upcoming sprint.
Decision: Not Discussed
Briefly mentioned — no action taken. Carry forward to next sprint.
Amanda Filsinger (General Manager) emailed on March 19 requesting to be added as a Nutshell user. She reached out to Mal, who looped her in with Diego.
Bob/Jonathan: Please confirm the process for adding new Nutshell users. Previously, Jonathan and Chris handled user provisioning. Should we go ahead and add Amanda, or does someone else manage this?
Decision: Approved (resolved)
Bob sent it back to Jonathan and Chris: “Jonathan, you and Chris were working on this. Please take care of this. If you can’t, let me know and I’ll figure it out.”