You have been brought in as a Business Analyst at Meridian Financial Services, a mid-size financial advisory firm with 450 employees across 12 regional offices.
ClientHub Pro takes 14.2 seconds on average to return a search. With 350 active advisors, 8,000 estimated duplicate records, and 47 search tickets in the last six months, roughly a third of the advisor team has quietly switched to spreadsheet workarounds.
My advisors keep personal spreadsheets because the search is so bad. That's a data governance nightmare, but I can't blame them.
Three artifacts, due in two weeks.
- 01Stakeholder Register
- 02Requirements Document
- 03Use Case
This page builds the second one.
Five people, five versions of the problem. Read them all before you decide.
- Email · Sarah Chen, VP of Sales · March 3, 2026
We can't search by account number, which is how half our conversations start.
- Email · Marcus Wright, CRM Administrator · March 5, 2026
8,000 duplicate client records were never cleaned up. The vendor's answer is a $45K-a-year Enterprise tier.
- Meeting note · Kickoff with Lisa Huang · March 7, 2026
The timeline expectation is that recommendations should be ready within 2 weeks. She wants requirements that are realistic and implementable, not a "wish list."
- Interview · James Petrov, Senior Financial Advisor · March 9, 2026
I think we need a whole new CRM. I've used Salesforce at my previous firm and it was miles ahead of this.
- Data · CRM usage statistics · March 10, 2026
Average search response time: 14.2 seconds (measured over 1 week). Vendor-quoted cost for Enterprise tier upgrade: $45,000/year.
James Petrov wants a full CRM replacement. Sarah Chen wants focused search improvements. Based on the evidence, what scope is appropriate for this project?
Consider the 2-week timeline, the budget sensitivity, and what's realistically achievable.
What the case actually needs.
Translate evidence into requirements. Each one should trace back to a person, not just a problem.
A requirement without a source is a guess. Tag each one to the person whose words it answers, and keep the Must column tight enough that Diana can fund it inside the $75K cap.
MoSCoW only works if you respect the M. For this case, two Musts is plenty, three at most. Anything more and Diana will push back on the $75K cap.
That is artifact two of three.
The Stakeholder Register comes before it, the Use Case after. In the full case you build all three and get feedback scored across five dimensions.
Meridian is free. No card. Module 1 first, then the case opens.
- 01Stakeholder Registernext
- 02Requirements Documentdone
- 03Use Case
- Stakeholder Identification
- Requirements Quality
- Use Case Structure
- Analytical Thinking
- Professional Communication