Website development with Next.js
I build marketing and product sites as a senior engineer - Next.js by default, pixel-accurate from Figma, fast enough that Core Web Vitals are not a later project. Direct contractor, not an agency. 11+ years in tech.
- Next.js sites - landing, corporate, catalog - with a stack that matches how you will publish
- Figma to production: spacing, type, motion. Not a theme with the logo swapped
- Custom admin control panel & CMS: staff can edit services, prices, and text without a developer
- Performance as a requirement: images, fonts, splitting, not a plugin after launch
- You work with me. Scope stays on the thread, not in a 40-page deck
Featured Case Study
Corporate website and custom admin dashboard for a medical & cosmetology clinic. The custom CMS allows salon staff to update services, price lists, and site content independently.
How a site engagement runs
01
Brief or Figma. We name the pages, the languages, and what “done” means.
02
Structure first: IA, components, content model. Then the first template in production.
03
Iterate on real URLs. QA, redirects, analytics, deploy. Then a long-term retainer if you want me to stay.
Next.js when you want speed, design control, and a stack I can own end to end. A CMS when editors must publish without a deploy. I pick from the job, not from a trend.
Yes - CSS and JS motion that does not fight Core Web Vitals. I will not drop a 4 MB Lottie on the first paint unless the brand actually needs it.
Send the constraint and the first action. I reply with the smallest version I would ship - and what I would refuse.
Start a conversationAlso shipping