Skip to content
Interface language: English
Design / Signal

B2B case studies: how to show your work without revealing confidential information

Prepare a credible account of a project: your scope, evidence, limitations and material approved for publication.

Article language: English

A woman in a light suit with one hand on a small stone door beside a glowing lamp.
In this article

A case study should help a prospective client understand how you work. A gallery labelled “another success” asks them to take your word for it, and words sometimes need an attachment too. Show the problem, your own scope, decisions and evidence of the outcome. If the project is confidential, choose a permitted part or a clearly labelled demonstration. A useful account can be discreet and specific at the same time.

Confidentiality limits available material, but it does not require an empty story. You can explain the method, criteria and your contribution while respecting honest boundaries. This workshop takes you from documentation to a public article. It does not replace checking rights to materials or obligations applicable to the project.

Which decision should the case study support?

Choose one buying situation. A prospective client may be comparing ways of running a project, looking for experience with a particular problem or checking whether a firm can accept a deliverable. When selecting a supplier, a reference conversation about the work (in Polish) is a different source from the supplier's own account. Describing every competence at once makes the strongest point harder to see. Write down one question the case study should answer.

Connect the story to the relevant service page (in Polish). If you provide design, show the decisions and how they were checked. If you also implemented the solution, describe the technical scope and acceptance. A site's appearance alone does not prove delivery of strategy, integration or subsequent maintenance.

Before writing, establish what the account cannot prove. Without sales data there is no basis for a promise of revenue growth. You can still document what was delivered and how the process was checked. Clear limits make the account more useful because the client knows what it can be applied to.

How do you collect material and separate fact from interpretation?

Prepare a working package: agreed scope, design versions, important decisions, acceptance results and available measurements. Add a source and a person able to confirm each claim. “We designed the form” needs a different basis from “the form improved enquiry quality”. The second claim needs evidence about subsequent effects.

Mark your interpretations too. You may explain why the team chose a layout, but do not attribute that intention to the client without confirmation. If documentation is incomplete, state the limitation or omit the strong claim. Compare a participant's memory after several months with the materials that remain.

A project decision register (in Polish) can help reconstruct alternatives and the conditions behind a choice. The case study can then show reasoning instead of inventing an inevitable path to a perfect outcome after the project. Real work usually includes corrections and compromises. If you describe a choice between solutions, show the conditions for comparing prototypes on the same task (in Polish), rather than presenting a preference alone as proof of effectiveness.

How should you describe your contribution and partners' work?

Start with responsibilities. Who prepared the strategy, copy, photographs, design, code and maintenance? If your team delivered only a part, name it precisely. The client should understand which competence they are assessing. A broad “we built the platform” can credit the firm with work done by others.

For jointly created materials, agree attribution and presentation rules. Access to a working file does not automatically permit every part to be shown publicly. Check the project agreements, licences and approved scope of use. Do not assume that a client's earlier publication gives the supplier the same rights.

The guide to accepting code and access (in Polish) describes handover and accounting for project elements. For the case study, make a separate list of material intended for publication. This helps prevent internal documentation being used accidentally while exporting a presentation.

How can you show a result without claiming someone else's effects?

Separate the deliverable from its business effect. Launching a site, shortening a form and a positive feature test are observable results of work. Sales growth can also depend on a campaign, seasonality or a changed offer. Do not present correlation as the project's proven effect.

If publishing a measurement, give the period, scope and method. A laboratory test is not the same as every visitor's experience. Check the conditions of both tests before comparing them, following the principles of website speed analysis (in Polish). A selected number without context can exaggerate a change.

No permission to publish numbers does not rule out an account. You can show acceptance criteria, a barrier removed and how correctness was checked. If the client gives a qualitative assessment, retain its actual meaning and the agreed quotation scope. Do not turn general satisfaction into a precise efficiency claim.

How do you prepare a safe visual version?

Inspect every screen and file at full size. Check names, addresses, identifiers, notification text, browser tabs and attachment metadata. Covering a visible name does not automatically remove all information that could identify a project. The context of several images can reveal more than one frame.

Replacement data should preserve the meaning of the demonstration without pretending to be the client's real records. Label a reconstruction or demonstration next to the material. When values have been changed, do not use that screen as evidence of a numerical result. The account should clearly separate documentation from an illustration of the method.

