From RFP to Running Platform in 5 Days
Chippewa County, Michigan — Municipal Website Refresh Initiative
Overview
When Chippewa County issued an RFP for a municipal website refresh, WAM DevTech made a decision: rather than respond with a proposal and concept designs, we would build a working system before the evaluation process began.
Nobody asked for this. It was not a requirement of the RFP. It was a deliberate choice to retire the technology risk before any contract existed — and to walk into the evaluation with something no proposal document can replicate: a live system.
In less than five days, the team scoped, architected, and deployed a production-grade municipal content management platform. Not a mockup. Not a prototype. A live, publicly accessible system built on enterprise-grade infrastructure, populated with real county data, and ready to demonstrate to county IT leadership on day one of the evaluation process.
The same infrastructure, the same codebase, the same architecture we would deliver on day one of the contract. The only difference between what ran at the interview and what Chippewa County would go live with is a domain name.
The Challenge
Municipal website projects are notorious for their complexity. Multiple departments. Strict role-based access control. Structured content with regulatory requirements. Public-facing transparency obligations. Performance and security standards that would make a private-sector CTO nervous.
The Chippewa County RFP called for:
Accessible to Non-Technical Staff
A modern CMS that county staff could manage without developer involvement. Department editors needed control over their own content without touching other departments' records.
Role-Based Access Control
Department-level permissions with distinct editor roles. A health department editor could not accidentally modify a sheriff's office record. Field-level control, not just page-level.
Long-Term Maintainability
A future-proof architecture that county IT could own long-term. No vendor lock-in. No platform that outlives its own support lifecycle. The county needed to own the system, not rent access to it.
Most firms respond to this kind of brief with a proposal and concept designs. WAM DevTech responded with a running system.
"AI doesn't fail because it can't code. It fails because it isn't given what it needs to succeed. The bottleneck is always architectural judgment, not typing speed."
The Approach: AI-Accelerated Code Intelligence
AI-Accelerated Code Intelligence is WAM DevTech's methodology for directing AI as a force multiplier under senior architectural oversight. A senior architect defines the data model, infrastructure pattern, security posture, and integration strategy. AI executes the implementation at a pace no purely manual team can match.
What AI Handled
- Boilerplate collection definitions and field schemas
- Docker multi-stage build configuration
- Astro component scaffolding and CSS
- Seed script generation from real county data
- ALB listener rules and ECS task definitions
- Lexical rich text renderer for the frontend
What Senior Architects Directed
- Headless CMS architecture selection and rationale
- AWS infrastructure design (ECS Fargate, RDS Aurora, ALB)
- Role-based access control data model
- Collection schema design for municipal content types
- Security posture and secrets management
- Production deployment patterns and health check strategy
What Was Built
In five days, a production-grade municipal content management platform was designed, built, deployed, and demonstrated — covering three layers of the full stack.
Content Management System
| Component | Detail |
|---|---|
| Platform | Payload CMS 3.x — open-source headless CMS built on Next.js 15 |
| Collections | 7 content collections: Departments, Public Notices, Meeting Agendas, Employment Postings, Pages, Media, Users |
| Globals | 3 global config objects: Site Settings, Navigation, Homepage |
| Editor | Full Lexical WYSIWYG rich text editor on all narrative content fields |
| Access Control | Role-based: Admin, Department Editor, Reviewer |
| Branding | Custom Chippewa County branding in the admin interface including county seal |
Public-Facing Website
| Component | Detail |
|---|---|
| Framework | Astro SSR with dynamic routing |
| Design | Custom design system in Chippewa County navy and gold |
| Homepage | Hero banner, quick access services, live notices and meetings feed |
| Departments | Full directory with individual department pages |
| Content Pages | Public notices with category filtering, meeting agendas with calendar display, employment postings with deadlines |
| Page Builder | Any page created in the CMS appears automatically at its slug URL |
Infrastructure
| Component | Detail |
|---|---|
| Compute | AWS ECS Fargate — containerized, auto-scaling, zero server management |
| Database | Amazon RDS Aurora PostgreSQL — fully managed relational database |
| Routing | Application Load Balancer with path-based routing rules |
| Secrets | AWS Secrets Manager for all credentials and environment variables |
| Images | Amazon ECR with multi-stage Docker builds and optimized production images |
| Reliability | Health check monitoring with automatic container restart |
Live demo: chippewacountymi.wamdt.com
Why Headless: The Technical Differentiator
Most municipal websites run on one of a handful of platforms: CivicPlus, Revize, WordPress, or Drupal. Each has a meaningful share of the local government market. Each also has meaningful constraints.
CivicPlus and Revize are purpose-built for municipalities — that is their strength and their limitation. They are proprietary SaaS platforms. The county rents access to the system. Content lives on the vendor's servers. Migrating away means starting over. When the vendor raises prices or changes the product, the county has limited leverage.
WordPress and Drupal offer more flexibility but carry their own costs: plugin ecosystem vulnerabilities, PHP runtime maintenance, upgrade cycles that break customizations, and performance overhead that requires significant caching infrastructure.
WAM DevTech chose a headless architecture for Chippewa County because municipal technology needs to outlast any single vendor's roadmap.
The website can be rebuilt without touching a single byte of content. The same content API can power a future mobile app, kiosk, or emergency notification system.
No PHP runtime, no plugin ecosystem vulnerabilities, no wp-admin brute force attacks. A dramatically smaller attack surface by design.
A health department editor cannot accidentally modify a sheriff's office record. Access control is enforced at the data layer, not the presentation layer.
The entire CMS configuration is version-controlled TypeScript — reproducible, reviewable, and auditable. No magic database tables. No mystery settings.
"CivicPlus and Revize own your content the moment you sign. WordPress owns your maintenance calendar. Payload CMS is a data platform with a publishing interface — the county owns everything, and the configuration is version-controlled code. For local government with long-term maintainability requirements, the choice is clear."
Replicable Methodology
The five-day timeline is not an anomaly. It is the expected output of AI-Accelerated Code Intelligence applied by a team with the right architecture skills. The same methodology applies to any municipal or local government engagement.
| Traditional Development | AI-Accelerated Code Intelligence |
|---|---|
| 2 to 4 weeks: discovery and requirements | Day 1: architecture decisions and infrastructure |
| 4 to 6 weeks: design and prototyping | Days 2 to 3: CMS configuration and collections |
| 8 to 12 weeks: development | Days 3 to 4: frontend build and content seeding |
| 2 to 4 weeks: testing and QA | Day 4 to 5: refinement, branding, and live demo |
| 1 to 2 weeks: deployment | |
| Total: 17 to 28 weeks | Total: 5 days to production-ready |
What This Means If Awarded
It is already built and proven. Content migration can begin on day one of the contract.
Not a hypothetical one. The system they will use is the system they evaluate. No surprises after contract award.
Production launch is a configuration change, not a build. The hardest technical problems were solved before the contract was signed.
The technology question is already answered. What remains is configuration, training, and content migration — not proof of concept.
"The price doesn't change when your requirements do. Fixed price confirmed within 48 hours."
ADA Compliance and the DOJ Title II Deadline
Chippewa County operates under the DOJ's final rule under Title II of the ADA, which requires local governments to meet WCAG 2.1 Level AA accessibility standards for public-facing websites. With a population under 50,000, Chippewa County's compliance deadline is April 26, 2027.
The platform WAM DevTech built was designed with WCAG 2.1 AA compliance as a foundational requirement — semantic HTML structure, proper heading hierarchy, color contrast ratios, and responsive design across all device sizes were built in from the start, not retrofitted. That is a different starting point than inheriting a legacy platform and attempting to patch it toward compliance.
A formal accessibility audit is a standard deliverable in WAM DevTech's go-live checklist, covering skip navigation links, ARIA landmark labels, focus indicator styling, keyboard navigation, and document language attributes. Any linked PDFs — forms, agendas, public notices — would be evaluated for tagged PDF compliance as part of content migration.
The headless architecture is a compliance advantage: accessibility fixes in the Astro frontend deploy independently of the CMS, with no risk of breaking content or admin functionality.
"We built the foundation. The compliance audit is a contract deliverable, not an afterthought."
Conclusion
This engagement demonstrated what becomes possible when AI-Accelerated Code Intelligence is applied to a municipal CMS challenge. Not a slide deck describing future capability. Not a proprietary SaaS platform the county would rent indefinitely. A working system, built to the county's requirements, owned by the county, running live in five days.
It is worth being precise about what this demo represents. It was built cold — from a public RFP document alone, with no discovery sessions, no stakeholder interviews, no internal documentation, no understanding of how county staff actually work day to day. That is the floor, not the ceiling.
If awarded, WAM DevTech would still conduct a full discovery process with Chippewa County — understanding the real workflows, the staff pain points, the integration requirements, and the edge cases that no RFP document captures. What gets built after that process would be substantially better than what ran at the evaluation. The demo proves the methodology works with the minimum viable information. Discovery unlocks what it can really do.
This is what AI-Accelerated Code Intelligence produced from a public document alone. Imagine what it builds from yours.
Facing a Municipal Website Modernization?
See what AI-Accelerated Code Intelligence can build from your requirements.