ProcessSeptember 3, 20265 min read

How I Actually Build and Ship Websites in 6–7 Days

Abby

Syed Abbas Ali (Abby)

Full Stack Developer · Delhi, India

5 min read

Every website starts with a clean architecture decision.

The first time a client asked me 'How fast can you build this?', I said 2 weeks. They looked disappointed. Their previous agency had quoted 4 months. That's when I realised the gap isn't technical — it's structural. Agencies are slow because of how they're built: account managers, design handoffs, approval chains, internal review cycles. None of that has anything to do with actually writing code.

I work solo. I talk directly to you. When you say 'change this button colour', it's done in 15 minutes, not next week after someone logs a ticket. That's where the 6–7 days comes from.

Day 1–2: I ask annoying questions before touching any code

Most developers want to jump straight into Figma or start typing. I've learned that's exactly the wrong move. The first thing I do is talk to the client — sometimes for two hours.

I want to know: Who is your actual customer? What do you want them to do on this website? What have you tried before that didn't work? What do your competitors do that you hate?

This phase saves me from building the wrong thing beautifully. I'd rather spend 4 hours in discovery than 3 days rebuilding a homepage because the CTA was wrong.

At the end of Day 2, you have a sitemap, a wireframe with content hierarchy, and a clear agreement on what we're building. No surprises after this point.

I use FigJam for wireframes. It's messy, collaborative, and doesn't pretend to be a finished design — which is exactly the point at this stage.

Day 3–4: Building the thing

This is where I go quiet. Notifications off, editor open, coffee ready.

I use Next.js as my base because it handles routing, SSR, image optimisation, and API routes out of the box. No wiring up a dozen libraries to do what Next.js does natively. I write in TypeScript — not because it's trendy, but because catching a type error at compile time is a lot better than debugging undefined is not a function at 11pm.

Design goes straight into Tailwind. No CSS files, no fighting specificity. If a client shows me a reference site they like, I can have a matching visual direction running in under an hour.

By end of Day 4, you have a working frontend. Navigable, responsive, and looking like the actual finished thing — not a prototype.

Mainframe SaaS project screenshot — clean dark UI with smooth transitions
Mainframe: Built in 5 days. Shipped to production on Day 6.

Day 5–6: The boring stuff that actually matters

Contact forms, email integrations, CMS hookup if needed, speed audits, cross-browser checks, mobile testing on real devices (not just Chrome DevTools). This is the part most agencies skip or rush — and it's where sites break in production.

I run Lighthouse on every page. The target is above 90 on performance and 100 on accessibility and SEO. If something scores badly, I fix it before handover.

SSL setup, environment variables, domain configuration, robots.txt, sitemap — all done before the final call.

"I once found a client's previous website was loading a 14MB uncompressed hero image. Their mobile load time was 11 seconds. We got it down to 1.2s. That one change alone was worth the entire project fee."

Real example, 2025

Day 7: Handover without the mystery

The handover call is usually 30–45 minutes. I walk through every page, explain every decision, and answer every question. If you want to be able to update your own content, I show you how. If you want me to keep maintaining it, we set that up too.

I send a short document after: what's live, what credentials are where, what to watch for, and how to reach me if something breaks.

That's it. No surprise invoices. No 'oh we forgot to include X' after launch.

Final thought

I'm not claiming I'm faster because I'm some kind of 10x developer. I'm faster because I cut out everything that slows projects down without actually improving them. If you need a website for your business and you don't want to wait 3 months or deal with 5 different people, let's talk. I'll tell you honestly whether I can help.

Tagged:#Process#React#Next.js#Freelance
Abby — Full Stack Developer
Written by

Syed Abbas Ali(Abby)

Full Stack Developer & Web Architect based in Delhi, India. 3+ years building websites and web applications for founders, startups, and growing businesses. I handle everything: design, frontend, backend, and deployment.

Start a project

READY TO BUILD SOMETHING?

Full stack engineering, clean code, 6–7 day delivery. Let's talk.