Hermes: AI Website Build Canada

Hermes wires one to three agents into the site at kickoff. We do not bolt a third-party chat widget on after launch. The chat agent grounds in your own documentation, not a vendor knowledge base. The lead-qual agent reads form submissions and routes them by intent before they hit your inbox. The content-discovery agent improves on-site search by reading the same content layer the chat agent uses. Each agent ships with structured event logs so you can audit prompt traffic. Most builds run two of the three agents. Operators with heavy form traffic add the third.

Hermes ships two stack options. First, WordPress plus Kadence Cloud suits buyers who want a self-edit surface their marketing team can update. Next, Next.js plus headless WordPress suits buyers who want a developer-facing surface with Git-based deploys. You pick the stack at kickoff. We do not support migrating an existing custom CMS into the Hermes build path: that work runs through a separate engagement. The two stack options cover roughly nine in ten buyer needs we see. The rest get routed to our Sovereign Infrastructure Brief for a custom path.

Hermes ships with Canadian-region hosting recommended by default. The inference layer sits in Canada. The vector store the agents read sits in Canada. The analytics tool we recommend sits in Canada. Personal data the agents touch is handled under PIPEDA. We can run the build in EU or UK regions if the operator has a documented reason; we do not run the default build in US regions. The Canadian-region default is the wedge: every other agency we benchmark defaults to a US region with a Canada toggle. Hermes inverts that default.

Hermes covers both. Design, build, agent wire-up, and the launch checklist are all in scope. The buyer brings the brand kit: logo in vector format, colour palette, and typography choices. We bring the layout system, the component library, and the design choices inside the brand kit. Hermes does NOT include brand identity work. If your logo and colour palette do not yet exist, you book a brand-identity engagement first or ship Hermes with placeholder assets and swap them in later. The build path is the same either way.

Four things sit outside Hermes scope. First, ecommerce builds run through a separate engagement. Cart, checkout, payment, inventory all need their own scope. Second, brand identity work also lives outside Hermes. That covers logo design, colour palette, and typography selection. Third, custom plugin development for WordPress runs through a referral partner. Finally, ongoing managed hosting is not in scope. You handle hosting yourself, OR you graduate to our Open Claw Basic tier for managed hosting after launch. The handover documentation covers the hosting choice and the migration path.

Four wedges define the AI website build Canada operators get from us. First, agents wired in from day one. Most agencies bolt a chat widget on after launch with a vendor knowledge base. Hermes wires agents into your own content layer at build time. Second, Canadian-region hosting by default. Most agencies default to a US region and offer Canada as a toggle. Hermes inverts that default. Third, observability built in. Most agencies hand over a site with no event logs. Hermes ships structured logs covering site traffic, agent prompts, and analytics. Finally, PIPEDA and WCAG 2.2 AA awareness from spec. Most agencies treat compliance as an afterthought. Hermes maps the launch checklist to both before go-live.