Original (March 13): Convert threshold from flat $500 to configurable percentage of job budget (5%), show below-threshold items in gray, fix inflated variance math. New feedback (March 23): Mal asked why “improving” events are listed — “Isn’t that a good thing? It seems we could simplify this email.” Bob responded (March 30): display only significant outliers at the beginning for team/job performance monitoring, but continue showing detailed information below for watching other movements.
Original V3 enhancements are live and running daily (5% threshold, below-threshold section, severity tiers, zero-revenue fix). For the new feedback:
Bob: Confirm the proposed approach — outliers first with detailed data below, and raising the improvement threshold to ~100%. We’ll implement by Monday once confirmed.
All active events were showing $0 in Nutshell’s pipeline Kanban view and revenue forecasts. The integration synced financial data to custom fields but never set the native lead.value field, which is what Nutshell’s forecasting UI reads.
Fixed and live:
Bob/Jonathan: Verify Nutshell pipeline view and forecasts now display correct dollar values for active events.
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. Emails sent from analytics@hmrdesigns.com.
Lambda is live and operational:
March 20 feedback from Bob: add conditional color coding on rows based on % of approved hours used (~33% light green, ~50% orange, ~75% pink, 80–90% red). Add a percentage column for filtering. Keep colors light. “I’d rather have more options than less.”
V4 built and deployed with all requested enhancements:
Jonathan: Review V4 report (link above) and confirm it’s ready to replace V3 for team distribution. Coordinate with Amanda on rollout timing.
Original bug: leads entered in Nutshell were not converting to events in Direct (reported by Michael Metiva). New issue (April 2): Corrin Walters reported she couldn’t add an event — the system required a separate Producer even though she was acting as both Designer and Producer for the “Next (Fulton Market)” event.
Both issues resolved:
March 20 feedback: expand trend heatmap to 6-month rolling window (was 3). Remove monthly detail section below the heatmap — “I don’t think we need this breakdown below anymore.” Original requests (inflated variance fix, noise filtering) were already implemented.
All changes implemented:
Bob/Jonathan: We’ll send the updated Sched vs Actual Hours report after this meeting for your review. Please confirm it’s ready to go live for regular monthly distribution.
March 20: Bob asked to prioritize this — “Can you make that a priority? I’d like to just take that off our list.” All existing HMR Nutshell integrations (sync-events, event creation, inquiry automation) needed migration from old API protocol.
Our work is complete:
No client action needed. We’re waiting on Nutshell to resolve a remaining issue on their side. Will update once fully closed.
Amanda Filsinger reported (March 30) that the Custom Projects notification email was counting weekends as working days. Projects submitted on Friday were already showing as overdue on Monday morning, which was confusing for Caro and the art team.
Fixed and confirmed working as of April 1:
March 20: Bob approved Tableau cancellation — “100%. Let’s get it cancelled right away.” Migrate remaining reports, build branded HMR portal on AWS. Tableau subscription to be sunset.
Portal deployed on AWS EC2 with two views live:
Bob/Jonathan: Review the live portal (link above). Confirm if ready to proceed with formal Tableau cancellation.
March 20: Bob requested the ability to query HMR data using plain English — “If you can make that one of your next priorities — figure out a way to get us the ability to query our data in AWS — that would be awesome.” Example: “What’s the average install hours needed at Four Seasons in July for the last five years?”
Chatbot built and functional:
Bob: Share examples of questions you’d like to ask, especially ones involving data that may not be in the current pipeline. This will help us prioritize which Direct fields to bring into Redshift.
March 20: Amanda Filsinger requested to be added as a Nutshell user. Bob routed it to Jonathan and Chris: “Jonathan, you and Chris were working on this. Please take care of this.” Previously, Jonathan and Chris handled all Nutshell user provisioning.
Bob: Diego can take over Nutshell user provisioning going forward (adding/removing users, managing roles). Would like confirmation that this process change is approved, or if it should remain with Jonathan and Chris.
Surfaced in the 2026-04-13 debrief. Not tracked as Jira tickets — bring these up for discussion, decision, or status on the next call.
subcontractor portion of budget field. Requires: (a) confirming sales team is consistently entering the sub budget split at job start, (b) deciding the forecast cadence/model, (c) a dedicated session to scope. Jonathan suggested this be formalized as its own workstream separate from the margin anomaly work.