How Palmer Krehel builds custom client dashboards with zero code and a few messages to Claude

Palmer Krehel is a freelance paid media specialist working across a portfolio of clients and agencies. Instead of forcing everyone into the same template, he builds each client a custom, client-facing dashboard on Coupler.io, Claude, and Cloudflare — no writing code manually, no developer, and edits that land while the client is still on the call.

0 lines

Custom code written across every dashboard he's built

~2 min

To stand up the repo for a new client dashboard

~10 min

Set up Cloudflare worker

Seconds

To turn stakeholder feedback into a live change

Role

Freelance paid media specialist

Use case

Custom client-facing dashboards

Stack

Coupler.io, Claude, Cloudflare, GitHub

Data sources

Facebook Ads
Google Ads
Google Analytics
HubSpot
LinkedIn Ads
Shopify
CallRail

Data destinations

JSON

Stop manual exports

Stop pulling numbers by hand — automate client reporting like Palmer Krehel did.

Start for free

The problem

Reporting that can't bend to what the client actually wants

Across the companies Palmer works with, dashboards were always the sticking point. Clients either didn't have them at all, or they were stuck inside Looker Studio and living with its limits — boards that load slowly and, more importantly, boards that are painful to change.

That second part is the real cost. Paid media reporting isn't a fixed spec. A CEO looks at a board and immediately wants a different cut, a new metric, a different view of the same spend. In a templated tool, every one of those requests turns into a rebuild, so the honest answer is usually "I'll get to it next week" — and the dashboard drifts away from the questions people are actually asking.

People don't have them, or they want to use Looker Studio, and there are a lot of limitations.

— Palmer Krehel

The solution

Coupler.io moves the data, Claude builds the board

Once Palmer found the JSON destination in Coupler.io, the whole workflow reduced to a handful of pieces: Coupler.io to move client data, Cloudflare to host it, GitHub for the repo, and Claude to build and edit the dashboard itself.

The mechanics are simple enough to repeat per client. Coupler.io exports the client's data as JSON on a schedule. That URL is stored as a secret environment variable in Cloudflare, so the board always reflects fresh data. A private GitHub repo takes under two minutes to create, gets connected to Cloudflare Workers and Pages, and Claude — connected to GitHub — does the building.

Palmer set the workflow up once, and now it's a repeatable process — the next client dashboard is a matter of pointing Claude at what he already built.

Access is handled through Cloudflare authentication: each dashboard is restricted to the client's email domain, with a re-login every 24 hours. No passwords, nothing public.

I literally didn't write a single line of code myself. Claude wrote everything for these boards.

— Palmer Krehel

The results

Any dashboard the client wants, changed on the spot

What the stack changed for Palmer:

Every board is custom — each client gets what they asked for, not a shared template bent to fit
Feedback lands immediately — a CEO's "this is what I want to see" becomes a live change in seconds, not a rebuild scheduled for next week
No developer, no engineering team — Palmer runs the entire thing solo
New clients are near-instant — a repo, a few environment variables, and a few messages to Claude
Dashboards load fast — clients consistently contrast them with the laggy boards they're used to