Hidden work is private virtue. Visible work is public trust. Here is why every project your agency ships should be a public document — and what happens when it is.
Hidden work is private virtue. Visible work is public trust.
Most agencies do excellent work that no one outside the client relationship ever sees. The design process that involved eight rounds of thoughtful iteration. The technical decision that saved the client three months of future rework. The positioning insight that shifted the client's marketing from vague to sharp. All of it stays inside the contract.
The result is a portfolio of finished things — polished screenshots, metrics at delivery — with none of the thinking visible. Buyers looking for someone who can solve their specific problem see the output without the insight. They cannot tell whether the work was excellent by accident or excellent by design.
Show the design. Show the design of the design.
It does not mean posting every Figma screen or publishing every Slack exchange.
It means publishing the thinking. The constraints that shaped the decisions. The options that were considered and the reasons they were set aside. The trade-off that was made and the outcome it was trading against. The moment when the original plan turned out to be wrong and what happened next.
That thinking is not confidential. It is educational. And education, offered consistently and publicly, is the most durable form of trust-building an agency can do.
When Adam Grant writes about his research in public, people trust his judgment before they read his books. When Paul Graham publishes his essays, founders trust his perspective before they apply to Y Combinator. The public record of thinking precedes the trust relationship.
Agencies rarely do this. They finish the work, photograph the result, and move to the next project. The thinking that made the work good disappears behind the contract.
A public project diary does not need to be long. It needs to be honest.
The format that works:
A one-paragraph description of the client's situation — enough context for a reader to recognize their own situation in the client's. The constraints that mattered: budget, timeline, technical limits, audience characteristics. Two or three decisions that shaped the outcome, with a sentence about why each was made. The result, stated specifically with a metric where one exists. One thing that would be done differently the next time.
That last element — what would be done differently — is the most important. It signals that the agency learned from the engagement. Learning is a more reliable predictor of future performance than a polished presentation of past success.
Buyers reading the diary are not just evaluating the finished work. They are evaluating the judgment of the people who produced it. The judgment is in the decisions, not the deliverables.
A portfolio page is a destination.
A public project diary is a discovery mechanism.
The buyer who searches for "how to improve e-commerce checkout conversion rate" may find a case study where the agency solved that exact problem for a prior client. They arrive not as a prospect responding to an ad but as a reader who found a useful answer. They have already received value from the agency before the first conversation.
Moz research on search intent and content marketing consistently shows that case studies and process documentation rank for specific, high-intent search queries that portfolio images cannot capture (Moz, 2024). The buyer searching a specific problem phrase is much closer to a purchasing decision than the buyer browsing an awards gallery.
Each public project diary is a permanent, searchable record. It does not expire when the campaign ends. It compounds over time as search engines index it, as readers share it in professional communities, and as the agency builds a body of public thinking that aggregates into visible expertise.
A portfolio of twelve polished images competes with every other agency's portfolio of polished images. A library of forty public project diaries that document the thinking behind real work in a specific niche competes with no one, because no one else has published that specific body of work.
Edelman's Trust Barometer research identifies the factors B2B buyers weight most heavily when selecting professional service providers (Edelman, 2025).
The two factors rated highest, consistently across multiple annual reports: demonstrated expertise and track record visibility.
Neither factor is satisfied by a portfolio image. Both are satisfied by a public project diary.
Demonstrated expertise means showing the thinking, not just the output. Track record visibility means making it easy for a buyer to find evidence of your work in a context that resembles their own. The public project diary satisfies both in a single document.
The buyer who can read how an agency approached a problem similar to theirs — the constraints that were faced, the decisions that were made, the outcome that resulted — does not need to be sold. They already have the evidence they need to decide whether to proceed. The discovery call becomes a conversation between two parties who both have relevant information, not a pitch from one party to a skeptical other.
There is a distinction worth drawing carefully.
Self-promotion is telling people how good you are. Building in public is showing people what you think and how you work, and letting them draw their own conclusions.
Self-promotion triggers skepticism. Building in public earns trust by removing the need for claims. The buyer who has read fifteen project diaries from an agency does not need to be told that the agency is good at the work. They have already seen the thinking. They have formed their own assessment.
The Content Marketing Institute's research on B2B content effectiveness consistently shows that educational content — content that teaches rather than sells — generates 3x the leads of explicitly promotional content and attracts buyers who are 30 percent more likely to close (Content Marketing Institute, 2025). The mechanism is trust: educational content positions the publisher as a credible source before the sales conversation begins.
Building in public is educational content applied to the agency's own work. Each project diary teaches the reader something about how to solve a problem in the agency's area of expertise. The teaching earns the trust. The trust earns the conversation.
The question that always comes first: won't clients object to their projects being published?
Some will. Build this into the engagement terms from the start. Include a standard clause in the contract: the agency may publish a project case study after delivery, subject to the client's review of the draft, with the option to request anonymization of any identifying details. In practice, most clients do not object — and many are pleased to be featured as a company that did interesting work.
The clients who object are often the clients who have concerns about what the case study would reveal. That is useful information about the nature of the relationship.
For clients who require strict confidentiality, publish an anonymized version. The industry, the problem type, the decisions, and the outcome can all be described without naming the company. A buyer searching for "how to redesign a healthcare B2B SaaS onboarding flow" benefits equally from a case study that describes exactly that work, whether or not the client's name appears in the headline.
The anonymized case study is still a public project diary. The thinking is still visible. The trust signal is still present.
Not every project warrants a diary. Some engagements are routine in ways that generate limited teaching value for future readers.
The cases that produce the most useful public diaries:
The project diary is worth publishing when the reader comes away knowing something about how to think about a problem — not just what one specific project produced.
Explore how we document and share client work at striveloom.com/case-studies and striveloom.com/services.
Choose the last project your team completed. Write 600 words about how it was made: the constraints, the decisions, the trade-offs, and the outcome. Publish it. Link to it from your portfolio page.
Do that for the next project. And the next.
At twelve public project diaries, you have a compounding body of evidence. At forty, you have a library that a buyer in your specific niche cannot find anywhere else. At that point, the portfolio page is almost redundant. The buyer has already been convinced by the thinking, long before they saw the finished product.
The work is what you make. The diary is what you know.
Show the diary.
A show your work policy is a commitment to publishing the thinking behind every completed project — not just polished portfolio images, but the constraints, decisions, trade-offs, and outcomes that shaped the work. It typically takes the form of project diaries or public case studies that document how the agency approached a real problem. The policy is built into standard client contracts as a standard term, with the client retaining the right to review the draft and request anonymization of sensitive details. The goal is to make the agency's judgment visible, not just its deliverables.
Self-promotion tells the audience how good the agency is. Building in public shows the audience how the agency thinks. The distinction matters because self-promotion triggers skepticism — the audience assumes the agency is presenting the best possible version of itself. Building in public earns trust by removing the need for claims. The buyer who reads fifteen project diaries has formed their own assessment of the agency's judgment. They did not need to be convinced. The trust was built through demonstrated thinking, not through marketing language.
A well-structured project diary includes: the client's context (enough for a reader to recognize their own situation); the constraints that shaped decisions (budget, timeline, technical limits, audience); two or three key decisions and the reasoning behind each; the outcome with a specific metric where possible; and one thing the team would do differently next time. The last element — what would change — is the most important trust signal, because it shows the agency learned from the engagement. A diary that acknowledges imperfection is more believable than one that presents everything as having gone perfectly.
Build the option into your standard contract from the start: the agency may publish a case study after delivery, subject to the client's review and the right to request anonymization. In practice, most clients do not object — and many welcome the feature. For clients who require strict confidentiality, publish an anonymized version describing the industry, problem type, decisions, and outcome without identifying the company. An anonymized case study still demonstrates the agency's thinking and generates the same search and trust value as a named one.
Yes — and it compounds over time. Project diaries rank for specific, high-intent search queries that portfolio images cannot capture: problem-specific phrases that buyers type when they are actively looking for solutions. Moz research on search intent shows that case studies and process documentation consistently rank for the kind of specific queries that indicate purchase intent, delivering qualified traffic that generic portfolio pages cannot attract. Each published diary adds search surface to the agency's domain. A library of forty diaries in a specific niche generates search visibility that no portfolio page can match.
Publish after every completed engagement, with a minimum of one per month for agencies with active project flow. The compounding value of the public record depends on consistency: a library of forty diaries built over two years is dramatically more valuable than forty diaries published in a single month, both for SEO (which rewards consistent publication) and for buyer trust (which builds through repeated encounters with the agency's thinking over time). The format does not need to be long. A 600-word diary that honestly documents one project's decisions is more valuable than a 3,000-word case study that presents only a polished narrative.
Founder & CEO of Striveloom. Software engineer and Harvard graduate student researching software engineering, e-commerce platforms, and customer experience. Builds the agency that ships like software — one team, one pipeline, one platform. Writes on AI agencies, web development, paid advertising, and conversion optimization.
Radical positioning means drawing a line so clear that most buyers self-select out before the first call. That's not a risk. That's the strategy.
Interruption is expensive. Permission compounds. Why the agencies building owned audiences in 2026 are winning while those buying attention are paying more for less.
Fans tell other fans. Clients tell their accountant. The difference between a transactional agency relationship and a tribal one — and how to build the latter.
Book a free 30-minute call to scope your project. Fixed pricing, transparent timelines.
| Portfolio image | Public project diary |
|---|
| Shows the finished output | Shows the thinking and the output |
| Answers: what did it look like? | Answers: how did they think? can they handle my problem? |
| Discovers via direct visits | Discovers via search, referral, community sharing |
| Competes on visual appeal | Competes on demonstrated judgment in the buyer's specific context |
| Does not compound over time | Compounds: each diary adds search surface and trust evidence |
| Opaque on process | Transparent on process — the buyer knows what working with this agency is like |
