How to Ask Someone to Be Your First Client

An ask that works contains three things and can be read in the time it takes to cross a room. Everything else in it is decoration, and decoration is what makes it sound like begging.

The three parts every workable ask contains

The named job. Not what you do in general, but the specific piece of work you are proposing to do for this person. "Your back garden" beats "landscaping services".

The terms. What it will cost, how long it will take, and when you could start. Vagueness here reads as either inexperience or a trap, and both cost you the answer. The figure itself is a decision you make before you write, in pricing a first client job.

One question they can answer. Not an invitation to think about it. A question with an answer at the end of it: "Want me to do it Saturday morning?"

Put together it sounds like this. "I am doing garden clearances this month. Yours looks like half a day - I would bag everything and take it away with me. Want me to come Saturday morning?" Nothing in that is clever. All of it is answerable.

The order matters as much as the contents. Job, terms, question. Lead with the question and you are asking for a favor before they know what they would be agreeing to. Lead with the terms and it reads as a price list from somebody who has not looked at their situation.

Why a specific request gets answered and an announcement does not

"I am open for work, let me know if you hear of anything" moves the entire job onto them. They have to work out what you actually do, decide whether they need it, imagine what it would cost and then compose a reply. Four decisions in exchange for doing you a favor, so what comes back is "will do!" — which feels like a reply and contains nothing.

A specific request leaves one decision: yes, no, or a correction. Corrections are the good outcome, because "not the garden, but could you do the gutters?" is a customer.

There is a second effect. An announcement asks people to sort you into a category they have to invent. A specific request tells them what you are, and they repeat it to somebody else in the words you gave them.

How to make it easy to say no, and why that gets more yeses

Write the exit into the message yourself. "If it is not something you need, just say so and I will not bring it up again."

That feels like handing them the escape route, and it is. Without it, the polite response to a request somebody cannot fulfill is silence, and silence is the worst reply you can get: it tells you nothing and keeps the contact sitting open in your head.

A clean no is usable. You cross the name off, you ask the next person, and the relationship survives intact — which matters, because a no today does not stop that person passing your name on later.

There is a version of this that goes too far. "No worries if not, honestly do not feel any pressure, I know how busy you are" stacks three exits on top of each other and reads as somebody who has already answered on the other person's behalf. One exit, one clause, then stop writing.

What to leave out, starting with the apology

Cut "sorry to bother you". Cut "I know this is random". Cut "I hate asking, but". An apology invites the other person to agree that you are an imposition, and they will take the invitation because you extended it.

Cut the backstory. Nobody needs to know why you are doing this, and the moment the ask acquires a reason it turns into a request for help rather than an offer of work.

Cut the list of everything you can do. A menu is not an offer. Pick the one job that fits this one person.

And cut the word "just". "I was just wondering if you might just need" - every one of those shrinks the sentence you are standing on.

Where the ask should land: in person, message or call

Match the channel to the way you already talk to this person. Somebody you see every week gets it in person, in the ordinary flow of a conversation, not summoned to a meeting. Somebody you text gets a text. Somebody who has never phoned you should not get a phone call, because an unexpected call from a person who wants something is an ambush and gets answered defensively.

Somebody you have not spoken to in years is the hard case. Message them, acknowledge the gap in one clause, and do not write three paragraphs of reunion first. That is worse, because it makes the catch-up look like a pretext.

Strangers are a different craft with different rules, worked out in how a cold message reads to the person receiving it. And the order you go through people in matters as much as the wording: who to ask first when you need a first customer.

A list of safe people and a twelfth rewrite

You can rewrite a message twelve times. If the person has no version of the problem, the twelfth version gets the same answer as the first, and the rewriting was avoidance dressed up as preparation.

Test it before you send. Can you name a specific occasion when this person had this problem? Not a hunch that they probably need it - an actual instance you know about. If you cannot, they are on your list because they are safe to ask rather than because they are likely to buy, and a list of safe people produces a lot of practice and no customers.

Run the same test across the whole list. If you cannot point at anybody on it having had this problem in living memory, the list is not the issue and neither is the phrasing - the job is. The fix is picking a different piece of work, one you can name somebody needing last week.

When a batch of asks produces silence instead of noes, that is a different diagnosis: what to do when nobody replies to your outreach. And when somebody answers with interest, the next move is turning that into a booking without leaning on them, which is closing a first customer without sounding pushy.

Send it once, unedited, to the person on your list you are least afraid of. Then send the same thing to the one who scares you.