Kimply AI venture studio Invite us to bid

The Kimply System for government website redesign

A five-stage method for redesigning public-sector websites. Every stage has one accountable owner, a fixed list of deliverables, and a written record your team can audit.

LAST UPDATED: NOVEMBER 2026

01 · Stages and deliverables

What you get at every step.

STAGE 01

Discover and audit

Owner · Kimply team

We measure the site you have before we touch it.

  • WCAG 2.1 AA accessibility audit of the current site
  • Inventory of every page, PDF, and form
  • Search Console and GA4 baseline
  • Interviews with department leads
STAGE 02

Spec and approve

Owner · Indy Leonard

Every requirement is written down and approved before a line of code.

  • Sitemap, templates, and requirements in one source of truth
  • One decision card per approval, sized for a 25-minute review
  • An append-only audit trail for procurement and council records
  • Run in Crema Spec, our own spec platform
STAGE 03

Design and build

Owner · Indy, Spenser, and Mike

Accessible, mobile-first templates your staff can update without a developer.

  • Templates built and tested to WCAG 2.1 AA
  • A CMS staff can update on their own
  • Forms, payments, and service requests connected to existing systems
  • Speed, security, and uptime hardening
STAGE 04

Content and SEO

Owner · Brianna Blaney

Plain-language pages that residents understand and search engines can find.

  • Rewrites at a 7th to 9th grade reading level
  • PDFs rebuilt as accessible web pages where possible
  • Headings, metadata, schema, and FAQs on every key page
  • Structured for Google and for AI answer engines
STAGE 05

Launch and support

Owner · Alicia Baron-Barlow

A clean cutover, trained staff, and a plan for what comes next.

  • A redirect map so no old link breaks
  • Staff training and a content style guide
  • Monitoring for accessibility, broken links, and search
  • An ongoing support plan

02 · Who does what

Clear roles for your team and ours.

City staff time is limited. This split keeps your team in the approval seat without doing the heavy lifting.

WorkKimplyYour team
Accessibility auditLeads and deliversProvides site access
Requirements and sitemapDrafts the specReviews and approves each decision card
Design and developmentBuilds and testsReviews at set milestones
Content rewritesWrites and optimizesFact-checks department details
Launch and redirectsPlans and executesApproves go-live date
Ongoing updatesTrains staff, optional supportOwns day-to-day updates

03 · Why it works

What makes the Kimply System different.

01

Specs before code

Requirements are written, reviewed, and approved in Crema Spec. Nothing gets built on a guess.

02

A paper trail by default

Every approval is logged with its reason. That record supports procurement, audits, and council questions.

03

Content is not an afterthought

Writers start at the audit, not the week before launch. Pages ship accurate, plain, and searchable.

04

Built for the people who run it

Your staff can update the site without a developer, and they leave training with a style guide.

04 · Forward-deployed engineering

Embed, build, productize.

94,000+ Emails audited in one live logistics engagement

Before our team automated a single workflow, we read the inbox. Every exception and rule was captured first.

We bring the same depth to a city website audit. Every page, PDF, and form gets counted before anything moves.

05 · FAQ

Government website redesign, answered.

What is forward-deployed engineering?

Forward-deployed engineering puts engineers inside a customer's team so they build where the work happens. Kimply embeds for about 90 days, builds the fix, then turns it into a repeatable product. We call it embed, build, productize.

What is included in a government website accessibility audit?

We test the current site against WCAG 2.1 Level AA, inventory every page, PDF, and form, and record search and analytics baselines. You get a prioritized list of issues before any redesign work begins.

Who approves decisions during the redesign?

Your team does. Every requirement is written as a decision card in Crema Spec, sized for a 25-minute review, and logged with its reason once approved.

Do you migrate our existing content and PDFs?

Yes. We inventory, clean up, and migrate content, and we rebuild key PDFs as accessible web pages where possible. A redirect map keeps old links working.

Can our staff update the site after launch?

Yes. Sites are built on a CMS your staff can run without a developer, and every launch includes training and a content style guide.

Next step

Ready to put the system to work?

Send us your RFP or scope. We will map it to the five stages and show you the plan.