Use case 1 · Foyer · October 14, 2026

Your website should read the brief before it pitches.

Most service websites ask a visitor to do the hardest part of the job themselves: translate a messy, specific situation into one of our menu items. Foyer flips that. It is a front door built on Quire that listens first, then arranges itself around what it heard.

An open glass doorway with nested architectural frames

The brochure problem

A typical services site is a brochure with a menu. Strategy here, engineering there, design and marketing on their own pages. It assumes the buyer already knows which box their problem fits in. Real situations rarely cooperate.

Take the scenario in the walkthrough: a sprawl of sites, brands, and platforms, with hundreds of local teams, and every one of those teams wants to keep publishing on its own. That last clause is the real constraint. It decides the governance model, the migration order, and the politics of the whole program. And it is exactly the kind of detail that never fits a dropdown.

The constraint that matters most is usually the one your contact form has no field for.

Listen first: say it in your own words

Foyer starts with one question: describe your situation. No service picker, no qualifying form. The visitor writes the brief the way they would explain it to a colleague.

The first thing Foyer does with that brief is read it back. This matters more than it looks. Before anyone reads a recommendation, they want to know they were understood. So the reading comes first and the composition follows. A reflected brief is also a trust check: if the read-back is wrong, the visitor can see it immediately, before a single claim is made.

Compose live, not from a template

From that point on, nothing on the page was written in advance for that visitor. It is assembled from the brief, live, in three parts.

The approach, through four lenses at once. Strategy, engineering, design, and marketing are held by one accountable team rather than passed between four of them. Each beat is tagged so the visitor can see which lens owns which part of the work, and the governance question and the delivery question are answered together instead of separately.

The layers: experience, data, activation, and optimization. This is where the work would actually land, and the order is deliberate. You cannot optimize an estate you have not yet governed.

The proof, selected against the brief. Instead of a wall of logos that leaves the reader to do the matching, Foyer picks from work that is genuinely comparable to the situation described.

A wall of logos asks the buyer to do the matching. Selected proof does it for them.

Watch the walkthrough (about 3 minutes). Captions available on YouTube.

Context that carries into the conversation

This is the part that usually gets lost on a website. When the visitor continues into Foyer itself, the brief they typed and everything the page composed from it is already in context. No repeated form. No starting over. No describing the estate a second time to a chatbot that has just met them.

So the follow-up can go straight to the hard question. In the walkthrough, it asks how to sequence the first 90 days. The answer comes back on the same thread: the inventory decisions, the governance model, the local publishing autonomy question, and the internal alignment that a consolidation of this shape always needs before anything gets migrated.

Guardrails, not improvisation

A front door that composes itself is only useful if it stays honest. Foyer runs on approved material, with guardrails on what it is allowed to claim. It routes across more than one model depending on the job. And its cost is usage-linked, so it scales with conversation volume rather than sitting as a fixed license.

This is the same principle that runs through Quire: source access is not publication permission. What the system knows and what it is allowed to say are two different things, and the second one is governed.

Why this is a Quire use case

Quire is an evidence-led demand and supply engine. On the demand side, it turns the knowledge already inside an organization into the prospect-to-customer journey. Foyer is that idea at the very first touchpoint. The same shared context that powers research, ICPs, and campaigns also powers the moment a prospect arrives and explains what they are dealing with.

And because the brief is captured in the visitor's own words, it does not stop at the website. It becomes evidence: what situations people arrive with, which constraints recur, which proof actually resonates. That is the journey learning loop, starting at the front door. When that demand turns into won work, the same context informs the supply side: which roles the work will need and who to find for them.

What to take away

Three ideas are worth borrowing, whether or not you ever build a Foyer of your own.

The walkthrough ends with a single ask, and so will we: type your own situation in your own words and see what the room gives you back. No form to fill in and nothing to download.

Win the work. Find the people for it.

See how Quire connects your organization's context to demand and supply.

Join the waitlist