Client Project Tracker
The problem
I had a communication problem hiding in plain sight. Projects were getting delivered, the work was good — but my clients had no idea what was happening between meetings.
I knew I should be sending regular updates. Weekly emails summarising what had been done, what was coming next, what was blocked. But those emails never got sent. Not because the work wasn't happening, but because writing status updates is tedious, easy to put off, and always loses to actual billable work.
The result was predictable. Clients would chase. "Just checking in — any progress?" Stakeholders who weren't on the call would be completely in the dark. Project managers would forward screenshots of Trello boards that meant nothing to the person receiving them. And when multiple people on the client side needed to stay informed — a founder, a marketing lead, an ops manager — keeping everyone aligned was a game of telephone.
The tools that existed didn't help. Jira and Linear are built for engineering teams, not clients. Sharing a board with a non-technical stakeholder just creates confusion. Email works in theory, but only if you actually write the emails. Slack channels go quiet. Notion pages get forgotten. The problem wasn't a lack of tools — it was that none of them made client communication effortless enough to actually happen.
What I built
A lightweight internal tool that gives every client their own status page — a single link they can check whenever they want, no login required.
Each client gets assigned a regular cadence: weekly, bi-weekly, or monthly. At the start of each cycle, I write a short update — what the goals are, what's being worked on — and add a task list. As tasks get completed, I tick them off. When the cycle ends, a closing note summarises what was achieved.
The key thing: every time something changes — a new cycle starts, a task gets completed, a comment is posted — anyone subscribed gets an email automatically. No drafting, no remembering, no "I'll send that update later." It just happens.
Clients and stakeholders subscribe themselves from the status page. They choose exactly what they want to hear about: new cycles only, task completions, comments, or all of it. They can unsubscribe with one click. No accounts, no passwords, no onboarding friction.
There's also a comment system so clients can ask questions or flag concerns directly against a specific cycle, rather than firing off a disconnected email. And a backlog section for longer-term items that sit outside the current cycle — feature requests, known issues, things that are acknowledged but not yet scheduled.
From my side, it's a simple dashboard. Create a client, start a cycle, add tasks, tick them off as I go. The emails handle themselves. There's a full log of every notification sent, so nothing falls through the cracks.
The result
Client communication went from something that never happened to something that happens automatically, every time.
Stakeholders who previously had no visibility — the CEO who's paying for the project, the ops lead who'll be using the software, the marketing manager who needs to plan around launch dates — now get updates without me needing to write or forward an email. They check the link when it suits them, or wait for the notification to land in their inbox.
The "just checking in" emails stopped. Clients feel informed, which means they feel confident. Conversations in meetings shifted from "what's been happening?" to "I saw you finished X — can we talk about what's next?"
It replaced an unpredictable, guilt-driven process with a consistent one. Not by adding complexity, but by making the right thing — keeping people in the loop — the path of least resistance.