Every client, one record.
Client and staff data was spread across tools. I built a central operations hub and rebuilt the client scorecard to be far more efficient.
Languages
Tools & platforms
AI & LLM
Skills
API calls per client for the scorecard
fields in the client master record
The thinking behind it
- 01 · What I noticed
Client data lived in four places, so nobody trusted any of them.
- 02 · What I decided
Create one master record per client and staff member, and rebuild the scorecard to be efficient.
- 03 · What I delivered
One source of truth, and a scorecard cut from 12 calls to 1 per client.
Old system vs new system
- Look in four tools
- Guess which one is right
- Run a slow scorecard
- Sources sync to one hub
- One record per client
- Scorecard in one call per client
Watch it run
Click through the four steps. In step 3, click any box to see what it does.
One record per client, and a faster scorecard.
Client data lived in four places, and the scorecard made twelve API calls per client to build. The hub creates one master record per client and staff member, and the scorecard was rebuilt to need one call per client.
Why it's built this way
One master record
An 85-field client record becomes the reference for everyone.
Fewer, bigger API calls
The scorecard pulls a year at once instead of month by month.
Staff in the same hub
People and clients live side by side, so ownership is clear.
What made it work
- 01
Pick one place to trust
Four sources means no source.
- 02
Count your API calls
Cutting 12 calls to 1 is often the easiest speed win.
- 03
Structure beats searching
A good master record saves daily hunting.
Have a similar mess? Tell me the step you hate.