Dear Kay,

Thank you for the opportunity to respond to the Town of Duck's Request for Proposals for Website Redesign and Content Management System Implementation. We've spent meaningful time on ducknc.gov over the past few days, navigating it as a year-round resident researching trash collection, a property owner checking development permit guidance, a visitor planning a Jazz Festival weekend, and someone watching the live boardwalk camera before a storm. That research shaped this proposal.

Your RFP makes two requirements unusually clear and we want to address them directly before anything else:

The site must function as an emergency information hub. Hurricane season starts June 1. When a Category 3 is bearing down on the Outer Banks, the website needs to serve 10x normal traffic, degrade gracefully when CDN nodes get hit, and let your team push an alert banner in seconds, not minutes. Our hosting stack is built on this assumption. We can show you, in interview, the load-shedding behavior under stress.

Daily automated accessibility scanning with no manual HTML remediation by Town staff. This is more than a checkbox. We integrate a third-party monitoring service (accessiBe-equivalent) and serve as the primary point of contact for any compliance issue. Your staff never has to touch HTML or hire a consultant for an audit response. Our proposal scopes this as Year-1-included, then $1,500/year ongoing.

The pages that follow are visual proof of what we mean. We've embedded screenshots of our deployed municipal platform from comparable engagements: the Town of Annapolis Royal (Nova Scotia, 530 residents) and the City of Waverly (Iowa, 10,400 residents). Both small-staff municipalities. Both use the same platform that would be tailored to Duck.

We are also a small, US-based specialist firm. WordPress, the platform we build on, is open-source. The Town of Duck would own its code, content, and design files at every step, with no vendor lock-in and no enterprise SaaS subscription. If the relationship ever needs to end, you take everything with you.

We would welcome the chance to walk through this proposal and the platform itself with you, the Assistant Town Manager, and any staff member who will work in the new CMS daily. Please consider this proposal an invitation to a conversation.

Sincerely,

Nathan Parikh
Founder & Chief Strategist, HappyWP
(949) 639-9637 · nathan@happywp.co

Below are screenshots of two HappyWP municipal sites currently deployed. Both are responsive, accessible (WCAG 2.1 AA at minimum, currently being upgraded to 2.2 AA), and built on the same WordPress-based platform we'd customize for Duck.

Town of Annapolis Royal, Nova Scotia (530 residents) — homepage
Heritage-warm palette, quick-action pill row, "popular services" cards, and "How do I…" accordions. Built on the same platform we'd tailor for Duck. annapolis-royal.happywp.net

City of Waverly, Iowa (10,400 residents) — homepage
River-motif palette referencing the Cedar River, prominent emergency announcement bar (top), Cedar River hero image, quick-task pills. Demonstrates the architecture supporting Duck's emergency-comms use case. waverly.happywp.co

The depth of content modeling matters as much as homepage aesthetics. A service page must give a resident exactly what they need (steps, fees, FAQs, related links) without making them click into multiple pages.

Annapolis Royal — service detail page
Single-page view of water billing: turnaround dates, payment steps, current rates, related services, FAQs. This is the content depth your residents would get for permit fees, beach safety guidance, waste schedules, and every other Town service.

Mobile is the primary device for emergency information lookup. Both demos are mobile-first.

Waverly on mobile
Note the announcement bar at top (used for emergency comms), the search-first hero, and the immediate visibility of "pay my utility bill" and "check trash and recycling" quick-action buttons. Translates directly to Duck's coastal-storm use case.

Annapolis Royal on mobile
Heritage-warm palette adapted for mobile. Top public-hours banner, search-first hero, popular services in a vertical scrollable column. Same template, different community identity.

Before drafting this proposal we audited ducknc.gov as four different users: a year-round resident researching trash collection, an out-of-town property owner checking development permits, a Jazz Festival visitor planning a weekend, and someone checking emergency preparedness ahead of a storm.

Findings From the Current Site

