← Back to projects

Project case study

Reportify

A reporting assistant that helps FACEIT players turn match incidents into structured reports without leaving the matchroom.

Why I built it

After a frustrating match, I didn’t want reporting players to become another chore. Reporting several people meant repeating the same steps, so reducing that friction became the main goal.

My earlier version, Ticketeer, automated filling in support tickets. But I rarely used it myself — it still wasn’t convenient enough. With Reportify, I shifted the workflow into the matchroom, where players could prepare and review reports in one place.

A faster reporting workflow

Fast Report lets users select multiple players, apply a shared report category, and start with all rounds selected. Before submitting, they can review and adjust those selections. A detailed mode lets them add context, screenshots, and video links.

Reports are queued and sent individually. The goal is to reduce repetitive actions while keeping users in control of what they submit.

Reportify Fast Report panel with shared settings and individual player controls.
Fast Report shared settings with individual player controls.

What I built

Browser extension
A vanilla JavaScript extension that brings quick and detailed reporting into the FACEIT matchroom, with queued submissions and browser-based voice transcription.
Product website
A responsive website built with Next.js, TypeScript, React, and Tailwind CSS to explain the product and guide visitors to installation.
Blog & technical SEO
An MDX blog with a guide on how to report a player on FACEIT. The website includes metadata, canonical URLs, Open Graph tags, a sitemap, and robots.txt.
Analytics
Google Search Console and Google Analytics 4, with a custom event tracking clicks on the installation button.

Results & learnings

Snapshot: November 13, 2026

As of November 13, 2026, Chrome Web Store reported 18 weekly users for the extension. Reportify was released as an update to the existing Ticketeer listing, retaining its user base.

Between November 4 and 13, the website recorded 47 impressions and no clicks in Google Search Console. I hadn’t yet promoted the new website through additional channels.

Earlier Reddit posts promoting Ticketeer generated approximately 43,000 views. That exposure belongs to the previous version, rather than the launch of Reportify.

The biggest change was moving from a tool I rarely used myself to a workflow I actually use after matches. That’s a useful personal signal, but it doesn’t yet tell me how other players experience the product.