An Edmonton gov-tech SaaS · $70K → $340K ARR.

This archetype is a slice of Edmonton gov-tech we ship into reliably: a $70K ARR civic SaaS or provincial-government-adjacent operator, founded by a UAlberta or Amii alum. The product is strong. It keeps losing RFPs to thinner competitors with better procurement collateral.

The pre-engagement state is familiar. A 2021-vintage Webflow marketing site failing WCAG 2.1 AA on color contrast and keyboard navigation. No audit-trail surface in the dashboard. Every RFP response written from scratch. RFP win rate: 7 percent.

Three structural problems compounded the growth ceiling. First, accessibility failures triggered procurement-stage blockers at provincial agencies. The buyer's accessibility officer flagged WCAG issues on the marketing site before the product evaluation even began.

Second, the dashboard had no audit-trail surface. Government compliance buyers could not validate data provenance, so the product lost competitive-evaluation rounds.

Third, every RFP response started from a blank page. Each one took two weeks of senior-engineer time and arrived too late to influence the procurement timeline.

Workstream 1 · Marketing-site rebuild on Next.js with WCAG 2.1 AA baseline. We migrated the site from Webflow to Next.js on Vercel. Every component was built and tested against WCAG 2.1 AA: color contrast, keyboard navigation, screen-reader landmarks, focus-visible states. The site's Core Web Vitals were all green at month 2.

Workstream 2 · Audit-trail dashboard surfaces. We built audit-trail UI inside the dashboard: append-only event logs, role-based-access export, and provenance trails for every data mutation. Provincial-agency procurement officers could finally validate data provenance during evaluation rounds. Win rate on competitive evaluations lifted from 22 percent to 41 percent.

Workstream 3 · RFP-shaped content surfaces. We built a public RFP-response library: pre-authored answers to 80+ standard procurement questions covering security, accessibility, data residency, vendor diversity, and SLA, exportable as a single document. Authoring time per submission dropped from two weeks to two days. RFP win rate moved from 7 percent to 19 percent.

Workstream 4 · Public docs portal. We built the public docs portal at /docs: API reference, integration guides, and changelog, with per-page TechArticle schema. Six months post-launch, the portal accounted for 24 percent of inbound qualified leads via organic search.

Workstream 5 · Procurement-aware case studies. We produced three deep-dive case studies with named customer agencies and real procurement-cycle data: months from RFI to PO, integration timeline, accessibility-audit pass rate. They became the most-cited content in active RFP processes.

This is one of our most-shipped engagement shapes for the Alberta capital. The pattern: Edmonton gov-tech or civic SaaS in the $50K to $200K ARR range, mixed-quality accessibility, no audit-trail dashboard surface, RFPs written from scratch, win rate stuck under 10 percent.

If that sounds like your product, the playbook transfers. The 14-week timeline holds steady. The workstreams compress or expand in the same proportions. The metrics typically land within plus or minus 20 percent of the archetype numbers above.

Five capabilities transfer directly to a comparable Edmonton engagement.

1. Marketing-site rebuild. Next.js with a WCAG 2.1 AA baseline that eliminates procurement-stage accessibility blockers.
2. Audit-trail dashboard UI. Append-only event logs and provenance trails.
3. RFP-response library. Compresses RFP authoring time from weeks to days.
4. Public docs portal. Captures technical-buyer organic search.
5. Procurement-aware case studies. Built on real procurement-cycle data.

Every Edmonton engagement starts with a 30-minute discovery call. Scope, timeline, and budget come back in writing within 48 hours. You work Mountain Time; we keep a seven-hour overlap to our New York HQ.