When we built the business dashboard for Jewgo listing owners, the temptation was to show everything: views, clicks, reviews, specials performance, search rank, competitor comparisons.
That would have been a vanity dashboard, impressive in a demo, ignored by the people who actually maintain listings.
A useful business dashboard answers four questions:
- What needs attention right now?
- What changed since I last logged in?
- What is stuck waiting on me?
- What decision do I need to make?
Every screen we shipped maps to at least one of those.
Who is this case study for?
This case study is for teams building an owner or operator dashboard inside an existing product. If admins field the same update requests daily, owners cannot see status without asking in chat, or your first dashboard draft is mostly charts, use this scope before shipping vanity metrics nobody acts on.
What Jewgo is
Jewgo is a location-aware community app for kosher restaurants, shuls, mikvahs, events, jobs, and organizations across South Florida, 2,000+ users on iOS and Android.
Listing owners (restaurants, shuls, event organizers, businesses) need to keep their information accurate without emailing admins or waiting for a volunteer to update a spreadsheet row.
What was broken before the dashboard
- Owners had no self-service view. Changing hours or adding a new special meant messaging someone on the community team.
- Admins became the manual connector between owners and the platform. Every update flowed through volunteers who already had too many chats to monitor.
- There was no exception list. Nobody could see at a glance which listings had missing photos, stale hours, or unanswered review flags.
- Reporting happened in group chats. Owners could not tell whether their listing was complete, visible, or outdated.
The pain was not missing analytics. It was missing operational clarity.
What we decided the dashboard should show
We scoped around owner decisions, not chart types.
Exceptions first: what needs attention
Lead with what’s incomplete or overdue:
- Listing missing required photos or hours
- Special expiring in the next 48 hours with no replacement
- New community review flagged for owner response
- Verification status pending admin approval
Why: Owners open the dashboard to decide what to do next. A ranked exception list beats a traffic chart.
Status at a glance: what’s live vs. stuck
Show listing state clearly:
- Published and visible near user’s location
- Draft changes not yet submitted
- Updates waiting on moderation
- Expired specials still showing old data
Why: Bottlenecks are visible when you see age and status, not when you see a monthly view count.
Change since last visit: what’s different
Highlight movement:
- New reviews since last login
- Admin approved or rejected a change
- Listing completeness score crossed a threshold
- New jobs or events linked to the business
Why: Dashboards get ignored when everything looks the same every time.
One action per screen: not ten metrics
Each view ends with a clear next step:
- Update hours
- Upload photos
- Respond to review
- Publish special
- Submit for verification
Why: KPI dashboards for small businesses work when they tie to a decision, not when they report history nobody acts on.
What we left out on purpose
- Aggregate traffic charts with no owner action attached
- Competitor benchmarking (not relevant to keeping a listing accurate)
- Historical analytics that required manual exports to stay current
- Metrics the team couldn’t define an owner for
If a number did not connect to something an owner would fix that week, it did not ship.
We did not build charts because charts were not the job.
How we scoped the build without overbuilding
We started with one morning question: “Which of my listings needs work today?”
We built that view first. Shipped it to a small set of listing owners. Watched whether they used it without reminders.
They did, because it replaced messages to admins, not because it looked good in a slide deck.
Then we expanded: specials management, review responses, verification status. Each addition had to pass the same test: does this remove a manual step?
The result
Jewgo listing owners can now see what needs attention, update their information directly, respond to reviews, manage specials, and track verification status without waiting on admins.
Admins spend less time relaying update requests, and the community sees fresher hours, specials, and event info because the people closest to the data can maintain it themselves.
The dashboard is part of the same platform as the consumer app, not a separate BI tool nobody opens.
What a custom business dashboard should actually show
This project is the practical answer to a common search question: what belongs on a custom business dashboard?
Not every metric. Not every chart. Exceptions, status, change, and the next decision, in that order.
If your team is rebuilding a spreadsheet every week so someone can see what needs attention, you probably don’t need more reports. You need a dashboard scoped around the one role that acts on the data.
That is what we built for Jewgo’s listing owners. And it is the standard we use on every internal tool and operations dashboard we ship: fewer charts, more clarity, every screen tied to work someone actually needs to do.
Related guide: What a Custom Business Dashboard Should Show
