Service
Website design packages priced as a project
Five, fifteen or thirty-plus pages at a fixed one-off price from $1,200, built as fast static sites, with a Core Web Vitals pass required at handover rather than promised.
In one line
A website design package is a fixed-scope build sold at a single project price. Here that means a stated page count, a mobile-first static build, a contact form, and a performance standard the site has to meet before it is handed over.
Website design packages and what each tier costs
Starter
Up to 5 pages
one-off
- 5 pages
- Mobile-first build
- Contact form
- Core Web Vitals pass at handover
- Not included: E-commerce
- Not included: Custom integrations
Growth
Up to 15 pages
one-off
- 15 pages
- Everything in Starter
- Blog set-up
- Basic schema markup
- Analytics configured
- Not included: E-commerce
Scale
30+ pages or e-commerce
one-off
- 30+ pages
- Everything in Growth
- E-commerce or custom integration
- Content migration
These website design packages are billed at the price shown, with no scoping call in the way. Starter ships in 2 weeks. Scale in 6 to 8 weeks. Every tier is billed once, as a project, and the scope is fixed by a brief you agree before anything is invoiced.
This is the one search on our list where competitors do publish prices, mostly from small studios. What they rarely publish is the page count each price covers or what happens when the build runs long.
Everything each tier includes and excludes
The same list that drives the price cards, laid out so the tiers can be read against each other. Exclusions are printed because an unstated exclusion is what turns a good month into an argument.
Starter
Up to 5 pages
Included
- 5 pages
- Mobile-first build
- Contact form
- Core Web Vitals pass at handover
Not included
- E-commerce
- Custom integrations
Growth
Up to 15 pages
Included
- 15 pages
- Everything in Starter
- Blog set-up
- Basic schema markup
- Analytics configured
Not included
- E-commerce
Scale
30+ pages or e-commerce
Included
- 30+ pages
- Everything in Growth
- E-commerce or custom integration
- Content migration
Which tier you actually need
Tiers are separated by page count, and the page count is the scope boundary. A fixed price only stays honest when both sides know what the number covers.
All three website design packages run the same process and the same reporting. What changes between them is volume.
Starter
A business that needs a credible, fast site quickly: home, services, about, contact, and one more.
You are on this tier when: You can describe the whole site in five URLs without straining.
Growth
A site with several service lines plus a blog, where schema and analytics need setting up properly rather than later.
You are on this tier when: You need somewhere to publish, and more than one service deserves its own page.
Scale
Thirty pages or more, e-commerce, or a build with content to migrate from an existing site.
You are on this tier when: You are selling online, or moving a site with history that must not lose its URLs.
Handover has a pass mark
Short answer
Every build has to pass Core Web Vitals at handover. That is a measurable gate rather than a promise about speed, and it is checked on the live site with Google’s own tooling before the project is closed.
Performance claims are usually made in adjectives on this search. A pass or fail against a published Google threshold is the only version of that claim a buyer can check themselves.
If the site does not pass at handover, the fix is inside the project price rather than a change request.
What you receive at handover
A build is finished when you own everything needed to run it without us.
- The site, live on your own hosting and your own domain
- The full source repository, yours to keep
- A Core Web Vitals pass, checked on the live site
- From Growth upward, blog set-up, basic schema and analytics configured
What a website build actually contains
Builds are the one thing here priced as a project rather than a month, so the timeline is the scope. Step through it before reading the tiers.
What a website build actually contains
Week 1 — Sitemap and content map. The page list is agreed before any design happens, with the purpose of each page written next to it. Pages added after this point are a change to the project, priced as one.
Weeks 1-2 — Design of the key templates. The home page and one interior template are designed first, because every other page inherits from them. Approval of those two is what unblocks the rest of the build.
Starter: 2 weeks — Build and content load. Pages are built and the agreed content is loaded. Starter ships in two weeks; larger builds run six to eight weeks, and the difference is page count, not care.
Before launch — Handover. You receive the site, its accounts, and its source. Nothing is held hostage on our side, which is the point of stating it here rather than in a contract nobody reads.
Select any milestone to read what is produced at it. Every date is a published commitment from this page, not an estimate of results.
What the price buys at each tier
Each build is invoiced once, at the price shown, against a page list agreed before design starts.
Page count sets the price and the calendar together. The build standard, responsive layouts, real content structure, handover of everything, does not change between tiers.
Prices resolve from the same source as the cards above. Switch metric to compare cost against volume.
How a month actually runs
Order, brief, production, delivery, report. The same four steps every month, so a second month can be compared against a first.
- 1
Week 1
Brief and structure
Page list, content sources, and what each page has to do. The page count in the tier is the scope boundary.
- 2
Weeks 2 to 4
Build
Mobile-first build against the agreed structure. Starter ships in about two weeks.
- 3
Before handover
Performance gate
Core Web Vitals checked on the live site. Failures are fixed inside the project price.
- 4
Handover
Keys and repository
Live on your hosting, source repository transferred, and a walkthrough of how to edit it.
What handover includes
Handover is a transfer of control rather than a launch announcement.
There is no mandatory care plan afterwards. The site keeps running whether or not you buy anything else from us.
- The live site on your own hosting account and your own domain
- The source repository, transferred to you
- A Core Web Vitals check on the live site, with the result
- A walkthrough of how to edit content without a developer
Why the builds are static
Short answer
Sites are built as static pages on Astro, which means the browser receives finished HTML rather than assembling it. That removes a whole category of speed problem and a whole category of security problem at the same time.
The practical consequence for you is a site that stays fast on a cheap host and has no database to be compromised or to fall over under traffic.
The trade is that heavily interactive applications are not what this stack is for, and we will say so rather than force it.
What happens after the site ships
There is no mandatory care plan. The repository is yours, the hosting account is yours, and the site will keep running untouched.
If you want ongoing search or content work afterwards, those are the separately priced retainers on this site rather than a bundled monthly fee attached to the build.
How this differs from the usual arrangement
Neither column is a verdict on quality. The left is how this service is normally sold, taken from the pages ranking beside this one.
A typical web design quote
- Price
- Custom quote after discovery
- Scope boundary
- "A few pages"
- Performance
- Described as fast
- Ownership
- Sometimes hosted on the agency’s platform
- Billing
- Monthly care plan bundled in
The Super Panel
- Price
- Published, by page count
- Scope boundary
- A stated page count per tier
- Performance
- Core Web Vitals pass at handover
- Ownership
- Your hosting, your repository
- Billing
- One-off project price
The three things buyers ask before ordering
Fixed-price builds fail in predictable ways, and these are the three that cause it.
What happens if the project runs long?
If the delay is ours, the price does not change. If the scope grows beyond the tier’s page count, the extra pages are priced per page rather than absorbed silently, because silent absorption is how quality quietly drops.
Who writes the copy?
You supply it, or you buy the content service separately. A build price that quietly includes copywriting is the single most common cause of a stalled project, because the writing becomes nobody’s deadline.
Why static rather than WordPress?
Static builds are faster on cheap hosting, have no database to compromise, and do not need monthly plugin maintenance. The trade is that heavily interactive applications are not what the stack is for, and we will say so rather than force it.
What this pairs with
A build is the natural moment to fix technical SEO, because the structure, schema and speed are being decided anyway rather than retrofitted.
Paid ads sit badly on a slow site: the landing page decides the conversion rate and the quality score, so the build usually comes first when both are on the table.
A build is the cheapest moment to get technical SEO right, which is why it pairs with the SEO package.
When a package build is the wrong choice
Short answer
A fixed-price package is a poor fit for a site whose page count is unknown, for e-commerce below the Scale tier, or for a project that needs custom integrations. In those cases a fixed price would be fiction and would fail you halfway through.
- You need e-commerce and are looking at Starter or Growth. That starts at Scale.
- The page count is genuinely unknown. A fixed scope cannot price an unknown.
- You need custom integrations with internal systems. Excluded below Scale.
- You want ongoing design changes after launch. This is a project, not a retainer.
Questions before you order
How much do website design packages cost?
Starter is $1,200, Growth is $2,800 and Scale is $5,500, each a one-off project price. Website builds are the one service here that is not a monthly retainer.
How long does a build take?
Starter ships in about two weeks. Scale runs six to eight weeks. The clock starts when the content and the page list are agreed, not when the deposit lands.
What counts as a page?
A page is a unique URL with its own layout or content. Repeating a layout with different text still counts, because the content and testing work is per page.
Do I own the site?
Yes. It goes live on your hosting and your domain, and the source repository is transferred to you at handover.
Can you do e-commerce?
At the Scale tier. E-commerce is excluded at Starter and Growth, because the testing and integration work does not fit those prices honestly.
Who writes the content?
You supply it, or you buy the content writing service separately. A build price that quietly includes copywriting is how fixed-price projects overrun.
What if the site fails Core Web Vitals?
It is fixed before handover, inside the project price. That is the point of making it a gate rather than a goal.
Do you offer hosting?
No. The site is deployed to your own hosting account so nothing about it depends on us continuing to exist.
Can I add pages later?
Yes, priced per page against the same logic as the tier you bought. The stack makes adding a page cheap.
Is a redesign of an existing site the same price?
Usually, when the page count is comparable. Content migration is included at Scale and quoted separately below that.
Sources cited on this page
- Google’s Core Web Vitals thresholds – Cited for the handover gate.
- PageSpeed Insights – The tool used to check the gate, so a buyer can repeat the test.
Start Website Builds from $1,200
Pick a tier and send the order. You get a brief form and a start date within one business day, and nothing is charged until that brief is agreed.
Entry point $300/mo. Cancel any time. No long contracts.
Still deciding?
Read how the process runs end to end: order, brief, production, delivery, report.
How it works