The no-spreadsheet way to track client feedback

Running three active builds at once means you're fielding feedback from three different clients, across email, WhatsApp, Slack, voice notes, and the occasional sticky note photo. By the time you've copied it all into a spreadsheet, something's already slipped through.

The spreadsheet isn't the problem — the manual copying is. Here's how to set up a feedback system that captures, organises, and surfaces the right notes without you ever opening a cell.

1. Give each build a single feedback inbox

The moment a client has more than one channel to reach you, things get messy. Pick one place per project — a dedicated WhatsApp thread, a shared email alias, or a simple form link — and redirect everything there.

Tell clients upfront: "For anything to do with the build, drop it here." It feels rigid at first, but clients actually prefer it because they always know where to go. You get every piece of feedback in one thread instead of hunting across five apps.

2. Log feedback in plain language the moment it arrives

When a client sends a voice note at 9 pm saying "the checkout flow feels clunky," don't flag it to deal with later. Transcribe or rephrase it into one sentence and drop it into a running notes doc — a Notion page, a Google Doc, even a thread in your project management tool.

The format matters less than the habit. Keep each entry to:

• Project name
• Date received
• Feedback in plain words
• Status (new / in progress / resolved)

That's it. No formulas, no pivot tables. Four columns in a doc beats a 40-column spreadsheet you'll stop updating by week two.

3. Do a 10-minute weekly sweep, not a daily scramble

Checking feedback constantly is how you lose half your day to reactive work. Instead, block 10 minutes once a week — Friday afternoon works well — to read through every open item across all three builds, update statuses, and flag anything that needs to move before the next client call.

This rhythm does two things: it keeps you calm during the week because you know there's a dedicated time to process feedback, and it gives clients a predictable response pattern so they're not chasing you for updates.

4. Separate "nice to have" from "blocking" the moment feedback lands

Not all feedback is equal, and treating it the same is what creates the panic. When a note comes in, tag it immediately as either blocking (the build can't move forward without addressing this) or nice to have (worth doing, but not urgent).

This single decision — made in 10 seconds when the feedback arrives — means you never sit down to a prioritisation session wondering what actually matters. You already know. Your blockers rise to the top; everything else waits its turn.

5. Send a weekly status update to each client without writing it from scratch

Clients send more feedback when they feel like it's going into a black hole. A short weekly update — three to five bullet points covering what moved, what's next, and any open questions — dramatically reduces the "just checking in" messages you receive.

The trick is not writing it fresh each time. Keep a simple template:

• Completed this week: …
• In progress: …
• Waiting on you for: …
• On deck for next week: …

Fill in the blanks from your running notes doc. The whole thing takes five minutes. Send it on the same day every week and clients start to trust the cadence instead of pinging you for reassurance.

---

If reading this made you think "I know this works, I just don't have the time to set it up and keep it running" — that's exactly the kind of operational work you can hand off to a Sidekyk. Send a WhatsApp message to your Sidekyk with the raw feedback as it comes in, and it can log it, categorise it, draft your client status updates, and remind you about blockers before your next call. No spreadsheets, no extra tabs — just the system running in the background while you focus on the build. Try it at sidekyk.ai.