Show your consulting work without sharing client documents

Your best work may sit in documents a prospective client will never see. An operations review can contain internal disagreements. A strategy document can reveal a business decision before it is public. Taking the names off those pages may still leave a recognisable situation.

You can create a fresh demonstration using fictional material. The useful question is what a buyer should be able to judge from it. A sample earns its place when it makes part of your expertise inspectable and accurately represents the work someone could buy.

That gives you a choice to make before designing the document: which promise on your website needs a concrete example?

Start with the question a buyer needs to settle

A prospect considering an operations review might wonder what happens after you collect information. Will they receive a description of familiar problems? Will they understand which uncertainty to investigate first? Will a recommendation explain what has to change in their team?

Choose one of those questions. A sample trying to explain the whole engagement can become another long document the buyer has to interpret.

The GOV.UK Service Manual’s guidance on making prototypes describes using prototypes to explore and test ideas before committing to a build, with detail suited to the current need. That guidance concerns government services. A useful commercial adaptation is to make only enough of a sample to help someone examine the part of your service they find difficult to picture.

If your promise is that a review helps managers choose a practical next step, show a recommendation and the reasoning behind it. Link the sample to what the customer is paying you to help them decide.

Make the reasoning visible in a small example

Consider a fictional consultancy that reviews handovers between account managers and a delivery team. The following inputs and sample are invented for illustration. They describe no client, completed engagement or measured result.

Its sample begins with a short assignment: a manager wants to understand why urgent requests arrive without enough information. The available material is a fictional handover form and an example of a team conversation. The consultant has not observed the team working.

A small extract could look like this:

Material available	Interpretation to examine	Suggested next step
The handover form has no field for who confirms the delivery date.	Responsibility may be assumed rather than agreed. The form alone cannot establish what happens in practice.	Ask both roles who confirms the date, then observe one handover.
The example conversation mentions urgency but gives no customer deadline.	The team may be using different meanings of urgent.	Compare what each role needs to know before accepting an urgent request.
The example contains no record of the delivery team’s response.	Acceptance is unknown; silence cannot establish agreement.	Check how the receiving team acknowledges an assignment.

The accompanying recommendation could be to clarify acceptance before replacing the whole workflow. It should explain the dependency: the consultant would first need to see whether the missing acknowledgement is a real working problem or simply absent from the supplied example.

A buyer can now examine something specific. They can see whether the consultant distinguishes an observation from an assumption, how the proposed investigation follows, and why the recommendation remains provisional. The table gives them material for a useful question during an enquiry.

You could demonstrate a different standard. A writing practice might show how it checks a claim against supplied facts. A training business might show how an exercise changes when participants have different responsibilities. Choose the judgment that matters in your actual service, then make it visible in an appropriate format.

Say exactly what the sample demonstrates

Put the explanation beside the sample, where someone encounters it. For the fictional review, a suitable label would say that the material illustrates how the consultancy examines incomplete handover information, using invented inputs. It would also state that it demonstrates no customer outcome.

Keep that distinction in the surrounding page. A heading about reducing delays could imply an effect the sample has never established. A heading about how a review examines responsibility describes what the reader can actually inspect.

A sample can show reasoning, clarity and the boundaries of a recommendation. It cannot establish that clients implemented the work or benefited from it. Those claims need their own evidence. Use customer feedback for the experience it actually describes, with appropriate context and permission.

Creating fictional material also leaves you responsible for checking it. Avoid reusing a distinctive combination of private facts under changed names. If you want to use real work, resolve the relevant permissions before making it public; this article does not determine what a particular agreement permits.

Check what AI added to the sample

AI can help draft fictional inputs or produce a first layout. Decide what you want the example to demonstrate before asking for variations. Review the recommendation yourself, including assumptions the generated draft makes sound settled.

In the handover example, a draft might add a claim that the proposed acknowledgement step prevents missed deadlines. Remove that claim: the sample contains no test of that effect. You can explain why you would investigate the step without pretending to know its business result.

Charlie Fountaine’s September 2026 GDS article on prototyping principles connects the format and level of detail to the question being explored, and recommends testing with people who would use the service. Apply that principle by asking a suitable prospective buyer to use your sample during a conversation. What can they now assess? Which part still needs explanation? Their response can improve the demonstration; it does not validate a claimed commercial return.

Keep the demonstration close to the service you sell

A public sample can become more polished than anything included in the paid assignment. That creates a delivery promise, even if the page never calls it one. Explain which parts are representative and which exist only to introduce the work.

Choose a sample you can keep accurate as your service changes. One useful extract with a clear limit can be easier to maintain than a complete fictional client engagement. If your strongest example depends on work your ordinary offer excludes, either explain that boundary or choose another example.

Use the offer worksheet to check the promise, scope and limits alongside your demonstration. A buyer should leave knowing what they could assess from the sample and what they would still need to discuss with you. That is a credible basis for the next conversation.