Guide

Having a website created: the most common mistakes and how to avoid them

Projects around having a website created rarely fail because of technology. The patterns repeat themselves — and can be prevented in advance.

Request assessment ↗Having a website created

Quote on request4 to 8 weeksAs of 2026

In short

The most common mistake with having a website created is starting with the technology instead of the actual bottleneck. A project that no one in the business really maintains delivers less in the long term than a smaller one that is actually used.

01 — Mistakes

The most common mistakes

Starting too big. Projects where nobody can use anything for months fail more often than average. A small, usable first step is almost always the better way.
Not involving the people who work with it. Requirements that only come from management rarely match the actual work.
Not defining a success measure. Without a metric defined in advance, you can't say afterwards whether it delivered anything — and the next decision will be made on gut feeling again.
Overlooking operating costs. The project price is only part of it. What operation costs over three years belongs in the same calculation.
Creating dependency. If you don't get access, documentation and source code, you're locked in. That needs to be clarified before commissioning, not after.

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 — Bottlenecks

What typically causes delays

Content and deliveries. By far the most common cause of delay. Text, images, price lists, access credentials — what's missing blocks progress.
Decisions. When it's unclear who approves, the project waits. A named contact person with decision-making authority noticeably shortens the timeline.
Access to third-party systems. Getting access to inventory management, phone systems, or CRM regularly takes longer than the integration itself.
Endless review rounds. Two correction rounds are normal, five are a sign that the goal wasn't clear at the start.

04 — Questions

Frequently asked questions

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.

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 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.

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.

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.

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.

Can we manage the site ourselves?

Yes. You maintain texts, images, and simple pages yourself. For structural changes you get in touch — or not, that's not a dependency we build.

05 — Decision

How to move forward

The most affordable next step is a conversation, not a quote. Twenty minutes is usually enough to clarify whether a project makes sense, what scope it involves, and whether we're the right fit.

If we're not, we'll say so. An honest no costs less than a project you abandon after three months — for both sides.

06 — Next

Having a website created by region

Next step

We'll look at your starting position.

Tell us what's eating up time today. That becomes an assessment with effort and benefit — and only then an offer.

Send inquiry ↗ office@pipeline-solutions.at OR +43 681 207 64 203