INTLO

Executive summary

INTLO is an intelligence company, which makes its website an unusually hard problem: a site that claims analytical capability while being a static brochure undercuts the claim it is making.

Digital Boutique built the site around a single governing principle — the site is the demo. The homepage hero is a working instrument running real market data. Every case study carries an embedded proof module rather than a screenshot. And every module states its own data mode, so a visitor always knows whether they are looking at live data, a cached snapshot, or a recorded replay.

The challenge

There is a specific failure mode for technical companies selling technical capability: the marketing site is the one artifact prospects judge them by, and it is usually the one artifact built to a lower standard than the product. A dashboard company with a screenshot of a dashboard has demonstrated that it can take a screenshot.

The obvious fix — put live product on the marketing site — creates a worse problem. Live systems fail in front of prospects, live client systems cannot be shown at all, and anything convincing enough to be worth showing usually contains data nobody is permitted to publish.

The build had to satisfy both constraints at once: prove capability through working interfaces, while never exposing a client system, client PII, or client revenue.

Approach

The resolution was to make the data mode explicit rather than to hide it. Each proof module declares itself LIVE, CACHED or REPLAY in mono caps, at the top of the frame. Once that label exists, a replay stops being a compromise — it is an honest artifact, and the modules that genuinely run live become credible precisely because the others are marked.

That single decision unlocked the rest. Client work could be shown as anonymized replay with no exposure risk. INTLO's own instruments could run live. The market-data hero could be genuinely live because it draws on public data.

Nine modules were built on a shared replay engine — a progress loop with play, pause and scrub, throttled to roughly 30fps, parking on the final frame for visitors who prefer reduced motion. Building the engine once meant each module is a shell plus fixtures plus a script rather than a bespoke rebuild.

Publish state is operator-controlled per entry, which is what allows client case studies to exist in the codebase before they are cleared to appear. Anything without sign-off ships unpublished.

What it produced

Seventeen products are indexed with per-entry build status, nine of them carrying interactive proof modules, verified by an end-to-end suite running twenty checks green.

The proof engine built here is the direct ancestor of the one running this Showcase — the pattern proved durable enough to become Digital Boutique's canonical approach to demonstrating client work without exposing it.