Guide

Website creation services: Risks and how to limit them

What can go wrong with website creation services, how likely each scenario is, and which agreements can prevent them upfront — without dramatization and without sugarcoating.

Quote on request4 to 8 weeksAs of 2026
In short

The biggest risk with website creation services isn't the technology, but that nobody maintains the system after launch. Incorrect answers can be limited by working exclusively from verified content and redirecting when uncertain; dependency is avoided by contractually ensuring that access, data, and documentation belong to the client.

01 — Risks

What can go wrong

  • The system answers incorrectly. Containable by having it work exclusively from verified content and escalate when uncertain rather than guess. This is a configuration decision, not a property of the technology.
  • The effort is underestimated. Most common reason: unclear starting situation. An honest assessment of the current state before the proposal prevents this more reliably than any buffer.
  • No one maintains it. The biggest risk of all — and the most easily avoidable.
  • Data protection gaps. Almost always arise from missing deletion deadlines and unclear responsibility, rarely from the technology itself.
  • Vendor lock-in. Avoidable if access credentials, data, and documentation contractually remain with the client.

02 — Warning signs

When to be skeptical

  • Guaranteed results. Anyone promising top Google ranking or a specific revenue increase is selling something they can't deliver.
  • No pushback. A provider who thinks every project is a good idea has either not listened or is only selling.
  • Time pressure. Limited-time discounts on project prices are a sales tool, not an offer.
  • Unclear ownership. Anyone who won't clearly say who owns data and access doesn't have your interests at heart.
  • No contact with technical expertise. If only sales sits in the first meeting, that's where misunderstandings arise.

03 — Contract

What needs to be clarified in writing

  • Ownership of data and access. They belong to the client. If a provider won't clearly confirm this, that's the most important information from the conversation.
  • Handover upon termination. In what format, within what timeframe, at what cost.
  • No minimum term without consideration. Lock-in is justifiable if something is delivered in return — otherwise not.
  • What a later change costs. The total cost isn't determined by the project price, but by the hourly rate in year three.
  • Documentation as a deliverable. Not as a promise, but as a line item in the proposal.

04 — Questions

Frequently asked questions

Does our website have to be accessible?

Since 28 June 2025, the Accessibility Act (Barrierefreiheitsgesetz) applies in Austria. Mainly affected are online shops, bookings, e-ticketing, and banking services in consumer business; micro-enterprises are exempt for services. A pure information site generally doesn't fall under it — we still build to WCAG 2.1 AA because it makes the site better for everyone and the rules tend to get stricter.

What does a website cost in Austria?

There's no serious way to answer that as a flat rate — the market ranges are huge because a one-pager and a multilingual company site with twenty pages are completely different projects technically. What matters most is how much content has to be created from scratch — that's almost always the biggest line item, not the technology. Send us a quick note about what you have in mind, and you'll get a proposal that fits your scope.

Are there subsidies?

For digitalization projects in Austria, there are several funding programs, such as KMU.DIGITAL (kmudigital.at) or the aws digitalization subsidy (aws.at). Whether your project currently qualifies, we check individually — the application must be approved before awarding the contract in any case.

WordPress or something else?

Depends on the case. WordPress makes sense when many people manage content and standard features are enough. Where speed, security, or custom functions matter, we build leaner. We don't recommend what we like building most, but what you can still operate in three years.

How long does it take?

Four to eight weeks is realistic if content and images arrive on time. The bottleneck is practically never development, but approval of texts and photos.

What does ongoing operation cost?

Hosting, domain, updates, and backups are ongoing costs — how much depends on the size and requirements of the site, and we state that transparently in the quote. Anyone who skimps on that skimps until the first security incident.

What happens to our old site?

The content is carried over as long as it's suitable, and old addresses are redirected to the new ones. Without these redirects, you lose the visibility built up over years — that's the most common mistake in a relaunch.

Next step

Send us a few sentences about your project.

We read every inquiry ourselves and respond personally. No sales team, no callback form into the void.