What a Business Website Build Actually Includes (And What It Doesn’t)

I’d rather explain exactly what my Business Website build covers than let a quote sit as an unexplained number, and I give you the figure on a scope call. Most pricing pages either hide the breakdown behind "get a quote," or pad the number until it feels arbitrary. Neither helps you decide whether it’s the right fit.

Where the budget goes

• Design time: a layout and visual direction built around your actual brand, not a theme with your logo dropped in.
• The build itself: a responsive, custom-coded site, not a page-builder template with sections dragged into place.
• Hosting, domain connection, and SSL set up correctly the first time, so the site is live and secure on launch day.
• An SEO-ready structure, proper headings, metadata, and page speed basics, baked in rather than bolted on afterward.
• A testing pass across real devices and browsers before anything goes live.
• 30 days of post-launch support to catch anything that only shows up once real visitors start using the site.

What it doesn’t include

This is the part most quotes leave out, and it’s the part that actually matters for deciding whether the build covers what you need:

• Copywriting from scratch. I’ll shape and structure the words you give me; writing all the sales copy for you is a separate conversation.
• Professional photography or custom illustration. Stock imagery, yes. A brand shoot, no.
• E-commerce or payment integration. That’s the E-Commerce Launch package, because it’s a genuinely different build.
• Ongoing hosting and maintenance past the 30-day window. That’s what the Store Care Plan is for, and it’s optional, not forced.
• Paid ad management. I’ll build a site that converts; running Google or Meta ad campaigns is a different skill and a different invoice.

Why "affordable" alternatives often cost more later

The cheapest option is rarely a custom-built site; it’s a bargain template from a marketplace, self-assembled over a weekend. That can be the right call for a very early-stage idea. Where it goes wrong is when that template becomes the permanent face of a real, revenue-generating business: nobody owns the decisions behind it, updates break things nobody understands, and the eventual rebuild costs more than starting properly would have.

If a custom build sounds like more than a template but the project genuinely needs custom workflows, integrations, or an online store from day one, that’s worth a scope call before committing to any package, mine or anyone else’s.