Free CourseBuild AI Tools

Module 4 · Build #2: The Client Hub

Daily use, backups & real client data

8 min

A tool only earns its keep if you actually use it. The good news: this one fits into your day in two tiny routines, each of them faster than what you do now.

The morning routine

  1. 1

    Double-click the hub, open TODAY

    One double-click, no command.
  2. 2

    Glance at who you’re seeing

    Names and their key facts, at a glance.
  3. 3

    “Prep me for [name]” before each meeting

    Read the one-page briefing.

Two minutes, and you walk into every meeting knowing exactly where you left off. No scramble, no blank.

The after-meeting routine

  1. 1

    Open their page

    The client you just saw.
  2. 2

    Dump your messy notes

    Typos, half-sentences, whatever’s in your head.
  3. 3

    Hit save

    No forms, no fields.

Thirty seconds, done. That’s the whole discipline. Do it right after the meeting while it’s fresh, and your hub stays current on its own — which is what makes tomorrow’s briefings good.

Real client data changes the stakes

This folder now holds real client information — treat it accordingly
  • Keep the GitHub repo private. If you back this up to GitHub the way you learned in Module 2, the repository must be private — never public. Business tools hold business details; client tools hold client details.
  • Be thoughtful about what goes in the notes. Write what helps you serve the client well. You don’t need to record every sensitive thing said in a room just because you can.
  • If you’re in a regulated profession — health, law, finance — treat this folder exactly as you’d treat any client file you’re responsible for. The same duty of care applies; the fact that it’s software doesn’t change it.
  • A private GitHub repo is still a third-party server. It’s fine for backing up the tool — the code — but if you’re bound by confidentiality rules, don’t reach for it to back up the client data. Prefer an encrypted external drive, or storage your profession already approves. (You can even ask Claude to keep the data in its own folder the code can exclude, so a backup of the tool never carries the client files with it.)

Backups: a one-minute weekly habit

Because all your data is just files in a folder, backing up is simple: copy the whole folder to an external drive or a private cloud folder, or push it to your private GitHub repo the way you learned in Module 2. Make it a weekly habit — Friday afternoon, one copy — and if your laptop ever dies, your client history survives it.

End of Module 4 — tool #2 is done

You’ve built software with memory: a private client hub that remembers everyone, captures notes in seconds, and briefs you before every meeting — running on your own computer, under your own control. Two tools down, one to go. Next up, the last build: a dashboard that finally tells you what your numbers are doing.