Jeremy KayeProduct EngineerGet in touch
← Work/Checker AutoGen

Checker AutoGen.

Fills Google Slides templates with campaign assets in seconds.

CHECKER AUTOGEN

Create a Checker Package in seconds

Role
Strategy · Design · Build
Year
2026
Stack
TypeScript · Next.js · Google Slides API · Drive API
Status
LIVE
AutomationGoogle Slides APIPost-production0 to 1
www.checkerautogen.com
The problem

Trailer houses spent hours assembling decks by hand.

Producers at trailer post-production houses build "Audience Quality" review decks for every campaign — dragging dozens of trailer cuts, thumbnails, and metadata into a Google Slides template. The work is repetitive, error-prone, and steals hours from the actual creative review.

Checker AutoGen workflow preview showing template selection and mapping flow
The solution

One form. One click. A finished deck.

Checker AutoGen connects directly to Google Slides and Drive. Producers paste in campaign metadata and a folder of assets; the tool reads templates, slots everything into the right placeholders, applies branded styles, and hands back a ready-to-share deck — in seconds.

01

Template-aware

Reads existing branded templates so output stays on-brand without a designer in the loop.

02

Asset-aware

Auto-matches thumbnails, cuts, and metadata to the right slide placeholders.

03

Edit-friendly

Output is a real Google Slides file — fully editable, no proprietary format lock-in.

Time per deck
~1 min
down from 10 min
Decks per month
135
across 3 producers
Time reduction
90%
$13,365 saved / year
◉ Process

How it came together

  1. 01

    Collected pain points

    Internal stakeholders walked me through their existing workflow and shared where it broke down — what was slow, error-prone, or just painful at scale.

  2. 02

    Scoped requirements

    Translated stakeholder feedback into top-level requirements: what the tool had to do, what it couldn't touch, and what 'done' looked like.

  3. 03

    Researched and planned

    Evaluated the available Google APIs, mapped out the architecture, and reviewed the build plan with stakeholders before writing a line of code.

  4. 04

    Built, designed, iterated

    Built the full Next.js app, designed the UI, and ran rapid feedback cycles with stakeholders — shipping fixes and refinements in real time.

◉ Outcome

What used to take 10 minutes per deck — multiplied across 135 decks a month — now takes one. That's 20 hours a month back in the hands of people who should be doing creative work, not data entry.

Visit live site
◉ Next project
MLK · 2024

Malk

Follow people with taste — video discovery beyond the algorithm.

Malkbeta

video discoveryshouldn't be a solo mission