Your 10-Second Dunder Mifflin Product Feedback

Dunder Mifflin Paper Company is a long-standing customer using Sturdy primarily to understand account health, renewal risk, and cross-sell potential across regional branches (Scranton, Stamford, Utica, etc.). 

Overall product feedback is constructive and pragmatic: they value Sturdy’s ability to capture call and email context from reps like Michael Scott and Jim Halpert, but they want clearer reporting for branch-level rollups, simpler UX for less technical reps, and more flexible tagging for “soft signals” (office politics, supplier changes, budget shifts). 

Sentiment is generally positive toward the core product capabilities, with requests focused on reporting, usability, and better mapping to Dunder Mifflin’s quirky, region-based org structure.

1. Branch-Level Rollup & Reporting Gaps 
   
   • Regional managers want a clean view of key signals by branch (Scranton vs. Stamford vs. Utica) without building custom reports every time.
   • Difficulty comparing branches on churn risk, expansion potential, and engagement patterns at a glance.
2. Ease of Use for Frontline Reps 
   
   • More advanced users (e.g., sales ops) are comfortable, but everyday reps find some workflows “one or two clicks too deep.”
   • Requests for more guided views: “show me what I need for my calls today” vs. open-ended dashboards.
3. Richer Context on “Soft” Signals 
   
   • Reps regularly mention leadership changes, merger rumors, and internal drama in notes and calls.
   • They want Sturdy to better capture and categorize these qualitative signals (e.g., “new CFO,” “budget freeze,” “supplier dispute”) and surface them in account summaries.
4. CRM & Territory Alignment 
   
   • Feedback that some signals don’t always route cleanly to the right branch or territory owner.
   • Desire for stronger alignment between Sturdy’s account structure and Dunder Mifflin’s CRM hierarchy.

Reporting & Analytics 

• Pre-built branch/region comparison dashboards (churn risk, upsell opportunities, top issues).
• Simpler ways to export summaries for executive meetings and paper-based reports (PDF/slide-ready views).

User Experience 

• A “morning brief” view per rep: key accounts, recent issues, and upcoming renewal/upsell conversations.
• Fewer steps to get from a signal to the underlying email/call snippet.

Signal & Tagging Model 

• Automatic tagging for leadership changes, supplier issues, and budget mentions.
• Ability to pin certain signals (“CFO asked for savings plan”) so they always appear in the next QBR or renewal review.

Integrations & Data Quality 

• Clearer mapping of branches and territories to ensure signals land with the right rep/manager.
• Occasional complaints about stale owner data when reps move territories.

Would you like me to prioritize these and propose a phased delivery plan?

• On branch-level reporting:
  “I’d love a simple view where I can see Scranton vs. Stamford vs. Utica side by side on risk and opportunities.”
• On usability for reps:
  “Our sales ops folks love the dashboards, but some reps just want a quick summary of what changed since their last call.”
• On soft signals:
  “The conversations are full of hints about budget cuts and leadership changes. If Sturdy could surface those patterns, that would be huge.”
• On routing and alignment:
  “Sometimes signals show up under corporate when they really belong to the Scranton branch. We need it to mirror our CRM more closely.”

Risks if Unaddressed 

• Underutilization by frontline reps, with Sturdy perceived as “more for ops” than for day-to-day sellers.
• Leaders may see Sturdy as powerful but “too heavy” if branch-level views remain hard to assemble.
• Potential for tool consolidation conversations if reporting and routing gaps persist.

Opportunities 

• Deepen adoption by shipping a branch comparison view tailored to Dunder Mifflin’s territory model.
• Turn Dunder Mifflin into a flagship case study for multi-branch reporting and “soft signal” intelligence.
• Use their feedback to refine a “rep morning brief” pattern that can be generalized to other customers.

1. Co-Design a Branch-Level Dashboard 
   
   • Run a short working session with Dunder Mifflin’s regional managers to define the 5–7 metrics they care about most (e.g., at-risk accounts, open issues, expansion candidates by branch).
   • Deliver a prototype view and gather feedback.
2. Introduce a “Rep Daily Brief” Experience 
   
   • Pilot a simplified, “what changed since last week” view for a subset of reps (e.g., Scranton branch).
   • Track whether it increases daily engagement and reduces time spent hunting for context.
3. Enhance Soft-Signal Detection & Tagging 
   
   • Add or tune models for leadership changes, budget pressure, and vendor/partner changes.
   • Ensure these tags roll up into account summaries and QBR templates for Dunder Mifflin.
4. Tighten CRM/Branch Mapping 
   
   • Work with their CRM admin to clean up account hierarchy and owner data.
   • Validate that key signals are routing to the right branch and territory owners.
5. Close the Loop with a Product Feedback Review 
   
   • Share a short recap back to Dunder Mifflin: what we heard, what we’re doing now, and what’s on the roadmap.
   • Position them as a design partner for multi-branch intelligence and soft-signal insights