• The seasonal vs. year-round audience is not architected. Beach visitors and full-time residents need different first-stop information but currently navigate the same hierarchy.
• Emergency information is not prominent. Storm-info and preparedness pages exist but require navigation through "Frequently Visited." Should be one click or an alert banner from the homepage.
• Mobile experience needs work. Several key pages require pinch-zoom, and the navigation is not finger-friendly.
• Accessibility is below the 2.2 AA standard the RFP requires. Multiple pages have low-contrast text, missing alt attributes, and form labels that screen readers cannot interpret cleanly.
• The Duck identity is underused. The Duck Herd, the boardwalk, the Jazz Festival, and the coastal character are not visually carried through the site. A redesign is an opportunity to make the site feel like Duck, not a generic municipal template.
• Search and document discovery are weak. Common queries (e.g., "trash schedule," "permit application," "council agenda") produce inconsistent or unhelpful results.

What the RFP Calls For That We Are Treating Seriously

Several requirements in your RFP stand out as more than checkbox items. We've scoped each at meaningful cost rather than as throwaways:

• Daily automated accessibility scans + monitoring + monthly audits — not standard WordPress capability. Requires a third-party tool integration (Year 1 included, $1,500/yr in subsequent years).
• Comprehensive pattern library — we're scoping this as a real component-architecture deliverable (buttons, tiles, accordions, tabs, media, CTAs), not just a style guide.
• Emergency-resilient architecture — CDN-backed hosting, graceful degradation, alert-banner publishing, performance under spike traffic.
• Multi-site capability — if Duck wants to spin up a campaign or special-event microsite in the future, the platform supports it without a new vendor engagement.

Every item maps to a specific requirement in your RFP. The screenshots above are illustrative of what each section produces, applied to Duck's content.

Discovery & Planning

• Project kick-off with Kay and the Assistant Town Manager
• Audit of current site content, IA, and analytics
• Seasonal vs. year-round audience mapping
• Sitemap, wireframes for key page types, content migration plan

Design & Pattern Library

• Two homepage design comps incorporating Duck's coastal identity, with one round of revisions per direction
• Atomic pattern library: buttons, tiles, accordions, tabs, media components, CTAs — ready for staff reuse
• Secondary page layouts (services, news, events, departments)
• Mobile-first responsive design

Development & CMS Configuration

• WordPress configuration with block editor (WYSIWYG), role-based permissions, draft/review/publish workflow, version history
• Custom content types: News, Events, Council Meetings & Documents, Departments, Services, Public Notices
• Site search with PDF/document indexing
• Calendar with category filtering (events, meetings, public hearings)
• MailChimp newsletter signup integration
• Social media integration

Accessibility (WCAG 2.2 AA, ADA, Section 508)

• Pre-launch manual + automated accessibility audit
• Third-party accessibility monitoring tool integration (daily scans, monthly audit reports)
• HappyWP serves as primary contact for any accessibility issue post-launch
• Editor-level a11y prompts in the CMS (alt text reminders, contrast warnings)

Emergency Comms Hub

• CDN-backed hosting with traffic-spike capacity
• Graceful degradation pattern: critical info paths remain available even if non-essential features are throttled
• One-click alert-banner publishing for staff
• Performance budget targeting <2s first-contentful-paint on 3G

Content Migration

• Vendor handles full migration of estimated 50-80 pages and public documents
• URL redirect mapping to preserve search rankings
• Document metadata and tagging preservation
• Reorganization where appropriate (with Town approval)

Testing, Launch, Training

• Cross-browser and device testing
• 30-day post-launch bug fix and refinement window
• Four training sessions via Zoom (recorded for future reference): administrator track + editor track
• Written documentation, video tutorials, in-CMS help

One-Time Build

Annual Recurring

Out-of-scope work: $185/hour standard, $277.50/hour after-hours / urgent (hurricane response).

The screenshots above are taken from these live deployments. Please click through if helpful.

• Annapolis Royal, NS (530 pop, heritage town) — annapolis-royal.happywp.net
• Waverly, IA (10,400 pop, river town) — waverly.happywp.co
• Janesville, WI (66,800 pop, mid-size city) — janesville.happywp.net
• Ballwin, MO (31,100 pop) — ballwin.happywp.co

Next Steps

If shortlisted, we'll prepare a 30-minute live demonstration tailored to you, the Assistant Town Manager, and any staff member who'll work in the new CMS. We'll walk through the platform, demonstrate a real editorial workflow (post a meeting agenda, publish a news update, push an emergency alert), and answer any technical or budget questions in real time.

For questions before then, reach Nathan directly at nathan@happywp.co or (949) 639-9637. We commit to a 4-hour response window during business hours.

This proposal is valid through August 15, 2026, and may be extended in writing.