Short answer
A website built with AI tooling takes 3–6 weeks, the range our own website service quotes. Week one sets positioning and the sitemap, weeks two and three the design system and the first pages, weeks three to five the remaining pages and content, and the final week measurement and handover.
The timeline decides whether a project happens more often than the price does. A campaign, a trade show or a funding round sets the date, and the vendor who can answer week by week is the one you can plan around.
Week 1: positioning, structure and sitemap
The first week settles what the site says and who it says it to. We go through the offer, the three or four questions a buyer asks before getting in touch, and set a sitemap where every page has a job. The week ends with an approved structure and a list of the content still missing.
Weeks 2–3: the design system and the first pages
The design system is built before the pages, because it is what makes the rest fast. Color, typography, spacing and components are defined in one place, and the home page plus one subpage go up first. You see the real site in a browser during week two, in the real typeface and on a real phone.
Weeks 3–5: the remaining pages and the content
Once the system exists the pages go quickly, and the weight shifts to words. Service pages, pricing, frequently asked questions and the articles meant to carry organic traffic come out of your own language: interviews, sales calls and old proposals. You review, we edit.
The final week: measurement, handover and launch
The last week is technical and holds no design decisions. Analytics goes in, speed is checked against a budget, structured data and the sitemap are generated, hreflang is verified, and old URLs are redirected. You get the repository, the documentation and a walkthrough of how to add content yourself.
What decides between three weeks and six
Five things, and four of them sit on your side. Those four are also the ones you can prepare before the project starts.
- Decision speed: a check-in that slips a week moves the launch a week
- How finished the content is on the day the project starts
- The number of integrations with systems you already run
- Whether the site ships in one language or several
- How much old content has to be migrated and redirected
A project with one decision-maker, finished copy and no integrations lands at the bottom of the range. What the build costs is on the pricing page; when you compare quotes, the timeline is the line item easiest to check. Ask for it week by week, and ask what happens the week something runs late.
Common questions
- What do we need in place before the project starts?
- A named decision-maker, a rough list of the pages you think you need, access to the domain and analytics, and whatever copy and imagery already exists. The rest takes shape during week one.
- How much of our time does the project take?
- 3–5 hours a week: one check-in, reviewing drafts, and the decisions only you can make. The week the copy is reviewed is the heaviest one for you.
- Is it faster if we skip the design system?
- No. The design system is what makes the pages after it fast, because every new page is assembled from parts already built and already reviewed. A project that skips it loses pace from week three.
- What happens if we miss a deadline on our side?
- The timeline moves by the same amount, and we say so the week it happens. That lets you choose between moving the launch and trimming the scope while the choice is still cheap.
- Can we launch in stages?
- Yes. A first version with the home page, services and contact can go live after three weeks, while articles and the knowledge base fill in after launch.
- What do we get delivered when the project ends?
- The repository with all code and content, the documentation, and a walkthrough of how to run the site. The rights are yours from day one, so the handover covers something you already own.
Tell us what you want to build
Thirty minutes, free of charge, and a straight answer on whether we are the right studio for it.