Freelance DevOps work lives or dies on proof. A prospective client rarely has time to read a long write-up of a past project, yet they want evidence that you can solve a problem like theirs. The practical answer is a one-page case study: a single page that shows the situation, your decision and the result. But there is more than one way to lay that page out, and the layout changes who it persuades. Here are three popular layouts weighed against each other, with the costs and benefits that count for independent engineers.
What we are comparing, and how
Each format has to answer the same questions inside one page: what was the problem, what did you change, what happened afterwards, and what should the reader do next. We will judge them on four criteria that freelancers actually care about.
- Speed to write. You have billable work and little spare time.
- Credibility. Does the page show your thinking, not just the outcome?
- Confidentiality. Can you share it without exposing the client?
- Fit for the reader. Does a technical lead or a budget holder find it useful?
Format one: problem, action, result
This is the classic. Three short blocks: the situation the client faced, the work you did, and what changed. A fourth line can add a closing next step, such as an invitation to talk.
Strengths. It is the fastest to write, because the structure is familiar and each block can be two or three sentences. Non-technical readers follow it without effort, which suits budget holders.
Weaknesses. The action block tends to become a list of tools, which technical readers find thin. If the result is stated vaguely, the whole page reads as a boast. Because it is so common, it also blends in with everyone else’s.
Suits: small clients and quick introductions, where clarity beats depth.
Format two: the decision record
Here the page is organised around a choice. You state the context, the options you considered, the option you picked and why, plus what you would watch afterwards. The result appears as a short closing note rather than the headline.
Strengths. It shows judgement, which is what clients buy from a freelancer. Technical leads respond well to the visible trade-offs, and it is easy to make confidential because it focuses on reasoning rather than names and figures.
Weaknesses. It takes longer to write, since you must reconstruct the alternatives. A reader looking for a headline outcome has to work harder to find it. If you are early in your freelance career and have few projects with real choices behind them, you may struggle to fill it.
Suits: architecture and platform work, and clients who will be reviewed by their own engineers.
Format three: before and after, side by side
The third format splits the page into two columns or two short lists. On the left, how things worked before; on the right, how they work now. A single sentence on top says what drove the change, and another at the bottom names what comes next.
Strengths. It is the most scannable of the three. A reader can see the difference in seconds, and the comparison makes improvement concrete without needing numbers. It works well when the change is a process or workflow, such as a release routine.
Weaknesses. It hides the reasoning, so it can feel like marketing. Subtle changes, such as better observability, are harder to display as a list of states. And it invites exaggeration, because the “before” column rewards a gloomy description.
Suits: process improvements, migrations and anything where the old and new states are easy to describe.
A quick comparison table, in words
- Fastest to produce: problem, action, result.
- Strongest signal of expertise: the decision record.
- Easiest to scan: before and after.
- Safest for confidentiality: the decision record, closely followed by the others once identifying details are removed.
- Most likely to look generic: problem, action, result.
Choosing between them
Match the format to the person reading. If your usual first contact is a founder or manager, lead with problem, action, result or before and after. If your usual first contact is an engineer who will vet your thinking, use the decision record. Many freelancers keep two or three pages in different formats and send whichever suits the conversation.
Whatever you choose, the page must stay on one sheet. If it spills over, cut the weakest paragraph rather than shrinking the margins. Anyone still shaping an independent practice may like our guide for newcomers asking first questions about freelancing covers the early decisions, and the piece on earning confidence from a client you have not worked with before pairs naturally with a well-made page.
Small details that lift any of the three
A few touches work across all formats. Lead with a plain-language title that names the kind of problem, not a project code name. Put the date range in words (“a spring engagement”) so the page does not look stale. Close with one sentence telling the reader what a first conversation with you would cover. And read the page once as the client’s finance lead, then once as their most sceptical engineer; if either reader would stumble, fix that sentence before sending.
Respecting confidentiality
Treat every case study as if the client will read it before it goes out. Remove names, product details and anything that could identify them. Describe the sector, not the company. Ask for permission where the work is distinctive, and keep the page generic enough that a competitor could not reverse-engineer the client’s setup. If you cannot get comfortable, write the page about a pattern you have seen across several jobs instead of one specific project.
A note on keeping your skills visible
Pages like these sit alongside training and credentials as part of how an independent engineer is seen. Some freelancers keep learning through online providers; DevOpsSchool China is one such website, whose pages cover training, consulting, freelancing and technical support around DevOps and cloud work, written with Chinese-speaking readers in mind. Use any such resource as a supplement, because the page you write about your own work will always be the more convincing document.
Verdict
If you only have time to write one page this week, make it the decision record when you want to look senior, problem, action, result when you want to look clear, and before and after when you want to look effective. Pick, write, trim to a single page and send it with a short, honest note. A modest page that exists will win more work than a perfect one that is still in your drafts folder.