Answer in brief
A development quote rarely explains what the work is made of. This walks the ten stages of a build, from the edges of the project to the handover of access, and names who closes each one: the supplier or you.
The short answer: what a website build actually contains: A website build breaks into ten stages, and every stage…
Website development is not one job. It is a chain of them: scope, structure, design, front-end build, data wiring, integrations, testing, deployment and support. A quote bills you for a particular selection of those links, rather than for the whole chain.
The useful way to read a proposal is as a list of stages with an owner written beside each one. Wherever no owner is named, the work quietly stays with you, and it tends to surface a week before launch, when changing anything costs more.
VITON13 sells development as five packages, each covering a different span of that chain. The Site Fix Pack costs $70: up to five agreed fixes with a mobile and desktop check and a before and after list at handover, in 1-2 working days, with 1 round of revisions.
The rest of this article walks the stages in order. Each one ends with a question worth putting to a supplier before you sign, because after signing the same question turns into a change request with its own price attached.
Stage 1: scope, goals and the edges of the project
The first stage answers a single question: what counts as a finished website. Goals, the page list, the languages, form requirements and a separate list of what falls outside the project all get fixed here. Without that edge, an argument about extra work is a matter of time.
Ownership is split. The business brings goals, its offer, legal requirements and honest dates. The supplier turns that into a volume of work, names the constraints and says plainly which items have to move outside the first launch.
A quote carrying one line that reads website and a number, with no page list and no languages, has skipped this stage. It gives you nothing to check the agreement against, which is exactly what a quote exists to provide.
Ask it this way: what do you treat as inputs from our side, and by which date do you need them? Without an answer, the project calendar rests on assumptions, and assumptions do not hold a delivery date.
Stage 2: site structure and the page inventory
Structure is the page list, how the pages link and how many templates they require. Ten pages on one template and ten pages on ten templates are different volumes of work, although both occupy the same line in a brief.
This is also where you decide which pages are generated from data and which are assembled by hand. A catalogue, a journal and a services list normally take one template each; an about page is almost always built on its own.
The supplier owns proposing the structure and showing how many templates it demands. You own confirming that every section you need is on the list, including legal pages, contact routes and anything your sector requires you to publish.
Ask it this way: how many unique templates does this price cover, and what happens to the price when we add an eleventh page? The answer shows whether the volume was estimated or the number was simply chosen.
Stage 3: interface design and the states nobody draws
Design inside development is more than appearance. It is layouts at several screen widths, menu behaviour, button states, what a form looks like when validation fails, and what a page shows when it holds no data yet.
Those states rarely reach the mockups and always reach the build. When nobody draws them, a developer invents them, and reworking that invention consumes the revision rounds your package includes rather than the ones you had planned for.
Launch Site costs $380 and covers a responsive build, core CMS or data wiring and deployment setup, in 3-5 working days, with 2 rounds of revisions before launch. Content and translations are supplied by the client, so that boundary is explicit from the outset.
Ask it this way: are error, empty and loading states part of the design work? Settling that now is easier than settling it at acceptance, when a form submits successfully and the visitor sees nothing confirming it.
Stage 4: copy and translations sit with the client
Content is the part of a project where dates slide for reasons unrelated to engineering. A developer can build a page in a day, but cannot know your warranty, your return conditions or the words you use for your own services.
VITON13 does not write client copy and does not produce translations. The Launch Site terms state that content and translations are supplied by the client, and Launch Site Express carries the same exclusion alongside photography and ongoing support.
The practical move is to name one person inside your company who owns text, and to give that person a date. A single owner with a deadline moves faster than a shared understanding that something will be sent during the week.
Ask yourself: do we hold copy in every language the site will publish, or are we launching in one and adding the rest later? The second answer changes the structure and the amount of front-end work alike.
Stage 5: front-end build and responsive behaviour
Here the design becomes working pages: grids, type, components, behaviour on a phone and on a wide monitor. Markup semantics are decided here too, and semantics are what accessibility and assistive technology depend on later.
Responsive is not one mobile version. It is a set of decisions about what collapses, what reflows and what receives a scroll container of its own. Tables and long headings need a check to themselves, because they behave unlike body text.
The supplier owns delivering pages that have been checked on mobile and desktop. In the Site Fix Pack that check is written into the scope itself, along with the before and after list handed over at the close of the 1-2 working days.
Ask it this way: which devices and browsers do you check before handover? The list should be finite and written down, or acceptance becomes an open correspondence about somebody's older phone and never quite closes.
Stage 6: CMS and data wiring
Next comes the question of who changes content after launch, and how. The options are narrow: edit the code, edit records in an admin panel, or pull data from a system you already run. Each option carries a different cost.
Launch Site includes core CMS or data wiring, which means the editable parts get defined in advance. If a field was never created, it cannot be changed through the admin panel later, however obvious that field may look to you.
You own telling the supplier what you intend to edit and how often. Prices, campaign copy and team pages change regularly; legal pages almost never do. That difference is what the field set should be built around.
Ask it this way: which blocks can I edit without a developer after handover? The answer decides whether you will be writing to support six months from now because one phone number needs replacing across three pages.
Stage 7: integrations — forms, analytics, payments
Integrations are the points where your site meets somebody else's system: a form sends an enquiry, analytics records events, a payment provider takes money. Every connection is separate work with its own credentials and its own failure modes.
With a form, the interesting part is not that it submits. It is where the enquiry lands and who sees it. A form that writes only to the visitor's own browser looks entirely functional while losing every enquiry it receives.
Product Build costs $880 and covers feature delivery, state and route logic, testing and hardening, in 2-3 weeks, with 2 rounds of revisions per delivered feature. Native mobile apps and payment licensing are not included in that package.
Ask it this way: who provides access to the CRM, the mailbox and the payment provider, and by which date? An integration cannot be verified without working keys, and issuing keys often takes longer than the integration work itself.
Stage 8: performance and accessibility
Speed and accessibility are not cosmetics applied at the end. They are set during the build and the data wiring: image dimensions, how many font files load, how much script ships and in what order. Retrofitting them costs more.
There are public references that let you discuss this concretely instead of by feel. MDN Web Docs explains what web performance is made of, and the W3C publishes a quick reference for WCAG 2.2 listing success criteria and how each is met.
The supplier owns naming which criteria the handover meets. You own not arriving the evening before launch with a forty megabyte video, and not requesting six font weights for a page that carries three levels of heading.
Ask it this way: which accessibility requirements do you cover, and how is that verified? A promise to build to standards, with no criterion referenced, commits nobody to anything and leaves an acceptance review with nothing to test.
Stage 9: testing and hardening
Testing answers what happens when things go sideways: a visitor submits a form twice, the network drops mid-request, a field receives four hundred pasted characters, an external service stops responding during checkout.
Product Build names testing and hardening as part of what is delivered. That is what separates a product build from a brochure site: a product has states and routes, and every one of them needs somebody to walk it deliberately.
You own making time for acceptance and running the scenarios yourself. The supplier's testing checks the machinery; your testing checks that the site describes your business correctly, in your terms and with your conditions attached.
Ask it this way: what exactly do you test, and what counts as a defect against a new request? That boundary decides whether you stay inside the revision rounds your package includes or start paying for additional work.
Stage 10: deployment, access and handover
Publishing is a stage, not a final button. Domain, certificate, mail records, environments, variables and backups all have to be configured and written down, or the next supplier opens the engagement with an excavation instead of work.
Launch Site includes deployment setup. Launch Site Express costs $520 and delivers the Launch Site scope in a priority queue with daily builds, a launch checklist and a handover call, in 2 working days, with 1 round of revisions after the first full build.
The accounts are yours. Domain, hosting, analytics and mail should be registered to your company with access granted to the supplier, not the other way round. The reverse arrangement creates a dependency that is awkward to unwind.
Ask it this way: what do I receive on handover day, and in what form? The answer should be a list of countable things: the repository, the credentials, an update procedure and a record of the settings that were applied.
Reading a quote and seeing what is missing
Take your quote and mark every stage in this article as one of three things: supplier does it, we do it, not discussed. The third category is your risk, now written into lines you can point at during a conversation.
Then deal with support. Ongoing Dev Support costs $290/mo and covers priority updates, a weekly release rhythm and technical maintenance; the cycle is monthly, stopping requires 30 days notice, and the volume is agreed at the start of each cycle. A new build or a redesign is scoped separately.
Check what appears in no package at all. VITON13 does not write client copy or translations, and does not build native mobile apps. Both jobs have a doer, and settling who that is before the start spares the project a stalled week in the middle.
The terms for the development service are published at /services/development. Compare them against your quote line by line before you sign, because a stage with no named owner is not a detail: it is an invoice that has not been issued yet.
Practical checklist
- Request the page list and the template count before signing a quote.
- Name one owner for copy and translations inside your company, with a date.
- Confirm whether error, empty and loading states are part of the design work.
- Establish which blocks you can edit without a developer after handover.
- Collect domain, analytics and payment provider access ahead of integration week.
- Write down what counts as a defect and what counts as a new request.
Questions and answers
Which stages does website development consist of?
Scope, structure and the page inventory, interface design, copy and translations, front-end build, CMS or data wiring, integrations, performance and accessibility, testing, deployment and handover. The supplier closes the engineering stages; copy, translations and access to external services stay with the client.
What does it cost to launch a website, and what does that price include?
The Launch Site package costs $380 and includes a responsive build, core CMS or data wiring and deployment setup. The timeline is 3-5 working days, with 2 rounds of revisions before launch. Content and translations are supplied by the client.
How is Product Build different from Launch Site?
Product Build costs $880 and is aimed at a product rather than a set of pages: feature delivery, state and route logic, testing and hardening. The timeline is 2-3 weeks, with 2 rounds of revisions per delivered feature. Native mobile apps and payment licensing are not included.
What if the launch has to happen quickly?
Launch Site Express costs $520 and delivers the Launch Site scope in a priority queue with daily builds, a launch checklist and a handover call. The timeline is 2 working days, with 1 round of revisions after the first full build. Content, photography and ongoing support are not included.
Do we need support after launch?
Ongoing Dev Support costs $290/mo and covers priority updates, a weekly release rhythm and technical maintenance. The cycle is monthly and stopping requires 30 days notice, with the volume agreed at the start of each cycle. A new build or a redesign is scoped separately.