Proof

Proof has to be real, approved, or clearly labeled.

This page tracks what is publicly provable now, what needs approval, and what is intentionally held back until evidence exists.

1

Verified case studies

19

Blueprints withheld

0

Fake proof allowed

Current public proof artifact

HMX Zone Website — Full-Stack Portfolio Built End-to-End

This website is itself a case study: a full-stack Next.js portfolio with route-based pages, lead capture, SEO metadata, case study routing, blog structure, and backend-ready architecture.

View proof briefView website offer
HMX Zone public website screenshot

Proof rules

  • Case studies require public, approved, or redacted evidence before they render as case studies.
  • Screenshots and videos must come from real systems. Diagrams are labeled as diagrams.
  • Testimonials, names, and logos need permission or public evidence before they appear.
  • Private metrics can be discussed as internal notes, but public proof needs a source artifact.

What still needs proof

Client screenshots

Needed

Ask for approval or prepare redacted screen recordings before adding.

Named testimonials

Needed

Only add names, companies, and logos after written/public approval.

Before/after media

Partial

HMX website proof exists; client systems need approved media.

Case-study manifests

Started

Verified studies now include evidence, media, privacy, and captured dates.

Blueprint handling

19 previously listed items are now treated as system blueprints, internal notes, or feasible build concepts until proof exists. They can be used for service positioning, but not as verified client case studies.

View system blueprints

Proof-first build

Build the system and the proof trail.

Book a build call to scope implementation, or request a system audit to define what evidence should be captured from day one.

Book a build callRequest a system audit