If you freelance in DevOps, most of your work begins with a call. A client describes a flaky deployment or a cloud bill that went sideways, you say “sure, I can help”, and you both hang up feeling good. Then the real project starts, and you discover how much you each filled in on your own. The habit that fixes this is wonderfully small: a quick written confirmation after the call. Yet a surprising number of freelancers resist it, usually because of a myth or two. Let us go through six of them, in the spirit of a friendly chat over coffee.
Myth 1: “A good client relationship does not need paperwork”
It sounds warm, and it is half right. A good relationship is the reason the message will be received kindly. But relationships are made of people, and people forget. A friendly client who briefly mentions “and you will look at monitoring too” on the way out of a call is not being sneaky; they honestly believe it was agreed.
A confirmation is not paperwork in the stiff sense. It is a text that says, “Lovely to chat. Here is what I took away.” If the relationship is as good as you hope, the reply will be a thumbs-up or a small tweak. If the reply reveals a different picture, you are glad you found out.
Myth 2: “It makes me look like I do not trust them”
Of all six, this worry is the most common, and it is nearly backwards. Clients mostly read the message as professionalism. Think about how you feel when a plumber texts you the arrival window and the call-out arrangement the evening before. You do not think they are suspicious of you. You think they are organised.
The trick is tone. Open with thanks, use “as I understood it”, and end with an invitation: “let me know if I have got anything wrong”. Phrased this way, the message sounds like care, not a contract clause.
Myth 3: “My contract already covers everything”
A contract is a wonderful backbone, but it tends to describe the project in broad strokes. The details that cause friction are small and live in conversations: which environments you can touch, who approves a change, whether weekend support is assumed. Those details rarely make it into the formal text, especially for short engagements where nobody wants to wrestle with paperwork.
Think of the follow-up message as the footnote that keeps the contract honest. It records the daily-life details that came up on the call. When you built your client base through channels like those described in our piece on building a reliable network and finding mentors, you probably noticed that experienced freelancers quietly swear by this habit.
Myth 4: “Only large engagements deserve a write-up”
Honestly, small jobs are where it helps most. A two-day fix feels too tiny to write down, so nothing is written, and then it grows. “Could you also check the staging server while you are in there?” turns a fixed-price job into a free extension unless somebody pauses to state the boundary.
For small jobs the message can be a single line: “Confirming I will fix the failing build and test it on staging by Thursday; anything further we will agree separately.” Ten seconds to type, and it keeps both sides comfortable.
Myth 5: “If I got something wrong, the client will correct me”
Many clients will not, at least not in the moment. Maybe they are busy, maybe they assume you know your own job, or maybe they are not technical enough to spot the gap. They will notice later, when the thing delivered is not the thing imagined, and by then correcting you costs real money and awkward feelings.
A written confirmation gives them a low-pressure moment to correct you. Reading a short summary at their own pace is much easier than interrupting a call to say “wait, that is not what I meant”. Our guide on earning the confidence of first-time clients makes a similar point: trust grows when people feel nothing is being hidden or assumed.
Myth 6: “Writing it up takes too long”
It takes about three minutes if you follow a template, and the template is three questions:
- What did we agree you would do, and what is outside it?
- By when, and what happens next on each side?
- If something changes, what is the plan for telling each other?
Compare those three minutes with the hours spent reconstructing a conversation weeks later, or the awkward email that begins “I am not sure we ever agreed this”. Even for a busy freelancer juggling several clients, the maths comes out firmly in favour of writing.
What a good message actually looks like
Here is a sample you can copy and adapt:
“Thanks for the call today. Just so we are on the same page: I will set up the deployment pipeline for the main app and document the steps, with a first working version by next Friday. Hosting costs stay on your account. If the app needs anything beyond that, I will tell you the time and cost before starting. Shout if I have missed anything.”
It is four short sentences. It names the work, the date, the cost responsibility and the change rule, and it still sounds like a person wrote it.
A word about money matters
Freelancers eventually bump into questions about invoices, registrations and how income is recorded. Those are for a professional to answer, not for a blog post or a client chat. If you are looking for one, a directory such as BestCaNow gathers chartered accountants in one searchable place, with filters for city, area of expertise and whether the meeting happens online or face to face. When you do speak with someone, send them the same kind of follow-up message, and keep the thread with your other records.
Weaving it into a freelance week
The easiest way to keep the habit is to tie it to a trigger you cannot miss. End every client call by saying, “I will send you a quick summary today.” That sentence does two jobs. It commits you to the message, and it tells the client to expect one, so the message arrives as a courtesy and not a surprise. Put a reminder in your calendar for the last ten minutes of the day if you tend to forget.
If you have a side income alongside a job, the habit matters even more, because your time is limited and your boundaries need to be clear. The ideas in our notes on running a freelance sideline next to a day job point the same direction: clarity up front protects the hours you have.
The short version
Written confirmation is not about distrust, bureaucracy or big projects. It is about giving two busy people one shared version of a conversation that would otherwise exist in two slightly different forms. Try it after your next call, keep it friendly and keep it short. You will probably get a cheerful “yes, that is it” most of the time, and every now and then you will get a reply that saves your whole week.
