How kShuttle Turned a Confidential Deployment Into an Enterprise Case Study Video

kShuttle’s best proof was also its least usable. The most sophisticated implementations sat behind confidentiality agreements, so the work that would have won the next deal could not be shown to anyone. This is how we made an enterprise case study video anyway — and why the constraint turned out to be the argument.

The problem: the best evidence was under NDA

kShuttle is a SOC-certified SaaS platform serving regulated industries. That certification is hard-won and it is exactly what an enterprise buyer in a regulated sector needs to hear about.

It also created the bind. The deployments that demonstrated real enterprise capability were covered by confidentiality agreements. The company could not name them, could not screen-record them, could not walk a prospect through them. So every sales conversation rebuilt the credibility argument from nothing, in words, and the quality of that argument depended on which representative happened to be in the room.

The more sophisticated the work, the harder it is to communicate quickly, consistently, and without breaching the confidentiality of the clients it was built for.

It is worth naming why this is worse than simply having no case study. A team with no proof knows it has none and compensates. A team whose proof exists but cannot be shown keeps almost getting there — gesturing at work it cannot describe, which a sceptical buyer reads as vagueness.

The approach: compliance first, in three phases

1. Choose the implementation, carefully

Not the most impressive deployment. The most representative one that could also be shown. We worked through the portfolio against two filters at once — what a prospect most needs to believe, and what could be made public without a difficult conversation — and landed on the M6 Groupe portal.

This is the phase most teams skip, and it is the one that decides whether the project is possible. Selecting on impressiveness alone produces a brilliant asset that legal will not clear.

2. Build a public-facing version that is genuinely public-facing

Not a blurred screen recording. A demonstration constructed from the outset to respect confidentiality — real in structure and behaviour, carrying nothing that belonged to the client.

Blurring is worse than useless here. It draws attention to the hidden thing, tells the viewer they are being shown a redaction, and makes the film feel like a workaround. A purpose-built demonstration looks like a product, because that is what it is.

3. Write it about outcomes, not architecture

The audience for an enterprise case study is rarely the person who will operate the system. It is a committee: a business owner, a finance signatory, someone from risk, someone from procurement. Most of them will never open the product.

So the narrative ran on the business outcomes that committee signs off. This is the coherence principle applied to a sales enablement video — material that is interesting but irrelevant to the viewer measurably reduces what they take away.[1] Architecture is fascinating to engineers and noise to a risk officer, and this video was for the risk officer.

What the video changed in enterprise sales

• Sales calls opened at qualification. The credibility argument arrived before the meeting and gave back its first third.
• One asset aligned several stakeholders. A committee that has all watched the same three minutes starts from a shared premise, without anyone rebuilding a deck for the people who missed the call.
• Compliance became visible as a trust signal. The film was demonstrably built without exposing a client’s confidential deployment — which is itself the most persuasive possible evidence of how kShuttle treats a client’s data.
• Messaging stopped varying by representative. Everyone in the sales organisation described the same capability the same way.

The third point is the one worth carrying away. The constraint was not worked around; it was used. A prospect in a regulated industry watching a case study that visibly protects the previous client is being shown exactly how they will be treated. No claim about discretion in a deck lands as hard as a demonstration of it.

The transferable part

Any company selling into finance, healthcare, defence, government or legal services, in Singapore or across the wider APAC region, eventually hits this wall: the best work is the least shareable. Four things travel from this project.

1. Select for clearability, not for impressiveness. The second-best deployment that can be shown beats the best one that cannot.
2. Build a purpose-made demonstration. Blurring signals concealment. Construction signals a product.
3. Write for the committee, not the operator. Outcomes over architecture, because most of the people who decide will never use it.
4. Let the constraint do the arguing. Visible respect for a previous client’s confidentiality is a stronger trust signal than any assurance you could write.

Placement matters as much as construction. Video that is added to an existing sales sequence substantially outperforms video that replaces part of it — g = 0.80 against g = 0.28 across 105 studies and 7,776 participants.[2] This film was never meant to replace the sales conversation. It was built to arrive before it, so that the conversation could start somewhere more useful.

Frequently asked questions

How do you make a case study video when the client work is under NDA?

Select the most representative deployment that can be cleared, then build a public-facing demonstration from scratch that carries nothing belonging to the client. Avoid blurred screen recordings, which signal concealment. For kShuttle, this meant choosing the M6 Groupe portal and writing the film around business outcomes, so it could be shown and buyers could follow it.

Who is the audience for an enterprise case study video?

Usually a buying committee: a business owner, a finance signatory, someone from risk and someone from procurement. Most of them will never open the product. Write the narrative around the business outcomes they care about, and keep technical architecture out of it, since it fascinates engineers and reads as noise to a risk officer.

Why use video for sales in regulated industries?

One asset delivers the credibility argument identically before the meeting starts. For kShuttle, sales calls then opened at qualification, a committee could start from a shared premise, and messaging stopped varying by representative. A film that visibly protects a previous client's confidentiality also shows a regulated buyer exactly how their own data will be treated.

Can a case study video be produced for sales teams across APAC?

Yes. A purpose-built demonstration needs no access to a client site, so the work runs through remote briefing, script and review rounds wherever your sales team is based. For regional buyers in markets such as Malaysia or Indonesia, the same film can carry subtitles or a local-language voiceover, planned at script stage.