Anisalytics Contact
← All case studies

AI & reporting automation

A daily briefing, without the daily rebuild

A dashboard for digging into developer feedback and a weekday briefing that surfaced what was changing.

~6 hours of manual prep saved per edition (estimate)

Portfolio illustration

The brief

Product teams lacked real-time visibility into developer friction.

The product team needed to know exactly what developers were asking for, where they were hitting roadblocks, and which conversations were accelerating. I built a dashboard for on-demand questions and a weekday briefing to surface the patterns that mattered.

01 / On demand

Explore the dashboard

Stakeholders could select a time frame, read the underlying mentions, and use Gemini to generate trend summaries, feature-request and pain-point analysis, and content ideas. They could also see which conversations were gaining traction.

02 / Every weekday

Get the briefing

Monday through Friday, the newsletter surfaced emerging and sustained trends, product-specific discussions, and possible blog topics drawn from developer conversations.

How I built it

From Brandwatch alerts to a custom Apps Script dashboard.

I built a pipeline that automated the recurring data pulls and briefing.

  1. Configured Brandwatch alerts to feed mention data into an existing BigQuery table.
  2. Built the dashboard and automated the reporting workflow in Google Apps Script.
  3. Integrated the Gemini API to analyze trends, summarize feature requests, and support the weekday briefing.

Estimated manual preparation

~6 hours

Per weekday edition if assembled by hand.

Stakeholder feedback · paraphrased

One stakeholder called it the best report they’d seen.

Another singled out how useful the dashboard and newsletter were for the team.