Self-service reporting

Report requests to engineering fell by about 30%, as stakeholders built the simpler reports themselves in a configurable tool I built with Claude Code.

Case study  3 of 6What I did: Built

Role
Spotted the need and built it, with Claude Code
Client
A business-messaging platform
Scope
Self-service reporting for the client teams
Adoption
Adopted for the simpler reports

01

The problem

At a business-messaging platform, stakeholders asked engineering for reports through tickets. Reports were built with client-specific code or periodically synced spreadsheets and, even when the required data was known, a typical one took about a day of custom development.

02

What I did

I spotted the opportunity from the volume of report tickets, ran a short proof of concept and demonstrated it to stakeholders.

I then built a configurable reporting interface over the existing front end and contacts data, with Claude Code. It was lightweight custom code with no framework, replacing client-specific code and periodically synced spreadsheets, and the client teams’ reports were recreated in it.

When the required data was known, a report took minutes to configure. Report requests to engineering fell by about 30%, as stakeholders built the simpler reports themselves. Feedback from real use drove the useful changes to the interface.

Fig. 1  From configuration to report

Diagram of the reporting tool. A configuration form with three fields and a button leads, along an arrow labelled minutes, to a finished report table. When the required data was known, a report took minutes to configure.

03

Results

  • Report turnaround

    Minutes

    down from a day of development, when the required data was known.

  • Report requests

    about 30% fewer

    report requests to engineering, as stakeholders built the simpler reports themselves.

04

Stack

  • JavaScript
  • HTML
  • CSS
  • PostgreSQL

Next case study  4 of 6What I did: Led

Leading a cross-service change

I led an identifier migration across the platform's core services, coordinating five engineers, with no known client impact attributable to the team.

Next case study

Contact

Get in touch

Tell me about your project, your team or the problem you're working on.

What would you like to discuss?

At least 20 characters.

I'll only use your details to reply. Privacy