A spreadsheet open in a tab on your laptop, and it's been there for about three weeks. It's the one where you were finally going to work out which of this year's projects actually made money. You opened it on a peaceful morning, typed in the first two rows, and then the phone rang. A contractor had a question about a sill level. Then a client called. Then someone in the studio couldn't find the latest layout. Then it was lunch. Then site. And somehow, three weeks later, that spreadsheet is still sitting there, quietly waiting for you. You've restarted the laptop twice. The tab is still there. You don't close it because, well, that is not what we do.
And honestly, none of those calls were unreasonable. The sill level did need an answer. The contractor was right to ask instead of being doubtful. The client had a fair question. Someone genuinely needed that drawing. Being available is part of the job, and in a lot of studios, it's part of what clients value most. Nobody hires an architect thinking, "Great, I hope they take a week to reply." The problem is that availability feels free because every interruption is small. Two minutes here, five minutes there, a quick call while you're opening a drawing, a message while you're halfway through something else. But what gets counted is the interruption, not what the interruption pushes out.
And the work that gets pushed out usually isn't another two-minute task. It's the stuff that needs proper thinking time. The spreadsheet. The fee structure you've been meaning to revisit. Whether to take on another large residential project. Whether it's finally time to hire someone for accounts. Those things don't get done badly. They just don't get done. That's the strange thing about being constantly available: the small stuff gets handled beautifully because it fits perfectly into the gaps, while the important stuff keeps waiting for a gap that never seems to come. Being reachable for small things can quietly make you unreachable for the big ones.
You can see it in how long decisions take. Small decisions happen quickly. Should the door swing the other way? Is this tile close enough to the sample? Can this detail stay as it is? Someone asks, someone answers, everyone moves on. The bigger questions somehow stay on the list forever. Whether to raise fees next year has been sitting there since March. The question of hiring someone for accounts has been coming up for about a year. Is that really indecision? Or does it just take a different kind of time to answer a big question? Big decisions need a clear stretch of thought, and if every quiet stretch gets filled with a call, message or "quick question," that time never appears.
Profitability is the clearest example. Most studios already have the information somewhere. The fees are in the agreements, the invoices are in the accounts, and the hours have been spent. So why is it still so difficult to answer a pretty basic question: which projects are actually making us money? Usually, because getting to the answer means pulling information together from four different places. And that takes a couple of uninterrupted hours. Two uninterrupted hours in a busy practice? Good luck. So it gets pushed to later, and later becomes the evening, or Sunday morning, or that drive home where you're mentally going through the numbers for the fourth time without actually having the numbers in front of you.
Architects working late isn't exactly new, and that's not really the point. The point is that the thinking work of the business, the work that actually shapes what the practice does next, ends up happening in whatever time is left after everyone else has had access to you. The fee question, the hiring decision, the profitability review, the bigger conversation about where the studio is going next. None of these are urgent in the same way as a site question, so they keep losing. And eventually, some of the biggest decisions in the practice are being made by the most tired version of the person making them.
Then there's another little problem. Clients learn your response time. Reply in four minutes often enough, and eventually four minutes stops feeling like a nice, quick response. It becomes the expected response. It's not written into the contract, but it becomes part of the relationship. Then one afternoon, you take an hour to reply and suddenly it feels like something has gone wrong. "Just checking in." "Any update?" "Did you get my message?" You did. You just weren't available. And once a certain level of availability becomes normal, it's surprisingly difficult to take it back without making it feel like you're providing less service.
The usual answer is to set better boundaries. Block the morning. Turn off notifications. Protect your thinking time. Sounds great. Until the sill level genuinely needs an answer before the next course goes down. The problem isn't that nobody knows how to block a calendar. It's that a busy practice has real interruptions. You can't protect every thinking hour by simply refusing to answer everything, because sometimes that just moves the cost somewhere else. The more useful question might be: can the work be made easier to answer in the first place?
Take that profitability spreadsheet. It needs two hours because someone has to collect the information, check it, organise it and then figure out what it actually means. If the fee, time spent and invoices were already sitting together, the same question might take ten minutes. And ten minutes can survive between two phone calls. Projectsmate keeps each project's fee, the time going into it and what's been invoiced in one place as the work happens, so the question in that spreadsheet becomes something you read rather than something you have to build.
Staying available is part of running a practice. It just shouldn't quietly decide which important work never gets done.