What was going wrong
A national membership organization had been running on a website built over a decade earlier. It was slow, visually dated, and difficult to navigate on mobile. Updating content required a developer — which meant news and announcements were always behind. The membership system was disconnected from the website, requiring manual updates when members joined or lapsed.
The part that stuck with me: their staff knew exactly what the site needed. They’d known for years. The problem was never the plan — it was finding someone who could actually execute it without creating three new problems in the process. That’s a different kind of build. It requires patience and someone who’ll read what’s there before touching anything.
What we built
- →
Conducted a full audit of existing content, navigation structure, and user journeys
- →
Redesigned the site architecture to support their content model and membership tiers
- →
Built on DNN with custom skin — fast, mobile-responsive, and 99+ PageSpeed score
- →
Created an editor-friendly content system — staff can update pages, news, and events without developer help
- →
Built a custom DNN membership module connected to their existing member database
- →
Integrated member login, directory access, and gated content based on membership status
- →
Set up automated email triggers for membership renewals, event registrations, and announcements
"Our members actually use the website now. That wasn't true before."
Already know what needs to change?
Sometimes the plan is there — you just need someone to execute it cleanly. Tell me where you are and what you’re working with.