The first message: three lines, and a reason that already happened

You write your first message to a new connection.

Five lines. Who you are, what your studio does, which software you use, what a typical project costs, and a link to your portfolio. You read it twice, fix a comma, and send it.

Then you wait.

Nothing comes back. Or, if you are lucky, one line: thanks, we already have someone.

The door closes before it opened, and you are not sure what you did wrong. The message was polite. The work is good. The price was fair.

The message was not the problem. The reason was. There wasn't one.

A message with no reason is a pitch

Put yourself on the other side of the screen for a second.

An architect running a practice, or a development manager with a tender due, gets a message like yours twenty times a week. From studios, from freelancers, from platforms selling renderings by the square metre, from tools promising to replace all of it. The messages look the same. Same opening, same list, same link.

They stopped reading them long ago. They recognise the shape and scroll on. Not out of rudeness. Out of self-defence.

So when your five lines land in that inbox, they get judged as pitch number twenty-one rather than as your five lines. And a pitch has one answer: no, or silence.

What gives a message a reason

Something that already happened, or is happening now.

That is the whole turn, and once you see it you cannot unsee it. A first message earns a reply when it follows an event in the real world that involved both of you.

A project they told you about when you met, online or in person. A challenge they mentioned in passing. An opportunity you can see in their market that they may not have noticed yet. Your portfolio book that landed on their desk last week. Your letter. A post of yours they touched. Someone who introduced you at a dinner.

Every one of those is a reason. And notice where most of them come from: your own board. The meeting, the book, the letter, the post. The message does not create the relationship. It follows one that the rest of your marketing already started.

If you have no reason, you don't write. Not yet. You go and create one first: send the book, go to the event, post the case study. Then you write.

Build a reason bank before you build a message list

Most studios do this backwards. They build a list of two hundred architects, then look for something to say to each one. The result is two hundred pitches.

Turn it around. Start from what happened this month and work outwards to the people it happened with.

Who did you meet at the last event? That is a list. Who received your book in the last campaign? That is a list. Who opened your letter, liked your post, replied to your newsletter, sat in a room with you at a client's office? Every one of those is a short list of people who already have a reason attached to their name.

Those short lists are your outreach for the month. Not the two hundred. The thirty who have a reason. You will write fewer messages and get more replies, and each reply is worth more because it started warm.

Write the reason down next to the name in your CRM before you write a single line. If the reason column is empty, that person is ready for a book, or a letter, or an invitation, rather than for a message. Send that first.

The three lines

With a reason in hand, the message writes itself. Three lines.

Line one is the reason. "Good to meet you at the talk on Tuesday." "Your copy of our book should have reached your office this week." "Saw your comment on the hospital project, thank you." One sentence, and it does the heavy lifting: it tells them you are not a stranger.

Line two is one thing useful to them. Not your price list. Not your software. One thing that helps the person reading: a project like theirs that you finished, an insight from the talk, a note about the tender they are working on. It is about them, or it is out.

Line three is one small question. Something they can answer in one word. "Is this the kind of project you have coming up?" "Did the book reach you?" "Worth a short call in the next weeks, or too early?" Then stop. No sign-off paragraph, no "looking forward to hearing from you", no second question.

Three lines. Send. And this time the wait is short.

The job of the first message is a reply

Not a project. Not a call. Not a quote request. A reply.

That sounds like a small goal, and it is, on purpose. A reply turns a stranger into a contact. A contact can be warmed. A stranger cannot.

When the reply comes, you are still not selling. You are warming. Every next message has its own reason, exactly like the first one did: your new case study went live, one of their projects appeared in the news, you promised in the meeting to send a reference. Each message follows something real, so each message is welcome.

And when nothing happened this week? Then you write nothing. Silence beats "just checking in". A message with no reason resets you back to pitch number twenty-one, and you spent a good first message to get out of that pile.

A rhythm you can keep

Reasons do not arrive on a schedule, so the follow-up cannot run on one either. "Every Tuesday I message ten people" produces ten messages with no reason on most Tuesdays.

Run it the other way. Once a week, look at what happened: what you published, what you sent, who you met, what your contacts did. Each event gives you a handful of people who now have a reason. Message those, and only those. Some weeks that is twenty messages. Some weeks it is three. Both are right.

Keep the thread in the same place. Every message, every reply, every reason goes into the pipeline you keep for LinkedIn alone, the one from part one of this series. In three months you will see something most studios never see: which reasons get answered, and which of your board pieces created them.

Why they answer

Every message follows something real. That is the entire reason people answer them.

You are not a stranger in their inbox. You are a follow-up. The book came first, or the meeting, or the letter, or the post. The message is the second touch, and second touches get answered.

That is also why the message is only one piece. It cannot work alone. It follows the meeting, the book, the letter, the post, and it hands the conversation to the discovery call and the proposal that come after. One piece of a bigger board: the Archviz Business Operating System.

What should your first message be following?

If you don't know what your first message should be following, that is the real question, and it is a positioning question rather than a copywriting one. Which pieces do you have, which are missing, and in which order should they run.

That is what a Studio Health Check answers. €107, thirty minutes on your whole business, credited if you continue. You leave with the missing pieces, an action plan, and a written 90 day roadmap. As Roderick Galea of Solid Eye put it after his: "It's specific and structured. I would recommend."

Book your Studio Health Check at businessofarchviz.com.