PIPELINEGuide
Having a website built: examples from practice
How a website is actually used in the daily life of small businesses — concrete processes instead of product promises, including the cases where it didn't work.
In practice, having a website built almost always starts with exactly one process, not with an overall concept. Most visitors decide in the first few seconds whether they stay — load time and clarity of the first screen weigh more heavily than the design. Expansion only happens once the first step demonstrably works in actual operation.
01 — Practice
What this looks like in concrete terms
Most visitors decide in the first seconds whether they stay — load time and clarity of the first screen matter more than the design.
A typical start looks like this: The business identifies the one process that causes the most trouble. What should someone do when they leave the site? That determines the page structure, not the other way around.
After go-live, there's no immediate expansion, just observation. Migration, redirects for old URLs, setup of tracking. Followed by training.
02 — Fit
When it's worth it
- The process in question occurs at least weekly.
- It follows rules you can write down — even if there are exceptions.
- Today it's manual work that no one enjoys doing.
- There's one person who decides, not three who need to coordinate.
- You can name what would tell you it worked.
03 — Scope
When we advise against it
- The process is still changing. As long as you're adjusting the process itself, manual work is more flexible and cheaper.
- Exceptions outweigh standard cases. Then you're automating exceptions, and that gets expensive.
- There's no data foundation. Without digitally available source data, the basis is missing.
- Volume is too low. With five transactions a month, no system pays off — not even an affordable one.
- The real bottleneck lies elsewhere. If you don't have enough inquiries, you don't need faster processing.
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.
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 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.
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.
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.
05 — Next
Related pages
- Having a website created — Overview
- Having a Website Built — Alternatives
- Having a website created — Costs
- Having a website built — economic viability
- Having a website built — measuring success
- Having a website created — Common mistakes
- Having a website created — DIY
- Having a website built — contract and ownership
- Landing page
- SEO
- Website relaunch
- All guides
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.