{"id":8825,"date":"2026-08-11T03:12:22","date_gmt":"2026-08-11T03:12:22","guid":{"rendered":"https:\/\/dextora.agency\/insights\/case-studies-that-sell-portfolio-pages\/"},"modified":"2026-08-11T03:12:22","modified_gmt":"2026-08-11T03:12:22","slug":"case-studies-that-sell-portfolio-pages","status":"publish","type":"insight","link":"https:\/\/dextora.agency\/en\/insights\/case-studies-that-sell-portfolio-pages\/","title":{"rendered":"Case Studies That Sell: Writing a Portfolio Page Clients Finish Reading"},"content":{"rendered":"<p>Most portfolio pages are galleries. A grid of screenshots, a client name, occasionally a line about what was delivered. They exist because a services business is expected to have one, and they are read the way they are written: quickly, and without changing anyone&#8217;s mind.<\/p>\n<p>A case study that sells does something a gallery cannot. It lets a prospective client recognise their own situation in someone else&#8217;s, and it gives them the evidence to argue your case internally when you are not in the room. Those are two different jobs, and both are structural rather than stylistic.<\/p>\n<h2>Who actually reads them, and when<\/h2>\n<p>Case studies are rarely the first thing a visitor sees and almost never the last. They are read in the middle of a decision, by two distinct people.<\/p>\n<p>The first is the person who found you and is checking whether you have solved their specific problem before. They arrive with a filter: same sector, same size, or same technical constraint. They will read one case study properly and skim the rest.<\/p>\n<p>The second is the person that first one has to convince. A director, a partner, a board. They never visit your site. They receive a link or a paragraph pasted into a message, and they judge it on whether it contains anything a sceptical colleague cannot dismiss. Writing for this second reader is what most case studies fail to do, and it is the reason numbers matter more than adjectives.<\/p>\n<div class=\"accent-block\">\n<p>A simple test for a finished case study: could someone paste two sentences of it into an internal chat and have the reply be a question about scheduling rather than a question about whether you are credible? If not, the missing element is almost always a specific number or a named constraint.<\/p>\n<\/div>\n<h2>The structure that works<\/h2>\n<table>\n<thead>\n<tr>\n<th>Section<\/th>\n<th>What it contains<\/th>\n<th>Length<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Situation<\/td>\n<td>The business context, and what was at stake commercially<\/td>\n<td>Two or three sentences<\/td>\n<\/tr>\n<tr>\n<td>The actual problem<\/td>\n<td>Not the brief, but what turned out to be wrong<\/td>\n<td>A short paragraph<\/td>\n<\/tr>\n<tr>\n<td>Constraints<\/td>\n<td>Budget, deadline, legacy system, team capacity<\/td>\n<td>A list of three or four<\/td>\n<\/tr>\n<tr>\n<td>What was done<\/td>\n<td>Decisions and trade-offs, not a feature list<\/td>\n<td>The bulk of the page<\/td>\n<\/tr>\n<tr>\n<td>What happened<\/td>\n<td>Numbers with a baseline and a period<\/td>\n<td>A short table<\/td>\n<\/tr>\n<tr>\n<td>What we would do differently<\/td>\n<td>One honest paragraph<\/td>\n<td>Optional and unusually persuasive<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The constraints section is the one clients notice. Everyone claims good work; describing the conditions the work happened under is what makes it believable and, more usefully, what lets a reader with similar constraints recognise themselves.<\/p>\n<h2>Numbers, and how to state them honestly<\/h2>\n<p>A percentage without a baseline is decoration. &#8220;Conversion up 140%&#8221; could describe a move from 0.5% to 1.2%, which is real, or from three enquiries to seven, which is noise. Both are worth reporting, and they are worth reporting differently.<\/p>\n<p>Four rules make a number defensible.<\/p>\n<ol>\n<li><strong>Give the before, the after and the window.<\/strong> &#8220;From 1.1% to 2.4% over the six months following launch&#8221; survives scrutiny; the percentage alone does not.<\/li>\n<li><strong>Say what else changed.<\/strong> If a redesign coincided with a new ad campaign, say so. A reader who discovers the confound themselves stops believing the rest of the page.<\/li>\n<li><strong>Prefer commercial figures where the client permits.<\/strong> Enquiries, orders and revenue outrank sessions and rankings, because they are the terms the second reader thinks in.<\/li>\n<li><strong>Report the ones that did not move.<\/strong> A case study where every metric improved reads as selective, for the same reason a page of five-star reviews does.<\/li>\n<\/ol>\n<p>Where a result is genuinely uncertain, the honest formulation is available and costs nothing: state what was measured, what was not, and what could explain the difference. That is the same discipline that makes any conversion figure usable, discussed in <a href=\"https:\/\/dextora.agency\/en\/insights\/landing-page-conversion-benchmarks-median-explained\/\">how to read conversion benchmarks<\/a>.<\/p>\n<h2>Working around confidentiality<\/h2>\n<p>The most common reason good work is never published is that the client will not agree to be named, and the usual response is to abandon the case study. There are three better options.<\/p>\n<ul>\n<li><strong>Anonymise the client, keep the specifics.<\/strong> &#8220;A Bulgarian distributor with 4,000 SKUs and two warehouses&#8221; is more useful to a reader than a logo with no detail. The recognisable part is the situation, not the name.<\/li>\n<li><strong>Publish relative rather than absolute figures.<\/strong> Most confidentiality objections are to revenue disclosure. Percentages, ratios and per-order figures usually clear legal review when absolute numbers do not.<\/li>\n<li><strong>Ask at the right moment.<\/strong> Permission requested at the point of a good result is granted far more often than permission requested six months later by email. Better still, put a clause about publication in the original contract, where it is a routine negotiation rather than a favour.<\/li>\n<\/ul>\n<p>One practice to avoid: describing work so vaguely that it could apply to any project. An anonymous case study with no specifics is worse than no case study, because it signals that either the work or the results will not survive description.<\/p>\n<h2>Format decisions that matter more than they sound<\/h2>\n<p>Three formatting choices change how much of a case study gets read.<\/p>\n<p><strong>Put the outcome at the top.<\/strong> A short summary box with the situation and the result, before the narrative. Readers who need only that will take it and leave satisfied; readers who need the detail will keep going. Burying the result at the bottom in the interests of storytelling loses the first group entirely.<\/p>\n<p><strong>Make each case study filterable.<\/strong> If your portfolio has more than about eight entries, sector and service tags do more for conversion than any individual page, because the visitor is looking for their own situation and will not read through everything to find it.<\/p>\n<p><strong>Show the artefact, not only the screenshot.<\/strong> A screenshot of a homepage proves that a homepage exists. A before-and-after of the specific screen that changed, or a photograph of the thing in use, carries information a full-page render does not.<\/p>\n<h2>Which three to write first<\/h2>\n<p>Most businesses have more publishable work than published work, and the instinct is to start with the biggest project. That is usually the wrong first choice, because the biggest project is the least representative of what you sell most often.<\/p>\n<p>A better selection rule picks three that do different jobs.<\/p>\n<ol>\n<li><strong>The typical one.<\/strong> The project that most closely resembles what a new client will actually buy. Unglamorous, and the one most visitors need.<\/li>\n<li><strong>The hard one.<\/strong> A project with a genuine constraint you worked around: an impossible deadline, a legacy system, a regulated market. This is the case study that wins the enquiries with unusual requirements, which are frequently the better-paying ones.<\/li>\n<li><strong>The one with the clearest number.<\/strong> Not necessarily the largest result, but the one where the measurement is unambiguous and the client will let you publish it.<\/li>\n<\/ol>\n<p>Written in that order, three cases cover recognition, capability and proof. A fourth adds little until the portfolio is being filtered by sector, and at that point the useful additions are sector-specific rather than more impressive.<\/p>\n<p>These are also the materials a prospective client uses to answer the questions in <a href=\"https:\/\/dextora.agency\/en\/insights\/choosing-a-web-contractor-nine-questions\/\">the supplier selection process<\/a>, which is a reason to write them for scrutiny rather than for admiration.<\/p>\n<h2>Where they belong on the site<\/h2>\n<p>A portfolio page collects case studies; it should not be the only place they appear. The service page for a given offering should link to the two or three cases that demonstrate it, because a visitor reading about that service is asking for exactly that proof at exactly that moment.<\/p>\n<p>The same applies in reverse: each case study should link to the service it belongs to, so a reader who arrives from search lands somewhere useful. That reciprocal linking is also the practical difference between a portfolio that gets found and one that only gets browsed, and it interacts with the placement logic behind <a href=\"https:\/\/dextora.agency\/en\/insights\/reviews-and-trust-signals-what-actually-reassures\/\">where evidence belongs on a page<\/a>.<\/p>\n<h2>A production process that survives a busy quarter<\/h2>\n<p>The reason portfolios go stale is not writing difficulty. It is that nobody owns the moment when a project ends, which is the only moment when the details are fresh and the client is pleased.<\/p>\n<ol>\n<li><strong>Capture at handover, not later.<\/strong> Fifteen minutes at project close: the numbers before, the numbers now, the three decisions that mattered, one quote from the client. Written into a shared document, not remembered.<\/li>\n<li><strong>Ask for permission in the same conversation.<\/strong> Satisfaction is highest immediately after delivery and decays.<\/li>\n<li><strong>Write it within a fortnight.<\/strong> After a month the specifics have blurred and the case study drifts towards generic.<\/li>\n<li><strong>Revisit the numbers at six months.<\/strong> Results that held up are more persuasive than launch-week figures, and a dated update is itself a credibility signal.<\/li>\n<\/ol>\n<p>Three well-documented cases beat twenty screenshots, and the third one is usually where a portfolio starts working, because that is the point where most visitors can find something resembling their own situation. Treated this way, case studies stop being a marketing artefact and become the most reusable output of <a href=\"https:\/\/dextora.agency\/en\/insights\/b2b-content-strategy-writing-that-brings-clients\/\">a content programme that brings clients<\/a>, since each one answers a real question a buyer asked.<\/p>\n<h2>The short version<\/h2>\n<p>Case studies are read in the middle of a decision by two people: the one comparing suppliers and the one they have to convince without you present. Write for the second. Use a structure of situation, the real problem, constraints, decisions, results and one honest reflection, and treat the constraints section as the part that makes it believable. State numbers with a baseline, a period and an acknowledgement of anything else that changed, and include the metrics that did not move. When a client will not be named, anonymise the name and keep the specifics rather than abandoning the story. Put the outcome at the top, tag the portfolio so visitors can find their own sector, and link cases to services in both directions. Capture the material at handover, because that is the only moment when the numbers are fresh and the client is happy, and three complete cases outperform a wall of screenshots.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>They are read by two people: the one comparing suppliers and the one they must convince without you. The structure that works, how to state numbers honestly, and how to publish when the client will not be named.<\/p>\n","protected":false},"author":5,"featured_media":8816,"template":"","insight_category":[154],"insight_tag":[168,176,170],"class_list":["post-8825","insight","type-insight","status-publish","has-post-thumbnail","hentry","insight_category-guides","insight_tag-business-process","insight_tag-content-strategy","insight_tag-conversion"],"acf":[],"_links":{"self":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight\/8825","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight"}],"about":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/types\/insight"}],"author":[{"embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/users\/5"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/media\/8816"}],"wp:attachment":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/media?parent=8825"}],"wp:term":[{"taxonomy":"insight_category","embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight_category?post=8825"},{"taxonomy":"insight_tag","embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight_tag?post=8825"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}