Your daily workflow and dashboard

Morning protocol, client prep, follow-ups

Every morning, open your terminal and type claude in your project folder. Claude reads your root file, but it does not know what day it is or what to do next until you tell it. That is the point. You design what happens when you say "good morning."

Your morning protocol is a section in your CLAUDE.md that tells Claude exactly what to do when you start a session. You write it. You decide what matters. Some people want an energy check-in. Some want their calendar pulled up. Some want to log their dreams or check for new signups. It is entirely up to you.

Here are some ideas for what your morning protocol could include:

If you have a client call, Claude can prep your notes. It pulls up their last session, reminds you of their action items, and drafts any follow-up emails you need. After the call, tell Claude what happened. It logs the conversation, updates the client record, and drafts your follow-up in your voice.

To set this up, add a "Morning Protocol" section to your CLAUDE.md. Write what you want to happen when you say "good morning." Then when you open Claude Code and say those words, it reads your root file and follows your instructions. Here is a starting point:

That is a starting point. Make it yours. Add integrations to check your email. Add a dream journal prompt. Add a revenue check. The protocol is whatever helps you start your day with clarity. You will keep refining it as you learn what actually helps and what you skip.

Daily logging and energy tracking

At the end of each day, or whenever you finish work, tell Claude: "Let's wrap up the day." Claude will ask you a few questions to close out the day.

It writes all of this into your daily log file. You do not need to format anything. Each day gets one file in your project: context/history/daily/2026/MM/DD.md. It contains your energy level, your morning check-in across all four languages, what you planned, what you actually did, your evening reflection, and any learnings.

Over time, your daily logs create something incredibly valuable: patterns.

You will start to see things. Maybe Mondays drain you because of back-to-back calls. Maybe you do your best creative work on Wednesday mornings. Maybe you avoid admin tasks until Friday and then feel overwhelmed.

This is self-knowledge backed by real data. Not a personality quiz. Actual records of how you spend your time and energy.

The system does not judge you. If you skip a day, that is fine. The next day, Claude just picks up where you left off. No guilt, no streaks to maintain. Just an honest record that gets more useful the longer you keep it.

Your dashboard: clients, pipeline, revenue

Your dashboard is a single page that shows everything about your business at a glance. It is not a separate tool you maintain. It reads from the data you are already creating through daily logs and client interactions.

All of this comes from data you are already creating. Daily logs feed your energy trends. Client conversations feed your client list. Your CRM (which you will build in Part 2) feeds your pipeline and revenue numbers.

In Part 1, you are setting the foundation: daily logs and client notes. In Part 2, you will add the CRM, the pipeline tracking, and the revenue dashboard. The pieces connect automatically because they all live in your system.

For now, the important thing is: start logging daily. That data becomes your dashboard later. Every day you log is a data point. Every day you skip is a gap in your picture.

Part 1 completion

Look at what you have now. A root file that knows who you are as a person and what your business does. A memory system that grows with every session. A daily rhythm that tracks your energy and keeps your work organized.

This is the foundation. Everything in Part 2 builds on what you created here.

Before moving on, do a quick check:

If something is incomplete, go back and finish it. Part 2 assumes you have a working root file and memory system.

Everything you built here, starting from you as a person, becomes the foundation for how your business shows up in the world. The system already knows your voice, your values, your energy patterns, and your priorities. Now it is ready to do real work with that knowledge.

You did not just install a tool. You built something that understands you. That is the difference, and that is what makes Part 2 possible.