The schematic design gets signed off. The contract says forty percent falls due at that point, and everyone involved knows it, because everyone read the contract when it was signed. Then the architect moves on to the next stage, and there's a site meeting, and a client call, and by the time the invoice actually goes out three weeks have passed. Nobody did anything wrong. The milestone was hit. The money was earned. The invoice just took three weeks to get sent, because sending it was the one part of the milestone that wasn't anybody's job in particular.
Then it sits. Not because the client refuses to pay, most of them fully intend to, but because an invoice that arrives a month after the work sits differently in a client's mind than one that arrives with it. It has stopped being the natural next step and become a separate request. Two weeks pass. The architect notices, and thinks about following up, and then doesn't, because the project is going well and the relationship is warm and there is something about raising money mid-project that feels like introducing a sour note into a conversation that was going fine. The follow-up gets postponed to a better moment. There is never a better moment.
This is how a payment schedule that everyone agreed to quietly stops governing anything. Not through dispute. Through delay, at both ends, each delay entirely reasonable on its own. The schedule was never the problem. It was clear, it was fair, it was signed. What it lacked was anything that made it happen on the day it said it would.
The awkwardness is not incidental to this. It is the entire engine. Asking a client for money they already owe should be the easiest conversation in a project, and it is somehow one of the hardest, because the architect has spent months building a relationship in which they are the person who understands what the client wants, and money moves them, briefly, into being the person who wants something from the client. That shift feels like a cost. So the ask gets delayed, and here is the cruelty of it: every week of delay makes the next ask harder, not easier. A reminder sent on the day the payment is due is administrative. The same reminder sent six weeks later is a confrontation. The architect who waited for a comfortable moment has spent the whole time making the moment less comfortable.
Meanwhile the studio is running on money that hasn't arrived. And because nobody is tracking the gap between what was earned and what was collected, the studio doesn't experience this as a collections problem at all. It experiences it as a cash problem. The account is tighter than it should be. Salaries are covered but only just. Nobody says the word receivables, because nowhere in the studio's day is there a number that separates the money owed from the money missing. The two feel identical from the inside.
Which leads to the wrong fix. A studio short on cash takes on another project, because another project brings an advance, and the advance closes the gap. It works, in the sense that the immediate pressure lifts. But the new project brings its own milestones, which will slip in exactly the same way, and now the studio is running two sets of unbilled work instead of one. The advance didn't solve the collections problem. It postponed it, and made it larger. A practice can run like this for years, always slightly behind, always covering the last project with the next one's advance, and never once identify what is actually happening, because at no point did anyone see the total of what the studio had earned and not been paid.
None of this is fixed by resolving to be better about invoicing. Every architect already knows they should send the invoice on time and follow up when it's late. Knowing was never the constraint. The constraint is that the moment of sending sits in the middle of a design day, and the moment of following up sits inside a relationship that feels too good to disturb, and both moments depend on a person deciding, in the middle of everything else, to do the uncomfortable thing right now.
What changes it is taking the decision out of the moment. The milestone completes and the invoice goes with it, not because someone remembered, but because the deliverable and the payment were connected from the beginning. The reminder goes on the day, not when the architect has worked up to it. The client sees what's due alongside the work it's due for, so the request is never a surprise arriving weeks after the fact. And the studio, at any point, can see the difference between what it has earned and what it has collected, which is the number that was missing the entire time.
The payment schedule an architect agreed to is usually a good schedule. It just needs to be something the studio can see, and something that acts on its own, rather than a clause in a document that governs the project only if somebody remembers it at the right moment and feels brave enough that day. That's the part of Projectsmate that matters here: the architect never has to decide to have the money conversation, because the schedule is already having it. What's left is the work, and a relationship where money was never the thing that got postponed until it turned awkward.