Procurement-grade web work from a single accountable builder.
I build websites for local governments, post-secondary institutions, and public bodies: accessible by law and by craft, and evidenced by working software rather than promises. This page is written for the evaluation committee reading it.
The survey sweeps as you read. Three beacons mark the evidence below.
An independent practice is not a small agency. It is a different model, with named advantages.
One person holds the whole system
Architecture, design, build, accessibility, and performance live in one head. Nothing is lost in handoffs between departments, because there are none.
The person you evaluate is the person who builds
The one who answers the interview questions writes the code, designs the templates, and picks up the phone for the life of the engagement.
Budget goes into the work
One person is on the invoice. Your budget buys design, code, and content, with no agency margin stacked on subcontractors.
Built to survive its builder
Every project lives in version control with documented state, and you hold the code, content, and accounts from day one. Should anything take me off the field, any competent successor can open the repository and resume. Nothing is locked in one head or one login.
Capacity: engagements are scoped in writing with hours, weekly averages, and float named up front, and plans are deliberately booked below theoretical capacity so no phase requires heroics to hold. An AI-assisted toolchain under written governance raises throughput; it never substitutes for my verification of any deliverable.
Evidence you can open today.
Every project below is live today and labelled exactly what it is: client work, owned product, or concept. The portfolio holds the full survey; these four are the most relevant to institutional evaluation.
The Kootenay List
A free regional business register operated as public civic infrastructure: measured at 5,836 businesses across 83 towns and 6,633 sitemap URLs, statically rendered with region-wide search, plus a grant and funding map and business-licence guides per town. Civic-scale information architecture with real uptime obligations.
Read the case study →
City of Silvermere
A complete 177-route municipal website concept with a working decoupled Drupal 10 authoring environment behind it: editorial workflow, roles, scheduled publishing, and translation. Built so evaluators can judge working software directly, and labelled as a concept everywhere it appears.
Read the case study →
Clear to Enter
An immigration education platform run as a live product: 2,186 sitemap URLs across a structured, bilingual content system with a 656-entry legal reference library. Large-scale educational content architecture, the same shape of problem a post-secondary website is, in production today.
Read the case study →Five phases. Every gate is yours.
The schedule protects the institution's pace; it does not depend on mine. Phases end at client-controlled gates, review time is budgeted, and every plan carries named float.
Discovery
Content audit, stakeholder input, success metrics, and a production plan you approve before anything is designed. Migration is scoped here too: which pages carry forward, which get rebuilt, and who writes what, decided with you rather than discovered later. The gate is yours: nothing advances until the plan earns sign-off.
Design
Information architecture built around your residents' or students' top tasks, then a design system your editors can hold. Every review happens against real content from day one.
Build
Template families land in your staging environment early, so evaluation happens on working software. Accessibility and performance are built in from the first commit.
Test
WCAG 2.2 AA verification, performance measurement, integration regression, and user acceptance on your side, with generous time budgeted for your review.
Launch and transition
Redirect mapping, analytics carryover, editor training built for your real team shape, and documented handoff. Hypercare follows launch, then a defect warranty. You hold every credential.
The policies are public, dated, and linked. Due diligence should not require asking.
I speak the process fluently.
I respond to RFPs, NRFPs, and RFIs through the standard BC channels, including Bonfire and BC Bid, with compliant documents built to the evaluation criteria: every mandatory answered in order, every claim evidenced inside the submission itself, and pricing built from the published scope, itemized so a committee can see where every dollar works.
Standard institutional requirements, including commercial general liability, errors and omissions, and WorkSafeBC registration, are arranged at award per each engagement's stated terms, with numbers quoted at bid time so no award waits on paperwork.
And the honest line, because committees deserve it in writing: every claim I make is verifiable against a live system or labelled as concept work. Every statistic traces to a source, every portfolio piece is my own build, and every proof point runs somewhere you can visit.
Smaller municipality weighing a resident-first rebuild rather than a formal procurement? The municipal websites page covers that architecture in depth.
Evaluating vendors? Start with a conversation.
A 45-minute capability call costs nothing and answers the questions a website cannot. I will walk through methodology, live systems, and evidence on any project you pick.
Running a business rather than a public body? The same craft serves the packages: start there.