02 · Built through my work at Grizzle
Client Temperature
A way to stay close to client relationships while giving the team room to work.
Why I built it
I’ve designed the team to work smoothly without needing me in every document. That also means useful context can pass me by. This weekly automation brings together Slack conversations, Google Doc comments and internal ClickUp feedback to suggest where a relationship is holding steady or needs attention.
What it has surfaced
It picked up a client’s new CMO announcement in a thread where I wasn’t tagged. That was valuable context for watching for changes in priorities or planning. Its assessments have broadly matched my own intuition, while adding information I hadn’t seen. I use it as a prompt to investigate and exercise judgement, not as a formal satisfaction score.
Client Temperature
A weekly read across conversations, feedback and delivery. Two relationships are steady; one has a planning change to follow up.
Northline Steady
Feedback is constructive, and next month’s topics are agreed. The team has cleared the last outstanding review.
Watch: Confirm the approver’s holiday cover before the next delivery.
Atlas Watch · leadership change
A new CMO starts next month. The announcement appeared in a project thread, while planning for the next cycle is still open.
Read: Engagement remains positive. The watch item is potential change in direction, rather than evidence of dissatisfaction.
Suggested next step: Confirm the handover plan and whether editorial priorities need revisiting.
Fieldwork Steady
The team has consolidated feedback and confirmed the next interview. Work is moving through the agreed review stages.
Example inputs: Slack threads, document feedback and internal project comments. An interpretation to review, not a formal satisfaction score. This excerpt shows three of the fictional accounts.