A brand photography plan (in Polish) helps select images and captions. For a case study add the credibility question: what exactly does this image show, and what does it not establish? A conceptual brand scene can create atmosphere but should not pretend to be a photograph of the client's team or premises.

Aeneia conceptual photography

What might a hypothetical confidential project look like?

This scenario is hypothetical. A firm designs a request-handling portal for a company it cannot name. Its documentation contains contact details and real cases. The team chooses to describe a navigation problem and the way it tested returning to an unfinished task.

It creates a demonstration using entirely replacement data, clearly labelled as a reconstruction. The text presents the starting point, considered alternatives and acceptance conditions. The firm does not publish customer counts, an overly narrow industry description or a combination of details that would make the organisation easy to identify. The person responsible for project obligations checks the scope.

The article states that the demonstration shows the method and that the account contains no client business data. There is no fictional quotation or name suggesting a real organisation. The result is useful material about a way of working whose limits the reader understands from the outset.

How do you structure the story without turning it into a meeting chronicle?

A suggested structure covers the situation, task, constraints, decisions, execution and checking. Each part should support assessment of competence. A chronology of every workshop rarely helps a client. Select moments that explain an important trade-off or change of approach.

Show at least one alternative considered. Explain why it was not chosen under those conditions. It need not have been objectively worse; it may have required materials, time or support the project did not have. Such an account lets a future client assess whether the method fits their own task.

Apply the principles of service-page writing (in Polish): concrete names, a clear actor and limited promises. Put sources for results next to claims. The reader should not have to search the footer to find whether a number came from a test, client observation or the author's assumption.

How do you check whether the material is useful and credible?

Ask someone outside the project three questions: what problem was solved, what was the firm responsible for and what does the result actually establish? If the answers differ, revise the text. Do not start by decorating the heading. The problem may be a hidden assumption or an unclear division of work.

Check whether the article offers more than general claims of competence. Google's guidance on helpful content encourages original information, analysis and clear grounds for trust. It is not a promise of a search ranking. The practical goal of a case study remains answering a prospective client's questions.

Review every evaluative term. “Intuitive”, “secure” and “effective” need an explanation of what was tested and within what scope. Often you can replace them with a description of the test: a user found the right document, and the test recorded a particular barrier for correction.

How do you manage approval and preserve the approved version?

Submit the complete material for review: text, images, captions and sharing title. Approval of a document alone does not automatically cover a screenshot added later. Identify elements needing particular confirmation, such as numbers, quotations and the description of the client's role.

Record who approved which version and within what scope. If a strong claim changes or new material is added after approval, repeat the relevant check. This is an operational publication-control practice. Detailed requirements depend on the project's agreements and should be assessed by the appropriate person.

Also establish a route for requesting corrections after publication. A changed offer, the end of a collaboration or withdrawal of permission for particular material requires assessment of the consequences. Do not erase history thoughtlessly, but do not leave an outdated quotation merely because the article looks good in a portfolio.

What can you show when a project cannot be published?

Choose an original demonstration on a neutral task, a description of a procedure or a hypothetical example. Each format can show competence when properly identified. Do not package an exercise as a story about a client who does not exist. Readers are entitled to understand the kind of evidence presented.

A demonstration should have its own goal and criteria. You could show two navigation variants and how they were assessed instead of inventing a sales result. Describe the limits of the materials and what the exercise did not test. Preparing an honest example takes work, but leaves the firm with a resource it can develop further.

Connect it to the offer only after explaining the guide's value. Readers should be able to use the method without making contact. A conversation can then follow from a recognised need rather than a promise that the evidence is hidden exclusively in a paid consultation.

Connect the case study with a presentation of the team's capabilities (in Polish). Readers should understand who handled each stage and whether that scope can be commissioned today. A portrait may accompany evidence but need not replace it.

What belongs on the publication checklist?

Before release, confirm:

  • Each strong claim has a source, scope and person who can confirm it.
  • The text distinguishes your contribution, partners' work and business effects.
  • Visual materials have been checked for confidentiality and rights of use.
  • Reconstructions, replacement data and hypothetical examples are clearly labelled.
  • Approval covers the complete version intended for publication.
  • A reader can explain the problem, decision and basis for assessing the result.

If you need a portfolio that clearly shows how you work, see Aeneia Design.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear