One quarter of client work notes: the habits they point to

A note from the Volant team, written at the end of March 2026. It looks back at what this blog covered in its first quarter. It is our opinion, not a study or anyone's results.

This blog has now run for about a quarter. That's a good point to stop and read the notes back as a set, and ask what they add up to.

Taken one at a time, they cover separate jobs: pricing a site, taking a deposit, researching a business before you pitch, writing a one-page scope, saying no to a request, briefing an AI agent, checking its work, and checking a site before handover. Read together, they point to a small number of habits. This note pulls those habits out so you can start them this week.

What the first quarter's notes covered

The quarter's topics sort neatly into six groups:

• Building. Making or changing websites, with or without the agent.
• Replies. Messages, calls and small questions from clients, including change requests and the ones you have to turn down.
• Checking. Reading what the agent built before a client sees it; testing links, forms and the phone view before handover.
• Money. Quotes, deposits, invoices, and working out who has paid.
• Finding work. Researching businesses and pitching.
• Agent context. Explaining a client to the agent, or fixing what it got wrong because it didn't know.

Most of the quarter's advice sits in the last five groups, not the first. That's no accident.

What the notes suggest about building

Only a small share of the quarter's notes are about building itself. That reflects our view, and it's an opinion rather than a measurement: building is no longer where most of the effort goes. Getting an AI agent to build a good website isn't the hard part any more. Given a clear brief, it writes pages quickly. What it can't do is know what the client meant, what you promised on a call, or what the business's opening hours really are.

So the notes spend their time on everything around the building. Replies arrive all day. Each one is short, but together they add up. Promises made out loud have to be found again later; our note on how easily a spoken promise gets lost in a busy week shows how one slips. Checking the agent's work takes real time, and it's the time we'd least want anyone to cut. Money is never large and never absent.

Then there's agent context: explaining the same client again at the start of each session. Of all six groups, it's the easiest to shrink.

The habit behind most of the advice

Write things down once, in the place they'll be read.

For the agent, that means a brief for each client in a file it reads at the start of every session. Claude Code's documentation says each session begins with a fresh context window, and that instructions in a CLAUDE.md file are loaded at the start of every session. Keep the client's facts there and update them when something changes, instead of pasting them in every morning. Our note on what to stop pasting into every agent session goes through what belongs in that file.

For you, it means one place per client for promises, requests, quotes and payments, checked every morning. The gain is less about minutes and more about not carrying everything in your head. That weight is tiring in a way no timesheet shows.

A daily note to see your own mix

The notes describe a typical week, not yours. To see which groups fill your own week, you need a record. The standard advice is to track every minute, and few solo designers keep that up for long. Starting and stopping a timer between a call, a quick reply and a fix on a live site is its own small job. It's the first thing dropped in a busy week.

A lighter habit lasts longer: a short note at the end of each day. Write a few lines on what you worked on, and sort each chunk into the six groups above. No minutes. You're not building a timesheet. You're looking for a pattern, and a month is enough to see one. It's the same idea again: write it down, because memory is the wrong tool.

Habits to try next quarter

Start with the groups that aren't building. That's usually where the easy changes are:

1. Replies: answer in two or three batches a day instead of as they arrive.
2. Promises: write each one down with a date the moment you make it.
3. Checking: give it a fixed slot, so the next build doesn't squeeze it out.
4. Money: check who has paid in one place, once a week.
5. Agent context: move anything you've typed twice into the agent's brief file.

If you're starting a one-person AI agency, try the daily note for a month before you change anything else. It will tell you more about your week than any advice, ours included. Keeping track of clients and promises is the part of that we care about most.

Why this matters to us

In December, our note on building an agency around an AI agent argued that the agent does the making, and running the business stays with the person. The notes since then, on lost promises and on what an agent should read each session, come at the same idea from other sides. Read as a set, the quarter's notes say it once more. If building is the small part, then the agency is everything else, and that's the part that needs looking after. It's also why Volant exists, which the about page explains.