The sessions / Launch & Costs

AI can produce a first version in minutes, but the first version is not the finished work. Time is spent deciding, checking and refining; money may go on the AI tool, a domain and any services the site needs. A small static site can be inexpensive. Complexity and responsibility are what raise the bill.

6 min read

Read as: HTML / Markdown

How long does it take?

Long enough to reach the level of confidence the project needs.

A model may create the first visible page in minutes. A focused one-page site about something you know well may become useful within a few hours. Making it coherent, accessible, mobile-friendly, checked and ready to put your name on may take several sessions across several days.

Those are not promises. They are different stopping points.

There are really three clocks:

1. Construction time: how long the model takes to produce and change the code
2. Decision time: how long you take to choose the words, structure, images and design
3. Assurance time: how long it takes to check that the result is accurate, usable and safe to publish

AI compresses the first clock most dramatically. The second still contains your taste. The third grows with consequence. A personal one-page site can be checked quickly because you can see nearly all of it. A service involving private data, logins or payments needs a different team and a different timetable.

The purpose of this course is not to promise that everybody can produce a website in twenty-one days. It is to give you the habits that make your time count when you decide to begin.

What does it cost to start?

For the kind of first project taught here, the technical bill can be small.

• The AI tool: a free allowance may be enough to explore. Regular building often needs a paid plan, and heavier use may need a higher one.
• The code repository: GitHub offers a free plan that is sufficient for a small personal repository.
• The hosting: a static site can sit within a host’s free tier. This site uses Cloudflare Pages, where static asset requests are free; limits and paid features still apply.
• The address: you can begin on the host’s supplied address for no extra charge. A custom domain is normally an annual cost, and the price depends on the name and registrar.
• Optional services: email, forms, analytics, fonts, images, databases, booking systems and other additions may have their own free limits or charges.

So it is possible to learn and publish a simple static page without a large infrastructure bill. It is not honest to turn that into “websites are free”. Prices change, free tiers have limits, and the project may eventually need things the first version deliberately leaves out.

What is the cost people forget?

Time spent checking.

The model can produce ten alternatives before you could have built one by hand. You still have to read them. Fast generation can even increase the amount of judgement required because it makes so many plausible options cheap to create.

There is also the cost of maintenance: renewing the domain, keeping accounts recoverable, reviewing dependency updates, checking links and making sure the site still says what you mean. A small static site keeps that work modest. Every connected service adds another account, another set of terms and another thing that can change.

And there is the cost of expertise. If a project reaches the boundary described in Rung 11 (logins, private data, payments or material consequences), budget for suitably experienced technical, security, privacy or legal review. AI can reduce implementation time. It does not make those responsibilities disappear.

How do I stop the cost from running away?

Decide the ceiling before you start.

For a first project, write down:

• The smallest useful version
• The accounts or subscriptions you are willing to pay for
• Which costs are monthly and which are annual
• Which free tiers you are relying on
• What would make you stop, simplify or ask for help
• What ongoing maintenance the project creates

Then ask the model to identify every external service before adding it. “Free to install” is not the same as free to operate, and a cheap tool that traps your data or requires a difficult migration may be expensive later.

Keep the first version static where you can. Use one repository, one host and as few connected services as the job genuinely needs. Simplicity is not merely easier to build; it is easier to price, verify, move and maintain.

What should I budget for my first site?

Budget in layers rather than guessing one total.

The rehearsal can cost nothing beyond tools you already have: build locally, use fictional or non-sensitive material, and do not buy a domain yet.

The smallest owned public version may add a month of the AI plan you choose and an annual domain, while the repository and static hosting remain within free allowances. That is enough for many portfolios, explainers and resource pages.

A professional or consequential version should have a separate assurance budget. The amount depends on what it does and who could be harmed if it fails. Ask for a written estimate with assumptions, exclusions, ongoing charges and the point at which further work needs approval.

Do not compare the price of a generated first draft with the price of a finished, reviewed and supported service. They are not the same product.

Where can I see this on the site?

The colophon names the main tools and services behind this site, so the apparent simplicity of a page does not hide its dependencies. The lesson on getting a site online explains the repository, host and push; the lesson on updating it once live explains the continuing work after the first publish.

Together they show where the time and money go: not only into producing files, but into owning the accounts, checking the result and maintaining the route by which changes reach the public.

So, how long does it take, and what does it cost?

A first page may take minutes. A small site you are prepared to stand behind usually takes hours or days of decisions, checks and refinement. A simple static project can begin with free repository and hosting tiers, plus whatever you choose to spend on an AI plan and a domain. More services, more data and more consequence add both cost and assurance time.

AI makes building cheaper and faster. It does not make judgement, accountability or maintenance optional. The honest budget includes all three.

The facts on this page that mirror the outside world were last checked against their sources on 9 August 2026; they are re-checked at every review.