Charlotte web development and WordPress developers who build for the next five years, not the launch party.
Custom themes, blocks, and integrations on the CMS that runs most of the web. We build on WordPress every week, and we inherit a lot of sites other people built. Either way the goal is the same: fast, secure, and editable by your own team.
Most slow WordPress sites are not slow. They were built slow.
The plugin list stays short because the theme handles the work.
WordPress runs a large share of the web because it is flexible. That flexibility is also how a site ends up with forty plugins, three page builders, and a theme nobody can edit.
We write the theme. That sounds obvious, but most agencies assemble a site from a purchased theme, a page builder, and whatever plugins close the gaps. It works on launch day and drifts from there. Every update is a risk, every new page is a fight with the builder, and the person who set it up has moved on.
A custom theme built for your content does the opposite. Templates match the pages you actually have. Blocks match the things your team actually publishes. The plugin list stays short because the theme handles the work. The site stays fast because there is nothing in the way.
What you get. A theme you own outright, with no licence to keep paying. Blocks and patterns your editors can use without a developer. A plugin stack we can defend line by line. Staged updates with rollback, so nothing quietly breaks. Redirects, canonicals, and schema handled in the build, not bolted on later. And a written handover, so the site is not a mystery if you ever leave.
Inherited a site? A large share of our WordPress work is stabilizing sites other people built. We start with an audit, tell you plainly whether targeted fixes will solve it or a rebuild is the smarter move, and protect existing rankings either way.
Four phases. No technical debt left behind.
Audit and plan
Current theme, plugin stack, hosting, performance, and search signals reviewed. We decide together what stays, what goes, and what must not break.
Content model
Post types, fields, taxonomies, and blocks mapped to the things you actually publish. Editors get one obvious way to do each job.
Theme build
Templates and blocks written from scratch against your real content. Performance and accessibility checked at every template, not at the end.
Launch and handover
Redirects mapped, metadata preserved, analytics wired, monitoring on before DNS. Then a written handover and a maintenance plan if you want one.
A merged nonprofit, one WordPress site, and updates that take fifteen minutes instead of forty-five.
Roof Above formed from two legacy organizations with two sites. We built one WordPress site with blocks matched to what the communications team publishes, so a routine update went from forty-five minutes to fifteen.
Read the Roof Above case study
More work like this.
WordPress · PublishingA publishing workflow the marketing team stopped dreading.
WordPress · NonprofitHospice care, grief support, giving, and careers. One nonprofit site the staff can run.
Web application · MembershipTwo thousand members in fifty countries, on a platform built to hold them.
Often paired with
Website Design
Conversion-first design, drawn against your real content before the theme is written.
Website designWebsite Maintenance
Staged updates, monitoring, and backups by the engineer who wrote the theme.
Website maintenanceSecond Opinion Audit
Not sure whether to fix or rebuild? Start with a written read of where the site stands.
Second opinion auditWhat people ask before hiring a WordPress developer.
Yes. Four Eyes is a Charlotte WordPress development studio. We build custom themes and blocks, customize existing WordPress sites, connect CRMs, forms, payments, and membership tools, and take over sites other developers built. Work is done in-house, never outsourced.
No. Charlotte is home, and we work with clients across the Carolinas and the rest of the United States. Local or remote, the process is the same.
Both. A lot of our work is stabilizing and improving sites built by someone else. We will tell you plainly whether targeted fixes will solve it or a rebuild is the smarter long-term move.
Not for the sites we build. We write custom themes and blocks so the site stays fast and your team edits real content, not a builder. If you already run a builder site, we can maintain it or plan a migration when it makes sense.
Not if it is planned. We map existing URLs, redirects, titles, and metadata before the build, keep content parity, and verify indexing after launch. Protecting rankings is part of the scope, not an add-on.
Yes. We work on the real causes: bloated plugin stacks, heavy themes, unoptimized images, poor caching, and layout shift. A caching plugin on top of a slow build is not a fix.
Yes. Maintenance is proactive: staged updates, monitoring, backups, security basics, and performance checks, so problems do not turn into emergencies.
It depends on the content model, integrations, and whether we are rebuilding or starting fresh. After a short call we give a written scope and a fixed figure for that scope. No hourly surprises.
Tell us what the WordPress site has to do.
The short form is enough to start. An expert reads it and replies within one business day with concrete next steps.
Brief reviewed by an expert within one business day. Thirty-minute call. Written scope within five days.
“I have built Web sites with a wide array of teams over the past 20+ years. It's been my pleasure to work with excellent designers, but none have come close to the level of ownership, intelligence and guidance Four Eyes Productions provided…”
"*" indicates required fields
Goes to Michael. No CRM, no autoresponder, no newsletter signup.