Website Foundry

A website you can design and operate through conversation.

Bring brand guidelines, assets, business context, and goals. Widerloom turns them into three live responsive design directions, lets you refine them in real time, and carries approved changes through preview, validation, publishing, verification, hosting, and handoff.

01 / Context

Give the system the truth of the brand.

Upload what already exists. The design layer should extract constraints and provenance rather than flatten everything into a prompt.

Drop brand guidelines, logos, copy, screenshots, or reference material PDF, images, documents, site context, and structured notes
Voice: capable · welcoming · plainspoken Visual: natural · editorial · quiet confidence Avoid: clutter · fear language · extreme-sports tropes Provenance: fictional demo inputs

02 / Rationalize first

Do not put a new skin on old entropy.

Experience Foundry can ingest the existing site, catalog, documents, media, data, analytics, and discovery context, then reconstruct the underlying information system before deciding what the new experience should be.

All numbers and organizations in this demo are fictional. Dense safety-critical interfaces require domain-specific validation beyond normal web testing.

03 / Build before the pitch

Show the future instead of describing it.

For suitable prospects, Widerloom can use lawfully accessible public or authorized information to create a private, clearly labeled speculative prototype before asking them to buy a project.

Public / authorized source

Acme Industrial Parts

9,842 part records41 PDF catalogs6 navigation schemes3 naming conventionsproduct photographytechnical tables

Rationalized model

Entities9,517
Families18
Attributes67
Conflicts143
Gaps286

Working prototype

Find the right part by what you actually need.

VX-220H2" · 316 SS · 425°Fstrong match
VX-220M2" · 304 SS · 350°Fpossible
VX-215H1.5" · 316 SS · 425°Fsize mismatch
Then the conversation changes.

“We built this from public information. Here is what we preserved, what we rationalized, what still needs your verification, and what this could become. Want it?”

private / non-indexedsource provenance retainedno fake checkoutdelivery range only after gaps are known

Spatial layer

Turn engineering source material into something you can walk through.

CAD, BOMs, drawings, manuals, and authorized telemetry can become a navigable spatial experience: exploded assemblies, component-linked documentation, training views, and eventually a properly validated digital twin.

A B C D PUMP-420
visual model2,400 components460 linked docstelemetry: demo
“Explode the drive assembly.” “Show every part tied to maintenance bulletin 47.” “Fly me through the coolant path.” “Overlay the last 24 hours of vibration data.” “Show which components changed between revisions.”

Illustrative interface only. A visual model is not a validated engineering digital twin. Stronger claims require authoritative geometry, configuration control, telemetry validation, simulation evidence, and qualified domain review.

04 / Three live directions

Not one comp and two color swaps.

Each direction uses the same brand truth and content facts but explores a materially different hierarchy, rhythm, typography, density, imagery posture, and interaction system.

See v1 before you buy

No leap of faith.

For suitable website and experience projects, the pitch can include three founder-reviewed directional prototypes. You can see the visual language, information architecture, interaction posture, and mobile direction before deciding whether to proceed.

Direction 01Grounded

A clear, brand-faithful interpretation with a strong information hierarchy.

Direction 02Elevated

A more refined editorial direction with stronger visual authorship.

Direction 03Distinctive

A bolder composition that explores how far the brand can stretch without becoming gimmicky.

You have already seen v1.

If you move forward, the engagement starts from a direction you already understand. The paid work completes the real system: deeper discovery, final content, integrations, migration, testing, hosting, verification, and continued operation.

founder revieweddirectionally realprototype, not productionlive refinement available

No strings attached

If it helps you, keep it.

The Widerloom-authored pitch designs and the design files we deliver with them are yours to keep and use, even if you decide not to hire us. Maybe the timing is wrong. Maybe the budget is tight. Useful work is still useful.

Third-party fonts, stock assets, and licensed materials remain subject to their own licenses. Widerloom's reusable platform code and internal tooling are separate unless explicitly included.

Human judgment

You do not review raw AI work.

AI can explore broadly. Before a direction reaches you, Widerloom's founder reviews it as actual creative work: rejecting generic ideas, sharpening hierarchy and composition, combining stronger elements, simplifying where needed, and making sure every option is worth your time.

Generate broadly12–30 candidate directionsAI exploration, layout systems, copy posture, component combinations
→
EvaluateEvidence + synthetic testsBrand fit, comprehension, accessibility, mobile, performance, task flow
→
Founder reviewCurate, edit, combine, rejectTaste, coherence, business fit, craft, restraint, distinction
→
You see3 already-iterated directionsWorking responsive experiences, ready for live adjustment

Founder-reviewed means a human review actually occurred for that revision. The system is not allowed to infer or manufacture that status.

05 / Conversation

Describe the change. See the diff.

The system should translate natural language into an explicit design and content change set instead of regenerating the site opaquely.

06 / Governed release

Easy to request. Hard to accidentally break.

Conversation starts the change. It does not bypass identity, scope, dependencies, accessibility, testing, approval, publishing, or rollback.

RequestInterpretDiffPreviewValidateApprovePublishVerify
A

Design validation

Responsive layout, semantics, keyboard use, contrast, content completeness, links, and performance budgets.

B

Release safety

Staging URL, explicit diff, version history, immutable release reference, production smoke test, and rollback.

C

Hosted operation

Domains, TLS, analytics, forms, observability, uptime signals, performance, backups, and operating cost visibility.

D

Customer independence

Structured content, assets, design tokens, component manifest, deployment docs, credentials, and handoff paths.

07 / AI they can trust

Do not hunt for an AI use case.

Start with a catalog, website, portal, search problem, or workflow the business already needs fixed. Rationalizing that system creates the clean information, provenance, permissions, and operating context trustworthy AI needs.

01

Useful first

Ship a materially better catalog, site, portal, search experience, or operating surface before asking the customer to bet on an abstract AI program.

02

Build the substrate

Create canonical entities, taxonomy, source provenance, permissions, freshness, relationships, search indexes, APIs, and workflow context as part of the work.

03

Add grounded AI

Semantic search, technical Q&A, guided selection, support copilots, and maintenance assistance can then work from authoritative business context instead of a loose pile of files.

04

Earn more authority

Measure usefulness and safety before allowing bounded actions. Keep consequential decisions under human authority unless a narrower authority has explicitly been granted.

Fix something realRationalizeShipGround AIEvaluateBound actions

The result is AI as an extension of a system the customer already understands and trusts, not an AI transformation program searching for a problem.

08 / After launch

The website stays conversational.

An authorized operator can request a new page, pricing update, team change, campaign landing page, FAQ revision, or design adjustment from the channels they already use.

“Launch a page for the fall program.” “Update pricing everywhere it appears.” “Use the darker treatment for the annual report.” “Add the new team member from this bio.” “Make mobile less animated.” “Roll back yesterday's homepage change.”

This page is a public-safe interactive prototype of the operating model. It does not claim that every ingestion, channel, hosting, or autonomous publishing capability is production-proven today.