This site is the case study.

We can't show you client work yet: LFW is new, and when the client work exists it will be our clients' to show, not ours. So judge us on the software you're using right now: everything below runs this site, was built by us, and can be clicked, not just claimed.

LFW Monitor

This site is audited every day: accessibility, performance, broken links, and email delivery. The findings and the fixes are published as they happen, not summarized after the fact.

The live numbers →

The booking system

The scheduler behind every "Book a call" is ours: real availability read from our calendar, timezone-aware slots, invites sent from our own domain. No Calendly, no Cvent, no iframe.

Use it →

LFW Analytics

Visits are counted at our own web server: no tracking script on the page at all, cookieless, nothing sent anywhere. It's why this site has no cookie banner: there's nothing to consent to. The same measurement sees every AI crawler that reads the site.

How it works →

LFW Experiments

The A/B test on our own homepage hero runs through the same registry and honesty gate every client experiment gets: declared before the data arrives, judged by rules that don't move.

How it judges →

LFW Events

The live demo gala on the events article is our registration system doing its job: RSVP, capacity, waitlist, QR ticket, phone check-in at the door.

RSVP to it →

LFW Anti-Spam

Our forms have no CAPTCHA and stay clean anyway: bots convict themselves against server-side traps and rate limits. Nothing legitimate is silently dropped.

The design →

LFW Looking Glass

Our own pages are captured nightly (rendered image and underlying code), every change recorded, the whole site archived and browsable as it stood on any date. Clients get the same.

What it answers →

Claude, in the loop

The systems above are built and operated with Anthropic's Claude (Fable and Opus) working alongside Leland: the code, the monitoring runbooks, and the librarian passes that keep records current. Disclosed here because tooling you'd hide is tooling you shouldn't use.

The person →

The client portal

Requests with reference numbers and a five-step tracker, passkey sign-in, per-role access. Built on the same stack as this site, part of every client engagement.

Walk the demo →

The plumbing

Static-first pages served by a lean Node process behind nginx and Cloudflare, on infrastructure we operate. One SQLite database (fast, durable, backed up) instead of a fleet of services.

Source Serif 4 and Public Sans are self-hosted, including the display cut used for headings and the website wordmark. The brand guidelines show the typography, colors, and interface details in use. Font requests stay on LFW.com.

Every page aims for WCAG 2.2 AA, and our own scanner audits this site daily, the same audit every client site will get.

If you want this level of care on your organization's site, book a call

Everything on this page can run on your site.

That is the point of publishing it: the stack described here is the one we install and manage for clients. To proceed, talk to us.

Book a call Send a note