People ask me how I manage my time, and I always feel slightly fraudulent answering. Not because I’m disorganized — I’m actually quite structured. But because the structure I’ve built still fails me regularly, and most advice about time management comes from people who’ve edited out the failures.
So here’s the real version. How I actually structure my week running PipelineRoad, building a software platform, managing a small team, and trying to remain a functional human being. Including the parts that don’t work.
The Architecture
My week has a deliberate shape. Not a rigid schedule — rigid schedules break the moment a client has an emergency or a deal needs attention — but a shape. A pattern that most weeks follow, with enough flex to absorb the chaos.
Monday and Tuesday are meeting days. Every client sync, every team check-in, every external call happens on these two days. I typically have six to eight meetings on Monday and four to six on Tuesday. They start at 9 AM and end by 5 PM, with thirty-minute gaps between calls that I use to take notes, send follow-ups, and eat things I can hold with one hand.
These days are exhausting. By Tuesday evening, I’m socially depleted in the way that only back-to-back video calls can produce. But the trade-off is worth it: by concentrating all my meetings into two days, I free the remaining three for work that actually requires uninterrupted thought.
Wednesday is processing day. This is when I take everything from Monday and Tuesday — notes, action items, client feedback, strategic questions, team requests — and turn it into organized, actionable lists. I export call transcripts. I write internal briefs. I update project trackers. I identify what needs to happen this week versus next week.
Wednesday feels unglamorous. It’s administrative work. But it’s the day that makes the rest of the week coherent. Without it, the insights from client calls would leak away, the action items would blur together, and by Friday I’d be reconstructing conversations from memory instead of working from clean documentation.
Thursday and Friday are deep work days. No meetings. No calls. Notifications off. These are the days I write strategy documents, review content, build systems, work on the platform, and do whatever creative or analytical work the week demands. Four to six hours of focused work per day, with breaks that are actually breaks — a walk, a meal, a conversation that isn’t about work.
That’s the architecture. Most weeks, it holds.
How the Client Load Works
Eight clients, each with different needs, different cadences, different personalities. The math on this is tighter than people realize.
Each client gets a weekly or biweekly sync. That’s the meeting itself — thirty to sixty minutes, depending on the client and the week. But the meeting is the visible part. The invisible part is the prep time (reviewing deliverables, checking metrics, anticipating questions), the follow-up time (writing notes, distributing action items, unblocking the team), and the thinking time (strategy, positioning, creative direction).
For a typical client, the meeting is maybe 20% of the time I spend on their account. The rest happens in the margins — in the thirty minutes before the call, in the hour after it, in the Thursday afternoon when I’m reviewing their content queue.
I’ve tried to systematize as much of this as possible. We have templates for meeting notes, for content briefs, for strategy reviews. The templates aren’t exciting, but they reduce cognitive load dramatically. I don’t have to decide how to organize information for each client. The structure already exists. I just fill it in.
The thing that doesn’t systematize is context switching. Going from a compliance SaaS client to a logistics platform to a consumer-facing app in the space of three hours requires a mental agility that I’m still developing. Each client has a different voice, different priorities, different stage of growth. Holding all of those simultaneously is the single hardest part of running a multi-client agency.
My coping mechanism is absurdly simple: I keep a one-page brief for each client pinned in my workspace. Not a full strategy document — a single page with their current priorities, their voice and tone, their key metrics, and whatever’s top-of-mind from the last conversation. Before each call, I spend two minutes reading that page. It’s like a mental loading screen. By the time the call starts, I’m in their world.
Protecting Creative Time
This is the part most founders get wrong, and I got wrong for a long time.
Creative work — writing, strategy, design thinking, product ideation — requires a fundamentally different mental state than meetings or administration. You can’t produce original thinking in fifteen-minute increments between calls. The ramp-up time alone takes twenty to thirty minutes. By the time you’re in flow, the next meeting notification appears and the whole thing collapses.
My solution was blunt: no meetings on Thursday and Friday. No exceptions. If a client needs an urgent call, it happens on Monday or Tuesday. If a team member needs a sync, it happens on Monday or Tuesday. Thursday and Friday are sacred.
This was hard to implement. Clients push back. “Can we hop on a quick call Thursday afternoon?” No. “It’ll only take fifteen minutes.” No. I don’t explain the cognitive science behind flow states. I just say I’m unavailable and offer Monday or Tuesday instead. After a few weeks, everyone adjusts.
The result is that I have two full days — roughly ten usable hours — of uninterrupted time per week. That’s where the best work happens. That’s where I write the strategy documents that change how we approach a client’s positioning. That’s where I think about the platform. That’s where I do the work that actually moves the business forward, as opposed to the work that maintains the business.
What I Still Get Wrong
I promised honesty, so here it is.
I overcommit on Wednesdays. The processing day regularly bleeds into Thursday morning because I underestimate how long it takes to organize a week’s worth of notes and action items. I know this, and I still do it. Some weeks, Thursday doesn’t start until noon.
I check Slack too often. My “deep work days” are not as deep as I pretend they are. I’ll go heads-down for ninety minutes and then, almost involuntarily, check Slack for fifteen. Then the fifteen becomes thirty. Then I have to re-enter flow from scratch. I’ve tried every tool, every app blocker, every technique. The honest answer is that I’m still addicted to the dopamine of responsiveness, and it costs me at least an hour of productive time every day.
I don’t protect weekends well enough. Running an agency and building a platform means the work is never done. There’s always another blog post to review, another email to send, another feature to think about. I work most Saturdays for at least a few hours, and I’m not convinced that’s sustainable long-term. The line between “I want to work on this” and “I can’t stop working on this” has blurred, and I need to redraw it.
And I underinvest in thinking time. The calendar has meetings, processing, and execution. What it doesn’t have is a dedicated block for pure strategic thinking. Time where I’m not producing anything, not responding to anything — just thinking about the business, about where we’re going, about what’s working and what isn’t. That kind of thinking gets crowded out by urgency, and the quality of my decision-making suffers for it.
The Trade-Offs
Every calendar structure is a trade-off. Mine optimizes for depth over breadth. By concentrating meetings into two days, I create space for focused work — but I also create two days that are brutally draining. By protecting Thursday and Friday, I enable creative output — but I also become less responsive to clients who want real-time availability.
These trade-offs work for our agency because we’re small and our team is capable of operating independently between syncs. They wouldn’t work for a client-facing role that requires constant availability, or a company where decisions need to happen in real time.
The thing I’ve learned about calendar design is that it’s a reflection of values. My calendar says: I value depth over speed. I value creative output over constant responsiveness. I value documentation over improvisation. Those aren’t universal values. They’re mine. And they produce a specific kind of agency — one that does fewer things, more deliberately, for fewer clients.
I used to think the goal was to do everything. To be available always, responsive instantly, productive constantly. That calendar looked like a Jackson Pollock painting — meetings scattered everywhere, no pattern, no breathing room.
The calendar I have now is quieter. More structured. Less impressive-looking. And it produces dramatically better outcomes — for our clients, for our team, and for me.
It’s still imperfect. But imperfect and intentional beats perfect and theoretical every time.