Architecture is a business that sells hours and delivers drawings, and both pass through a channel where nothing is recorded. The client approves a floor plan by audio, changes their mind about the coating in a Sunday message, the builder sends a photo asking for a measurement at seven in the morning, and the decision that will cause two weeks of rework is made in a conversation that no one will be able to find later. None of this is a project problem. It’s a channel problem — and it’s the kind of problem that consumes margin without appearing on any spreadsheet.
In this article
- The client channel and the construction channel are not the same
- The revision request that arrives on Sunday
- The approval that never arrives, and the one that arrives and disappears
- The construction asks and cannot wait
- Decisions made by message need to become documents
- One year in numbers
- Communication by project phase
- The lead that arrives and the budget that doesn’t close
- When the firm grows and the partner steps back
- Five mistakes that consume the firm’s margin
- The numbers to track
- Frequently Asked Questions
The client channel and the construction channel are not the same
Every small and medium architecture firm has a phone number where everything passes: the partner who sold the projects. The client arrives with a finishing question, the foreman with a measurement question, the supplier with a delivery deadline, the carpenter with an execution detail, and the client’s mother with an opinion about the wall color.
This works until about five or six simultaneous projects. After that, four things break at the same time:
- The urgent tramples the important. The construction question is always more urgent than the project revision, and the project revision is what is being paid for.
- No one knows what was decided. A finish defined in conversation disappears, and three weeks later the client remembers it differently.
- The scope continuously leaks. Each isolated request is small; their sum in the month is a week of unbilled work.
- The partner becomes a bottleneck. They travel, enter a three-hour visit, and eleven projects stop responding.
The separation that solves this is not creating two phones — it’s creating two conversations with different rules within the same channel.
The client conversation deals with decision, approval, scope, deadline, and value. It has business hours, requires record-keeping, and almost always can wait a few hours. The construction conversation deals with execution, measurement, detail, and unforeseen events. It is urgent by nature, technical, and the right person to answer is often not the same.
Look at the messages that arrived last Friday after 18h. Separate those that required immediate response from those that only seemed to require it. In most firms, more than 80% could wait until Monday — and the cost of having answered all was not the time, but having taught everyone that the firm responds at any hour.
The revision request that arrives on Sunday
Every architect knows the message: "just a little thing, can you see how it would look with the countertop on the other side?" It’s not in the contract, takes three hours, and refusing seems rigid after two months of good relations.
The problem is never the first request. It’s the twelfth, when the sum of those three hours became thirty-six hours in the month and the project margin disappeared without anyone noticing — because each item alone was small and polite.
What solves this is not saying no. It’s recording and showing. Every out-of-contract request receives the same three-part response: confirmation that it’s possible, the cost in hours or value, and the question of how the client prefers to handle it — use one of the revisions provided in the contract, approve as additional, or leave it for a later phase.
Two things happen when this becomes standard. A significant portion of requests simply disappear when priced — not out of bad faith, but because the client had no idea it cost anything. And those that remain are billed, which is how it should have been from the start.
What makes this possible without friction is the contract having stated beforehand: how many revisions are included in each phase, what constitutes a revision, and the value of the additional hour. Charging for something not agreed upon causes conflict; charging for something foreseen in the contract is management.
The approval that never arrives, and the one that arrives and disappears
These are two different and equally costly problems.
The approval that doesn’t come. The material was sent, the client didn’t respond, and the firm can’t move forward, can’t bill the phase, and can’t allocate the team to the next item. Three things cause this, and none are lack of interest: the material was sent without clear instructions on what is expected; the recipient doesn’t decide alone and needs to consult a spouse, partner, or family; and there is no agreed deadline, which makes the approval compete with everything urgent in the client’s life and always lose.
The fix is cheap: every submission includes four elements — what it is, what is expected ("I need a yes or adjustments"), the deadline linked to a practical consequence ("by Thursday to maintain the executive delivery on 20"), and what happens if it doesn’t come.
The approval that arrives and disappears. More dangerous. The client approves by audio, the project advances, and two months later, with construction underway, they say it wasn’t exactly what they approved. Without formal records, this discussion is always lost by the firm — even when it is right.
The rule that closes this: nothing advances with verbal or audio approval. Every approval becomes a document — it can be an image with the date and list of what is being approved, sent back with a request for written confirmation. It takes a minute and solves virtually all project disputes.
The construction asks and cannot wait
During execution, the firm becomes a hub of questions from people with the tool in hand. Here the logic is opposite to the client’s: these questions really are urgent, because a stopped or wrongly executing builder immediately costs money.
Four decisions organize this:
One channel per construction, not per person. Everyone executing on that construction — foreman, carpenter, marble worker, electrician, client when relevant — in one place, with visible history. So the answer given to the electrician doesn’t need to be repeated to the builder.
Technical answers always with reference to the drawing. "It’s 12 centimeters" is an answer no one will remember. "It’s 12 centimeters, according to detail 04 on sheet 07" is a traceable answer and prevents the same question from returning the following week.
Photo before and after anything that will be covered. Installation inside the wall, waterproofing, ceiling structure. It’s the record that resolves future disputes and almost never exists.
Construction decisions that change the project go back to the client. This is the most important boundary: the foreman can ask how to execute; they cannot decide to change. Every change that affects outcome, cost, or deadline goes through the client, in writing, even when it seems small.
Continue reading for free
Fill out once and unlock this and all other blog articles. We charge nothing — we just want to know who we’re writing for.
It takes 20 seconds. Prefer to talk directly on WhatsApp?
Decisions made by message need to become documents
This is the habit that separates a professional firm from one that is always putting out fires. Every relevant decision made in conversation is transformed, the same day, into a short record and sent back for confirmation.
The format that works has four lines and takes two minutes:
- What was decided, in an objective sentence.
- Who decided and when.
- The impact on deadline, cost, or scope, if any.
- What happens now, with date.
Sending this back to the client with the phrase "please confirm this is correct" produces three effects. It formally closes the decision. It often reveals a misunderstanding while it’s still free — because in a significant portion of cases the client responds that they understood differently. And it creates the history that supports any future conversation about what was agreed.
There is a variation of this that is even more valuable in construction: the weekly summary. A message every Friday with what happened during the week, what is coming next, and what is waiting for the client’s decision. It costs ten minutes per construction and produces two effects no one anticipates — the client stops feeling that nothing is happening, and the line "what is waiting on you" speeds approvals without any explicit pressure, because no one likes to appear as the blocked item.
Before executing any change requested in conversation, one sentence: "this changes what was already approved in the previous phase — do you want me to adjust and resend for approval, or do we proceed as is?" It forces the decision to be conscious, records that there was a change, and transfers to the client the choice they were already making without realizing it.
One year in numbers
A firm with three architects and 11 simultaneous projects measured for two months what was happening on the channel before changing anything.
What the measurement showed. 47 hours per month in out-of-contract services — extra revisions, comparative studies, unforeseen execution guidance, and supplier follow-up. Average time between material submission and approval: 16 days. Three projects with open discussions about "what was approved." Two complete phase reworks, costing 84 hours combined.
What was implemented. Contract with number of revisions declared per phase and additional hour value; standard three-part response for every out-of-scope request; material submission always with deadline and consequence; mandatory written approval with four-line record; separate channel per construction; weekly summary per project.
Twelve months later. Out-of-contract hours: 19 per month, of which 14 were billed as additional. Average time to approval: 5 days. Open approval discussions: none. Complete phase reworks: one, due to the firm’s own error.
The calculation. 28 hours per month recovered, at an internal cost of R$ 95 per hour, are worth R$ 31,920 per year in returned capacity. The 14 monthly hours billed as additional, at R$ 210, total R$ 35,280. And the reduction from 16 to 5 days in approval time shortened the average project cycle by about five weeks, allowing the firm to deliver three more projects in the year, with an average ticket of R$ 34,000: R$ 102,000.
Total: R$ 169,200, produced without hiring anyone and without increasing the hourly rate.
The partner summed it up uncomfortably: the firm never had a price problem. It had a problem letting work leave for free through the back door, one polite message at a time.
Communication by project phase
Each phase has a different communication risk, and treating them all the same way is what generates the feeling that the client "changed their mind" when in fact they never understood what was being decided.
Survey and preliminary study. Risk: expectation. It’s the phase where the client imagines things that were not said. The antidote is to write the program of requirements and have it approved before drawing anything.
Preliminary design. Risk: infinite change. This is where the scope leaks the most. The number of revisions needs to be declared and counted out loud at each one: "this is the second of the three revisions provided."
Executive project. Risk: late change. A change here costs much more than in the previous phase, and the client doesn’t know this. Stating the cost before executing is an obligation, not a negotiation.
Coordination and complementary projects. Risk: silence. It’s the longest and least visible phase to the client, and it’s when they feel that "everything stopped." It’s the phase where the weekly summary is most valuable.
Construction. Risk: parallel decision. The client talks directly with the supplier and foreman, decisions are made without the firm, and the result is attributed to the project. The defense is the written rule: execution changes always go through the firm, in writing.
The lead that arrives and the budget that doesn’t close
Lead capture in architecture has a characteristic that hinders: almost every initial contact asks for price, and almost every firm responds with price.
Four changes significantly improve conversion:
Qualify before quoting. Four questions solve this: what is the intended scope, what is the area, what is the desired deadline, and is there already a budget for the project. Quoting without this produces a generic proposal that is compared only by price.
Never give a price in a message without conversation. The isolated number without context is compared with the isolated number from another firm, and the decision becomes an auction. A twenty-minute conversation beforehand completely changes the basis of comparison.
Proposal with detailed scope and what is not included. The "not included" section is the most important and most absent part of the proposal. It prevents future conflict and, paradoxically, increases trust at decision time.
Follow up after sending. Architecture proposals are rarely decided in the week they are sent. Follow-up at two, seven, and twenty-one days, with something useful in each contact, recovers a large portion of what the firm considers lost.
When the firm grows and the partner steps back
Every firm reaches the point where the partner needs to step out of daily service, and almost all make this transition poorly — announcing to the client that they now speak with someone else, which is read as a downgrade.
The transition that works has four steps. The new person joins in, not replaces: participates in conversations for a few weeks with the partner still present. The partner introduces with authority, saying what this person decides alone, not just that they will help. The history goes along, so no one asks the client to retell what was already agreed — which is exactly when trust breaks. And the partner continues to appear at moments of presentation, relevant decision, and problem, with a defined cadence instead of disappearing.
Done this way, the client perceives faster service instead of loss of access, which is exactly how it needs to be sold.
Five mistakes that consume the firm’s margin
- Accepting approval by audio. The discussion that comes two months later is always lost by whoever has no record.
- Executing extra requests without pricing. The margin disappears in three-hour pieces, politely.
- Mixing client and construction channels. The urgent tramples what is being paid for, every day.
- Sending material without deadline and instruction. It’s the number one cause of stalled approval, and it’s one line of text.
- Disappearing during coordination phase. The client interprets silence as abandonment, precisely in the most laborious phase.
The numbers to track
- Out-of-contract hours executed and how much was billed.
- Average time between material submission and approval, per project — the ranking shows where the cycle stalls.
- Percentage of decisions recorded in writing out of total relevant decisions.
- Reworks per phase, with cause classified among firm, client, and construction.
- Proposals sent, followed up, and closed, with time to decision.
- Projects with weekly summary sent, as a percentage of the portfolio.
Architecture is sold as creation and sustained by process. The creative part is almost never the cause of conflict — the cause is usually a revision that no one priced, an approval that no one recorded, and an entire phase in which the client heard from no one. All this lives in the channel, and the channel is the cheapest thing to fix in an architecture firm.
Frequently Asked Questions
How to organize communication of an architecture firm on WhatsApp?
By separating two conversations that currently live on the same number. The client conversation deals with decision, approval, scope, deadline, and value: it has business hours, requires record-keeping, and almost always can wait a few hours. The construction conversation deals with execution, measurement, detail, and unforeseen events: it is urgent by nature, technical, and the right person to answer is often not the same. When the two mix, the urgent tramples the important every day, because the construction question is always more urgent than the project revision — and the revision is what is being paid for. This does not mean two phones, but two conversations with different rules within the same channel, with one channel per construction gathering foreman, carpenter, marble worker, and electrician in one place with visible history.
How to charge for extra project revision without wearing out the client?
By recording and showing the cost instead of refusing or simply doing it. The response that works has three parts: confirm it’s possible, inform the cost in hours or value, and ask how the client prefers to handle it — use one of the revisions provided in the contract, approve as additional, or leave for the next phase. A significant portion of requests disappear when priced, not out of bad faith, but because the client didn’t know it cost anything, and those that remain are billed. What makes this possible without conflict is the contract having stated beforehand how many revisions are included in each phase, what constitutes a revision, and the value of the additional hour. Charging for something not agreed causes fights; charging for something foreseen in the contract is management.
How to record project approval made by message?
By transforming every relevant decision, the same day, into a short record sent back for confirmation. The format has four lines and takes two minutes: what was decided in an objective sentence, who decided and when, the impact on deadline, cost, or scope, and what happens now with date. Sending this with the phrase "please confirm this is correct" produces three effects: it formally closes the decision, reveals misunderstandings while still free, because in a significant portion of cases the client responds that they understood differently, and creates the history that supports any future conversation. The rule that closes the risk: nothing advances with verbal or audio approval. Without formal record, the discussion that appears two months later, with construction underway, is always lost by the firm — even when it is right.
How should the architect respond to construction questions?
With four rules, because during execution these questions really are urgent: a stopped or wrongly executing builder immediately costs money. One channel per construction, not per person, gathering everyone executing with visible history, so the answer given to the electrician doesn’t need to be repeated to the builder. Technical answers always with reference to the drawing, because 12 centimeters according to detail 04 on sheet 07 is traceable and prevents the same question from returning the following week. Photo before and after everything that will be covered — installation inside the wall, waterproofing, ceiling structure — which is the record that resolves future disputes and almost never exists. And the most important boundary: the foreman can ask how to execute, but cannot decide to change, and every change that affects outcome, cost, or deadline goes through the client in writing.
Why does client approval take so long in architecture projects?
Three things stall approval and none of them is lack of interest. The material was sent without clear instructions on what is expected, and a PDF with the phrase "sent for approval" doesn’t say if it’s to approve everything, comment, or choose. The recipient doesn’t decide alone and needs to consult spouse, partner, or family. And there is no agreed deadline, which makes approval compete with everything urgent in the client’s life and always lose. The fix is cheap: every submission includes four elements — what it is, what is expected, with an explicit request for a yes or adjustments, the deadline linked to a practical consequence, like by Thursday to maintain the executive delivery on 20, and what happens if no response comes. In a real firm, this reduced the average approval time from 16 to 5 days.
The firm doesn’t lose margin on price — it loses on loose conversation
VeyloCRM separates the client channel from the construction channel on one number, keeps the history of each project visible to those executing, records what was approved and what was requested out of contract, and reminds follow-up when an approval stalls — so no hour is given away in three-hour pieces.