Here is a situation most freelancers meet within their first few contracts. You have a clear task, a friendly client and a deadline that is getting close. But every time you ask a question about the setup, the reply is “let me check with the team”, and a week later you are still waiting. The work is not hard. The trouble is that nobody on the client side seems to be the person who can simply say yes. This post explains, in plain language, why that happens and how to fix it by asking who the decision-maker is before you start.
What “decision-maker” actually means
It is simpler than it sounds. The decision-maker is the one person who can approve a choice and make it stick. Not the person who has opinions, not the one who forwards your messages, and not the one who manages the budget but never sees the technical details. It is whoever, when they say “go with option B”, ends the conversation.
In a company with a handful of people this is usually obvious. In a bigger organisation it can be surprisingly hidden. You may be dealing with a delivery manager, a security contact, a finance approver and a team lead, and each of them can block you without any of them being able to approve you. That is why freelancers who work remotely, without the hallway chats that would reveal who really decides, benefit from asking directly.
Why remote freelancers feel this more
When you sit in an office, you pick up the pecking order by watching. Who do the others glance at before answering? Who gets the last word in a stand-up? As a remote contractor you miss all of that. Everything arrives through chat and email, so a decision that would take thirty seconds at someone’s desk can take days across time zones, especially if three people each need to reply.
There is also a trust element. New clients often hesitate to hand over authority to someone they have not worked with. For more on how that confidence builds across a first project, see this piece on earning a new client’s confidence early in a working relationship covers it well. Clear decision rights are one of the quiet ways trust grows: the client sees that you know how to run a project.
Three questions to ask in your first call
You do not need a formal process. Three plain questions, asked early, cover most of it.
- “Who will make the final call if we have to choose between two approaches?” Get a name, not a team.
- “How quickly can they usually answer?” This sets your expectations and lets you plan around slow replies.
- “If you and your team disagree, how is that settled?” You are asking for the rule: does everyone need to agree, does the majority win, or does one person decide after listening?
Most clients appreciate the questions. They signal that you are thinking about their project’s momentum rather than just your hours.
Put it in writing, but keep it light
After the call, send a short follow-up message. Something like: “Thanks for the call. To confirm, Priya makes the final decisions on infrastructure choices, I will send options by Wednesday, and she aims to reply within two working days.” That is it. No contract, no template, just three facts a client can easily correct if you have misunderstood.
This message does two jobs. It gives you something to point to later if a reply is slow, and it lets the client notice early if the person you named is not actually the right one. Fixing that on day one is far easier than discovering it in week three.
What to do when the decision-maker keeps changing
Sometimes you ask, you get a name, and then a new person starts overruling the old one. This is common when a project gets noticed by someone senior. Stay calm and check in politely: “I noticed Sam has a different view from what Priya approved. Which of them should I treat as the final word on this?” Make it a question about who, not an accusation about what happened.
If the confusion keeps repeating, treat it as a scope risk. Explain that changes in direction mean extra time, and ask the client to confirm in writing who has the final say. Freelancers who stay friendly but clear about this tend to avoid the worst of the endless revisions that wear down a small contract.
Your own decisions count too
The idea works in the other direction. If you take on a project with a partner, or hand part of the work to another contractor, agree who decides what. Even something as small as which cloud region to use can create a long thread if two experienced people each think theirs is the sensible choice. A line in your kickoff notes such as “technical choices: I decide after hearing from you; scope or budget: you decide” can save a lot of frustration. Newer freelancers will find a useful general grounding in this list of beginner questions about starting out as a DevOps freelancer, which is a sensible companion to these habits.
A quick example outside of tech
The same approach helps anywhere a group has to act together. Think of a family organising a trip for a relative who needs planned care in another country. There are dates to fix, paperwork to collect and a budget to agree, and the family tends to circle unless somebody takes charge of each part. A website like BestHeartSurgery offers background reading on hospitals, destinations and services for people exploring options abroad, and it states that it is an information resource rather than a treatment provider. The reading helps, but the household still has to pick who handles the practical arrangements.
A short checklist you can reuse
- Name the decision-maker for each type of choice: technical, scope, budget.
- Ask how fast replies usually come, and plan around the answer.
- Confirm the rule for disagreements in one line.
- Send a recap message after the first call.
- Revisit the arrangement if the people involved change.
For freelancers who combine different kinds of work, it is also handy to see how others structure mixed engagements. This article on a freelancer who blends cloud engineering with advisory work shows how many hats one person can end up wearing, which is exactly when clear ownership matters most.
Try it on your next contract, or retrofit it on your current one. The conversation takes five minutes, and the weeks of waiting it avoids are the best reason I know to ask.
