Month-end reporting for 40+ clients, done before anyone asks.
An accounting firm rebuilt every client's monthly numbers by hand. I built one workflow that pulls each client's financials and hours and fills their dashboard automatically.
Languages
Tools & platforms
AI & LLM
Skills
client configurations from one control point
down from hours (director-timed)
months of history backfilled
The thinking behind it
- 01 · What I noticed
Every client was the same job with different settings. The team was rebuilding the same report 40+ times.
- 02 · What I decided
Build one workflow with per-client settings, so a fix or a new metric reaches every client at once.
- 03 · What I delivered
Month-end for 40+ clients in about 15 minutes instead of hours.
Old system vs new system
- Export each client report
- Copy numbers into sheets
- Pull hours separately
- Update each dashboard
- Repeat for 40+ clients
- Month closes
- One workflow loops every client
- Financials and hours pulled
- Dashboards updated, failures flagged
Watch it run
Click through the four steps. In step 3, click any box to see what it does.
One workflow, 40+ different clients.
Every client has its own connection, its own settings and its own quirks. I built a single control point that resolves each client at run time, keeps their sign-in tokens fresh, and marks any metric that fails instead of silently skipping it. Six edge-case bugs found in real runs were fixed along the way.
Why it's built this way
One parameterized workflow, not 40 copies
A fix or a new metric reaches every client at once.
Tokens refreshed and written back automatically
Connections keep working month after month without manual sign-ins.
Failures are visible
A failed metric is marked as failed, so nobody trusts a wrong number.
Have a similar mess? Tell me the step you hate.