Services

Work a board can approve this quarter.

Start with solution consulting or one of four sprints. The full system comes once we both know the shape of the problem.

The first step

Solution consulting

We map your sites, data, and accessibility gaps with a senior person, then write a build or extend brief your leadership can take to the board.

2 weeks Read about solution consulting

Four ways in

Each one stands on its own.

01

Accessibility sprint

A manual audit against WCAG 2.2 AA, a fix pass on the real code, and notes your staff can keep using. Overlays are not the deliverable.

3 to 6 weeks Request an accessibility sprint
02

AI transformation sprint

An AI use policy the board can adopt and one internal workflow that saves staff time. Nothing faces members until it passes an accessibility review.

3 to 6 weeks Read about the AI sprint
03

Custom site and portal

The public site and a member or program portal on one stack you own, connected to the records your staff already work from.

8 to 14 weeks Scope a build
04

Data plumbing

Clean, connect, and migrate the records spread across spreadsheets, old systems, and inboxes into one record you can trust.

Scoped to your records Read about data plumbing

AI connectors

MCP development

Connect your company’s systems to AI tools through Model Context Protocol connectors: auth, scopes, and audit logs you control. Staff stop pasting records into consumer chats.

3 to 6 weeks for a first connector Read about MCP development

A first connector usually includes:

  • One live connector to a system of record you choose.
  • Only the tools you approve. Reading is the default, and a person has to allow any change.
  • A log of every call, which your IT or legal team can review.

In every engagement

What stays true.

  • You own the code, the data, and the roadmap.
  • One project lead, from the first call onward.
  • Staging you can click in week three.
  • Extra work sits in a change budget, never silent scope.
  • Canadian data residency, stated before the build.
  • If we part ways, the repo, admin docs, and runbook are yours.