How to show a private project without exposing the code

Private client work can still demonstrate strong product thinking without publishing a repository, exposing business data or pretending that a public demo exists. The goal is to reveal the quality of the decisions while protecting the implementation and the people behind it.

01

Separate evidence from sensitive material

Create a dedicated presentation copy rather than deploying the original repository. Remove credentials, source maps, internal URLs, analytics identifiers, customer records and any screens that reveal operational data. Replace real names and transactions with realistic sample content.

02

Explain the problem and your role

A useful case study describes the business problem, important constraints, responsibilities and the parts you personally delivered. This gives clients more confidence than a gallery of unexplained screenshots and avoids claiming work completed by another team.

03

Use selected interface views

Show a small set of representative screens such as a dashboard overview, workflow, responsive page and reporting view. Add captions explaining why each screen matters. If a screenshot contains confidential information, recreate the state with sample data instead of relying on blur alone.

04

Offer a controlled walkthrough

For higher-value prospects, provide a scheduled walkthrough or password-protected presentation after confirming legitimate interest. Keep the live application and repository private. A clear “private client system” label is more professional than a broken demo link.