PIPELINE
EN
DeutschEnglishFrançaisItalianoEspañol中文
INQUIRY

Guide

Implementing having a website created: step by step

The path from decision to live operation — in the order that has proven effective in small businesses, including the points where projects typically get stuck.

Request assessment ↗Having a website created
Quote on request4 to 8 weeksAs of 2026
In short

Having a website created is implemented by first identifying the bottleneck, then defining it narrowly, and only then implementing it. The implementation itself takes 4 to 8 weeks; a project is almost never delayed by technology, but by missing content, access, and decisions.

01 — Getting started

Where to begin

  1. Name the bottleneck

    Not the most interesting thing, but what takes the most time. A week of tracking what repeats delivers a more realistic list than any workshop.

  2. Define a small scope

    One process, one measurable goal. What works gets expanded — what doesn't costs little.

  3. Survey the starting situation

    Which content, data, and access is available. For having a website created, this is the factor that influences effort and timeline most strongly.

  4. Decide who is responsible

    For the implementation and for operations afterward. Without this definition, every system becomes outdated.

  5. Only then request proposals

    With a clear scope, proposals become comparable. Without it, you get numbers that have nothing to do with each other.

02 — Process

The steps in detail

  1. Vision and structure

    What should someone do when they leave the site? That determines the page structure, not the other way around.

  2. Design

    A design for the home page and one subpage. Only once that's right does the rest get built.

  3. Implementation

    Build, add content, technical review for speed and accessibility.

  4. Go-live

    Migration, redirects for old URLs, setup of tracking. Followed by training.

03 — Participation

What we need from you

  • A contact person who can make decisions — not just forward them.
  • Access to the affected systems, in time and not on launch day.
  • Real examples from daily business — the messier, the more useful for testing.
  • Two to four hours for coordination, distributed over the project duration.
  • An answer to the question of what success means. Without it, nothing can be assessed afterward.

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

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

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.

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.

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.

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.

06 — Next

Related pages

Having a website created by region

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.

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