How much website technical support costs in Moldova

Website support is the one budget line you notice only when it is absent. While everything works, paying for it feels unnecessary. On the day the site stops opening just before a weekend, the question sounds different.

The short answer

A retainer beats one-off requests from two tasks a month upward — and, more importantly, it includes the preventive work that stops those requests from arising.

What support covers

Uptime monitoring

A system checks availability and warns you before a customer notices. Without monitoring, outages are usually discovered through a buyer phone call.

Updates

CMS, modules, libraries. Outdated components are the main route into small business websites, because their vulnerabilities are public.

Backups

Regular copies and, more importantly, storage away from the server. A copy on the same server does not protect against server failure.

Fixing defects

A page will not open, a form will not send, the layout broke after an update. Response is part of the package.

Improvements

Hours you can spend on changes: new pages, feature tweaks, integration setup. What counts as an improvement is worth fixing in advance.

The report

Once a month: what was done, how many hours were used, what we recommend next. Without a report a retainer becomes payment for something unknown.

From practice: most emergency requests are the consequence of six months without updates. Prevention is roughly an order of magnitude cheaper than recovery.

Retainer or one-off work

One-off work is cheaper in the moment but contains no prevention: you pay for recovery instead of avoidance.

What happens without support

• vulnerabilities in old modules stay open — how websites are protected;
• speed degrades as content grows, and search positions follow;
• forms stop sending after a hosting change or an update, and nobody notices immediately;
• there is no current backup at the moment one is needed;
• every small edit turns into a hunt for an available contractor.

How to choose a package

• Count how many changes you requested over the last six months.
• Estimate what an hour of downtime costs in your niche.
• Check whether the site handles payments or integrations: those need watching.
• Decide who is responsible for backups — you or the contractor.

If the site brings in leads, take a package with headroom: unused hours cost less than urgent work at double rate.

An example from Synergy practice

Client: an online store with online payment and a regularly updated catalogue.

Why a retainer: a store handling payments cannot be left without updates and monitoring, and catalogue and promotion changes happen every month.

What it covers: monitoring, updates, off-server backups, defect fixing, improvements within the hours, and a monthly report.

Result: updates and changes happen on schedule rather than in emergency mode.

See the Broderie Store case →

Frequently asked questions

Is support mandatory after launch?

No, but without it the site ages. The minimum worth having either way: updates and backups.

Can we maintain the site in-house?

If you have a technical specialist, yes. What matters is that they have access, documentation and time, not just willingness.

What if we need more hours than the package includes?

Extra hours are billed at the hourly rate, or the package moves up a tier. Agree this before work starts.

Does support include promotion?

No. Support covers uptime and development of the site; promotion is a separate service: SEO for business in Moldova.

What happens to the site if we change contractor?

Nothing, provided you hold the access and source code. Check that before, not after.

Conclusion

Support is not insurance against breakage but a way of not getting there. Three quarters of emergencies come from deferred updates and missing backups — that is, from the absence of regular work.

Synergy offers three support packages from €75 per month, each with a monthly report of the work done. Details and package contents are on the technical support page.