Need a new site, or the rebuild you keep putting off? I'm Raffi. My latest is HOUS, a Next.js site for an LA real estate firm, and I stay on for the fixes after launch.
HOUS sells modern and architecturally significant homes in Los Angeles, alongside a deep editorial journal. When it left WordPress, 373 journal posts and 42 listings had to come with it, each at a URL people and Google already knew. I rebuilt the site on Next.js 16 and React 19, with Storyblok as the CMS, so editors can lay out pages visually.
Search is the risky part of a WordPress to Next.js migration. I set up 55 permanent redirects and kept the old URL format, so old links land on the right page in one hop. I also wrote a converter that turned the old WordPress posts into Storyblok content.
I plan the site, build it, connect it to the tools you already use, and stick around for what breaks. I take on client projects alongside my job as the senior web developer at Wilshire Law Firm.
We work in two-week stretches. You see every change on a preview link before your visitors do. I write down why the site is built the way it is, so whoever works on it next can pick it up.
“…he always took the time to explain complex ideas clearly and made sure we felt confident at every step.”
Whichever your team will inherit. If you already have a React frontend or hire React engineers, stay with Next.js. If you're running a marketing site with a small dev team, Nuxt has more built in and is often faster to maintain. I'll recommend based on your team, not my preference.
I've built in both. Next.js:HOUS, and years earlier a custom Shopify storefront in React and Next.js at Deloitte.
Nuxt: PS260, a New York post house (Nuxt with Storyblok), Canada Remembers Guide (Nuxt 3), and headless WordPress and Nuxt builds for agency clients at Funkhaus from 2020 to 2023.
I've built reel-first sites for PS260 in New York, Hudson Artists in Detroit and Nu Context. At PS260 and Hudson Artists the reels come straight from the studio's Simian library, so nobody uploads the same video twice.
Strada Investment Group opens on an aerial view of San Francisco, with its projects one click away. Burch Creative Capital leads with its own line, “Creativity is our capital”, and lets the portfolio speak for the firm.
The dashboards, Slackbots and automations your team wants but never gets budget for. AI has made small tools cheap to build, and I review the code so you can rely on them.
Prototyped in Cursor, Lovable or Bolt and starting to wobble? I'll audit the code and fix what's risky before paying customers find the gaps.
Most marketing sites land between $12k and $45k. Where yours lands depends on how complex it is, how many other tools it connects to, and how soon you need it.
After a free 30-minute call, you get a written scope within 48 hours, and a fixed price before any work starts. No hourly mystery bills.
If you need a simple template site on a small budget, I'm probably not the right person.
The person on our first call is the person who writes your code. There's no account manager in between, and nothing gets handed to a junior team.
No. PS260 is in New York, Strada in San Francisco and Hudson Artists in Detroit. We work over calls and preview links, wherever you are.
Both. I build from your designer's files, and for smaller projects I can design it myself. I'm comfortable in Figma but I'm an engineer first.
I offer monthly retainers for performance monitoring, security patching, content updates and continued feature work. Most clients move into a retainer after launch; some hand off to their internal team with documentation.
A headless rebuild of an LA architecture real-estate site on Next.js and Storyblok, migrating 373 articles and 42 listings from WordPress.
PS260, a New York editorial and post studio, started with a concept video. Now its reels play full-screen, and its producers update the site themselves.
Torment, an independent snowboard magazine, puts its newest video part up top like a magazine cover. Years of features are a search away.
Book a free 30-minute call and bring whatever you have. A Figma file, a Notion doc, or a complaint about your current stack is plenty. You'll leave with a recommended approach and a rough estimate.
