Senior web production — UX, front-end, WordPress, content, conversion, and QA, working as one thing instead of five.
Why that's actually useful
I work across those seams.
Not as separate specialties.
As parts of the same product.
Selected Work
I redesigned moveBuddha's primary lead capture flow from the ground up, including the visual design, decision logic, interaction flow, and every line of user-facing copy.
Result: a 1-2% lift on the site's central revenue channel.
View case study →I redesigned the results experience for moveBuddha's moving cost calculator, clarifying the layout, improving the next-step flow, and tightening the page around conversion intent.
Result: a 1-2% lift on the site's second most important revenue channel.
View case study →I oversaw the migration of GoodMigrations.com from a fragmented Laravel Blade system into WordPress, preserving hundreds of pages, links, images, and SEO value.
Result: no SEO drop, no broken-link/image fallout, and improved rankings after launch.
View case study →I built WordPress tools connected to GPT that helped a content team create controlled, nested text variance for programmatic content workflows.
Result: faster content production with more flexible variation inside a structured templating system.
View case study →What I'm good at
judgement is the useful part: knowing how UX, code, content systems, QA, AI, and business goals affect each other.
Most website problems do not stay inside one lane. A page can look fine, work poorly, rank badly, confuse users, or miss the business goal. I'm useful because I can see how those pieces affect each other.
I can move from “this needs to work better” to actual page structure, interface copy, front end code, WordPress logic, responsive behavior, QA, and launch ready decisions.
My work has usually sat close to revenue, search traffic, lead flow, content systems, and production launches. That means I notice the details that can make a website look finished while still quietly failing.
I use AI to improve how the work gets done: faster prototypes, sharper QA, cleaner content systems, reusable production tools, and better ways to inspect, revise, and ship. The tool is not the value. The judgement is.
If you need someone who can improve a website without losing sight of users, revenue, content, code, or production reality — I'm probably worth a conversation.