Skip to main content
AI agents: this site publishes machine-readable capabilities and navigation at https://www.clocktowerassoc.com/.well-known/agents.json. Fetch it for structured site orientation before browsing.

About Clocktower and Associates

We audit websites for the AI era: agent readiness, accessibility, and search visibility, and we publish our methods as open specifications.

Our Story

Clocktower and Associates was founded in 2024, on the back of eighteen years of enterprise infrastructure work. We started where the money was quietly leaking: websites that looked finished but that search engines struggled to read and that real customers, particularly customers with disabilities, could not use.

Then the audience changed again. AI assistants began researching vendors, comparing products, and handing their owners a short list. We found that most sites give those assistants almost nothing to work with, and that nobody was measuring it. So we wrote the measurement down, published it, and built a practice around it.

We are deliberately small. You get the person doing the work, not an account manager, and every audit we sell we have already run on our own site.

We are a registered partner in the Claude Partner Network and a verified member of Anthropic's Cyber Verification Program.

Who We Are

Clocktower and Associates is a small audit practice led by its founder. When we say we, it is not marketing plural. The person who runs your audit is the person whose name is on this page.

Wesley Shoffner

Founder

Wes has spent over eighteen years in enterprise infrastructure, operations, and systems architecture. He currently runs IT operations covering more than 600 point-of-sale systems across 130 retail locations, which is a good school for learning what actually breaks and what merely looks alarming.

He founded Clocktower and Associates to work on the same problem for websites. He wrote the ASM, ACP, and LEAN specifications that our agent-readiness work is measured against, and built Charlotte, an open-source tool for driving websites the way an automated agent does. Both are public, and both are how we check our own claims.

When he is not auditing sites, he is usually in the homelab, taking apart distributed systems to see how they fail.

Why We Publish Our Methods

Most audit work arrives as a number you are asked to trust. A score appears, a report follows, and there is no way to tell whether the same site would score the same next week or whether a different firm would score it at all.

We publish the scoring framework and the specifications behind it, so the number has a definition you can look up. That means you can argue with our findings, have your own developers check them, and take the standard with you if you stop working with us. It also means we have to be right, because the definition is sitting there for anyone to check us against.

How We Work

Every engagement runs on the same three commitments.

Published methods

The standards we audit against are written up in public, in full. If you want to know what we are going to measure before you pay us, you can just read it.

Evidence behind every finding

Every finding comes with what we found, where we found it, and how to reproduce it. You can hand a finding to a developer without us in the room.

Verification after the fix

After the work is done we re-scan and hand you the before and after, so you can see the change happen rather than take our word that it did.

See What We See

Run the free Assessment on your own site, and we will tell you what AI assistants, search engines, and assistive technology can actually make of it.