What I actually do — and what it costs

Custom WordPress, built to load fast and to stay that way. AI does the grunt work — boilerplate, first drafts, the repetitive parts — and I make every decision about how it looks and how it behaves. That split is exactly why the price is what it is.

• Design and build, on your content or content we shape together
• Tested on real screen sizes, not a browser window dragged narrow
• Enquiry forms with spam filtering that actually holds
• Analytics, search basics and SSL configured properly, not just switched on
• A walkthrough at handover so you can edit your own pages

violinbychristine.com was rebuilt and moved onto managed hosting in the same project.

The rule is the same either way: the new setup is built and tested alongside your live one, and we only switch when it's ready. No maintenance page, no lost email, no weekend where your site is simply gone.

• Full move onto infrastructure I run and monitor
• DNS and email cut over carefully — email is where migrations usually go wrong
• Hacked or infected installs cleaned up, then hardened so it doesn't recur
• Abandoned sites taken over, including ones where the last developer has vanished
• Your old host stays live until you're happy

southeastbelmont.com came off shared hosting onto a server of its own, with no downtime and nothing lost.

Your site runs on infrastructure I build, tune and watch. When you email, you get me — not a ticket number, not a support tier, not someone reading your question off a script.

• Uptime, speed, SSL and backup checks running around the clock
• WordPress core, theme and plugin updates applied and then verified
• Daily off-site backups
• Firewall, brute-force protection and a hardened server configuration
• Small changes and content edits included, within reason

Six sites run on it today, including this one, at 99.99% uptime.

Donation forms, event pages, volunteer signups — and the security that has to sit behind all of them. I already keep an animal rescue's donations safe, so this isn't a category I'm guessing at.

• Donation forms hardened against card testing and fraud from day one
• Event and volunteer signup pages your own team can update
• Grant-friendly basics: accessible, fast, and not embarrassing in an application
• The same monitoring and backups everybody else gets

When hhhar.org's donation form was hit by a card-testing attack, it was locked down the same day and every fraudulent charge refunded.

The free scan is automated and shallow by design — it's meant to start a conversation. This is a week of me inside your site with the same checklist I run against my own.

• Performance measured page by page, not just the homepage
• Security and exposure review — what's reachable that shouldn't be
• Accessibility pass
• Plugin, licence and version debt: what's abandoned, what's risky, what's fine
• A written report and a call, in priority order, with rough costs against each item

It's the same checklist that runs against my own sites every week — done by hand, and with your context rather than a generic score.

The same kind of thing I built to watch these sites: something that checks, collects and routes so that a person doesn't have to. Usually the second conversation we have, not the first.

• Form submissions routed, acknowledged and chased automatically
• Reports that assemble themselves instead of someone rebuilding a spreadsheet
• Alerts when something genuinely needs you — and silence when it doesn't
• Connections between the tools you already pay for

The uptime, speed and backup monitoring behind every site above is exactly this, running on my own infrastructure.