HTML with GPT for enterprise work

Show the work, not just the prompt.

Twelve browser-native draft artifacts that make AI-assisted output inspectable, interactive, and easier for humans to review. Built with static HTML, CSS, SVG, and a bit of JavaScript.

Fictional data only Static demo, not enterprise system

Inspired by Thariq Shihipar's original HTML effectiveness examples. This site uses original enterprise scenarios, copy, sample data, and design.

1. Decision brief

Proceed with phased entry via governed pilot.
Business impact visible Risk trade-offs reviewable Decision caveat explicit
12Controls
6Owners
4Risks

2. Dependency map (SVG)

Order Svc API Gate Payments Portal

Solid lines, dotted paths, and selected nodes stay code-native and inspectable.

3. Risk register (CSV)

IDRiskOwnerScore
R-101Data residencyPriya12
R-104Privileged accessSam8
R-107Rollback gapLee6

4. Evidence pack

Recommended presentation path Open the proof in four moves
Runs in modern browsersStatic files. No app server required for the public demo.
Fictional dataNo company data, customer data, secrets, or employer branding.
Web standardsHTML, CSS, SVG, File API, storage, and clipboard patterns.
Human-reviewedOutputs are drafts until people verify facts, edit wording, and sign off.
ShareableOpen, copy, download, print, and link from GitHub Pages.

Two enterprise lenses, one browser.

HTML is not replacing enterprise systems or human judgment. It is a high-signal artifact format for turning AI-assisted thinking into something people can inspect, edit, challenge, and sign off.

Business and office users

Useful when work is cross-functional, decision-heavy, and usually trapped in static notes, decks, or spreadsheets.

  • Compare options without losing the decision context.
  • Turn meeting notes into tracked actions and follow-ups.
  • Navigate policy and process paths by role and intent.
  • Triage CSV-like business data before raising system work.

Enterprise engineers

Useful when the artifact must explain risk, dependencies, evidence, and review focus without pretending to be the source of truth.

  • Show architecture choices as interactive decision records.
  • Make change impact visible with dependency maps.
  • Prepare review aids, incident narratives, and control packs.
  • Keep boundaries explicit: demo, draft, review aid, not sign-off.

Explore the 12 samples.

Each sample is a standalone, public-safe HTML artifact with real interaction, richer fictional data, diagrams, prompt cards, and boundary notes.

Open first sample
01Business

Decision brief explorer

Weighted criteria, options matrix, stakeholder heatmap, and exportable recommendation.

Open sample
02Business

Meeting action tracker

Owner filters, due timeline, decision log, persisted state, and follow-up export.

Open sample
03Business

Policy/process navigator

Role selector, process map, review flow, controls, and RACI-style guidance.

Open sample
04Business

CSV triage workspace

Upload or paste CSV, quality scorecards, filters, anomaly flags, and cleaned export.

Open sample
05Business

Risk acceptance brief

5x5 matrix, mitigation timeline, control checklist, and printable risk draft.

Open sample
06Business

Customer conversation simulator

Branching scenarios, tone comparison, response checklist, and safe-language boundary.

Open sample
07Engineering

Architecture decision record

Option scorecards, current/target diagram, timeline, consequences, and ADR export.

Open sample
08Engineering

Change impact map

Interactive node graph, risk paths, filters, evidence table, and reviewer checklist.

Open sample
09Engineering

Pull request reviewer aid

Annotated diff mock, severity filters, reviewer checklist, and ownership matrix.

Open sample
10Engineering

Incident timeline

Multi-lane timeline, five-whys, event filters, remediation board, and export.

Open sample
11Engineering

Control evidence pack

Evidence readiness dashboard, checklist, heatmap, and no-formal-evidence boundary.

Open sample
12Engineering

Feature-flag risk editor

Toggle matrix, dependency graph, blast-radius score, rollout timeline, and JSON export.

Open sample

Evidence first. Claims second.

The demos rely on ordinary web platform capabilities. Where a capability matters, the page links to browser, standard, accessibility, or security references.

Accessibility

W3C WCAG 2.2 guides keyboard, contrast, semantics, and inclusive interaction expectations.

Security caveats

OWASP CSP guidance frames browser content as something to review deliberately.

What is proved here

The site demonstrates browser-native interaction, diagrams, local parsing, export, and presentation flow using fictional data.

How this was made

Created by Vishal Shah with GPT assistance and reviewed as self-contained HTML artifacts. A related Claude-assisted experiment explores the same idea. This is not a model comparison.

Human review required

LLMs can hallucinate or omit important context. Treat every generated artifact as a draft until accountable people verify facts, adjust wording, and sign off on its use.

12HTML samples
0Build steps
0Runtime frameworks
YesGitHub Pages ready
YesFictional data
YesBoundaries stated

Boundaries protect credibility.

These artifacts can make enterprise work easier to review, but they should never blur the line between a useful draft and accountable human decision-making.

No production sign-off

Production sign-off still belongs with accountable people and official enterprise systems with identity, logging, ownership, and retention.

No sensitive data

All sample content is fictional. Real use needs data classification, privacy, access, and retention review.

No hidden AI claim

The HTML demonstrates artifact design. AI output quality, facts, and accuracy require human evaluation because LLMs can be wrong or incomplete.

No formal evidence claim

Control packs and risk briefs are drafts or review aids, not official evidence by themselves.

Built for a talk, useful after the talk.

Press P or use the Present button for a short keyboard-friendly walkthrough. The same page can be linked from LinkedIn or vishalshah.app.

PEsc
vishalshah.app