Answer in brief
A business owner wants a number, not a lecture. This is a walk through the five fixed prices of the VITON13 development service, and where the line falls between the build, the content, the design and the monthly support.
The short answer: five fixed prices
You want a number, so here are the numbers. The VITON13 development service is sold as five fixed-price packages: Site Fix Pack at $70, Launch Site at $380, Launch Site Express at $520, Product Build at $880, and Ongoing Dev Support at $290 per month. Everything after this section is about which one matches the job in front of you.
A price only answers a question when the scope is written down beside it. Each of those figures carries its own body of work, its own timeline and its own term for revisions, and those terms do not travel from one package to another. Reading them as a single tariff is how a budget goes wrong at the point where changes are expensive.
The stated timelines are these: 1-2 working days for Site Fix Pack, 3-5 working days for Launch Site, 2 working days for Launch Site Express, 2-3 weeks for Product Build, and a monthly cycle with 30 days notice to stop for Ongoing Dev Support. Note the change of unit on Product Build: weeks, not working days.
And here is what none of the five includes. VITON13 does not write your content and does not produce your translations, and native mobile apps sit outside Product Build. That belongs in the opening section rather than a footnote, because it is exactly where a website budget grows quietly once the contract is signed.
One price, four separate budgets
“What does a website cost” is really four budgets sharing a single label: the build, the content, the design, and the support that runs after launch. While they sit on one line, any figure you hear will feel either suspiciously small or unaccountably large, and arguing about it goes nowhere.
The build is engineering time. Templates, interface states, routes, forms, the wiring between a page and wherever its data actually lives, and the setup that publishes all of it. That is the part the five packages below put a price on.
The content is text, photography, product records, legal pages and translations. Launch Site places this outside the package in plain words: content and translations are supplied by the client.
Support is a recurring row rather than a one-off. Counting it from the beginning instead of discovering it in month two changes the shape of the entire budget, and it means the decision to launch gets made on honest arithmetic.
The build budget: what an engineer's hours buy
Build hours go into structure rather than decoration: page templates, empty states, error states, form behaviour, routes, and the connection to a data source. None of that shows up in a screenshot, and all of it decides whether the site holds together in the first weeks after launch.
Speed is engineering work, not a checkbox someone forgot to tick. What loads first, how much script reaches the browser, how images are handled: the MDN Web Docs performance documentation is a fair map of those topics, and it gives you the vocabulary to ask a supplier specific questions.
Accessibility lives in the same budget. Keyboard operation, visible focus, contrast, field labels and the size of interactive targets are all set out in the W3C quick reference for WCAG 2.2. Building them in while the templates are being written means edits in those same files; coming back to them later means editing every template again.
Testing and hardening appear as a named part of the Product Build scope. The smaller packages do not carry that line, and that is a boundary rather than an omission: $70 buys verification of the fixes you agreed, not an audit of the entire system.
The content budget: the row no package carries
Across all five packages, content stays on your side of the table. Launch Site states it directly: content and translations are supplied by the client. Launch Site Express names content, photography and ongoing support among its exclusions.
The reason is not commercial. The description of your service, your return terms, your product specifications and the voice you use with buyers are known by the person running the business. A supplier can build the place where that text will live, but cannot know what you have promised a customer.
This lands on the calendar directly. A 3-5 working day build assumes the words and images exist by the time the templates are ready to hold them. When content is written in parallel, the calendar is governed by the content rather than by the build.
Translations are content multiplied by the number of languages you sell in. A second language does not double the build, but it does double the volume of text that somebody has to write, check and keep current whenever the offer changes.
The design budget: what happens before the code
Design and development are different budgets, and folding them into one figure is uncomfortable for both sides. The packages described here are build work: a responsive build, core CMS or data wiring, and deployment setup.
The boundary is stated rather than implied. Site Fix Pack does not include redesign. If the honest answer to your problem is “it should look different”, you are not looking at a five-item repair job at all.
No figure for the visual work appears in this article, and that is deliberate: this is the development service and its five prices, while design is discussed and quoted separately. That is an ordinary way to run a project, not a number being kept from you.
The practical split is simple. Decide first whether you are buying a new appearance or a working build. You may genuinely need both, but they are two decisions, two rows in a budget and two different conversations with different people.
$70, Site Fix Pack: a bounded repair
Site Fix Pack costs $70 and covers up to five agreed fixes. The timeline is 1-2 working days and the revision term is one round. The scope is set by a list agreed before work starts, and that list is what draws the edge of the package.
The package includes a mobile and desktop check, and a before/after list at handover. That list exists for acceptance rather than paperwork: you can see which five items were closed, and you can test each of them yourself.
New pages, redesign and migrations are not included. Those three exclusions are written down, and a “tiny new page” falls outside the line exactly as a large one does. That is the condition under which a fixed price can stay fixed.
The package fits when the site works but carries a set of defects you can describe in words. Write your five items down before the conversation about money. If the list will not reach five, or runs to fifteen, you are looking at a different package.
$380, Launch Site: the standard launch
Launch Site costs $380, runs 3-5 working days, and carries two rounds of revisions before launch. It is a build designed to put a working site on the internet, not to absorb every wish that will occur to you over the following year.
The scope is a responsive build, core CMS or data wiring, and deployment setup. Those three cover the road from a layout to a live address: how it looks, where the words come from, and how updates reach the production server.
Content and translations are not included; the client supplies them. Read that term alongside the content section above and it becomes clear why it is worth absorbing before signing rather than after the first invoice.
Two rounds before launch should change how you gather feedback. Collect the comments of everyone entitled to give them, deliver them as one set, and keep the second round for what genuinely emerges from the first. Feedback that arrives as it occurs to people spends rounds without improving the site.
$520, Launch Site Express: buying the calendar
Launch Site Express costs $520 and delivers the Launch Site scope in a priority queue: 2 working days, daily builds, a launch checklist and a handover call. The work has the same shape; the operating mode is what changes.
The revision term is not the same, and this is precisely the place where one package's terms must not be carried over to another. Express has one round after the first full build, rather than two rounds before launch. Both the count and the moment differ.
Content, photography and ongoing support are not included. Photography deserves separate attention: in a two-working-day build, missing images show immediately, because the schedule has no room in which to wait for them.
What you are buying is a date. A trade fair, a season, an advertising flight: when the deadline comes from outside the project, the gap between $380 and $520 buys queue position and daily builds, not extra features.
$880, Product Build: when the site is a product
Product Build costs $880 and runs 2-3 weeks. Weeks, not working days, and the unit is not a typo: a different scale of work needs a different calendar, and planning it as “a week and a bit” prepares a disappointment for everyone involved.
The scope is feature delivery, state and route logic, and testing and hardening. Hardening is about how the system behaves when something goes wrong: bad input, a dropped connection, a form submitted twice, an empty response from a neighbouring service.
Native mobile apps and payment licensing are not included. Both are worth raising with your team before the start, because both have a habit of surfacing halfway through the project phrased as “surely we should just add that”.
Revisions are counted differently here: two rounds per delivered feature. That should reshape your acceptance process as well. Review each feature when it is ready rather than saving everything for the end, by which point the rounds attached to the early features are already spent.
$290 a month, Ongoing Dev Support: the budget with no end date
Ongoing Dev Support costs $290 per month. The cycle is monthly, and stopping it takes 30 days notice. Of the five packages, this is the one that keeps existing once the site is already running.
The scope is priority updates, a weekly release rhythm and technical maintenance. A weekly rhythm is not a promise of speed on any individual ticket; it is predictability, so everyone knows when changes reach the site.
No revision count is stated for support, and none needs to be invented. A different term is stated instead: the volume is agreed at the start of each cycle. In practice that makes the conversation about priorities part of the service rather than an interruption to it.
A new build or a redesign is not included; both are scoped separately. Support does not work as a way to buy a rebuild quietly in instalments, and that condition protects both sides from a scope that shifts a little further every month.
Revisions and exclusions: where later costs come from
Five packages carry five different revision terms: one round on Site Fix Pack, two rounds before launch on Launch Site, one round after the first full build on Express, two rounds per delivered feature on Product Build, and on support a volume that is agreed at the start of each cycle.
The difference is not cosmetic. Each term is attached to its own event: a handover, a launch, a first build, an individual feature, the start of a month. Carrying a term from one package to another creates an expectation that nobody ever offered.
The exclusions work the same way. New pages, redesign and migrations; content and translations; content, photography and ongoing support; native mobile apps and payment licensing. That is four distinct sets, not one disclaimer repeated four times.
Before you sign anything, finish this sentence in your own words: “this package does not include …”. If the sentence will not finish, the scope is not understood yet, and the number in your head does not mean anything yet either.
Turning the packages into your number
Start from where you actually are. No site at all is a conversation about a launch. A site that works but breaks in named places is a conversation about a repair. A site that works and now has to learn something new is a conversation about a product build.
Add the content row. Who writes the copy, in how many languages, by which date, and who takes the photographs. That row sits outside every package and inside your budget and your calendar.
Add support as a recurring row across twelve months at the stated monthly price. Decide whether you can carry it before launch rather than after: saving on maintenance is a saving that exists only on paper, and the bill arrives in the form of broken things.
Then open the service page and match your own list against the scope of each package. The figure you came looking for is the sum of the build, the content, the design and the support, and all four parts are now in front of you.
Practical checklist
- Split the budget into four rows: build, content, design and support.
- Write your task list before discussing price, because the list selects the package.
- Name an owner and a date for copy, photography and translations.
- Read the revision term of the exact package you are choosing, not a neighbouring one.
- Check that package's exclusions and finish the sentence “this does not include …”.
- Budget twelve months of monthly support before launch rather than after it.
Questions and answers
What does website development cost at VITON13?
Five fixed prices: Site Fix Pack at $70, Launch Site at $380, Launch Site Express at $520, Product Build at $880, and Ongoing Dev Support at $290 per month.
What is included in the $380 Launch Site?
A responsive build, core CMS or data wiring, and deployment setup, delivered in 3-5 working days with two rounds of revisions before launch. Content and translations are supplied by the client.
How is Launch Site Express different from Launch Site?
For $520 you get the Launch Site scope in a priority queue: 2 working days, daily builds, a launch checklist and a handover call. Revisions are one round after the first full build, and content, photography and ongoing support are not included.
Why are content and translations outside the price?
VITON13 does not write client content or produce translations; the client supplies them. Product copy, photography and legal pages depend on knowledge of the business, so they form a separate row in your budget and your schedule.
How many revisions does monthly support include?
No revision count is stated for support. What is stated is that the volume is agreed at the start of each cycle, at $290 per month, with 30 days notice to stop.