Three days, not six weeks
Six weeks is how long the meetings take. The work is faster than that, and a modern toolchain made it faster again. Here is the whole of it, hour by hour.
Most website projects are not slow because the work is hard. They are slow because the work waits: for a kickoff, for a mood board, for a revision round, for the one person who has not replied. We took the waiting out and left the work in.
What follows is the whole of it. Three business days, from the call to your domain.
NewWebsite.builders ships a finished website in 3 business days. Day 1 is a 30 minute call that settles the pages, the words, the look and a fixed price. Day 2 is the build, watched live on a preview link. Day 3 is one review pass and the launch, with the source code and the hosting keys handed over in your name.
Day 1: one call, one direction
Thirty minutes on a call settles four things: which pages the site needs, what each of them has to say, how it should look, and what it costs. You leave with that written down and a price that does not move.
The reason it fits in half an hour is that we do not ask you to imagine anything. You describe the business, we ask about the visitor you want and what you need them to do, and you get a direction back rather than three to choose between. One direction, argued for, is faster to correct than three to compare.
- The pages. Usually 1 for a landing page and 5 to 10 for a full site, named and ordered before anything is built.
- The words. Whatever you already have, plus what we write from the call. You are never asked to fill in a blank page.
- The look. Type, colour and the feel of the thing, agreed in words rather than in a slide deck.
- The price. One number, on the same call, in writing the same day.
The one thing that does move the date is material. If the photographs and the logo arrive on day 3, the site launches when they do. That is the only variable, and it is on your side of the line, so it is worth knowing about on day 1. There is a short list of what to have ready in what to prepare before a website build.
Day 2: the build, in daylight
Day 2 is the actual work. Components go in one at a time, and you get a preview link on the first morning that fills in while you watch. Nothing is hidden until a reveal, because a reveal is where four weeks of misunderstanding usually surfaces.
Every component is written for your site rather than picked from a theme. That is slower per component than dragging a block into place, and much faster over a whole site, because nothing has to be undone afterwards to make it fit.
Your words are modelled into the CMS as the pages go in, so what you see on the preview is the same content you will be editing later. There is no separate step where a finished design gets retro-fitted into a content system and quietly loses a third of its layout.
Two things are true of the build that are worth stating plainly. There is 0 page builder runtime shipped to your visitors, and there are 0 themes involved. The page a visitor downloads contains your site and nothing else.
Day 3: review, launch, handover
Day 3 opens with your review pass. You go through the preview and write down what is wrong. We work through that list together, in one sitting rather than across a week of email.
Then the site goes live on your domain, on an edge network, with SSL. The repository, the hosting keys and the CMS login all land in your name the same day. Not a copy of them, and not an account we hold on your behalf: the accounts are yours, and if you never speak to us again the site keeps running.
After launch you have 14 days of fixes included. Anything broken, anything wrong, anything that reads badly. It is included because a site that ships in 3 days should be corrected in the days after it, not held hostage for a support retainer.
What three days actually means
Three business days is the build window, and it starts when the scope is signed and the material is in. It is not three days from the first email, and it is not three days of you waiting by a phone.
In practice the calendar looks like this. You book a call. The scope and the price come back the same day. You say yes and send the material. The three days start on the next working morning, and you spend about an hour of your own time inside them: the call on day 1, the review on day 3.
Three days covers a landing page or a multi-page site. Anything with a login, a checkout or a database behind it is a custom build, scoped on the same call and quoted in writing within 24 hours. It does not ship in 3 days, and we say so before you pay rather than after.
Why it is not slower
The honest answer is that most of a six week project is not build time. It is the gaps: the wait for feedback, the wait for a second opinion, the wait for the revision that arrives after the developer has moved on to something else and has to load the whole thing back into their head.
Compressing the calendar removes the gaps and the reloading with them. The work is continuous, it is held in one head, and it is finished while it is still fresh. That is why the result is better rather than rougher, which is the part people expect to be a trade.
The two clients who have said this out loud put it more usefully than we can. Hans at 't Kippegie: quick, and good, a combination he had not seen before. Melvin at GetRanked.io liked the design guide enough that his team restyled their own product to match it.