Design and development are normally a project cost. Domain renewal, email subscriptions, paid tools and ongoing maintenance are separate responsibilities. A static brochure website may suit a free hosting tier while its domain and mailbox still have recurring costs. Free static hosting does not make the domain, email or maintenance free forever.
Keep the renewal register separate from the list of routine content changes. A domain renewal has a date and account responsibility; correcting a service description has an approval and publishing responsibility. Combining both into a single maintenance label can leave one of them unattended. The register should remain understandable when the original person who set it up is unavailable.
For budget planning, distinguish required operating services from optional convenience tools. The website might need its domain and enquiry storage, while an embedded scheduling or newsletter service may be a later choice. Do not assume that an optional tool will remain free or that its subscription is bundled into the original creation fee. Before adding it, record what customer task it improves, who owns the account and how the site behaves if the subscription stops. This keeps future costs connected to actual business needs rather than a growing collection of unnoticed services.
Separate creation from keeping the site available
A website has an initial production stage and an operating life. Design, implementation, content placement, agreed checks and first-publication preparation belong to the creation scope. These tasks produce a deliverable. Recurring costs concern services that continue afterwards, such as holding the domain registration, maintaining mailboxes or paying for an optional external system.
Use a cost register rather than a single lifetime website price. For each item, record what it does, whose account holds it, whether it renews, when it renews and who approves changes. The register can include items with no present charge; this still makes responsibility visible. Keep private payment details out of project documentation that might later be shared with a developer.
A domain renewal keeps the address registered under the registrar’s terms. Web hosting serves the site files or application. Business email stores and delivers messages through its own provider. These services can use the same domain while being billed and managed separately. Confusing them can cause an unnecessary service change or an avoidable interruption during a website move.
Distinguish maintenance from hosting
A host making files available does not normally edit an outdated service description for you. Content maintenance means checking business facts, updating approved text or images and keeping related versions consistent. Technical maintenance can involve dependency review, deployment configuration, backups and checking that forms still work. The exact activities need to be named in the agreement.
Separate planned changes from incident response. Replacing a photograph next month is not the same as investigating an unavailable form. Ask what support channel is used, which types of work are included and how a request is estimated if it falls outside the agreement. Avoid interpreting a general promise of support as unlimited redesign or round-the-clock operational cover.
Backups also need a practical definition. A source repository can preserve code history, while uploaded content or enquiry data may live elsewhere. Identify what is backed up, who controls access and how recovery is performed. A backup that nobody knows how to restore provides less assurance than its mere existence suggests.
Evaluate a simple operating scenario
Imagine a small consultancy with stable service pages and a contact form. Its public pages may suit a static hosting option within the provider’s free conditions. The consultancy may still pay for its domain and a business mailbox. If it later adds a paid scheduling service, that subscription is a new operating item rather than part of the original free-hosting claim.
Now imagine the owner wants fresh articles and service revisions every month. The cost discussion changes because someone must prepare, approve and publish material. This does not necessarily require a management panel, but it does require an agreed workflow and responsible people. Choose the workflow from actual editing needs instead of assuming that a panel eliminates all publishing work.
Orvunweb’s package amounts are one-time creation fees. Continued maintenance, paid services, email and domain charges are separate subjects. The enquiry itself does not create a purchase agreement or payment commitment; a written offer defines the accepted scope. Review that offer against the operating register so the launch does not become the first time recurring responsibilities are discussed.
A useful final check is to ask what happens six months after delivery when a service changes or a renewal notice arrives. If you can name the account, the owner and the next action, the operating arrangement is understandable. If nobody knows, clarify responsibility before treating the initial project price as the complete cost of ownership.
Practical checklist
- Record renewal dates
- Identify account owners
- Separate optional support from hosting
A concrete example: A static brochure website may suit a free hosting tier while its domain and mailbox still have recurring costs.
A boundary to keep clear: Free static hosting does not make the domain, email or maintenance free forever.
Your next step
Tell Orvunweb about your project
