The homepage's strongest proof, six named communities with populations, points to six pages that return 404. A clerk or city manager who clicks "Read case study" to show a council member gets an error, on a site selling reliability to government.
First action
Today, point the six links at the existing /resources case studies (Macon County and Perinton already have pages) so nothing 404s, then write the four missing ones.
How to measure it
Demo requests after a case-study view
- Now
- –
- Target
- +30% relative
- By
- 6 weeks after the pages ship
Steps
Stop the 404s today
Redirect the six /case-study-guides/ URLs to the closest live page (Macon County and Perinton have resources pages; the rest go to /communities until written).
Narrative and Content Lead 30 minutes
Fix the template
One layout: population, prior system, weeks to go-live, processes online, one before-and-after number, a named quote, and a "talk to someone at a town this size" button.
Narrative and Content Lead 1 day
Get the numbers from Deployment
Go-live dates, process counts and processing-time changes for each community from the deployment records.
Deployment Strategy Manager 1 day
Get approval from each community
Staff sign-off on quotes and numbers; many governments need a communications office to approve.
Founding Account Manager 1 to 2 weeks
Publish the four missing studies
Clarksville, Nederland, Butte-Silver Bow and Lawrenceburg.
Narrative and Content Lead 1 week
Add the population filter
A filter on /communities by population band and state that lists the matching studies.
Head of Marketing 2 days
Arm the outbound team
Each Business Development Manager gets the study closest to each prospect's population for their sequence.
Head of Business Development & Operations 1 hour
Add a broken-link check
A weekly crawl of the homepage and solution pages so this does not recur.
Head of Marketing 1 hour
Build this page. The page built from this outline, in your voice, live on your site. Usually live within days.
Book a working sessionWhy it works
Publish a case study at each of the six /case-study-guides/ URLs (Macon County, Clarksville, Nederland, Perinton, Butte-Silver Bow, Lawrenceburg) with the same structure: population, what they replaced, weeks to go-live, the permit and license types now online, one before-and-after number, and a quote from a named staff member. Add a "find a community like yours" filter by population band and state on /communities.
Local government buyers decide by peer comparison: "who like us has done this, and how long did it take". The homepage already lists go-lives from 3 to 11 weeks; turning them into readable pages gives every Business Development Manager and AE a link that answers that question, and the Narrative and Content Lead is hired to build exactly this customer story engine.
Ready to use
Landing page outlineCase study page outline
H1: How {Community}, {State} (population {pop}) moved {processes} online in {weeks} weeks
1. The starting point: what they used before and what it cost staff
2. The go-live: week-by-week, who was involved
3. The result: one before-and-after number (e.g. days to issue a permit)
4. In their words: quote from a named staff member, with title
5. What residents see now: screenshot of the portal
6. Towns like {Community}: two more studies in the same population band
CTA: Talk to a community your sizeRisks and how to handle them
A community will not approve its numbers
Publish the process change without the number, or replace it with another community in the same population band.
Evidence
- programmable.infoSite scan: 6 of the 39 homepage links checked are broken, and all six are the "Read case study" links (Macon County NC, Clarksville IN, Nederland TX, Perinton NY, Butte-Silver Bow MT, Lawrenceburg TN), each returning a 404 under /case-study-guides/.Source
- Your websiteHomepage: "The operating system for modern government"; agencies in 40+ states, 7,000+ mission-critical processes, 200+ municipal and county agencies, a 98% renewal rate, processes up to 95% faster and implementations about 5x faster than legacy software; named go-lives took 3 weeks (North Royalton and Niles, Ohio) to 11 weeks (Vermillion, South Dakota).Source
- HiringNarrative and Content Lead: own the editorial calendar "optimized for SEO and AI discoverability", "original data reports, gated guides", ghostwrite for the founders, and "build our customer story engine" with case studies and customer videos; raw material includes "analyzing permitting data across the country".Source
- Your websiteCommunities page: "Hundreds of municipalities and counties are modernizing local government with GovWell"; Hampton, Georgia's Community Development Director: business license processing "went from 10 days to under an hour"; Twinsburg, Ohio issues building permits twice as fast.Source