An architect I talked to last spring sent a proposal for a 3,200 sq ft custom home build. The clients had walked her property, sat in her office for two hours talking about ceiling heights and north light, and left saying "we'll be in touch by Friday." Friday came and went. So did three more Fridays. She marked the lead dead and moved on.
Eleven weeks later they emailed her back. They'd been waiting on a HELOC approval, then their kid's college tuition came due, then they had to sort out the easement on the back of the lot. Could they still hire her? They signed the contract that afternoon for $187,000 in design fees.
That story isn't unusual. It's what happens in architecture sales cycles. And it's what happens when an architect understands that silence almost never means "no" — and follows up the right way until it actually does.
Why Architecture Clients Go Quiet After the Proposal
Architecture has the longest decision cycles of almost any freelance trade. You're not selling a logo or a one-month consulting engagement. You're selling something that will cost the client between $50,000 and several million dollars, take 12 to 36 months to deliver, and reshape their daily life or their business.
That kind of decision doesn't get made in a week. It rarely gets made in a month. Clients have to coordinate with banks, partners, planning departments, family members, and sometimes co-owners or investors. Any one of those parties can stall the whole process for weeks at a time, and none of them have anything to do with whether your proposal was good.
Research consistently shows that 80% of sales require at least five follow-up attempts, and 44% of salespeople give up after just one follow-up. Architects lose work not because their fee is wrong or their portfolio is weak, but because they stop following up at exactly the moment the client was finally ready to talk again.
If you want the full mental model for how follow-up works across freelance trades, the complete guide to proposal follow-ups for freelancers lays out the psychology and structure in detail.
The Architect Follow-Up Timeline
The cadence that works for architecture is longer and gentler than what works for a graphic designer or a copywriter. A logo client decides in two weeks. A custom home client decides in two months. Your follow-up rhythm has to match.
Here's a sequence that's reliable for residential and small commercial work:
Day 3: A soft confirmation that the proposal landed. Frame it around questions about scope, drawings included, or phasing — not around when they'll decide.
Day 10: A value-add note. This is where architects can do something almost no other freelancer can. Send a brief observation about the site, a thought about a constraint you noticed during the walk-through, or a quick comparable from a recent project at a similar budget.
Day 21: A planning-cycle nudge. Architecture projects are calendar-sensitive — permitting takes months, construction windows hinge on season. If their goal is to break ground next spring, the schedule conversation is itself a real reason to reach out.
Day 35: A second value-add or schedule update. Something specific to their project. Don't repeat yourself.
Day 50–60: The breakup email. Short, professional, no pressure. Tell them you don't want to keep cluttering their inbox, that you'd love to work together if the timing lines up, and that they should feel free to reach out later.
That's five touchpoints over about two months. For architecture, that's not aggressive — it's about right. Some practices stretch the cadence further on multi-million dollar commercial proposals, where decision cycles can run six months or more.
4 Architect Follow-Up Email Templates
These aren't word-for-word scripts. They're frameworks. Keep your own voice — clients can tell when you're reading from a template.
Template 1: Day 3 Confirmation
Subject: Proposal for the [Project Address] project
Hi [Name],
Just wanted to confirm the proposal came through okay — sometimes attachments get caught in spam filters or quarantined by corporate IT.
If anything in the scope, drawing set, or phasing isn't clear, I'm happy to walk through it. I want to make sure we're aligned before you make any decisions.
[Your name]
Template 2: Day 10 Value-Add
Subject: Something I noticed about the [Project Address] site
Hi [Name],
I've been thinking more about the site since our walk-through. Two things stood out that I didn't mention in the proposal — [specific constraint or opportunity, e.g. "the eastern setback is tighter than I initially read, which actually opens up an interesting option for the kitchen orientation"].
Happy to talk through it on a quick call if that would be useful. And if you have any questions about the proposal in the meantime, just let me know.
[Your name]
(Note: This only works if the observation is genuine. Don't fabricate one. If you don't have something specific, skip this template and go to template 3.)
Template 3: Day 21 Planning-Cycle Nudge
Subject: Schedule for [season/year] starts
Hi [Name],
I'm starting to map out my schedule for the rest of the year, and I wanted to flag where things stand on your project.
If you're still aiming to break ground in [season], we'd ideally want to start schematic design in the next four to six weeks to keep the permitting timeline realistic. No pressure if the timing has shifted — I just wanted you to have an accurate picture of the lead time.
[Your name]
Template 4: The Breakup Email (Day 50–60)
Subject: Closing the loop on the [Project Address] proposal
Hi [Name],
I don't want to keep filling your inbox, so I'll keep this short. If the timing didn't work out, priorities shifted, or you decided to go in another direction, that's completely fine — I appreciate you considering me either way.
If circumstances change down the road, please don't hesitate to reach out. I'd still be glad to work on the project.
Best, [Your name]
The breakup email feels counterintuitive. Why would you tell a prospect you're stepping back? Because it removes the social pressure that's been making them avoid replying. Clients who feel cornered ignore emails. Clients who feel released often write back the same day. It's the single highest-response email in a follow-up sequence.
What Makes Architecture Follow-Ups Different
Architecture sits in a weird spot. Your fee is large enough that clients won't decide quickly, but the work is intimate enough that the relationship has to feel personal. Generic "just checking in" emails read as wrong in a way that doesn't quite happen in shorter-cycle trades.
A few things change how you should think about follow-up if you're an architect:
The site is your asset. Almost every other freelancer has to follow up with words. You can follow up with observations about a physical place. A note about how the light hits the lot at 4pm, a quick thought about a comparable down the street, an offhand mention of a material that would weather well in their climate — these signal that you've been thinking about their specific project, not running a sequence.
The schedule is real. Permit timelines, construction seasons, and project windows aren't manufactured urgency. They're hard constraints. You can mention them in a follow-up without sounding like a salesperson because they actually matter. A web designer's "I'm filling up my May schedule" sometimes lands as pressure. An architect's "we'd need to start schematics by July to break ground next April" lands as a fact.
The decision often isn't theirs alone. A homeowner couple is often two clients. A small business is often three or four. When you follow up, assume your proposal is sitting in someone's inbox while they wait for a partner, spouse, lender, or board to weigh in. Your follow-ups have to be forgiving of that delay.
Handling the "We're Still Comparing Bids" Response
If the client tells you they're getting other proposals, most architects either go silent or get nervous about price. Both are wrong.
The right response is to acknowledge it and then redirect the comparison. Something like: "That makes sense — for a project at this scale, you should be comparing options. While you're looking at the others, the things I'd encourage you to compare beyond fee are the level of construction administration included, the number of design iterations, and how each architect handles changes once the contractor's on site. Those are where surprise costs usually live, and they're easy to miss when you're just looking at the bottom-line number."
You're not bad-mouthing competitors. You're giving the client a framework that benefits anyone who runs a thorough practice — which probably includes you. Clients comparing proposals often default to fee because nobody has given them anything else to compare. Give them something else.
The Problem With "Just Checking In"
Look at the last follow-up email you sent on a stalled proposal. There's a decent chance it said some version of "just checking in to see if you had a chance to review the proposal."
That email is invisible. Clients read it, vaguely intend to reply, and forget about it inside a minute. It carries no new information, asks no specific question, and gives them no reason to write back today instead of next week.
Every follow-up email should have exactly one reason for being. A specific question about scope. A useful observation about their site or project. A scheduling fact they should know. A genuine deadline. If your email doesn't have one of those, don't send it yet. Wait until you have something.
Subject lines that actually get proposal follow-up emails opened breaks down what works for this in more detail.
When Fee Is the Real Reason They Went Quiet
Sometimes clients aren't slow because of permits or partners. They're slow because the fee surprised them and they don't know how to say so.
The signals to watch for: lots of engagement during the discovery phase, then a sharp drop-off the day after they got the proposal. Quick replies before the number, slow replies after. Vague questions about "what's actually included."
Discounting immediately is the wrong move. It trains the client to expect a lower number every time and signals you weren't sure about your fee in the first place.
A better play is to open the door to phasing on your Day 10 or Day 21 follow-up. Something like: "If the full scope is more than you'd planned for right now, I'm also happy to talk about doing this in phases — we could start with schematic design only, get you a permit-ready set, and decide on construction administration separately."
This doesn't cut your hourly. It restructures the engagement. A lot of clients would rather start smaller and grow the scope than say no entirely. And it shifts the conversation from "can we afford this?" to "which phase do we start with?" — which is a much better place to be sitting.
What If They Already Hired Someone Else?
About one in five proposals that go quiet do so because the client chose another firm. They feel awkward telling you. So they don't.
If a client eventually replies and tells you they went with someone else, don't argue. Don't ask why. Send a short, gracious reply, wish them well on the project, and ask if you can stay in touch for future work or if they know anyone else who might be planning a project. About a quarter of these conversations turn into a referral or a project two years later when the first architect didn't work out. Treat the relationship as long-term and most architects who could've been competitors become friendly contacts in your local market.
For a deeper look at why clients vanish in the first place, why clients ghost proposals (and what to do about it) covers the most common patterns.
How Many Times Should You Follow Up?
Five follow-ups over roughly eight weeks is the right ceiling for most residential and small commercial work. On larger commercial projects with longer decision cycles, you can go further — six or seven touchpoints over three months isn't excessive if the proposal is six figures or more.
After the breakup email, if there's still no response, move on. Don't keep poking. Just leave the door open. "Feel free to reach out if anything changes down the road" takes ten seconds to write and occasionally pays off two years later when the client's circumstances shift.
How many follow-ups to send after a proposal has the underlying data on where response rates drop off if you want the full breakdown.
Automating the Mechanics Without Losing the Personal Touch
If you're a sole practitioner sending six or seven proposals a month — or a small studio with two architects each running their own pipeline — tracking which proposal is on day 10 and which is on day 35 becomes its own task. It's the kind of administrative work that quietly slips when you're heads-down on construction documents for an existing client.
This is exactly what we built ChaseNudge for. It handles the reminder sequencing so you never forget a follow-up, while letting you keep full control over the actual message and timing. You set the cadence once, and it makes sure no proposal goes more than two weeks without contact — even when you're buried in CDs or on site for a punch list walk.
The tool doesn't write the emails for you or replace the judgment calls — like when to share a site observation versus when to send a schedule nudge. It just removes the overhead of remembering where every open proposal is in its sequence.
The Bigger Picture: Follow-Up as Part of Your Practice
The architects who close the most work don't necessarily have better portfolios or better fees than the ones who don't. They have a follow-up process they actually run.
They send proposals, follow up on a clear schedule, and do it for every lead — not just the ones they remember or feel motivated about. They treat follow-up as part of the job, the same way they treat issuing RFIs to a contractor or filing a permit application. It's not optional. It's just the work.
If you close one more proposal a year because of a better follow-up process, that's often $50,000 to $200,000 in design fees that were already in your pipeline. The portfolio was strong enough. The fee was right. The proposal was thorough. The only thing missing was making sure the decision actually got made.
Don't leave it to chance.
FAQ
How soon should an architect follow up after sending a proposal? Three to four days is the right window for the first follow-up. Any sooner reads as anxious or pushy on a six-figure fee; much longer and the client's momentum fades. Frame the email around clarifying questions, not around when they'll decide.
How many times should I follow up on an architecture proposal before giving up? Five follow-ups over roughly eight weeks is the standard range for residential and small commercial work. On larger commercial projects, six or seven over three months isn't unreasonable. After a breakup email, move on but leave the door open.
What should an architect say in a follow-up email to a slow client? Each email should have one clear reason for being — a specific question about scope, a site observation, a schedule fact tied to permitting or construction season, or a phased-engagement option. Generic check-ins get ignored. Specific, useful follow-ups get replies.
What if the client says they're getting other architectural bids? Acknowledge it, then redirect the comparison. Encourage them to compare construction administration scope, design iterations, and how changes are handled — not just the bottom-line fee. Clients comparing proposals default to price unless someone gives them a better framework.
Should I lower my fee if a client goes silent after seeing the proposal? No. Discounting trains clients to expect lower numbers and signals you weren't confident in your fee. A better move is to offer phased engagement on a later follow-up — starting with schematic design only, for example — which preserves your rate and opens the door to a smaller initial commitment.