How I Rebuilt My Site in 5 Hours with AI
The exact process I followed. No fluff.
Why I needed to rebuild it
My old site wasn't converting. It looked generic, the copy was weak, and I wasn't proud to share it.
I didn't want to spend weeks with a designer or a contractor. I wanted to ship something I was proud of, fast.
So I used Claude Code, my design skills, and the workflow below to rebuild it in one afternoon.
What I was going for:
- •Clean, premium visual design that felt like me
- •Copy that actually explains what Oktya does
- •Fast load times, mobile-first
- •Deployed and live by end of day
AI doesn't replace design taste. It executes your taste faster. You still need to know what good looks like.
Start with a design brief, not code
Before touching a single component, I wrote a detailed brief for Claude. Colors, typography, vibe, references.
I want to redesign my website. Dark background, purple accent (#56429A), clean minimal layout.
Inspiration: Linear, Resend, Vercel. Mobile-first.
Tone: technical but approachable. Not corporate.
Key sections: hero, how it works, results, CTA.
Claude returned a full component structure with Tailwind classes. I reviewed it, adjusted a few things, and we were off.
Why this works
Claude is a great executor. But it needs direction. The more specific your brief, the less iteration you need.
Don't start with 'build me a website.' You'll get something generic. Start with a brief.
Audit the current site first
Before designing anything new, I had Claude audit what I already had.
I fed it the current HTML/components and asked for a brutal honest review.
Review this website code and tell me:
1. What's visually weak
2. What's hurting conversion
3. What should be cut
Be direct. I can handle it.
What it found:
- 1Weak hero. The headline was generic and didn't explain the value proposition clearly.
- 2Too much text. Paragraphs that could be replaced with one sharp sentence or a visual.
- 3No social proof. No client names, no results, no proof that this actually works.
The audit is what separates a redesign from a re-skin. Without it, you're just making the same mistakes look different.
Build section by section, not all at once
I didn't try to build the whole site in one prompt. I worked section by section, reviewing each one before moving to the next.
- Hour 1Brief + audit + hero section
- Hour 2How it works + results section
- Hour 3Pricing + FAQ + footer
- Hour 4Mobile review + fixes
- Hour 5Deploy to Vercel + domain + final QA
What I learned
Section-by-section keeps context tight and makes it easier to catch problems before they compound.
Want to do this for your project?
I help founders and small teams implement AI in their actual operations.
Built with Claude Code · 2026