Company Context

AtlasFlow is a B2B SaaS workflow platform used by mid-market operations teams to automate approvals, intake forms, and internal service requests. The company has 1,200 paying customers, $28M ARR, and is expanding into enterprise accounts where deals are larger but implementation cycles are longer.

Problem

A newly signed enterprise client, NorthBridge Logistics, is requesting a “custom dashboard and reporting experience” before full rollout to 12,000 employees. The request came from the executive sponsor, but the implementation team has received conflicting input from operations managers, IT, and compliance. Some stakeholders want real-time operational visibility, others want auditability and exports, and engineering says the current reporting architecture can support only limited customization within the next quarter.

The account is worth $1.8M ARR if expanded, but the company cannot afford to build a highly bespoke solution that slows the core roadmap for all customers. Your task is to define how you would handle the ambiguity, identify the real user needs, and recommend a product direction that balances client value with platform strategy.

Deliverables

1. Explain how you would structure the problem and reduce ambiguity in the client requirements.
2. Identify the most important user segments and their underlying jobs to be done.
3. Propose what you would build for an MVP versus what you would defer or reject.
4. Define how you would align internal and external stakeholders around trade-offs and scope.
5. Specify how you would measure whether the chosen solution is successful.

Constraints

• MVP recommendation must be deliverable within 10 weeks.
• Only 1 product manager, 4 engineers, and 1 designer are available this quarter.
• Existing reporting infrastructure supports configurable widgets, CSV exports, and role-based access, but not fully custom analytics.
• The solution should ideally be reusable across other enterprise customers, not a one-off build.