Skip to content

Confidentiality

A limited glimpse, on purpose.

The demos give a limited view of my work, using fictional data and placeholder branding. Client identities, confidential workflows, proprietary calculation logic and production data are excluded. They show selected features, not complete client applications.

How the demos are kept clean

01

Rebuilt, not copied

Each demo is written fresh as a front-end-only app. There is no server or database, and nothing is shared with the client system.

02

Fictional everything

Companies, people, parts, tenders and rates are generated in your browser, with dates relative to today. Reset them any time.

03

A build that refuses leaks

Every build runs a leak check first. If any word from the real system (a name, a stage code, a module) appears in the source, the build fails.

Example build output

$ npm run build
> node scripts/leak-check.mjs && next build

Leak check FAILED: 1 banned word(s):
lib/seed.ts:42  "████████"  name: '████████ Pvt Ltd',

# fixed, then:
Leak check passed.
✓ Compiled successfully

Per demo

What each one leaves out

Forge PMS

For Excluded: client identity, an engineering and manufacturing firm

  • Client identity and branding
  • Their real stage names and codes
  • Production data, drawings and suppliers
  • Integrations with their other systems

Relay CRM

For Excluded: client identity, a B2B engineering sales team

  • Client identity and branding
  • Their real stage names and data sources
  • Contacts, companies and deal values
  • Integrations with their mail and chat tools

Rate Analysis

For Excluded: client identity, a civil roads contractor

  • Client identity
  • All calculation screens and proprietary formulas
  • Real tenders, rates and quantities
  • The licence server

If you are considering sharing your own processes with me, this is the standard they will be held to.