Writing to an architect for the first time

Architects don’t need another marketing email. They need to know that you’ve actually read their application.

We’ve seen the inside of a lot of architects’ inboxes. The pattern of kitchen-designer outreach is bleakly consistent: a generic enquiry, often a Mailchimp template, often signed by “the team”, often referencing the practice’s Houzz profile but not any actual project they’re working on. They get deleted in about four seconds.

The good ones look completely different. They’re short. They mention a specific project the architect has filed in the last week. They reference one heritage constraint or scope detail by name. They offer to send one example of similar work, in the body of the email, not as an attachment. They’re signed by a person.

That’s the whole secret. Below is roughly what we’ve seen work, and why each part of it matters.

The shape of a useful first letter

One paragraph on the project

Open with the project. Not your studio. The architect already knows what they filed; they want to know that you read it. Mention the location, mention the listing if there is one, and mention one detail that signals you understood what the project actually is. “The lower-ground kitchen with the new lightwell” says more than “your recent application”. The detail proves you’ve done the reading. The reading proves you’re worth a reply.

One paragraph on your studio

Resist the urge to list everything. One sentence on the kind of work you take on, one sentence offering an example of similar work that might be relevant, one sentence on what you’d like the conversation to be — usually a fifteen-minute call, not a site visit, not a sample drop, not a brochure. You’re asking for a small thing. Architects say yes to small things.

A clean sign-off

No “Best regards” boilerplate. No five-line email signature with social icons. Your name, your studio, a phone number, a link to one project you’re proud of. That’s it.

The architect is going to forward your email to one person — the homeowner — if it’s good. Write it as if you know that’s what will happen.

What not to do

Don’t attach a brochure on the first email. Architects don’t open brochures. The homeowner doesn’t want a brochure either; they want a designer who understood the heritage angle.

Don’t mention pricing. Pricing on a first email reads as a sales tactic, even when it’s offered as “just to give you a sense”. The architect is not the buyer; the homeowner is. Talking about pricing on the first email skips two steps and makes you sound like volume.

Don’t reference the architect’s portfolio in vague terms. “I love your work” is worse than saying nothing. If you genuinely want to reference their portfolio, name a specific project. If you can’t name one, leave it out.

Don’t copy the homeowner. The architect introduces you when, and if, they think you’re right for the project. That’s the relationship. Bypassing them — even by going to the planning officer for the homeowner’s details, even via the Land Registry — costs you the architect for the next decade.

Why we drafted Planning Signals to do this

The architect introduction is the highest-leverage piece of writing in a kitchen designer’s month. It’s also the bit that gets put off, because it requires actually reading the planning application, then writing something that sounds like a person.

We added a draft generator to the product because we kept seeing the same designers miss the same projects, not for lack of skill but for lack of time. The draft is a starting point, not a send button. You read it, you change the bits that sound wrong, you mention something the model couldn’t have known, and you sign off as yourself.

The kitchen designers we’ve been quietly working with use it once or twice a week, on the projects that matter. The rest of the time they don’t need it. The right answer to most planning applications, frankly, is to read it, decide it’s not for you, and move on.