miz

Service 02

Website Building

A fast, clear site you can update yourselves.

scope itbuild itlaunch it

The brief I hear most from small businesses is simple. Make it fast, make it clear, and let us update it ourselves. That’s the site I build.

Static first, when it fits

When your content mostly holds still, a static site wins. Quick to load, cheap to host, very little to break or patch. When your team updates content daily, WordPress fits better. When you sell online, it’s Shopify. The platform is a scoping decision, and I’ll recommend one and tell you why before you commit to anything.

Some of this you can check yourself. I’ve built WordPress sites for Mateenbar in the US and Australia, RiceFX, dgshsourcing.com, and gobasports.com, and client sites across North America and Australia have landed on time and on budget. The site you’re reading now is a static build with no tracking scripts, so view source if you’re curious.

How a build runs

Scope comes first. We agree on pages, content, platform, and price before design starts. You approve the design before I build, because changes cost the least at that stage. The build itself is plain and careful. Semantic HTML, speed tested on real phones, and the SEO basics (titles, metadata, sitemaps, redirects) done properly.

Launch day covers DNS, redirects, and a final performance check. Then the handover, which I treat as part of the job. Your content ends up in a Git repo or a CMS your team can edit, and before I step away you’ll make a change yourself with me on the call.

What it costs to keep

A static site has almost nothing to maintain, and hosting runs from free to cheap. WordPress and Shopify carry their own hosting and app costs, which I lay out in the scope so nothing surprises you later.

Either way, you own it all. Domain, hosting, code, and content sit in your accounts. If you never call me again, the site keeps working.

How it runs

  1. Scope

    We agree on pages, content, platform, and price before anything gets designed.

  2. Design

    You see and approve the design first, while changes are still cheap to make.

  3. Build

    I build on whichever platform we scoped, static, WordPress, or Shopify, and test it on real phones as I go.

  4. Launch

    DNS, redirects, and a final performance check on launch day.

  5. Handover

    Content lives in a Git repo or a CMS your team can edit, and I show you how.

Numbers I can back up

Questions I get

Static site, WordPress, or Shopify?

It depends on the job. If your content mostly holds still, static wins on speed, hosting cost, and upkeep. If your team updates content daily, WordPress fits. If you sell online, Shopify. The scope spells out which one and why.

Can we update the site ourselves?

Yes, that's the point of the handover. Content lives in a Git repo or a CMS, whichever suits your team, and we make a change together before I step away.

Who owns the site?

You do. Domain, hosting, code, and content sit in accounts under your name. Any competent developer can pick it up later, and nothing stops working if we part ways.

How long does a build take?

It depends on scope, which is why scoping comes first. Small sites move quickly and bigger builds take longer, and you'll have a real timeline in writing before we start.

Do you write the copy?

I'll shape the structure and headings and edit what you have so it reads clearly. If you need copy written from scratch, we scope that in up front.

All services