ABOUT
Web designer and developer. I do both jobs on purpose.
I'm Muhammad Zohaib. I design websites and I build them, which is a slightly unusual combination — most people do one or the other and hand the file across.
Doing both changes the work. When you know you'll be coding the thing yourself, you stop drawing layouts that look good in a static frame and fall apart in a real browser. And when you've sat in the conversation about what the business is actually trying to win, you make different decisions about what deserves the first screen.
I work on my own, remotely, with clients in the US, the UK and elsewhere. That keeps the line between you and the work short: you explain the problem to me directly, and I’m the one solving it.
01
Getting a website to fine is quick. Most of the actual work happens after that — the spacing that's two pixels out, the heading that reads awkwardly on a narrow phone, the button that's a shade too quiet. Nobody notices any of it individually. Everybody notices the result.
02
An impressive-looking site that leaves people confused has failed at the only job that mattered. Structure first, then visual direction on top of it. Never the other way round.
03
A site that takes four seconds to appear has already lost people who will never know what they missed. Performance gets considered from the first sketch, not patched the day before launch.
04
If a deadline is unrealistic, if a budget doesn't match the scope, if an idea won't work — you'll hear it on day one rather than in the final week.
HOW I WORK
Most of the risk in a website project comes from ambiguity — nobody's quite sure what's being built, what it costs, or when it's finished. This is how that gets removed.
A call, or a long message thread if you'd rather write. I want to know what the business does, who you're trying to reach, what isn't working now, and what you'd count as this having gone well. If I'm not the right person for it, I'll tell you here rather than halfway through.
Before any visual work: which pages exist, what goes on each, and in what order. You approve a written outline and a fixed price. Nothing after this point turns up as a surprise on an invoice.
I design the key pages first — usually the homepage, one service or product page, and the contact path — so we settle the direction before it multiplies across the whole site. Two rounds of revisions are included, and they’re where the design actually gets good.
The approved design becomes a working website: hand-built front-end, responsive across the sizes people genuinely use, tested on real phones. You get a staging link early and can watch it come together instead of waiting for a reveal.
Speed and accessibility checks, search setup and metadata, every form tested end to end, then it goes live. You get a short walkthrough so you're not messaging me every time a price changes.
A full website usually runs seven to ten days from the day scope is approved. A landing page is closer to three or four. You'll have real dates before you commit to anything.