A web consultancy's site is its portfolio
We tell clients that accessibility matters, that AI search is changing how customers find businesses, and that page builders quietly cost more than they save. If our own site didn't prove every one of those claims, none of them would be worth much.
So we set a simple, slightly uncomfortable rule: nothing goes in an article unless this site already does it. This page is the audit trail.
02 — The BuildStatic where it counts, dynamic where it pays
The site you're reading is plain, fast, static HTML — there's no framework rendering this page, no client-side hydration, and nothing between you and the content. Behind it sits a purpose-built CMS we wrote ourselves: articles live in a database, and publishing regenerates every affected page, the sitemap, and the search index in one step.
That architecture is a deliberate trade we recommend to clients constantly: visitors get the speed and security of static files, while the business gets WordPress-quality editing without WordPress-scale attack surface and maintenance.
We didn't just build the site — we built the publishing system
Every article, page, and image on this site is managed through a custom admin panel we designed and built ourselves — a working sample of the custom CMS development we sell. One click publishes an article, regenerates every affected page, updates the sitemap, and rebuilds the search index.
Dashboard
- Two-factor authentication, session hardening, and rate limiting — security as a default, not an upgrade
- Version history on every article and page, so nothing is ever lost to a bad edit
- Image uploads optimized automatically — resized, converted to WebP, and stripped of metadata
- The live site stays static HTML — visitors never wait on a database, and there are no plugins to patch
This matters to your project for a simple reason: when we say we can build you a publishing tool that fits how your team actually works, this is the receipt.
04 — Accessibility100/100 — on all 75 pages, not just the homepage
Most agencies that mention accessibility have run one audit, once, on one page. We ran Lighthouse on all 75 pages of this site — homepage, every article, every legal page — and every single one scores 100/100. That took real work: fixing colour contrast inside article content, restructuring heading hierarchies, and rewriting components that looked fine but read poorly to screen readers.
- Keyboard navigation and visible focus states on every interactive element
- Reduced-motion support — every animation on this site switches off if your system asks it to
- Theme-aware contrast rules enforced at build time, because automated checkers miss real failures
- A skip link, semantic landmarks, and a strict heading hierarchy on every page
This is the exact process an accessibility audit applies to your site — we just ran it on ours first.
05 — AI SearchBuilt to be the answer, not just a result
When someone asks an AI assistant who builds accessible websites in Calgary, the assistant needs machine-readable evidence. Our homepage carries seven interlocking schema types — business entity, organization, website, page, breadcrumbs, FAQ, and a services catalogue — all cross-referenced so that crawlers understand exactly what we do, where we do it, and how the pieces connect.
- FAQ answers written the way an assistant would speak them aloud
- Speakable markup pointing voice assistants at the sentences that matter
- An open-door robots policy for AI crawlers — GPTBot, ClaudeBot, PerplexityBot, and Google-Extended are all welcome here
- 64 articles structured to directly answer the questions people actually ask assistants
What this means for your project
The point of this page isn't that our website is nice. It's that everything above is repeatable — the accessibility discipline, the schema architecture, the static-plus-CMS trade, and the performance habits are the same process we bring to client work, documented in public where you can check it.
The cheapest way to evaluate a web developer is to inspect the site they built for themselves.
Run this page through Lighthouse. View the source. Ask an AI assistant about us. Then tell us about your project — and expect the same receipts when we're done with yours.