Click Refresh.

Years ago I built a dashboard for a client. Pre-AI.
Here’s how that went:
Monday: call. Take requirements.
Tuesday and Wednesday: go build. Debug. Fight the join that doubled revenue.
Thursday: show him. “Close. Can we split it by region?”
Friday: back to the cave.
Next week: repeat.
Days of round trips for a handful of changes.
Read or listen to this post on Substack.
Same client, last week. Different playbook.

We booked one long call. He talked. I pasted his feedback straight from the transcript into Claude, made the change and ran the tests.
“Click refresh.”
There it was.
Next change. “Click refresh.”
By the end of the call he had exactly what he needed to walk into his big meeting and crush it.
The feedback loop went from days to minutes.
Here’s the part nobody posts about.
Claude isn’t why I can change a live dashboard while the client watches. The harness is. The tests, the guardrails and the setup I built before the call are what let me say “click refresh” with a straight face instead of praying.
Speed without a harness is just breaking things faster.
If your data team isn’t moving like this, or you’re in data and want to, let’s jam.
Let’s Turn Your Data into Growth
No more guesswork or missed opportunities.


